1 Signature scheme 10/10, weighted 30%
Band 10: A post-quantum signature is the mandatory scheme for all accounts on mainnet.
Falcon-512 is the mandatory signature for every spend on Tidecoin mainnet. In the v0.18.3 release, CPubKey::Verify calls PQCLEAN_FALCON512_CLEAN_crypto_sign_verify and no other verifier, and pubkey.h fixes the public key at 897 bytes plus a prefix byte. The secp256k1 library is still vendored in the tree, but the signature check every script runs goes to Falcon-512. A mainnet transaction in block 2,784,867 confirms it: each of its 53 inputs carries an 898-byte key and a 655 to 663-byte signature.
source
2 Deployment stage 10/10, weighted 25%
Band 10: Tier 1: Native.
Tier 1: Native. Falcon-512 has protected every unit of supply since the genesis block of 27 December 2020, so there is no classical cohort to migrate and nothing a holder has to opt into.
source
3 NIST alignment 7/10, weighted 15%
Band 6 to 8: The scheme is NIST-selected but the standard is not yet final, or a NIST-approved scheme is named but not yet deployed.
Falcon was selected by NIST for standardisation as FN-DSA in FIPS 206, which was not final at the time of writing. Tidecoin's whitepaper says it runs vendored PQClean Falcon implementing the original round 3 specification, and that since genesis it has verified signatures in a legacy mode with a relaxed norm bound derived from the pre-2019 acceptance threshold. A strict mode using the standard bound, plus Falcon-1024 and FIPS 204 ML-DSA, is written into the 1.0 release candidates but gated on an upgrade with no mainnet height set.
source
Placement in the band A 7 rather than the 8 a deployed NIST selection would otherwise earn: what verifies on mainnet today is Falcon under a relaxed acceptance bound that Tidecoin itself describes as a legacy mode, rather than the scheme as specified. It is above a 6 because the scheme is the NIST selection, deployed and mandatory, not merely named.
4 Migration path 8/10, weighted 15%
Band 6 to 8: A credible published plan exists with a mechanism identified, but key parts are unbuilt or undated.
There is no classical legacy to migrate. What remains ahead is a scheme upgrade within post-quantum cryptography: the whitepaper bundles strict Falcon verification, Falcon-1024 and ML-DSA into the AuxPoW activation, keeps public keys unchanged between legacy and strict modes so wallets need no key migration, and in the mainnet chain parameters that activation is still set to disabled.
source
Placement in the band The top of the band rather than a 7, because no holder has a classical key to move. Not a 9: the move from the legacy Falcon mode to the strict one and to the further schemes is designed and coded but has no activation height on mainnet, and the releases carrying it are candidates rather than final releases.
5 Exposure 9/10, weighted 10%
Band 9 to 10: No quantum-vulnerable public keys are exposed on-chain, or the exposed keys protect nothing.
No Tidecoin public key is a quantum liability in the sense this dimension measures, because every spend has been signed with Falcon-512, whose security rests on lattice problems that Shor's algorithm does not address. Public keys are revealed when outputs are spent, as on Bitcoin, but a revealed Falcon-512 key gives a quantum adversary nothing to harvest.
source
Placement in the band Not a 10: the claim that a revealed key is no liability rests on a scheme that is not yet a final standard and that mainnet verifies under a relaxed legacy bound, so it is believed rather than settled. It is above an 8 because no classical key protects any Tidecoin output.
6 Verification 5/10, weighted 5%
Band 3 to 5: A post-quantum component exists, on mainnet, on a persistent testnet or as a merged implementation, but is unreviewed.
The Falcon-512 component is open source under the MIT licence and its use is checkable on-chain, where every input carries a Falcon-sized key and signature. We found no review of Tidecoin's integration by anyone outside its developers and no audit. The README says Tidecoin was discussed on NIST's pqc-forum mailing list, which we do not count as review of the implementation, and review of the upstream PQClean library does not count here either.
source
Placement in the band The top of the band rather than a 4: the component is live, mandatory, openly licensed and visible in every mainnet spend, so an outsider has everything needed to check it. It cannot reach 6 without public review or a named audit of Tidecoin's own code, which we did not find as of 23 October 2026.