A treasury ledger for Mantle Bridge transfers
A bridge reconciliation matches each cross-chain instruction to the funds actually received. The key condition is that a deposit and a withdrawal reach their destination at different stages, so a source-chain transaction alone does not prove the destination balance is ready.
If your team uses the canonical route and needs an on-chain record for each transfer, the official Mantle Bridge submits the deposit or withdrawal through the bridge contracts. Record the source transaction hash when it is submitted, then reconcile against the destination transaction and balance once the transfer completes.
Track each transfer through both chains
Give every transfer a unique internal reference, and keep a row for each direction. For deposits, the Ethereum transaction locks the asset; the destination credit on Mantle is a separate event to verify. For withdrawals, the Mantle transaction starts the exit; the Ethereum funds are not available until the exit is ready and claimed.
- Internal payment or treasury reference
- Source and destination networks, wallet addresses, token and amount
- Source transaction hash, submission time and gas paid
- Destination transaction hash, credited amount and completion time
- Current status, such as submitted, pending or completed
For a withdrawal, keep the final Ethereum claim as its own reconciliation step. A submitted Mantle transaction is evidence that the exit began, not that Ethereum received the funds. Check the bridge status and confirm the destination transaction before marking the transfer complete.
Reconcile amounts and fees separately
Compare the destination amount with the amount sent, accounting for token decimals and any fee shown before submission. Keep network gas separate from the asset amount: an ERC-20 deposit may require an Ethereum approval and deposit transaction, while a withdrawal can require gas on Mantle to start and Ethereum gas to claim.
For example, say the team sends 10,000 USDT and the transaction records 8 USDT in gas. The expected asset credit is 10,000 USDT if the bridge route shows no asset deduction; record the 8 USDT as a separate expense, not as a shortfall. If the destination credit differs from the expected amount, leave the row pending review until you can match it to the on-chain transfer.
Set a close rule for pending transfers
At each treasury close, classify transfers by their latest verified stage rather than by the date they were requested. Keep pending deposits and unclaimed withdrawals in a transit account, and move them to the destination wallet balance only after confirming the destination transaction.
Use the same procedure for each Mantle Bridge transfer, and retain both transaction hashes with the ledger entry. Before sending a regular payout, ask yourself: can the team fund the required gas and wait for the destination-stage confirmation before it needs these assets?
Comments
Post a Comment