Kolibrio
  • Kolibrio Orderflow Service
  • Solana
    • How it works
    • API: Quick Start
      • SendTransaction
    • FAQ
    • Advanced
      • Subsidy Transactions
      • How to Protect Against Frontrunning on SOL
      • Stats API
  • Ethereum
    • How it works
    • API: Quick Start
      • eth_sendRawTransaction
      • eth_sendBundle
      • eth_getTransactionByHash
      • eth_getTransactionCount
    • Pending Transactions on Chain Explorer (Etherscan)
Powered by GitBook
On this page
  1. Solana

How it works

PreviousSolanaNextAPI: Quick Start

Last updated 6 months ago

SOL Transaction Pipeline Flow

1

SOL Originator sends a target transaction to Kolibrio OFA

The originator submits the target transaction using the standard sendTransaction RPC method. Two key parameters are specified:

  • rev_recv: The address where the revenue will be sent (paid in SOL).

  • tx_broadcast_mode: Defines how the target transaction will be broadcast. Options include backrun_only, jito, and public. The default is backrun_only, meaning Kolibrio OFA will only submit the target transaction if arbitrage is discovered.

2

Target Transaction Simulation and Signal Sharing

Kolibrio OFA simulates the target transaction, removes the signature, and shares the target transaction signal with arbitrage searchers, allowing them to run calculations but not submit the target transaction.

3

Auction Execution and Target Transaction Broadcast

Kolibrio OFA collects bids from arbitrage searchers based on their calculations in a 30-100ms time window. After the auction is finished, Kolibrio OFA broadcasts the winning bid as a bundle to Jito. Immediately after, it broadcasts the original target transaction based on the specified tx_broadcast_mode, but only if required by the broadcast mode (e.g., jito orpublic).

4

Settlement and Revenue Distribution

Once the target transaction is included in a block, it is followed by an arbitrage backrun, which automatically sends the SOL revenue to the rev_recv.