Deployed bytecode matches signed release tag
Falcon Finance's assessment for RD-F-136 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No public GitHub repository for Falcon Finance smart contracts. Cannot verify deployed bytecode against a signed git tag. Protocol uses closed-source development. Etherscan source is verified but no reproducible build path exists.
Detail #
Data cache: github.repo_url=null, foundry_toml_present=false, hardhat_config_present=false. Profile §9: 'FalconFinance GitHub org exists but appears unrelated (Uniswap v2 fork). No official Falcon Finance DeFi smart-contract GitHub found.' Solidity version v0.8.28+commit.7893614a visible in Etherscan, but no signed release tag or build artifact is publicly accessible.
Sources #
- DocsFalcon Finance audits page — no GitHub source linkhttps://docs.falcon.finance/resources/auditsretrieved 2026-05-12
- USDf implementation ABI — no timelock-gated functionshttps://etherscan.io/address/0x3aDf34C09DAC24E4BAeFB1b1df4C2992edC2b789#coderetrieved 2026-05-12
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 →