Deployed bytecode matches signed release tag
Fluid'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 #
Public repo uses merge-sync pattern without explicit signed release tags. Etherscan Exact Match provides partial confidence. Latest commit 2026-03-04 (a9949b48) is a sync merge. Full bytecode-to-commit tracing requires local build.
Sources #
- GitHubfluid-contracts-public: latest commit 2026-03-04 sync merge; no signed release tagsInstadapp/fluid-contracts-public commit a9949b48retrieved 2026-04-29
- Etherscan Exact Match verification — partial confidence for bytecode correspondence0x53EFFA0e612d88f39Ab32eb5274F2fae478d261C Exact Matchretrieved 2026-04-29
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 fluid factor RD-F-136 score yellow collected_at 2026-04-29 10:35:01