Obtain the status of a specific bridge transaction by withdrawal hash
This endpoint provides the status of a bridge transaction as created through the POST /quote/user or POST /quote/bridge-swap/user endpoints based on a given withdrawal transaction hash. For status information for Smart Deposit Address transactions, the GET /sda/deposit-addresses/{depositAddress}/{depositChain} endpoint should be used.
Authorizations
JWT token for authentication
Path Parameters
The transaction hash of a withdrawal for a bridge transaction, e.g. "0x5c504ed432cb51138bcf09aa5e8a410dd4a1e204ef84bfed1be16dfba1b22060".
Response
BridgeExecuted
- Option 1
- Option 2
- Option 3
The projectID that the transaction is associated with.
The blockchain that the tokens were bridged from.
The blockchain that the tokens were bridged to.
The native value of the tokens that were sent on the chainIn.
The USD value of the tokens that were sent on the chainIn.
The native value of the tokens that were sent on the chainOut.
The USD value of the tokens that were sent on the chainOut.
The amount of native gas token (e.g. ETH, MATIC, BNB) that was delivered to the user's wallet on the destination chain as part of gas boost functionality, where Rhino.fi delivers a small amount of native gas token to the destination address, ensuring that further transactions from this address can be made immediately.
The value, in USD, of amountNative.
The total cost of the transaction as paid by the end customer, denominated in the token.
The total cost, in USD, of the transaction.
Any chain specific costs charged to the end customer for the chainOut part of the overall transaction. Further information about which chains have these associated costs can be found here: https://learn.rhino.fi/articles/7749894324-tron-and-solana-onchain-gas-costs. If these costs are being paid by the client then this value will be zero and the gasFee and gasFeeUsd in the sponsored fee body will be non-zero.
The gasFee value, in USD.
The resulting fee charged from the $-based Client Surcharge. This is applicable to both legacy and PAYG/Subscription clients. For legacy clients this is deducted from the tokens sent on the chainOut and will be sent to the client at month end. For PAYG/Subscription clients this will be rebated at month end.
The platformFee value, in USD.
The resulting fee charged from the %-based Client Surcharge. This is applicable to both legacy and PAYG/Subscription clients. For legacy clients this is deducted from the tokens sent on the chainOut and will be sent to the client at month end. For PAYG/Subscription clients this will be rebated at month end.
The percentageFee value, in USD.
The cost on the chainIn to sweep the received tokens into Rhino.fi's control. For legacy clients this is deducted from the tokens sent on the chainOut. For PAYG/Subscription tier clients this is paid by Rhino.fi as part of the PAYG/Subscription monthly cost so no direct cost is passed onto the end customer, unless configured this way. This is only relevant for transactions involving a Rhino.fi Smart Deposit Address; for bridging/swapping-only activity the sourceGasFee will be paid directly by the customer within their depositing transaction.
The sourceGasFee value, in USD.
For both legacy and PAYG/Subscription clients, represents the fees that are paid by the client on behalf of the end customer.
The address on the chainOut that received the bridged tokens.
The address on the chainIn that sent the tokens for bridging.
The datetime that the bridging / bridging+swapping quote was created.
The datetime that the bridging / bridging+swapping quote was committed with Rhino.fi.
The asset being bridged, sent on the chainIn and received on the chainOut.
The USD price of the token at the time the quote was created.
The transaction hash of the deposit made on the chainIn.
The datetime that the deposit transaction was committed on the chainIn.
The transaction hash of the withdrawal of the tokens to the recipient on the chainOut.
The datetime that the withdrawal transaction was committed on the chainOut.
EXECUTED Provides information about whether the transaction is expected to be completed "fast" (typically under 30 seconds), "standard" (typically under a minute) or "slow" (can be up to 20 minutes). For more information on our bridge processing speeds please read this article on the Rhino.fi Knowledge Base: https://learn.rhino.fi/articles/8257872655-bridge-speed.
fast, standard, slow The estimated time for the transaction to complete in milliseconds.
x >= 0Custom Routing Rules as configured by Rhino.fi for a specific client, e.g. to move funds after the initial bridge into a yield bearing vault. To understand more about how Routing Rules can help automate onchain actions and ensure that your funds land in an active state, please contact your Rhino.fi Customer Success Manager or speak to a member of the Rhino.fi sales team.
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
- Option 8
- Option 9
The number of Flow Credits that this transaction will use from the client's agreed Rhino.fi PAYG/Subscription tier.
bridge The datetime that Rhino.fi first discovered the deposit transaction on the chainIn.
The datetime that the deposit transaction reached the required number of confirmations on the chainIn.
The datetime that the deposit transaction is expected to reach the required number of confirmations on the chainIn.
The block on the chainIn at which the deposit transaction is expected to reach the required number of confirmations.
The transaction hash of the swap performed on the chainIn before bridging.
The datetime that the pre-bridge swap was committed on the chainIn.
Whether the deposit transaction has reached the required number of confirmations on the chainIn.