Cross-Chain Bridge Security Checklist
17 security checks specifically for cross-chain bridges. Covering validator security, message verification, liquidity pools, and integrations with LayerZero, CCIP, Wormhole, and Axelar.
Automate with Krait CLI
47% of these checks can be automated against your codebase. 9 checks require manual review.
/krait:scan --deepInstall Krait →CATEGORIES
Validator Set Security
CriticalKraitMulti-sig thresholds, validator rotation, slashing conditions, Byzantine fault tolerance
Relay Network Security
HighKraitRelayer incentives, censorship resistance, delivery guarantees
Message Passing Security
CriticalKraitMessage authentication, replay prevention, ordering guarantees, timeout mechanisms
Lock-and-Mint Mechanisms
CriticalKraitSupply conservation, mint authority controls, burn proof verification
Liquidity Pool Bridges
HighKraitRebalancing mechanisms, slippage protection, pool insolvency
Oracle Integration
HighKraitPrice feed accuracy across chains, manipulation resistance, failover mechanisms
Circuit Breakers
HighKraitPause mechanisms, volume limits, velocity controls, emergency governance
Finality Handling
CriticalKraitSource chain finality, reorg protection, confirmation requirements
Emergency Recovery
HighStuck funds recovery, upgrade mechanisms, guardian actions
LayerZero Integration
HighEndpoint configuration, trusted remote setup, lzReceive safety
Chainlink CCIP
HighRouter configuration, ccipReceive implementation, fee handling
Wormhole Integration
HighVAA verification, guardian set validation, message parsing
Axelar Integration
HighGateway validation, GMP calls, token transfers
Signature Validation
CriticalReplay attacks, malleability, threshold signatures
Access Control
CriticalRole management, admin functions, upgrade authorization
Reentrancy
CriticalCross-function, callback reentrancy, state consistency
Integer Overflow
HighAmount calculations, fee handling, supply tracking
Need a Professional Bridge Audit?
Cross-chain bridges have lost $2B+ to exploits. Get your bridge audited by the team that understands the complex security model.