Deployed bytecode matches signed release tag
Aave v3'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 #
v3.6.0 release tag exists at aave-dao/aave-v3-origin (2025-01-08). T-10 noted a commit SHA discrepancy between Governance Proposal 429 (b3ce634) and v3.6.0 release tag (5a230ec). This discrepancy was not resolved independently in this session.
Sources #
- GitHubAave V3 Origin - GitHub Releases (v3.6.0 = 2025-01-08)aave-dao/aave-v3-origin releasesretrieved 2026-04-27
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 aave-v3 factor RD-F-136 score yellow collected_at 2026-04-27 23:28:46