Inventory first
Before migration, a team needs to know where cryptography exists and what it protects. Quantum Core answers that question from the source code, locally.
Post-quantum readiness
Map the cryptographic surface before migration becomes urgent.
Quantum Core is a local C++ scanner for wallets, exchanges, validators, custody systems, bridges and DeFi teams. It inventories the cryptography a codebase uses, separates what is broken today from what has to move before 2035, and produces a Cryptographic Bill of Materials.
Quantum Core is part of Functor. It shares Functor's engineering and its token, $FCTR. There is no separate Quantum Core coin, and none is planned.
Quantum Core field modelt = live
3329
H|ψ⟩ = λ|ψ⟩secp256k1 → migrationML-KEM / ML-DSAinventory ≠ audit
Localno upload
C++20scanner
v0.5.0released
Crypto does not need another quantum narrative. It needs a precise inventory of wallets, signatures, validator keys, bridge keys, custody flows and exchange secrets.
Crypto-native
The rules are written for wallets, exchanges, validators, bridges, custody and governance keys, not for generic application code.
Two scores
Defects that are broken today gate a build. The asymmetric surface that must migrate is reported separately and never fails one.
Broken today
MD5 and SHA-1, DES and RC4, ECB mode, predictable randomness, static IVs, disabled certificate verification, weak password hashing, hardcoded keys. Each is mapped to a CWE.
Migration surface
RSA, ECDSA, Ed25519, secp256k1, wallet keys, validator and bridge keys, custody flows. Deprecated in 2030 and disallowed in 2035 under NIST IR 8547.
Where it runs
A single C++20 binary with no dependencies. Command line, GitHub Actions or a pre-commit hook. Nothing is uploaded.
What it produces
Markdown for review, SARIF for the GitHub Security tab, JSON for automation, and a CycloneDX 1.6 Cryptography Bill of Materials for auditors.
Why Functor runs it.
The same problem
Functor is a layer-1 exchange. Its accounts, validators and bridge all rest on elliptic-curve signatures, which is exactly the surface that has to migrate.
Used on our own chain
Quantum Core scans the Functor codebase. The chain core currently reports a weakness score of 0 and one asymmetric site, the secp256k1 signature scheme planned for accounts.
Shared engineering
Both are written in C++ and Rust, are deterministic, and are tested the same way. Quantum Core's scanner ships with its own test suite, run on every change.
One token
Functor has one token, $FCTR. Quantum Core does not issue its own and will not.