Deployed bytecode matches signed release tag

Evidence summary #

Core protocol contracts are immutable — bytecode fixed at deploy cannot drift. GitHub repos m0-foundation/protocol and m0-foundation/ttg are public. Release-tag-to-bytecode verification would require toolchain confirmation. Upgradeable periphery contracts were upgraded from audited baseline; specific commit SHAs vs deployed bytecode not confirmed by curator.

Sources #

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 →