Compare the same protection object
A transaction signature authorizes a spend. A validator signature contributes to consensus. A key-encapsulation mechanism helps establish a communication secret. These roles cannot be combined into one quantum-readiness score. The table identifies documented signing scope, then records the boundary of the evidence available for this review.
Project documentation establishes what a team describes. It does not independently establish the software running across a network, the absence of vulnerabilities, or the safety of custody services. For a repeatable assessment, note the network name, software release, signature parameters, and evidence date. That makes a later documentation change distinguishable from a confirmed change in consensus rules.
Sources:Tidecoin official source repositoryEthereum Foundation post-quantum research program
Signing scope and evidence across seven networks
Rows are grouped by the subject being studied, without a performance or investment ranking. References to signing options and migration proposals retain their documented scope; no row asserts that every component of a network has completed a post-quantum transition.
| Network | Protection object | Documented signatures | Deployment or evidence boundary |
|---|---|---|---|
| QRL | Existing-network transaction authorization | XMSS | Legacy-chain documentation; successor activation unmeasured. |
| Abelian | Native authorization and privacy constructions | Lattice-based linkable ring signatures | Mainnet documented; advisory fixes do not establish operator upgrades. |
| Mochimo | Native transaction authorization | WOTS+ | White paper and signing code; no live-chain replay. |
| Tidecoin | Native transaction authorization | Legacy Falcon-512; conditional upgrade paths | Strict-mode and additional-scheme activation unverified. |
| Cellframe | Supported native-wallet transactions | Falcon, CRYSTALS-Dilithium, SPHINCS+ | Dated wallet notice; wrapped CELL follows host-chain rules. |
| Bitcoin | UTXO spending conditions | ECDSA and secp256k1 Schnorr | Classical signatures; BIP 360 remains Draft. |
| Ethereum | Accounts and validator consensus | EOA elliptic-curve signatures; validator BLS | Separate multi-layer migration work; completion not established. |
Sources:QRL one-time signature keysAbelian technical white paperOfficial ABEL mainnet documentationMochimo technical white paperTidecoin official source repositoryCellframe wallet signature announcementCellframe official FAQBIP 340: Schnorr signatures for secp256k1BIP 360: Pay-to-Merkle-RootEthereum validator key documentationEthereum Foundation post-quantum research program
Key lifecycle changes the operational comparison
QRL documents one-time indexes within an XMSS address. Mochimo describes progressing to a different spending key through transaction change. These are different ways of integrating one-time signatures into a usable asset system. Recovery and concurrent signing deserve attention alongside signature size.
Tidecoin and Cellframe illustrate another issue: a scheme name can cover specific versions or wallet choices. Record accepted parameters and fallback routes before treating two implementations as equivalent.
Sources:QRL one-time signature keysMochimo technical white paperTidecoin official source repositoryCellframe wallet signature announcement
Include implementation problems and remediation evidence
Abelian published ASA-2026-001 in October 2026, covering transaction-validation, wallet-output, RPC, and message-handling issues. The advisory identifies mitigated revisions while explaining that independent operators still need appropriate releases. That distinction belongs beside the cryptographic design.
Neither a mathematical proof nor a published fix establishes every live installation. A useful comparison records affected components, reviewed remediation, and remaining deployment uncertainty. It should also avoid inferring historical exploitation when the available evidence does not establish it.
Sources:Abelian ASA-2026-001
Read migration as a sequence of observable milestones
Bitcoin proposal status and Ethereum research milestones answer different questions from deployed transaction acceptance. Follow specification revisions, implementations, tests, audits, activation, and user adoption separately. A draft or demonstration is useful evidence at its own stage.
For a particular asset journey, also identify the network, wallet, bridge, and custodian. The linked profiles explain these boundaries in more detail. This comparison supplies a research map, without asserting a universally safest network or assigning a completion date.
Sources:BIP 360: Pay-to-Merkle-RootEthereum Foundation post-quantum research programCellframe official FAQ