industry · quantum risk
Kamino oracles & Quantum Risk
Verdict
Kamino oracle dependencies are not quantum-proof. Vaults liquidate based on classical feed integrity.
Overview
Map which Pyth/Switchboard/other feeds each market uses and who can update config.
Cryptographic profile
- Signatures: Host-chain account signatures for role holders (typically classical ECDSA/Ed25519), Multisig/module keys as deployed
- Hash: Host-chain dependent
- Public-key exposure: Oracle accounts used by Kamino markets
- Hosts/context: Solana price feeds for vaults
What breaks
- Compromise of oracles related keys for Kamino
- Equating role separation or multisig with post-quantum algorithms
- Untracked multi-chain deployments of the same protocol
Mitigations
- Document privileged addresses from official docs per chain
- Hardware/MPC for guardians, admins, and large governors
- Return to /is-quantum-proof/kamino for protocol context
- Use category hubs: lending, dex, perps, stablecoins
FAQ
Related?
/is-quantum-proof/oracles
Admin?
/is-quantum-proof/kamino-admin-keys
Key concepts (technical dictionary)
Terms used on this page — open a definition: