External keeper/relayer not redundant
Sanctum'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 #
Sanctum's core products (Router, Infinity, Unstake Reserve) do not require an external keeper or relayer for pricing — all pricing reads are synchronous on-chain at transaction execution time. No off-chain rate-update relayer analogous to Jito's Wormhole rate updater exists. Gateway product routes through multiple providers (RPCs, Jito bundles, Triton, Paladin, Temporal) — multi-route redundant architecture for transaction delivery, not a single-keeper dependency for TVL-bearing operations. No single-operator keeper/relayer dependency identified.
Sources #
- URLIntroducing Sanctum GatewaySanctum Gateway: 'simultaneous delivery of transactions to various delivery channels' via RPCs, Jito bundles, Triton Cascade — multi-route, not single-keeperretrieved 2026-05-04
- 00-profile.md §7Profile §7: no external keeper/relayer for core pricing; all pricing is synchronous on-chain readsretrieved 2026-05-04
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 →