Moving between chains safely

Bridges are where most large crypto losses have happened. Not because bridging is exotic, but because a bridge holds a lot of value in one contract. This is what to check before you use one.

What a bridge actually does

Nothing physically moves between chains. A bridge locks your token on the chain you are leaving and issues a matching token on the chain you are arriving at. Both sides are contracts, and the guarantee is only as strong as the weaker one.

The safeguards on this bridge

• Rate limits. A cap on how much can cross in a given window, so an exploit cannot drain the contract in a single block.
• Per-transaction caps. A ceiling on any single transfer, which is what turns a catastrophic loss into a contained one.
• Timelock on parameter changes. Those limits cannot be quietly raised — a change is visible on-chain before it takes effect.
• Route simulation. The client simulates the route before you sign and shows the exact amount that will leave your wallet.

Checking the other side arrived

A bridge transfer is two transactions on two chains, so it is normal for the destination to lag the source by a few blocks. On Danny Chain, blocks close about every 2.0 seconds, so a wait of more than a minute or two is worth investigating rather than repeating.

Never resend a bridge transfer because the destination looks empty. Find the source transaction on the explorer first — if it confirmed, the funds exist and the second leg is pending. Sending again simply bridges twice.

Habits worth keeping

• Bridge a small test amount first when using a route for the first time.
• Keep a little of the destination chain's gas token before you arrive, or you will land with funds you cannot move.
• Revoke bridge approvals you no longer use — an approval is a standing permission, not a one-off.