Frontrunning Protection
Method: blxr_private_tx
Parameter | Description |
| [Mandatory] Raw transaction bytes without |
| [Optional] An integer value that represents the time, in seconds, needed to wait for a Private Transaction to be included in a block. If omitted, it defaults to 0. If |
curl https://api.blxrbdn.com \-X POST \-H "Content-Type: application/json" \-H "Authorization: <YOUR-AUTHORIZATION-HEADER>" \-d '{"method": "blxr_private_tx","id": "1","params": {"transaction": "f86b018477359...4d4b0e0b58219"}}'
Result Field | Description |
| Transaction hash |
{"jsonrpc": "2.0","id": "1","result": {"ffd59870844e5...bfa54a69"}}
The bloXroute Private Transactions Program is available for Enterprise tier users. In order to send Private Transactions, you need a balance of Private Transaction credits. Enterprise plans include 250 Private Transaction credits. Users can purchase additional credits through the Account Portal.
The average time for Private Transactions to be included in a block is affected by the hash rate of the mining pools participating in the program. Currently, the hash rate is above 30%.
Other than not broadcasting Private Transactions, mining pools are likely to treat private transactions the same as public transactions. It is the user's responsibility to submit Private Transactions with the proper gas price to be successfully mined.
Users can develop strategies for the waiting period between sending a Private Transaction and sending a public transaction. Note that if a user decides to send the transaction publicly, it is advantageous to replace the transaction with a higher fee. bloXroute conveniently only charges for Private Transactions that are mined. Users can also use the timeout parameter to instruct the BDN how long to wait for the Private Transaction to execute before sending it publicly
Participating mining pools agree not to broadcast Private Transactions to the peer-to-peer network, however there are still scenarios that Private Transaction can be exposed to the public before confirmation: for example, in circumstances where the block containing the Private Transaction becomes an orphan or uncle block. By using the Private Transactions Program, users understand that it is not guaranteed that Private Transactions will always be kept private.
