Deployed bytecode matches signed release tag
Babylon 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 releases exist with version tags (v4.2.7 Apr 14, 2026; v4.0.0 Nov 6, 2025 etc.). No independent bytecode-vs-commit-SHA match verification performed at this tier. Cosmos SDK binary compilation is known to produce non-deterministic outputs across OS/Go versions without explicit reproducible build tooling. No formal 'reproducible builds' attestation published for Babylon Genesis binary. Release discipline above average for Cosmos SDK chains but no signed artifact verification confirmed.
Sources #
- GitHubBabylon Genesis Chain ReleasesGitHub releases with version tags — 10 recent releases confirmedretrieved 2026-05-04
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 →