Protocol Model
DraftStatus: Draft Version: 0.1.0 Last Updated: 2026-05-16 Owner: Axodus DeFi
Purpose
Protocol integrations define how Axodus DeFi evaluates external protocols, adapters, connectors, and smart contract dependencies.
Protocol Categories
Categories may include DEXs, lending protocols, staking protocols, liquidity pools, yield aggregators, oracle providers, bridges, and derivatives protocols. Integration does not imply endorsement or guarantee.
Integration Record
A protocol integration record should include protocol identifier, name, category, chain, integration purpose, supported assets, safe and verified contract references if public, liquidity context, audit or security status, governance status, risk level, oracle dependencies, bridge dependencies, pause or exit plan, reporting requirement, and status.
Review Checklist
Review should confirm protocol purpose, contract verification, audit or security status, admin controls, liquidity and exit conditions, oracle dependencies, bridge dependencies, fees, historical incidents, governance or parameter risks, treasury or user exposure, reporting data, and emergency exit plans.
Status Model
Use Research, Watchlist, Approved For Test, Approved For Limited Use, Approved, Paused, Deprecated, or Prohibited.
Risk Considerations
Protocol risk includes smart contract bugs, admin key risk, oracle risk, bridge risk, liquidity constraints, composability failures, and external governance changes.
Protocol State Model
A protocol design separates user intent, eligibility, asset custody, strategy logic, risk policy, transaction authorization, settlement, accounting, and exit. Each transition requires an identified interface and failure path. Repository or contract artifacts do not prove deployment, liquidity, custody, active strategies, or production operation; unconfirmed interfaces remain blocked dependencies.