industry · quantum risk
Aave admin and guardian keys & Quantum Risk
Verdict
Aave admin and guardian keys: still classical key risk unless PQC is verified. Aave is not quantum-proof. User positions inherit classical host-chain signatures; protocol guardians/admins and oracles add high-leverage classical keys that can freeze, upgrade, or reprice markets.
Overview
Lending protocols encode emergency and risk powers. Those roles are almost always classical keys or governance contracts controlled by classical keys.
A CRQC narrative that only discusses borrower EOAs understates how market-wide parameters are administered.
This spoke isolates the admin-keys key graph for Aave on host chains: ethereum, arbitrum, optimism, base, polygon, avalanche. User wallets remain classical on those hosts unless a different scheme is proven.
Cross-read the protocol hub at /is-quantum-proof/aave, category hubs under /is-quantum-proof/defi, and the free /assessment for organizational posture. Educational only—not investment advice.
Cryptographic profile
What breaks
- Compromise of admin-keys related keys
- Equating role separation with post-quantum algorithms
Mitigations
- Document role addresses from official docs
- Enforce hardware/MPC on privileged roles
- Return to /is-quantum-proof/aave for full protocol context
FAQ
Are guardians quantum-proof?
Not by role name—only by the algorithms backing their keys.
What should risk teams document?
Every address with pause, upgrade, or risk-parameter rights per deployment.
Key concepts (technical dictionary)
Terms used on this page — open a definition: