Deployed bytecode matches signed release tag

mETH Protocol's assessment for RD-F-136 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

GitHub mantle-lsp/contracts latest commit: 2025-10-31 (Merge PR #18 fix-pm). Staking proxy upgrade to 0x01a360392c74b5b8bf4973f438ff3983507a06a2 occurred 2025-10-30 (block 23689062) — one day before the final merge commit. Bytecode likely corresponds to the final merge, but no formal signed release tag verified. Match is plausible but not formally attested.

Sources #

GitHub
mETH Protocol GitHub commit historymantle-lsp/contracts latest commit: 2025-10-31 Merge PR #18 fix-pm by shellteoretrieved 2026-05-16
Etherscan
Staking proxy Upgraded event Oct 2025Staking proxy Upgraded event: 2025-10-30 block 23689062 to impl 0x01a360392c74b5b8bf4973f438ff3983507a06a2retrieved 2026-05-16

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 →

rubric_version v1.7.0 protocol meth-protocol factor RD-F-136 score yellow collected_at 2026-05-16 02:17:50