External keeper/relayer not redundant

Falcon Finance's assessment for RD-F-062 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

Falcon does not use on-chain keepers for core minting/redemption. The sUSDf Staking Rewards Distributor (0x8AF2EFa...) is the closest keeper-adjacent contract but its source is not confirmed verified and its failure mode is not documented.

Detail #

Yield generation occurs entirely off-chain via Fireblocks/Ceffu/Binance/Bybit. The Staking Rewards Distributor at 0x8AF2EFa47efB2095b80D82577c597186Ea2FFFea is listed in docs but per profile §8 its source verification status is not confirmed. No Gelato, Chainlink Automation, or custom on-chain keeper found in core protocol.

Sources #

Docs
Falcon Finance Smart Contractsdocs.falcon.finance/resources/smart-contracts — sUSDf Staking Rewards Distributor 0x8AF2EFa...retrieved 2026-05-12

Methodology #

Determine whether the protocol depends on a single keeper or relayer (Gelato, Chainlink Automation, custom) with no redundancy or failover.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol falcon-finance factor RD-F-062 score gray collected_at 2026-05-12 04:06:37