Technology
Hybrid architecture: post-quantum signatures (PQC) + efficient ZK verification (Groth16) + full EVM compatibility.
Dilithium / Falcon
What they are, why they’re used today, and how QRYPTA integrates them.
Groth16
Why we chose Groth16 on ETH and BNB: tiny proofs and low-cost verification.
BNB Chain + Ethereum
Why we deployed on both networks and why this positions us as pioneers.
Dilithium and Falcon
Dilithium and Falcon are post-quantum signature schemes designed to remain secure even against practical quantum computers. They matter today because the industry is already migrating from classical signatures (ECDSA) toward quantum-resistant alternatives—especially for infrastructure expected to last decades.
What is Dilithium?
A lattice-based signature. It’s robust, comparatively straightforward to implement, and well-suited for bank-grade deployments where conservative security is preferred.
What is Falcon?
Also lattice-based, often with smaller signatures. Great for bandwidth reduction, but more delicate to implement—making it ideal as an advanced option.
Which do we use in QRYPTA and why?
QRYPTA supports both Dilithium and Falcon, with Dilithium recommended as the default for production (conservative security and stability), while Falcon remains an optional/upgrade path where signature size is critical. In our architecture, the PQC signature is produced off-chain and verified on-chain through a ZK proof—preserving EVM compatibility without sacrificing post-quantum resistance.
Groth16: why we chose it
Groth16 is a ZK proof system (SNARK) known for tiny proofs and efficient verification on EVM. For a token that needs on-chain verification without massive gas costs, Groth16 is a practical, mature choice.
Small proofs
Great for mainnet: fewer bytes, less gas, better UX.
Efficient verification
Integrates well with EVM thanks to pairing precompiles.
Same standard on ETH and BNB
One cryptographic path, same security invariants.
How does it fit with PQC signing?
Key idea: we avoid heavy PQC verification directly in Solidity. Instead, the wallet produces the PQC signature and a ZK proof that attests validity (plus anti-replay parameters like nonce/deadline). The contract verifies the proof and executes the transfer—strong security with controlled costs.
Why BNB Chain and Ethereum
We chose ETH for credibility, liquidity, and institutional/developer ecosystem. We chose BNB for gas efficiency, speed, and massive retail reach. Both are EVM, enabling a consistent and auditable experience across two major markets.
Why does this make us pioneers?
Because we’re bringing an on-chain verifiable PQC + ZK transfer flow to mainnet on two major networks, with ISO 20022-style references for traceability. It’s not a one-off demo—it’s a transfer pattern that scales to compliance, auditing, and enterprise reconciliation.
Ethereum’s post-quantum migration
In January 2026, Vitalik Buterin again pushed for Ethereum to prepare sooner rather than later for quantum resistance, arguing long-term cryptographic safety should be a design goal and a point of pride.