bloXroute Documentation
WebsiteBlogTwitterDiscord
  • Welcome to bloXroute
  • Introduction
    • Why Use bloXroute?
    • Products
    • Create An Account
    • Technical Support
  • SOLANA
    • Trader API
      • Introduction
        • Regions
        • Authorization
        • Rate Limits
        • Tip and Tipping Addresses
      • Quick Start
        • Transaction Submission
        • Front-Running Protection & Transaction Bundle
        • Go SDK
        • Python SDK
        • Typescript SDK
        • Rust SDK
      • API Endpoints
        • Core Endpoints
          • submit
          • submit-paladin
          • submit-batch
          • balance
          • rate-limit
          • transaction
          • priority-fee
          • GetPriorityFeeStream
          • GetBundleTipStream
          • submit-snipe
        • Pump.fun
          • quotes
          • swap
          • swap-sol
          • GetPumpFunNewTokensStream
          • GetPumpFunSwapsStream
          • GetPumpFunAMMSwapsStream
        • Raydium
          • quotes
          • pools
          • pool-reserves
          • swap
          • cpmm-swap
          • clmm-swap
          • route-swap
          • GetPoolReservesStream
          • GetSwapsStream
          • GetNewRaydiumPoolsStream
          • GetNewRaydiumPoolsByTransactionStream
        • Jupiter
          • quotes
          • swap
          • swap-instructions
          • route-swap
        • Openbook
          • markets
          • orderbooks/{market}
          • depth/{market}
          • tickers/{market}
          • open-orders/{market}
          • unsettled/{market}
          • place
          • replace
          • cancel
          • settle
          • GetOrderbooksStream
          • GetTickersStream
      • Best Performance for Landing Transactions
      • Support
        • API Health
        • Contact us
        • Suggestions
        • Wiki
          • Terms & Concepts
          • Resources
    • Optimized Feed Relay (OFR)
      • Transaction Streamer
      • Gateway and OFR Requirements
      • Gateway and OFR Setup
      • Gateway Startup Arguments
      • OFR performance
      • Logging
      • Submitting Transaction
      • Upgrading Gateway
      • Troubleshooting
  • BSC & ETH
    • EVM Blockchain Distribution Network (BDN)
      • How to Connect
      • The bloXroute Gateway
        • Local Gateway
          • Installation and Startup
            • Authentication & Certificates
            • Requirements
            • Supported Clients
            • GitHub repository option
            • Docker container option
            • Startup Script
            • Startup Arguments
          • General Connectivity Troubleshooting
          • Logging
          • Upgrading your Gateway
        • Add Your Gateway as a Trusted Peer to Your Execution Layer Client
        • Connecting Your Gateway with the Consensus Layer
      • IPs & Relays
        • Relays IPs
        • Private Relays
        • Cloud-API IPs
          • ⏩Reducing Latencies using the BDN
    • APIs
      • Authorization
      • Check Transaction Quota
      • Submit a Transaction
        • Raw Transaction Construction
        • Tx-Validation
        • Batch Transaction
      • Private Transactions
        • ETH Private Transactions
        • BSC Private Transactions
      • Transaction Bundles
        • Bundle Simulation
        • Bundle Validation
        • Bundle Submission
          • BSC Bundle Submission
            • List of BSC Validators
          • ETH Bundle Submission
          • Bundle Submission with Gateway
        • Bundle Tracking
          • BSC Bundle-Trace
          • ETH Bundle-Trace
          • ETH Bundle Inclusion Status
        • Bundle Refunds
          • Priority Fee Refund
          • Bundle Refund
          • Latest Bundle Refunds
      • Backrun Arbitrage
        • BackRunMe: Bundle Submission
          • BSC submit arbOnly
          • ETH submit arbOnly
            • blxr_info
            • ETH arbOnly Simulation
      • Token Launch Sniping
      • Other Utilities
        • List of bloXroute Builders
        • List of External Builders
        • Tx-Trace
        • Ping
    • Streams
      • Requirements
      • Subscription limits
      • Working With Streams
        • Creating a Subscription
          • Websocket
          • gRPC
        • Handling the Notification
          • Websocket
          • gRPC
        • Cancelling a Subscription
          • Websocket
          • gRPC
        • Local Node Validation
      • newTxs and pendingTxs
        • Filters
        • Raw TX Reconstruction
      • BackRunMe: arbOnlyMEV
        • ETH arbOnlyMEV
        • BSC arbOnlyMEV
      • transactionStatus
      • txReceipts
      • newBlocks
      • bdnBlocks
      • ethOnBlock
      • MEVBlockValue
      • MEVNextProposerInfo
    • Block Builders and Validators
      • Validator Gateway
      • MEV Relay (For Validators)
      • Block Submission
      • Proposer MEV-Protect
      • Compliance Lists
      • Preconfirmations
    • Protect RPCs
      • ETH Protect RPC
      • ETH Gas Protect RPC
      • BSC Protect RPC
      • SOL Protect RPC
  • Base Network
    • Submit Transactions
    • Streams
      • GetBdnBlockStream
  • TON NETWORK
    • TON Trader API
      • Quick Start
      • Fee Schedule
      • Connection
      • Submit Signed Transaction
  • Resources
    • BDN Explorer
    • Block Explorer
    • Guides
      • Algorithmic Trading
      • Setting Up a Local Gateway
      • Gateway as Web3 Bridge
    • Architecture
      • BDN Architecture
        • Network Components
        • Performance Techniques
          • Block Compression
          • Cut-through Routing
          • Optimized Topology
      • bloXroute Protocol
        • Versioning
        • Message Structure
        • Message Types
    • Contact Us
