1---2name: cross-chain-bridge3description: Build cross-chain messaging and asset bridging — lock-and-mint, liquidity networks, and message verification4allowed-tools: [Read, Write, Grep]5effort: high6metadata:7 source: https://skillmd.com/skills/uitbreidenos/cross-chain-bridge8---910## When to activate1112- Building token bridges between EVM chains13- Implementing cross-chain messaging protocols14- Designing wrapped asset mechanisms (wrapped ETH on Polygon, etc.)15- Integrating existing bridges (LayerZero, Wormhole, Axelar)16- Building cross-chain NFT bridges1718## When NOT to use1920- For single-chain applications21- For centralized exchange transfers22- For off-chain cross-database synchronization2324## Instructions25261. **Choose bridge pattern.** Lock-and-mint (canonical), liquidity network (fast), or message-passing (general).272. **Select verification.** Validators (centralized), optimistic (fraud proofs), or light client (trustless but expensive).283. **Implement lock side.** Deposit contract, event emission, nonce tracking, replay protection.294. **Implement mint side.** Verification of source chain event, mint/claim function, replay protection.305. **Handle edge cases.** Source chain reorgs, validator downtime, stuck transactions, partial fills.316. **Security.** Multi-sig for validators, rate limiting, maximum bridge amounts, emergency pause.327. **Testing.** Simulate both chains with Foundry. Test reorg scenarios, validator failures, concurrent bridges.3334## Example3536```37Lock-and-Mint Bridge Flow:3839Source Chain (Ethereum):401. User deposits 1 ETH to Bridge contract412. Bridge emits LockedEvent(user, amount, destinationChain, nonce)423. Relayer picks up event4344Destination Chain (Polygon):454. Relayer submits proof of LockedEvent465. Verifier confirms event authenticity (validator signatures)476. Bridge mints 1 WETH on Polygon to user487. User can redeem WETH back to ETH via reverse flow49```