Loopring was an early zkRollup DEX. It is now a stalled one, with a Groth16-over-BN254 prover that Shor breaks, development paused since 2023, a 2024 team wallet incident, and Binance delisting pressure. The scorecard floor is where projects without active governance end up, because no migration of any kind is coming.
Summary
Loopring is a zkRollup DEX in terminal decline. Uses Groth16 over BN254 (pairing-based, Shor-breakable). Development effectively stalled since 2023. Binance delisting 2024+ reduced ecosystem support. Project lacks active coordination for any migration — crypto or otherwise. Band 1 Unaware. Failing/abandoned project — very low confidence.
What the gates say
- Hybrid: FAIL. No hybrid plan on file.
- Evidence: FAIL. Reconstruction gap on at least one sub-score.
- 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 22 / 100
zkRollup using Groth16. BN254 pairing curve.
ECDSA secp256k1 (inherited from Ethereum) · Groth16 SNARK over BN254 (pairing-based) · EdDSA (internal account signatures) · Keccak-256No PQC families deployed
No NIST PQC primitives deployed
2 HNDL Exposure 8 / 100
Project in terminal decline — user funds mostly withdrawn. Limited absolute HNDL surface.
Active since 2020. Cold-key EdDSA keys persist for dormant accounts.
Groth16 proofs are Shor-breakable. Historical order books persistently exposed.
Standard TLS. No PQC KEM.
3 Metadata & Privacy Exposure 22 / 100
zkRollup aggregation provides modest mempool privacy but on-chain state is transparent.
Centralized Loopring-operated sequencer. Declining infrastructure.
ETH<->Loopring bridge usage visible.
Historical DEX order patterns + trader identities could retroactively deanon under Shor.
4 Migration Architecture 15 / 100
Groth16 requires trusted-setup ceremony for any circuit change. Team has deprioritized protocol development.
Loopring Smart Wallet (pioneer in smart-contract wallets) offers key rotation at contract layer. But team-controlled.
V1 through V4 protocol evolution up to ~2023. Stalled since.
No hybrid PQC plan. Project no longer actively developed.
5 Deployment Execution 0 / 100
no public artifact found
no public artifact found
no public artifact found
no public artifact found
No PQC announcements.
6 Supply Chain Vendor Readiness 2 / 100
Binance delisting has reduced vendor integration.
7 Governance & Coordination 10 / 100
Centralized Loopring team sequencer.
Development effectively stalled. No recent upgrades.
Daniel Wang (founder) — reduced active presence. No named PQC lead.
Team hack in 2024 (GameStop-related wallet issue). Weak response.
The X + Y vs Z inequality
X (data shelf life): 5-10 (declining — many users have withdrawn)
Y (migration time): 15+ (project effectively abandoned)
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 | 50% | 40% |
| arrives slowly mid migration | 15% | 15% |
Peers in the rollup-L2 profile
Order-book view of the 9 chains closest to Loopring 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.
zkRollup using Groth16. BN254 pairing curve.
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
Loopring is scored at the floor because the project lacks active governance to execute any migration. Historical technical merit (early zkRollup) is offset by present-day stall. Evidence gate fails due to sparse/stale public documentation.
Scorecard metadata
- Profile: rollup-L2
- Scored: 2026-04-18 by
layerqu-v2-scoring-agent-3 - v1 reference:
chainscreen-v1-archive - QRI raw: 6 · after caps: 6
- 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 (most dims <3 artifacts × 0.5)
- Casado (4 vendor tiles pqc=0 → migration_stage max 3)
- Hybrid gate FAIL → QRI cap 60