★ Default bytes32(0) acceptable as valid root
Curve Finance's assessment for RD-F-154 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
[★ CRITICAL] N/A for LayerZero V2 architecture. LZ V2 does not use a Merkle root commitment model. The Nomad $190M bug class requires a confirmAt[bytes32(0)] = 1 initialization in a Merkle root acceptability check — specific to Nomad's Replica architecture where the zero default could be trusted. LZ V2 uses per-packet payload hash commitment to the endpoint; there is no 'acceptable root' mapping that can be zero-initialized to enable replay. Architectural mismatch: not applicable.
Sources #
- URLLayerZero V2 WhitepaperLayerZero V2 whitepaper: payload hash commitment model vs. Merkle root acceptabilityretrieved 2026-04-28
- Nomad Bridge Hack Root Cause AnalysisNomad bridge hack root cause analysis — bytes32(0) as acceptable root, specific to Nomad Replica architectureretrieved 2026-04-28
Methodology #
Determine whether the bridge inbox accepts a default-value (bytes32(0)) Merkle root as a valid proof root (Nomad bug class).
See the full factor methodology and distribution across all protocols →