Skip to content
—
QuantascanAlpha

The QRL → QRL 2.0 migration

How value is expected to move from QRL Legacy to QRL 2.0 — the snapshot, the on-chain XMSS claim, and what is and isn't public yet.

6 min readUpdated 2026-06-20

On this page▾

QRL is moving from QRL Legacy to its successor, QRL 2.0. A natural question for any holder is: what happens to my coins? This guide explains the announced migration model — and is careful to separate what has been stated publicly from what has actually shipped.

Status: This describes the announced model. The claim mechanism is not yet present in QRL's public source code, and QRL 2.0 is still a test network. Treat this as a roadmap, not a process you can use today. We will update it when the specification is published.

The model in three steps

Based on QRL's public statements, the migration is expected to work like this:

  1. Snapshot. At a cutover moment, balances on QRL Legacy are captured and used to seed QRL 2.0's genesis allocation — the chain's starting state.
  2. On-chain claim. A holder proves ownership by signing with their old XMSS wallet. That signature is verified on-chain, and the holdings are released. (This follows a QRL lead developer's June 2026 statement that "the XMSS signature will be verified on chain to release the holdings to a new ML-DSA-87 wallet.")
  3. Payout to a new wallet. The released value lands in a new ML-DSA-87 wallet on QRL 2.0 — a fresh, unrelated address.
Three-step migration flow: a snapshot seeds the QRL 2.0 genesis allocation, the holder proves ownership with an on-chain claim signed by their old XMSS wallet, and the value is paid out to a new, unrelated ML-DSA-87 wallet.1 · SnapshotLegacy balances → genesis2 · On-chain claimsign with old XMSS3 · New walletML-DSA-87 payoutThe new wallet is unrelated to the old address — the link is a recorded claim, not a computation.
The announced migration in three steps — snapshot, on-chain XMSS claim, payout to a new ML-DSA-87 wallet. The claim mechanism is not yet in public source.

What is and isn't public

It is important to be precise here, because details matter for anyone planning ahead:

  • The testnet genesis allocation does exist in QRL's source — a small, hard-coded set of starting balances used for testing.
  • The mainnet genesis allocation is still a placeholder in the code (a TODO awaiting the real snapshot data).
  • The on-chain claim/verification mechanism is not yet in the public source. There is no published claim transaction type or verification contract yet, which means it will arrive in a future client release in a form not yet specified.

In short: the direction is clear and stated by the developers; the exact mechanics are not yet published.

Old address ↔ new address is a claim, not a fact

Because the new QRL 2.0 wallet is generated independently, it is not derivable from your old QRL Legacy address. The two use different keys and different signature schemes. So any statement that "old address X corresponds to new address Y" is a claim that must be recorded — for example, by the on-chain claim above — and is never something you (or this explorer) can compute from the addresses alone.

This is why Quantascan keeps the two chains' identities separate by default. Where a verified link eventually exists, it will be shown as a claim; until then, each address is presented on its own chain.

What it means for supply charts

Migrated QRL appears on QRL 2.0 as a genesis allocation / claim, not as freshly mined or staked coins. So:

  • It should not be counted as organic new issuance (mining or staking rewards) on QRL 2.0.
  • Cross-chain supply views treat the migrated amount as a transfer of existing value between chains, not as new minting.

You can read more about issuance in QRL tokenomics and supply.

QRL Legacy doesn't disappear

A migration does not mean the old chain is deleted. QRL Legacy becomes a permanent, read-only archive: its blocks, transactions and balances stay fully browsable here. It is a predecessor that remains visible, not a network that is shut down.

Where to go next

FAQ about The QRL → QRL 2.0 migration

Common questions about this page
How does the QRL to QRL 2.0 migration work?
Per the announced model: QRL Legacy balances are captured in a snapshot that seeds QRL 2.0's genesis allocation, and holders claim their funds on QRL 2.0 by signing with their old XMSS wallet. The signature is verified on-chain and the holdings are released to a new ML-DSA-87 wallet. The exact claim mechanism is not yet public.
Will QRL Legacy be shut down after migration?
No. QRL Legacy becomes a permanent, read-only archive. Its history stays fully viewable on this explorer; it is a predecessor, not a network that gets switched off.
Is my new QRL 2.0 address linked to my old QRL address?
Only if a migration claim records that link. The two addresses are derived from different keys, so a connection between them is a claim, never something you can compute from the addresses.
Can I migrate today?
Not yet. The claim and snapshot specification has not been published in QRL's public source, and QRL 2.0 is still on its test network. This article describes the announced model, not a shipped, usable process.
← Back to Learn