Submitting Transaction
This endpoint is used to broadcast a signed transaction
How OFR Handles Transaction Propagation
When you submit a transaction to the OFR endpoint, bloXroute’s infrastructure determines the current Solana leader and forwards the transaction to the Trader API instance that is geographically closest to that leader. This dynamic routing reduces latency and increases the probability of successful inclusion on-chain.
This behavior is fully abstracted away from the user. You do not need to manually manage or track leader locations—OFR handles that for you.
Recommended Submission Strategy
To maximize reliability and minimize latency, we recommend submitting each transaction to:
Your nearest Trader API endpoint, and
The OFR
/submit
endpoint.
This dual submission approach ensures both localized propagation from your own infrastructure and optimized propagation through OFR’s leader-aware routing.
Gateway setup
The two flags required at gateway startup for transaction submission are: -run-http-server
and -http-port
:
Additionally, gateway can be started with the -tx-submission-only
flag. This will launch the gateway in a dormant mode in which no shreds are sent nor received from OFR, effectively turning it into a local transaction submission API only.
Request
Method:
POST ./submit
Example
The Solana Gateway, connecting to the bloXroute Optimized Feed Relay (OFR), should run with http server flags, and more details about flags can be found here.
Last updated