Venum

Appearance

Transaction Submission ​

Venum submits your signed transaction via Jito's block engine infrastructure to all 5 regional block engine endpoints simultaneously.

Request ​

bash
POST /v1/swap
json
{
  "signedTransaction": "SIGNED_TX_BASE64",
  "quoteId": "q_42_1712000000000"
}

What Happens ​

  1. Venum deserializes and verifies the signed transaction
  2. Checks the quoteId is valid and not expired (30s TTL)
  3. Verifies the fee instruction is present and correct
  4. Submits to all 5 Jito sendTransaction endpoints simultaneously:
    • mainnet.block-engine.jito.wtf
    • amsterdam.block-engine.jito.wtf
    • frankfurt.block-engine.jito.wtf
    • ny.block-engine.jito.wtf
    • tokyo.block-engine.jito.wtf
  5. Returns the transaction signature immediately

Response ​

json
{
  "signature": "5Kx9abc...3nF",
  "status": "submitted",
  "quoteId": "q_42_1712000000000"
}

status: "submitted" means the transaction was sent to Jito. It does not guarantee on-chain confirmation — check the signature on Solscan or via RPC getSignatureStatuses.

Why Jito? ​

Standard Solana RPC submission exposes your transaction to searchers who can sandwich it — buying before your swap and selling after, extracting value from your slippage. Jito's sendTransaction endpoint routes your transaction through the block engine, which includes it in a bundle that prevents sandwiching.