A cross-chain transfer usually asks you to trust 2 separate things: the source chain’s finality and the bridge’s verifier. On a centralised exchange, the exchange handles both behind the scenes; from your wallet, you approve a transaction and rely on another system to confirm it on the destination chain. A route through Mayan bridge shows why the route matters: an app can offer several ways to move assets, each with its own checks.
Source-chain finality sets the first wait
Finality means the point when a transaction is treated as settled and unlikely to be reversed. A bridge verifier must decide when the source transaction is settled enough to act on it.
For example, Wormhole Guardians watch supported chains and sign a message after observing an event. A destination contract checks those signatures before acting. Wormhole requires 13 of 19 Guardians to agree, but the time they wait depends on the source chain and the chosen finality setting.
Wormhole’s published estimates put finalized messages at around 14 seconds on Solana and 19 minutes on Ethereum. Those are estimates, and actual waits can vary. Faster confirmation can mean more chance that a source-chain reorganisation—a change to recently recorded blocks—undoes the event.
The verifier decides whose report counts
A bridge verifier sets the rules for accepting a cross-chain message. In Wormhole’s model, a quorum, or required group, of Guardians signs a message, and the destination contract checks their signatures.
Other routes can use a different trust arrangement. Circle CCTP, for instance, has Circle provide a signed attestation—a statement confirming a USDC burn on the source chain. The destination contract checks that attestation before minting USDC there. The underlying chain still determines when the burn is final.
So “supported on both chains” does not mean “verified the same way.” The route may rely on a group of independent signers, a named issuer’s attestation, or another system. Even within one app, the verifier can change with the route selected.
Check the route before you approve
Before signing, check which route the quote uses, how much you should receive, and which token will arrive. A quoted amount is the expected result; the minimum amount is the least the route promises under its stated conditions.
A common mistake is to treat a bridge quote like an exchange order and assume the app handles every risk. Instead, check the source and destination chains, the route name, the token, and the minimum received. Also keep enough of the source chain’s native token—the coin used to pay transaction fees—to submit the transfer.
After signing, the source transaction may confirm before the destination transfer finishes. A relayer, a service that carries the signed message to the destination, may still need to submit it. For Mayan bridge routes, the method shown for that transfer helps explain who verifies the message and why the wait can vary.
The useful habit is to judge each route by its finality rule and verifier, then sign only when those checks and the quoted result make sense to you.
Top comments (0)