External keeper/relayer not redundant
Usual (USD0 / bUSD0 / USUAL)'s assessment for RD-F-062 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Core USD0 minting/redeeming is user-triggered via DaoCollateral; no external keeper required for core operations. CBR activation is admin-triggered (multisig), not an automated keeper dependency. No Gelato, Chainlink Automation, or similar keeper identified for the oracle/minting path. LayerZero executor (for OFT cross-chain) is a Cat 10 concern, not Cat 3.
Sources #
- EtherscanDaoCollateral Implementation — EtherscanDaoCollateral ABI — swap, swapRWAtoStbc, redeem are user-callable; no keeper/automation interface in core contractretrieved 2026-05-17
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 usual factor RD-F-062 score green collected_at 2026-05-16 20:39:44