Start with the network holding the asset

Cellframe describes a native network and a native CELL asset used within that ecosystem. Its FAQ separately identifies wrapped CELL on Ethereum and BSC. These representations may share a ticker, but the transaction rules that move them are not identical. Identifying the chain and representation is a necessary first step before evaluating a post-quantum claim.

A transfer of a wrapped token uses the host chain and token contract. A post-quantum feature on Cellframe does not automatically replace the host chain signing rules or remove bridge-related assumptions. This is why the profile concerns native Cellframe transactions separately from the broader set of markets and applications that may display the name CELL.

Sources:Cellframe official FAQ

Wallet signature choice is part of the protection scope

An official September 2025 wallet announcement says the interface displays the signature type selected when a wallet was created. It lists Falcon, CRYSTALS-Dilithium, and SPHINCS+ as recommended supported choices at that time. The important implication is that the wallet signing type is an explicit property, rather than something that should be inferred from the token symbol.

A precise assessment should name the wallet version, selected scheme, parameters, and node release accepting its transactions. The announcement supports a statement about documented options, but it is not an independent test of every available wallet build. This review has not created a wallet or submitted a transaction to confirm current network acceptance.

Sources:Cellframe wallet signature announcement

Treat migration notices as dated operational evidence

The same announcement discusses removing support for older signing types, including BLISS, Picnic, and Tesla, in a planned Node 6.0 release. It tells affected users to create a wallet using a supported type and transfer funds. That records a migration requirement described by the project; it does not establish the present release or activation state by itself.

For continuing coverage, track the actual release, acceptance rules, and consequences for older wallets. Do not assume that every deprecated algorithm has the same failure mode, or that an announcement proves all users have moved. A useful update explains who is affected, which implementation changed, what evidence supports the change, and which deployment details remain unverified.

Sources:Cellframe wallet signature announcement

Do not silently replace submission names with standard names

CRYSTALS-Dilithium and SPHINCS+ are names associated with the designs from which ML-DSA and SLH-DSA were standardized. A deployed implementation using an earlier name or parameter set is not automatically byte-for-byte compatible with the final standard. Falcon is selected for FN-DSA, while NIST still lists that standard as in development.

The right method is to inspect the implementation, parameter choices, test vectors, and release provenance before making a conformance claim. A family-level description can help readers navigate the options, but it cannot substitute for that work. This profile therefore retains the scheme names used in the dated wallet notice and does not present them as a certificate for Cellframe.

Sources:NIST PQC standardization statusCellframe wallet signature announcement

Native authorization is one part of an asset journey

Someone researching CELL may encounter an exchange, a wrapped representation, a bridge, a native wallet, and an application. A valid native post-quantum signature only addresses one part of that sequence. Contract administration, bridge custody or validation, software updates, recovery mechanisms, and the policies of a custodian introduce separate trust and implementation questions.

This review establishes the distinctions supported by the official FAQ and wallet announcement. It does not audit those services or observe current network behavior. A deeper profile should connect each representation to its network, locate current node and wallet releases, identify independent reviews, and record the precise protection scope. That is more informative than applying a single security label to every asset carrying the same ticker.

Sources:Cellframe official FAQCellframe white paper