The documented baseline is Falcon-512 transaction signing

Tidecoin is an independently maintained cryptocurrency derived from the Bitcoin codebase. Its official materials describe using Falcon-512 instead of the conventional elliptic-curve signature system for native transactions. That is a claim about Tidecoin rules, not evidence that Bitcoin itself has adopted Falcon or that a token on another network inherits the same properties.

Falcon is a lattice-based signature design with different implementation requirements from hash-based stateful systems. For this profile, the important questions are the precise signature encoding, accepted verification rules, and software version. General statements such as post-quantum from genesis do not establish the status of every later networking, wallet, or consensus feature.

Sources:Tidecoin official source repositoryTidecoin Falcon implementation notes

Legacy and strict verification describe different acceptance rules

The project Falcon page distinguishes a legacy mode from a stricter mode associated with an AuxPoW transition. It describes different verification bounds and compatibility requirements. These distinctions matter because the name Falcon-512 alone does not capture every rule a blockchain node uses to accept a historical or newly created signature.

The page labels one mode current and another upcoming, but a dated web statement is not a live activation check. A reviewer should identify the relevant consensus condition, release, and network height before claiming a transition has happened. This article does not independently establish which mode a transaction submitted to the live network would encounter today.

Sources:Tidecoin Falcon implementation notesTidecoin official source repository

Falcon deployment is different from final FN-DSA adoption

NIST selected Falcon for a future signature standard and currently lists FIPS 206 as in development. The finalized 2024 standards were ML-KEM, ML-DSA, and SLH-DSA. Consequently, a statement that Falcon-512 became a finalized NIST standard in 2024 should not be used to characterize Tidecoin.

The project repository identifies its Falcon implementation as a pinned PQClean version of the Round 3 specification. A future FN-DSA standard can introduce differences that matter for signing, verification, and interoperability. Existing use of Falcon does not automatically demonstrate conformance with that future document, and algorithm selection is not validation of a wallet, node binary, or whole cryptocurrency.

Sources:NIST PQC standardization statusTidecoin official source repository

Separate additional signatures from transport key establishment

Current repository documentation describes height-gated paths involving additional Falcon parameters and ML-DSA. It also describes ML-KEM for opportunistic peer transport encryption. These are different kinds of protection: a transaction signature authorizes a spend, while a key-encapsulation mechanism helps establish a secret for communication.

Code, tests, and a documented activation mechanism are valuable development evidence. They do not prove that a feature is mandatory, currently enabled, or used by all peers. An upgrade record should identify the trigger, release, observed activation, and fallback behavior. In particular, adding ML-KEM transport does not convert a legacy signature into ML-DSA or resolve every exposure elsewhere in the protocol.

Sources:Tidecoin official source repositoryNIST PQC standardization status

A deployment claim needs a release and a network observation

This review has not run a Tidecoin node, replayed its chain, confirmed current height, or audited side-channel resistance. The repository reports a historical replay result, but explicitly distinguishes that result from a live height. Likewise, project statements about the absence of incidents are statements by the project, rather than proof that no incident has ever occurred.

A stronger follow-up would pin a release and source revision, inspect activation rules, then record the live network and accepted transaction behavior. It would also examine wallet key derivation, recovery, signing implementation, and relevant independent audits. Until that evidence is collected, use documented signing and conditional upgrade descriptions instead of a single completed-migration badge.

Sources:Tidecoin official source repositoryTidecoin Falcon implementation notes