How to Read a Bridge Mint-and-Burn Transaction on-Chain
A mint-and-burn transaction on a bridge is the on-chain record of a wrapped-assets/wrapped-token-lock-and-mint-explained/">wrapped token being created (minted) or destroyed (burned) when you move assets between blockchains. To read one, you locate the bridge’s smart contract on a block explorer, find the transaction hash, and interpret the event logs that show the mint or burn function being called, along with the amount and the destination or source address. This page walks you through the specific steps.
Why you need to read these transactions
Bridge transactions are not simple transfers. When you send 1 ETH from Ethereum to Arbitrum via a lock-mint bridge, the Ethereum side burns or locks the ETH, and the Arbitrum side mints a wrapped version. Reading the mint or burn event confirms that the bridge actually created or destroyed the token, rather than just moving IOU entries around. It also lets you verify that the amount matches what you sent, and that the custodian (if any) is acting properly.
Step 1: Get the Transaction Hash
You need the transaction hash from the chain where the mint or burn happened. For a bridge deposit, the mint occurs on the destination chain. For a withdrawal, the burn happens on the source chain. Find the hash in your wallet history, the bridge UI’s transaction log, or a block explorer search by your address.
Step 2: Open the Transaction on a Block Explorer
Paste the hash into a block explorer for the relevant chain (Etherscan for Ethereum, Solscan for Solana, etc.). Look for the “Logs” or “Event Logs” tab. This is where the bridge contract emits the mint or burn event.
Step 3: Locate the Mint or Burn Event
Mint and burn events are standardized by the ERC-20 or SPL token standard. On Ethereum-compatible chains, a mint event typically looks like:
Transfer(from: 0x0000000000000000000000000000000000000000, to: <your_address>, value: <amount>)
A burn event looks like:
Transfer(from: <your_address>, to: 0x0000000000000000000000000000000000000000, value: <amount>)
The zero address (0x000...000) is the key signal. If from is zero, tokens were created. If to is zero, tokens were destroyed. On Solana, the event may be in the instruction logs as MintTo or Burn.
Step 4: Check the Amount and Token Address
The value field shows the raw amount, usually in the smallest unit (wei for ETH, lamports for SOL). Divide by the token’s decimals (often 18 for ERC-20, 9 for SPL) to get the human-readable number. The token address is the wrapped asset - confirm it matches the bridge’s canonical token.
Step 5: Confirm the Bridge Contract Called the Event
Scroll to the “To” field in the transaction overview. That address should be the bridge’s smart contract on that chain, not a random wallet. Cross-check the contract address against the bridge’s official documentation or a trusted source like DeFi Llama. If the event came from a different contract, the token may not be legitimately wrapped.
Step 6: Look for Additional Bridge-Specific Events
Many bridges emit custom events alongside the standard transfer. For example, a lock-mint bridge might emit a Mint event with fields like user, amount, originChain, and nonce. These confirm the bridge’s internal accounting. On optimistic rollup bridges, you may also see a MessagePassed or SentMessage event that tracks the cross-chain message.
Example Walkthrough (Ethereum to Arbitrum)
Say you bridged 10 ETH from Ethereum to Arbitrum. On Ethereum, you see a Transfer event where your ETH is sent to the bridge contract (a lock). On Arbitrum, find the matching transaction hash from the bridge UI. Open it on Arbiscan. In the logs, you see:
Transfer(from: 0x0000000000000000000000000000000000000000, to: 0xYourAddress, value: 10000000000000000000)
The zero from address means 10 wrapped ETH (wETH on Arbitrum) were minted to you. The to address is yours. The bridge contract address is listed in the “Interacted With” field. That is a clean mint-and-burn record.
Common Red Flags
- No zero-address transfer event. If the transaction does not contain a
Transferfrom or to zero, no mint or burn happened. The bridge may be using a different mechanism or the UI is misleading. - Multiple mint events in one transaction. A legitimate bridge mints once per user per transaction. Multiple mints could indicate a bug or exploit that created unbacked tokens.
- Mint from a non-bridge contract. If the event comes from an address you cannot verify as the official bridge, the wrapped tokens may be counterfeit.
- Amount mismatch. Compare the amount in the mint event to what you sent. Differences can mean fees, slippage, or an error.
Why this matters for safety
Reading the mint-and-burn transaction is how you independently verify that a bridge operation completed correctly. It also lets you spot anomalies - like a bridge minting tokens without a corresponding lock on the source chain - that can indicate a hack or misconfiguration. Combined with checking proof-of-reserve data, it is the most direct way to confirm that a wrapped token is backed.
Not financial advice. ucit.lol publishes market data and general information about UCIT. Crypto assets are volatile and you can lose everything you put in. Nothing here is a recommendation to buy, sell or hold, and we make no price predictions.
Prices are sourced from third parties and may be delayed or wrong. Verify anything you intend to act on against a primary source.