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 ordinary sendTransaction route requires a recent blockhash. Durable-nonce transactions are rejected; when the capability is available, use the two-transaction durable-nonce pair flow on /hofund sendIdeal.
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.
Acknowledged is not landed. Track the signature through ThorEdge RPC, or poll getHofundSubmissionStatus with the submission id.