Test-mode parameters in deploy
Falcon Finance's assessment for RD-F-141 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Deployer EOA (0x804016…) retains permanent Safe signer status — a structural anomaly. However, admin was set to the Safe from genesis, not left as EOA. No test oracle, infinite allowances, or test admin addresses in deployed contracts. Partial test-mode concern.
Detail #
Deploy pattern: Safe was the admin from day 1 (not EOA transitioning to Safe). The deployer-as-signer pattern is intentional but creates structural concentration that resembles an unfinalised test parameter. No infinite token allowances, no test oracle endpoints, no test address whitelists identified in USDf or sUSDf ABIs.
Sources #
- EtherscanDeployer EOA on Etherscanhttps://etherscan.io/address/0x804016c31e52805eb00e0Ef42126Fd3e980A0b33retrieved 2026-05-12
- Safe Transaction Service — Falcon Finance Admin Safehttps://api.safe.global/tx-service/eth/api/v1/safes/0x1E482B60bf19Cb1cc859389e0eA3DED153f16Bd7/retrieved 2026-05-12
Methodology #
Determine whether the deployed configuration retains test-mode parameters (test oracle address, infinite allowance, admin = deployer EOA).
See the full factor methodology and distribution across all protocols →