submit-snipe

This endpoint is designed to maximize your landing speed for a pair of transactions that compete with each other (mainly token sniping use case).

This endpoint accepts a pair of competing transactions and submits the first to the Jito block engine while sending the second through bloXroute staked connections. Both transactions must include a minimum bloXroute tip of 0.001 SOL, and the first transaction must also include a valid tip to one of Jito’s tipping walletsarrow-up-right.

Since the first transaction is submitted through Jito-protected flow, a priority fee is generally not required, while the second transaction sent through staked connections should include a competitive priority fee.

circle-info

If you do not want both sniping transactions to land successfully, you are responsible for making them mutually exclusive, such as by using the same durable nonce so that the first landing transaction invalidates the other.

Request

Method:

POST ./api/v2/submit-snipe

Parameters:

Parameter

Type

Description

entries

PostSubmitRequestEntry []

A list of signed transaction. See PostSubmitRequestEntry below

useStakedRPCs

boolean

OPTIONAL. Specify if you would like to send transactions using staked RPCs. If not provided or if False, fastBestEffort is used. Default False.

PostSubmitRequestEntry

Parameter

Text

Description

transaction

TransactionMessage

See TransactionMessage below

TransactionMessage

Parameter

Text

Description

content

txbase64Payload

Raw bytes of signed transaction.

Request example:

Response:

Fields:

Field

Type

Description

transactions

list

A list of signature.

Field

Type

Description

signature

string

Solana signature of the submitted transaction

error

string

Return error message.

submitted

boolem

If the transaction has been submitted.

Example:

You can look up this signature in a Solana Explorer like SolScanarrow-up-right or Solana Explorerarrow-up-right.

Last updated