Two names with an important boundary
Falcon is the signature construction submitted by its designers to the NIST process. FN-DSA is the name associated with its developing FIPS 206 standard. On the NIST standardization page checked for this entry, FIPS 206 remains in development, while FIPS 203, 204 and 205 are already published.
A network can deploy Falcon-based code before a final FN-DSA specification. That is a statement about that network’s implementation, not evidence of compliance with an unpublished final standard. Record the exact scheme name in use rather than replacing Falcon-512 with FN-DSA in a project description.
Sources:NIST PQC standardization process
Why the construction attracts interest
The designers build Falcon over NTRU lattices and use fast Fourier sampling. Their materials emphasize compact signatures as one design objective. The underlying construction and sampling procedure differ from the module-lattice approach used in Dilithium.
This is useful background for a protocol evaluating data overhead. It does not provide a universal performance verdict. The designers’ website reports measurements for a specified reference implementation and machine; those results are not measurements of a blockchain node, mobile wallet or hardware signing device.
Sampling is an implementation responsibility
The signer must produce values with the distribution required by the construction. A review should therefore examine the selected implementation’s numerical behavior, secret handling, randomness and side-channel defenses. These are engineering questions to investigate, not a finding that a particular library is vulnerable.
Our suggested evidence package includes the implementation revision, test-vector results, supported platforms and an independent review of sensitive signing code. A fast verification path does not remove the need to evaluate signing. Hardware restrictions also matter: a construction suitable for a desktop implementation may need different engineering on a constrained device.
What a chain’s Falcon claim should specify
For a digital-asset project, first identify the exact signature variant, accepted encodings and network rules. Then determine whether it is used for transaction authorization, consensus messages or another proof. A signature feature can be optional or limited to one component.
The next questions concern deployment evidence: which release introduced the rule, whether activation has occurred and which wallet paths use it. Source code containing a verifier does not alone show that live transactions are required to use it. CoinTalk’s Tidecoin and Cellframe profiles keep these questions separate from the algorithm’s NIST selection.
Sources:NIST PQC standardization process
How to compare without overclaiming
Keep standardization status, cryptographic parameters and operational evidence in separate columns. A useful size comparison states its encoding and exact parameter set. A useful speed comparison uses the same hardware, compiler and measurement procedure. Neither result is a complete security assessment.
This article has not checked a live chain’s activation state or audited a Falcon implementation. It provides a map for reading those claims. Revisit the linked NIST process page before publication or integration because the developing standard’s status can change.
Sources:NIST PQC standardization processFalcon designers: specification and reference code