Oracle role per asset

Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap's assessment for RD-F-049 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

Each Kashi pair has exactly one oracle configured at init() — no secondary or fallback oracle role. Oracle serves as Primary only. AMM swap path has no oracle role (internal pool math). Set-once pattern means no oracle role hierarchy exists — single point of failure per Kashi pair.

Sources #

Etherscan
KashiPairMediumRiskV1 Etherscan ABIKashiPairMediumRiskV1 0xbe9081e742d9e24aa0584a4f77382062f033752f — oracle() view + init(bytes data) encoding patternretrieved 2026-05-17
URL
BlockSec: Kashi KashiPairMediumRiskV1 logic bugBlockSec Kashi exploit analysis — confirms single oracle, no fallbackretrieved 2026-05-17

Methodology #

For each oracle, classify its role as Primary / Secondary / Fallback per asset/market.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol sushi factor RD-F-049 score yellow collected_at 2026-05-16 19:50:37