Blink
  • Blink
    • Welcome to Blink
  • Get Started
    • Tx Originators
    • Integration
      • General
      • Wallets
      • Oracles
      • Bots
      • Individual Users
      • Security
    • Custom Configuration
    • API Reference
      • eth_sendRawTransaction
      • eth_sendPrivateTransaction
      • eth_getTransactionByHash
      • eth_sendBundle
      • eth_getTransactionCount
    • Misc
      • Privacy Policy
  • How it works
    • State Update Auction
    • Gas Recoveries
    • MEV
  • Additional Features
    • Gas Sponsored Swaps
  • Searchers
    • Integration
      • Listen To Transactions
        • MEVBlocker Compatible (V2)
        • MEVBlocker Compatible (V3)
        • V1 (Deprecated)
      • Bid on Transactions
      • Querying a Bundle
    • API Reference
      • eth_sendBundle
      • eth_cancelBundle
      • Page
  • Base
    • API Reference
    • How it works
    • Searchers
  • Solana
    • Searchers
      • Integration
        • Rust Decoding A Transaction
      • API Reference
        • sendBundle
        • getSignature
  • CAREERS
    • Senior Software Engineer
Powered by GitBook
On this page
  • Submitting a Bid
  • Authentication
  • The Winning Bid
  1. Searchers
  2. Integration

Bid on Transactions

PreviousV1 (Deprecated)NextQuerying a Bundle

Last updated 10 months ago

Submitting a Bid

Bids are submitted to Blink via https://ethauction.blinklabs.xyz/v1/{$API_KEY} as a bundle.

Bundles are submitted using the RPC call along with an array of transaction rawTxHex's and a block number.

Blink operates exactly the same way as Flashbots bundles with one exception.

Given the searcher doesn't have the rawTxHex for the transaction exposed on the WebSocket they must instead include the txHash for the user's transaction.

A sample "Post Body" is included below, "txHash" & "rawTxHex" are placeholders for the actual values.

{
    "id": 1,
    "jsonrpc": "2.0",
    "method": "eth_sendBundle",
    "params": [
        {
            "txs": [ 
                "txHash",
                "rawTxHex"
            ],
            "blockNumber": "0x779352"
        }
    ]
}

Blink will take the txHash and replace it with the rawTxHex for that transaction. The "refundPercent" & "refundRecipient" fields will also be added.

Your bundle will be immediately sent to all builders that have implemented "refundPercent" & "refundRecipient".

Blink enforces the User transaction to be the first in the array. This ensures no malicious MEV on the User's transaction. Bundles that do not put the users transaction first will be rejected.

Authentication

Authentication is not required but you can authenticate to establish a searcher "reputation" and be prioritised over searchers when there are matching bids.

You can authenticate using the same methodology as Flashbots, Blink requires you to sign the payload and include the signed payload in the X-Blink-Signature header of your request.

Any valid Ethereum key can be used to sign the payload. The Ethereum address associated with this key will be used by Blink to keep track of your requests over time and establish a searcher "reputation". You can change the key you use at any time.

The Winning Bid

For a given transaction the refund percentage will be fixed for all bundles, consequently, the Searchers who bids the most to the builder should, in theory, land their bundle on-chain.

For more information on bundles, see .

For more information on authentication, see .

eth_sendBundle
here
here