Deployed bytecode matches signed release tag
Wormhole's assessment for RD-F-136 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Deployed bytecode matches signed release-tag commit | Core Bridge last deployment September 2022; the github repo shows last commit 2026-04-24 but the deployed implementation has not changed since Sept 2022. No git tag-to-bytecode verification could be confirmed programmatically (foundry_toml_present: false in data cache limits automation). Manual audit chain between GitHub main and deployed impl cannot be confirmed without build artifact. | Data cache (foundry_toml: false); Etherscan impl ad...
Sources #
- Curator noteExtracted from 02-governance-admin.md — RD-F-136; no URL citedretrieved 2026-04-28
Methodology #
Determine whether the deployed runtime bytecode corresponds to a signed git tag in the protocol's repository.
See the full factor methodology and distribution across all protocols →