Stale-approval exposure on deprecated router

Babylon Protocol's assessment for RD-F-168 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

Not applicable. ERC-20 approvals and router patterns are EVM concepts. BABY is a native Cosmos denomination (ubbn), not an ERC-20. No EVM-style approve/transferFrom allowances exist. No deprecated router contracts on bbn-1 identified. Structurally inapplicable to this architecture.

Sources #

Docs
Babylon Genesis Tokenomics | Babylon DocsNon-EVM — BABY is native Cosmos denomination (ubbn); no ERC-20 approval pattern; no deprecated routerretrieved 2026-05-04

Methodology #

Count the number of active user approvals (ERC-20 `allowance`) to deprecated router or protocol contracts.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol babylon-protocol factor RD-F-168 score not_applicable collected_at 2026-05-04 19:43:27