sendBundle

curl --fail-with-body "$HOFUND_BUNDLE_URL" \
  --header 'content-type: application/json' \
  --data '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "sendBundle",
    "params": [
      ["<BASE64_SIGNED_TRANSACTION_1>", "<BASE64_SIGNED_TRANSACTION_2>"],
      { "encoding": "base64" }
    ]
  }'

curl --fail-with-body "$HOFUND_URL" \
  --header 'content-type: application/json' \
  --data '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "sendBundle",
    "params": [
      ["<BASE64_SIGNED_TRANSACTION_1>", "<BASE64_SIGNED_TRANSACTION_2>"],
      { "encoding": "base64", "mevProtect": true, "revertProtection": true }
    ]
  }'

{ "jsonrpc": "2.0", "id": 1, "result": "<BUNDLE_ID>" }

{ "jsonrpc": "2.0", "id": 1, "result": ["<SIGNATURE_1>", "<SIGNATURE_2>"] }

A bundle lands as one unit or not at all. Hofund forwards it to Jito atomically and never splits or retries it through another rail. Two surfaces accept sendBundle and they differ in size and config:

Route	Transactions	`params[1]`
`/hofund`	1–4	Exactly `{ "encoding": "base64", "mevProtect": true, "revertProtection": true }`
`/hofund-bundle`	1–5	Exactly `{ "encoding": "base64" }`

One member with an application instruction (not a tip-only transfer) must pay both the Thor and the Jito tip floors. A tip-only member does not qualify.

Parameters

string[]

required

Fully signed transactions in execution order, canonical padded base64, at most 1232 bytes each, no duplicates.

object

required

The exact config object for the route, as in the table above. Any other key or value is rejected.

Response

string | string[]

On /hofund-bundle: the Jito bundle id. On /hofund: the member signatures in order.

Headers: X-Hofund-Submission-ID and X-Bundle-ID.

Errors

Code	Message
`-32602`	`sendBundle transaction count exceeds 4` (`/hofund`)
`-32602`	`one bundle member must pay at least N Thor and M Jito tip lamports and include an application instruction with a writable static account`
`-32010`	Jito capacity exhausted; `Retry-After: 1`

Other `/hofund-bundle` methods

Method	`params`	Result
`getBundleStatuses`	`[["<bundle-id>", …]]`, 1–5 unique 64-hex ids	Jito’s response, unchanged
`getInflightBundleStatuses`	same	Jito’s response, unchanged
`getTipAccounts`	`[]`	The Jito tip accounts Hofund uses
`getThorTipConfig`	`[]`	See Status and tips

curl --fail-with-body "$HOFUND_BUNDLE_URL" \
  --header 'content-type: application/json' \
  --data '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "sendBundle",
    "params": [
      ["<BASE64_SIGNED_TRANSACTION_1>", "<BASE64_SIGNED_TRANSACTION_2>"],
      { "encoding": "base64" }
    ]
  }'

curl --fail-with-body "$HOFUND_URL" \
  --header 'content-type: application/json' \
  --data '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "sendBundle",
    "params": [
      ["<BASE64_SIGNED_TRANSACTION_1>", "<BASE64_SIGNED_TRANSACTION_2>"],
      { "encoding": "base64", "mevProtect": true, "revertProtection": true }
    ]
  }'

{ "jsonrpc": "2.0", "id": 1, "result": "<BUNDLE_ID>" }

{ "jsonrpc": "2.0", "id": 1, "result": ["<SIGNATURE_1>", "<SIGNATURE_2>"] }

API reference

ThorEdge RPC

FastGate RPC

Yellowstone gRPC

Bifrost

Hofund

Parameters

Response

Errors

Other `/hofund-bundle` methods

​Parameters

​Response

​Errors

​Other /hofund-bundle methods

Parameters

Response

Errors

Other `/hofund-bundle` methods