NEAR has the cleanest key-rotation architecture in the batch and zero deployed PQC to rotate to. The access-key system means a migration could happen without redesigning accounts. The awkward part is that architectural readiness and operational readiness are not the same thing, and NEAR has one of them.
Summary
NEAR scores Band 2 (Acknowledged) on awareness only. Ed25519 across tx + validator, SHA-256 hashing — no PQC in core or testnet. NEAR's structural advantage is account abstraction: native access-key rotation means a PQC migration is architecturally feasible via access keys, NOT via account redesign. Despite this edge, zero PQC code, zero roadmap, zero milestones published.
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 35 / 100
Minimal inventory, only Ed25519 + SHA-256 published.
Ed25519 (tx + validator) · SHA-256No PQC families in core.
2 HNDL Exposure 22 / 100
Implicit accounts: Ed25519 pubkey = account. 90-100% exposure. Named accounts also store pubkey on-chain.
Same 100% exposure via access-key system.
Tx-oriented chain; short validity window typical.
Standard TLS — no PQC for RPC or validator comms.
3 Metadata & Privacy Exposure 34 / 100
Pseudonymous, human-readable account names improve observability further.
Pagoda/FastNEAR RPC concentration.
Rainbow Bridge and Aurora link tx flows.
No native privacy — no retroactive risk above baseline.
4 Migration Architecture 40 / 100
NEAR runtime upgrades are coordinated via Foundation. Access-key system is pluggable.
Native NEAR accounts are AA-like: function-call access keys, full-access keys, key rotation fully supported. Best-in-class.
Nightshade 2.0 shipped smoothly. 5 years 100% uptime.
Access-key scheme could theoretically add PQC keys but no hybrid envelope architected.
5 Deployment Execution 2 / 100
No mainnet PQC traffic.
No announcements.
6 Supply Chain Vendor Readiness 5 / 100
7 Governance & Coordination 45 / 100
Estimated Nakamoto coefficient 8-12.
Foundation coordinates rapid upgrades. 5-year clean uptime.
NEAR Foundation (Switzerland).
No PQC adversarial precedent; chain never faced a crypto-break scenario.
The X + Y vs Z inequality
X (data shelf life): 5-10 (Ed25519 EOA-like)
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% | 10% |
| arrives slowly post migration | 80% | 75% |
| arrives slowly mid migration | 35% | 35% |
Peers in the L1 profile
Order-book view of the 9 chains closest to NEAR Protocol 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.
Minimal inventory, only Ed25519 + SHA-256 published.
NEAR runtime upgrades are coordinated via Foundation. Access-key system is pluggable.
Native NEAR accounts are AA-like: function-call access keys, full-access keys, key rotation fully supported. Best-in-class.
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
Native AA/access keys scored 18/25 on sub-score 4b — strongest migration architecture feature in batch alongside Polkadot. But Dim 5/6 voids dominate; chain is architecturally ready but operationally zero.
Scorecard metadata
- Profile: L1
- Scored: 2026-04-18 by
layerqu-v2-scoring-agent-4 - v1 reference:
chainscreen-v1-archive - QRI raw: 18 · after caps: 16
- Confidence interval: ±15
- PQC washing ratio: 1x
- Burn-vs-rescue: undeclared
Caps triggered
- Mosca (5a<20% → QRI max 60)
- Sutor (5d=0 → Migration Stage max 2)
- Preskill (Dim 5, Dim 6 <3 artifacts → ×0.5)
- Casado (4 tiles pqc=0 → migration_stage max 3)
- Hybrid gate FAIL → QRI cap 60