Oasis sells privacy via Intel SGX, not via cryptography. That feels reassuring right up to the moment you notice the attestation itself is ECDSA. Break the attestation, forge the enclave, and the historical sealed state is no longer sealed by anyone you can verify.
Summary
Oasis Network treated as privacy-L2 (TEE-based privacy via Sapphire + ROFL). Band 2 (Acknowledged). Unique exposure profile: privacy rests on Intel SGX attestation (ECDSA) rather than crypto primitives. Quantum break of ECDSA forges attestations, potentially unsealing historical confidential state. Zero PQC work. EU DAC8 (Jan 2026) creates demand but no PQC response.
What the gates say
- Hybrid: FAIL. No hybrid plan on file.
- Evidence: PASS. Sources reconstructable by third party.
- Primitive naming: PASS. Named primitives at every scored sub-level.
Burn-vs-rescue policy on file
undeclared
Seven dimensions
Each dimension scores 0-100 internally; the weighted roll-up produces the QRI on the left. Open a row to read the sub-score detail.
1 Cryptographic Exposure 30 / 100
TEE-based privacy is non-crypto — SGX attestation uses RSA/ECDSA.
Ed25519 (consensus + tx) · SHA-512 · Intel SGX attestation (ParaTime TEE)2 HNDL Exposure 20 / 100
Ed25519 pubkey exposed.
Same.
Tx-once.
SGX-based confidential compute — if SGX cracked OR underlying attestation ECDSA broken, historical sealed data is at risk.
3 Metadata & Privacy Exposure 45 / 100
Sapphire confidential EVM conceals tx-level state but not tx graph at consensus layer. Metadata (sender/receiver/amount) visible depending on Sapphire vs Cipher ParaTime.
Oasis Foundation-operated RPC heavy.
Bridges to Ethereum; correlation possible at bridge endpoints.
TEE privacy is different profile — confidentiality rests on SGX seal keys + attestation. If ECDSA attestation breaks, historical attestations forgeable; sealed state potentially reconstructable. Lower than pure-crypto privacy but non-trivial.
4 Migration Architecture 25 / 100
ParaTime modular but core Ed25519 fixed.
Standard Cosmos/Oasis keys.
Multiple upgrades since 2020.
ParaTime could host PQC ParaTime in theory.
5 Deployment Execution 0 / 100
6 Supply Chain Vendor Readiness 5 / 100
7 Governance & Coordination 30 / 100
~120 validators.
Sapphire, ROFL AI rollouts.
Oasis Foundation (UC Berkeley founders).
No PQC or SGX-break precedent.
The X + Y vs Z inequality
X (data shelf life): 10-20 (confidential state shelf-life infinite if SGX sealed)
Y (migration time): 10-15
Z10 (10% CRQC year): 2036 · Z50 (50%): 2041
Verdict: X+Y > Z (danger).
Four-scenario grid
| Scenario | Value preserved | Privacy preserved |
|---|---|---|
| quantum never | 100% | 100% |
| arrives suddenly pre migration | 5% | 20% |
| arrives slowly post migration | 78% | 55% |
| arrives slowly mid migration | 30% | 30% |
Peers in the privacy-L2 profile
Order-book view of the 5 chains closest to Oasis Network by QRI.
Public artifacts used for this scorecard
Each entry below is a sub-score citation. Clicking the link takes you to the public source. A third party should be able to reconstruct every number on this page from these URLs in 48 hours.
TEE-based privacy is non-crypto — SGX attestation uses RSA/ECDSA.
Supply chain snapshot
A chain's supply chain cannot migrate faster than its slowest dependency. Zero PQC roadmaps in any of the four categories is a structural blocker, not a lagging indicator.
Analyst notes on the scoring
TEE-privacy retroactive-deanon profile is different from zk-privacy: SGX seal keys themselves are independent of Shor. However, SGX attestation relies on ECDSA/RSA which Shor breaks, allowing forged attestations — less severe than a ring-signature Shor-break but still material. Scored 3d=10/25.
Scorecard metadata
- Profile: privacy-L2
- Scored: 2026-04-18 by
layerqu-v2-scoring-agent-4 - v1 reference:
chainscreen-v1-archive - QRI raw: 15 · after caps: 13
- Confidence interval: ±15
- PQC washing ratio: 1x
- Burn-vs-rescue: undeclared
Caps triggered
- Mosca (5a<20%)
- Sutor (5d=0)
- Preskill (<3 artifacts several dims)
- Casado
- Hybrid gate FAIL → QRI cap 60