Send Ghost Transaction
sendGhostTransaction allows you to submit a Solana transaction where the tip is supplied out of band, separately from the transaction itself.
Unlike a standard sendTransaction, the transaction need not contain a transfer to any one of Astralane's tip wallets. Instead, the tip is supplied through a parameter while making the sendGhostTransaction request to one of our endpoints.
Key points:
Out of band tipping - tip is provided separately from the transaction
Supplying the tip in the request is mandatory, specified in lamports
Smaller txn payload - no tip transfer needs to be embedded in the transaction
Same routing path - ghost transactions use the standard bundle router + dedicated iris pathways
Multiple transports - available through JSON-RPC, plain text, binary HTTP, and QUIC
Supports legacy and versioned transactions
Send Ghost Transaction - Plain Text
The plain-text implementation uses the /iris2 endpoint.
URI Params
api-key
String
Mandatory, API key used for authentication
method
String
Mandatory, must be sendGhostTransaction or send_ghost_transaction
tip
u64
Mandatory, out-of-band tip in lamports
mev-protect
Boolean
Optional, enables MEV protection. Default is false
swqos-only
Boolean
Optional, if set to true, transaction is only sent through SWQoS. Default is false
Example Request
The request body must contain the base64-encoded signed transaction.
The transaction itself must not contain a tip transfer.
Here, 1000000 represents a tip of 0.001 SOL.
Expected Response
Send Ghost Transaction - Binary
The binary implementation uses the /irisb endpoint.
Unlike /iris2, the request body contains the raw serialized transaction bytes instead of a base64-encoded transaction.
URI Params
api-key
String
Mandatory, API key used for authentication
method
String
Mandatory, must be sendGhostTransaction or send_ghost_transaction
tip
u64
Mandatory, out-of-band tip in lamports
mev-protect
Boolean
Optional, enables MEV protection
swqos-only
Boolean
Optional, if set to true, transaction is only sent through SWQoS
Example Request
Where tx.bin contains a single serialized Solana transaction.
Send Ghost Transaction - QUIC
Ghost transactions can be submitted over QUIC using a dedicated ghost-enabled QUIC listener.
A standard QUIC listener cannot be used for ghost transactions.
The target listener must be configured with
ghost: true.For example:
:6000- Ghost QUIC listener:7000- Standard QUIC listenerSending a ghost frame to a standard QUIC listener will cause the frame to be interpreted as a normal transaction and dropped.
Wire Format
Each QUIC stream contains a single ghost frame:
The first 8 bytes contain the tip in lamports encoded as a little-endian u64.
The remaining bytes contain the serialized Solana transaction.
Authentication
Authenticate with your api_key
Example
For a tip of 1,000,000 lamports:
The resulting bytes are sent as a single QUIC frame.
QUIC Response
QUIC ghost submissions are fire-and-forget.
There is no response body or transaction signature returned by the QUIC listener.
Common Errors
If the transaction contains a recognized tip transfer, the request will be rejected:
If the tip parameter is missing:
Transaction contains a recognized tip transfer
JSON-RPC error
400 error
Frame dropped
Non-base64 encoding
Only base64 encoded transactions are supported
-
-
Missing tip
Invalid request
400 - missing required tip param
-
Method not recognized
401
401
-
Method not allowed
405
405
-
Ghost frame shorter than 8 bytes
-
-
Frame dropped
Last updated