Powered by GitBook
On this page
  • Summary
  • Approach
  • Example
  • Receiving Refund
  1. BSC & ETH
  2. APIs
  3. Transaction Bundles
  4. Bundle Refunds

Priority Fee Refund

Get refund for the ETH Mainnet MEV Bundles and Private Transactions

Summary

The priority fee refund program allows transaction source partners (searchers, traders, wallets, Telegram bots) to receive back a portion of the priority fee without sacrificing inclusion rate. Builders participating in the program bid on the percentage from the profit the builders have made from the transaction priority fee they are willing to refund.

To maximize the refund - searchers should submit the transactions ONLY to bloXroute and not directly to other builders. If a transaction is received by other builders, there will be no refund available.

It is very simple to send a "blxr_submit_bundle" (or "blxr_private_tx") request with refund, just make sure to use the following two parameters in your request payload:

  • priority_fee_refund: true

  • refund_recipient: <wallet-address>

Approach

User submits bundles and private transactions, with priority fee refund flag, to bloXroute infrastructure. bloXroute holds the transactions for a few seconds before the next scheduled slot to determine which builder, that participates in the program, has the highest chance to win the block. bloXroute will only forward the transaction to this builder. bloXroute continues to monitor the chances of the builder to win the block and if the chances are low - the transaction would be sent to all builders requested by the user. If several builders have similar chances to win the slot, bloXroute will send the transaction to the builder which bids the highest in the priority fee refund auction.

Example

For instance, block builder A is a participating builder in this program, and block builder B is a builder not in the program. bloXroute keeps checking the values of blocks built by various builders at different times for the current slot.

  • Case 1 [builder A keeps this transaction as an exclusive transaction]: If builder A’s block is always more profitable than builder B and other builders’ for all timestamps that bloXroute performs checks at, then the transaction would be sent to builder A exclusively.

  • Case 2 [builder A and other builders all receive the transaction]: If builder B’s block becomes more profitable than builder A’s at any time in the block bidding process, then the transaction would be forwarded to all the block builders (including builder A, builder B and others) requested by the user.

Receiving Refund

Transactions that remain exclusive will be eligible for refund. The builders share a portion of the gas fees (priority fees) in the form of refund with the searcher who submits the transaction. The refund amount is based on the builder block profit. The higher the profit the builder is able to keep, the higher the refund amount will be. Therefore, the refund amount (or percentage) is dynamic for each specific opportunity, and the refund payment happens on chain up to 1 - 2 hours after the transaction lands.

PreviousBundle RefundsNextBundle Refund