Blockrazor
Use POST /blockrazor with the same request shape described in the official BlockRazor docs. Bifrost supports both official BlockRazor HTTP contracts:
v1 JSON body:
/sendTransactionv2 low-latency plain text body:
/v2/sendTransaction
Reference:
Tip Addresses
Current BlockRazor tip addresses recognized by this Bifrost deployment:
FjmZZrFvhnqqb9ThCuMVnENaM3JGVuGWNyCAxRJcFpg96No2i3aawzHsjtThw81iq1EXPJN6rh8eSJCLaYZfKDTGA9cWowVAiHe9pJfKAj3TJiN9VpbzMUq6E4kEvf5mUT22Gywj98ophM7GmkDdaWs4isqZnDdFCW7B46TXmKfvyqSm68Pwb4jS7eZATjDfhmTXgRJjCiZmw1L7Huy4HNpnxJ3o4ABhJh5rZPjv63RBJBuyWzBK3g9gWMUQdTZP2kiW31V9B2M4NG5eyZp5SBQrSdtemzk5TqVuaWGQnowGaCBt8GyM5jA59cXMKQqZAVdtopv8q3yyw9SYfiE3vUCbt7p8MfVf5YktoWygr1Bp9wiS1xtMtUki1PeYuuzuCF98tqwYxf61295Avbam4qGShBYK7E9H5Ldew4B3WyJGmgmXfiWdeeyVEDi4rSy2LZgKJX74mbLTFk4mxoTgT6F7HxxzG2HBAFyKBnGKHAC386n4Qmv9xtpBVbRaUTKixjBe3oagkPFKtoy6Dd7K2Fp7AtoN8xCghKDRmyqr5U169t48Tw5fEd3wT9mqAP6qExwrbRgBAVaehg4b5xHENX815sMabtBzUzVB4v8S
v1 JSON Contract
Send Content-Type: application/json and the upstream JSON body:
Fields:
transaction: required, signed transaction stringmode: optional,fastorsandwichMitigationsafeWindow: optional,3-13revertProtection: optional booleanAuth: upstream v1 uses the
apikeyHTTP header
Example:
v2 Plain Text Contract
Send Content-Type: text/plain and put request parameters in the query string, exactly as BlockRazor v2 expects.
Notes:
Upstream v2 expects Base64 transaction text in the body
Upstream v2 only permits
Content-Type: text/plainQuery params such as
mode,safeWindow,revertProtection, andauthare forwarded upstreamIf your Bifrost deployment already has BlockRazor credentials configured, you can usually omit
auth
Response
For v1, BlockRazor returns JSON with a
signaturefield.For v2, BlockRazor returns standard HTTP status codes as documented upstream.
Last updated