sendTransaction submits one transaction. On /hofund you choose the lane per request; on a lane route the URL fixes it.
The transaction must pay the Thor tip floor to a Thor tip account (fast rails), and additionally the Jito tip floor to a Jito tip account (protected). Read both sets from
getFastTipConfig and getThorTipConfig.
Every sendTransaction route accepts recent blockhash or caller-owned durable nonce transactions through the same request format.
Durable nonce
Build and fully sign the transaction with your nonce value inrecentBlockhash. Instruction 0 must be the only AdvanceNonceAccount instruction, using a writable nonce account, the readonly recent-blockhashes sysvar, and a signing nonce authority. These accounts and the System Program must be static message keys. Legacy and v0 transactions are supported.
Hofund verifies signatures, instruction structure, and the selected lane’s tip requirements locally. It forwards the signed bytes unchanged with skipPreflight: true; validators check the live nonce value and authority. Acceptance does not prove the nonce is still usable or the transaction landed.
Exact retries retain the existing signature-based replay rules. Different signed variants may share one nonce account and value. sendIdeal is available when you want Hofund to verify and submit a fast/Jito pair together. Atomic sendBundle requests still require recent blockhash transactions.
Parameters
string
required
Fully signed transaction, canonical padded base64, at most 1232 bytes decoded.
object
required
Send configuration.
minContextSlot is rejected: -32602 minContextSlot is unsupported and is not enforced by Hofund sender rails.object
/hofund only. Exactly { "mevProtect": true } routes the transaction through Jito instead of the fast rails. Do not combine with ?mev-protect=true./hofund-fast, /hofund-direct-tpu, and /hofund-swqos you can send deadlineMs and region as headers instead: Hofund-Deadline-Ms and Hofund-Expected-Region. Sending both the header and the body field is rejected.
Response
string
The transaction signature, once one selected rail returned a verified acknowledgement (fast) or Jito accepted the transaction (protected).
X-Hofund-Submission-ID; X-Bundle-ID on the Jito path.
Nonce transaction status follows its signature. An unobserved signature is unknown; a receipt deadline or blockhash validity check cannot prove nonce expiry.
Acknowledged is not landed. Track the signature through ThorEdge RPC, or poll getHofundSubmissionStatus with the submission id.