industry · quantum risk
Spark oracles & Quantum Risk
Verdict
Spark oracle paths are not quantum-proof. Price integrity depends on classical feed signatures and adapter ownership.
Overview
Savings and lending products that depend on prices inherit oracle quantum risk. Inventory feeds alongside admin keys.
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 adapters securing Spark markets
- Hosts/context: Collateral and rate-related feeds
What breaks
- Compromise of oracles related keys for Spark
- 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/spark for protocol context
- Use category hubs: lending, dex, perps, stablecoins
FAQ
Related hubs?
/is-quantum-proof/oracles and /is-quantum-proof/lending
Protocol page?
/is-quantum-proof/spark
Key concepts (technical dictionary)
Terms used on this page — open a definition: