Breakage analysis per dependency
Spiko's assessment for RD-F-052 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Oracle staleness: subscription/redemption contracts revert; underlying T-bill holdings unaffected (off-chain AMF fund). CCIP failure: cross-chain transfers halt; single-chain operations continue. CACEIS failure: NAV not publishable; all on-chain pricing becomes stale at next business day. ATM3 oracle cannot be replaced by admin action — only full contract redeployment restores oracle if the feed address changes.
Sources #
- URLSpiko Smart Contracts — Spiko Tech Blogtech.spiko.io/posts/spiko-smart-contracts/ — confirms CACEIS as off-chain NAV data sourceretrieved 2026-05-16
- ATM3.sol — spiko-tech/contracts GitHubATM3.sol — immutable oracle reference means oracle address cannot be updated if oracle contract must be replacedretrieved 2026-05-16
Methodology #
Produce a short per-dependency text describing which protocol functions halt or degrade and impact severity if each declared dependency fails.
See the full factor methodology and distribution across all protocols →