Dependency graph (protocols depended upon)
Axelar Network's assessment for RD-F-050 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Axelar's primary existential dependency is its own Cosmos-SDK L1 validator set (~47 active validators, 60% weighted quorum for cross-chain operations). Secondary dependencies: AxelarAuthWeighted auth module for proof validation, InterchainGovernance (7-day delay) for EVM parameter changes, custom 3-of-6 Multisig as mintLimiter. No external third-party DeFi protocol dependency for bridge function. Yellow because the validator set is a non-redundant single trust root — chain halt causes full bridge halt with no fallback.
Sources #
- EtherscanAxelar Custom Multisig (mintLimiter)Custom Multisig 0xCC940AE49C78F20E3F13F3cF37e996b98Ac3EC68 — 3-of-6, mintLimiter roleretrieved 2026-05-17
- Axelar Network Security DocumentationAxelar security model — validator set as trust root, quadratic voting, 60% cross-chain quorumretrieved 2026-05-17
Methodology #
List all external protocols whose failure would directly impair this protocol (LST providers, bridges, stablecoin issuers, keepers).
See the full factor methodology and distribution across all protocols →