KVANTA5 is the world's first SHA-256
proof-of-work settlement chain secured by NIST FIPS 204 ML-DSA-87
quantum-resistant signatures from Genesis. Every transfer is protected
at Security Level 5 — with 6-minute finality.
Whether you are moving funds for the first time
or the thousandth, the process is the same — straightforward on the
surface, rigorously secured at every layer below it.
01
Create Address
Generate your quantum-resistant KV5 wallet address. No central authority. Your keys, your funds.
02
Initiate Transfer
Enter the recipient address and amount. Set your fee priority. Review and confirm.
03
Network Validates
Your transaction enters the mempool. Miners confirm it in the next block — typically under 60 seconds.
04
Settled in 6 min
After 6 block confirmations, your transfer is irreversibly settled. Track it in real time.
02 // Why KVANTA5
The architecture of permanence
Three battle-tested technologies. One unified
settlement layer. No novel cryptographic assumptions. No experiment.
Just proven components, precisely assembled.
LAYER 01
⬡
SHA-256 Proof of Work
The
same consensus mechanism that has secured trillions in value since
2009. ASIC-compatible, commodity-classified, and battle-hardened against
all known attacks.
LAYER 02
🔐
ML-DSA-87 Signatures
Every
transaction is signed with NIST FIPS 204 Level 5 quantum-resistant
cryptography from the very first block. Not added later — built in from
genesis. Future-proof by design.
LAYER 03
⚡
DGW Style DAA
Adaptive
difficulty recalibrates every block using a 24 block window with a
±300% per-block cap. Block times remain stable under extreme hashrate
fluctuations.
ASSURANCE
○
Fixed Supply Cap
231,000,000
KV5, hard-capped at the protocol level. No inflation, no discretionary
issuance. Full supply schedule documented in the Technical Prospectus.
Against Quantum Attacks
Protected
From block #0 — not patched in later
Settlement Speed vs Bitcoin
10× Faster
6 min vs 60 min average
Total Supply
231,000,000
KV5 — permanently hard-capped
Attack Neutralization
5 blocks
~5 minutes to isolate bad actors
KV5-ECON-001 · REV 1.0 · PUBLIC DATA
For exchanges, researchers & comparative analysis
Settlement Cost Under Quantum Security
Post-quantum signatures carry real overhead —
roughly 67× the payload of ECDSA, per input. Measured against that
cost, KVANTA5 still settles value at a fraction of legacy proof-of-work
chain fees.
STATUS · LIVE MAINNET DATASIGNATURE · ML-DSA-87COMPARED AGAINST · BTC / BCH
—
Cheaper vs Bitcoin
—
Cheaper vs Bitcoin Cash
—
Live KV5 Transfer Cost
67×
Signature Payload vs ECDSA
01 — Per-Transaction Cost
Live Cost, Same Transfer Pattern
Live node fee rates applied to anonymous,
representative single-input/single-output transaction sizes: 110 vB for
Bitcoin, 191 bytes for Bitcoin Cash, and 7,321 vB for KVANTA5.
AWAITING LIVE FEED
BitcoinAwaiting node estimate
$0.19avg / median tx
Bitcoin CashAwaiting node estimate
$0.0046average tx fee
KVANTA5Awaiting node estimate
$0.0000037block #77,020 avg
Bar lengths use a balanced 0.40 power scale
across the current Bitcoin, Bitcoin Cash, and KVANTA5 reference-transfer
costs. Bitcoin is normalized to 100%; smaller values remain visually
distinguishable without the heavy compression of a logarithmic chart.
Extremely small positive values retain a 2.5% minimum visibility marker.
Values refresh once per minute from a same-origin static JSON feed
generated on infra1. The feed publishes no wallet addresses, transaction
IDs, amounts, or other wallet-linked data.
Chain
Fee Basis
Live Rate
Reference Size
Estimated Cost
Bitcoin
Awaiting feed
—
110 vB
—
Bitcoin Cash
Awaiting feed
—
191 bytes
—
KVANTA5
Awaiting feed
—
7,321 vB
—
BTC
and BCH use the local infra1 nodes' current fee estimates or policy
floors. KVANTA5 uses its smart estimate when available, otherwise the
median of recent confirmed non-coinbase fee rates when enough samples
exist, otherwise the active policy floor.
02 — Network-Scale Efficiency
Lifetime Value Moved vs. Fees Paid
LIVE $0.002255 / KV5
A different dimension from per-transaction
cost: how cheaply the chain has moved real economic value over its
entire operating history.
Fee share of value moved is price-independent — still 0.0000405%
03 — Why This Is Notable
Cheap Despite the Overhead, Not Because of a Shortcut
KVANTA5 does not achieve these numbers with a
lighter security model — it carries substantially more cryptographic
weight per transaction than the chains it's being compared against.
~7,219 bytes
per signed input (ML-DSA-87) vs ~108 bytes for ECDSA — a ~67× larger payload, per the KV5 Infrastructure Requirements spec.
1–5 ms
signing cost per transaction — roughly 10–100×
heavier than ECDSA chains, per the same spec — yet still transacting at a
fraction of their fees.
04 — UTXO Consolidation
Many Signatures, Still Negligible Cost
Block #77,190 — a 124-input mining wallet
consolidation into 2 outputs. Every one of those 124 inputs carries its
own full ML-DSA-87 signature (~7,219 bytes each), yet the total fee
remains a fraction of a cent.
Metric
Value
Notes
Inputs consolidated
124
Each independently signed with ML-DSA-87
Outputs
2
Total output 6,250 KV5
Total fee paid
0.0233 KV5
≈ $0.000129 at $0.005517 / KV5
Fee per signed input
~0.000188 KV5
≈ $0.00000104 per ML-DSA-87 signature
Transaction size
905,862 bytes
Weight 3,623,448 wu — driven almost entirely by the 124 post-quantum signatures
Total fee at $5.00 / KV5
≈ $0.1165
Still ~12 cents to consolidate 124 ML-DSA-87-signed inputs
A
comparable 124-input consolidation on an ECDSA chain would carry
roughly 1/67th the signature payload per input — yet KVANTA5 still
clears the whole batch for around a tenth of a cent, underscoring that
the fee-efficiency numbers above hold even under heavy, real-world
wallet-management load, not just simple 1-in/2-out transfers.
Documentation
Understanding KVANTA5
Everything you need to know — clearly explained
Technical Specification
Chain Parameters
Parameter
Value
Notes
Ticker
KV5
Native settlement coin
Total Supply
231,000,000 KV5
Hard cap — no inflation
Consensus
SHA-256 PoW
Bitcoin-equivalent work function
Block Time
60 seconds
Target — enforced by DGW DAA
Confirmations for Finality
6 blocks
~6 minutes to settled
Signature Scheme
ML-DSA-87
NIST FIPS 204 — Dilithium
Security Level
Level 5
AES-256 equivalent — highest tier
Output Type
Native P2QR
FIPS 204 Level 5 Quantum Resistance
DAA Algorithm
Dark Gravity Wave 4/4
24-block history window
Difficulty Cap
±300% per block
Prevents manipulation
Legal Classification
Commodity
No staking, no yield
Common Questions
Frequently Asked
KVANTA5 is a
post-quantum settlement chain — a network designed specifically for
moving value securely and permanently. Unlike most blockchains, every
single transaction on KVANTA5 has been protected by quantum-resistant
cryptography since block #0. This means that even a quantum computer
cannot compromise a transfer made on KVANTA5.
A transfer is
considered final after 6 block confirmations. Since each block is mined
approximately every 60 seconds, settlement typically takes 5–7 minutes
from the moment you send. You can watch the progress in real time on the
Track page.
Traditional digital
signatures rely on mathematical problems that a quantum computer could
solve quickly. ML-DSA-87 is based on lattice cryptography — a
mathematical structure that remains secure even against quantum attacks.
NIST formally standardised this algorithm in FIPS 204 at Security Level
5, the highest tier available.
No. Once a transfer
reaches 6 confirmations, it is permanently recorded on the KVANTA5
blockchain and cannot be reversed by anyone. Please verify the recipient
address carefully before confirming.
The network fee
compensates miners who include your transaction in a block. On KVANTA5,
fees are very small — typically 0.005 to 0.050 KV5. Unlike traditional
wire transfers, there is no intermediary taking a percentage of your
transfer amount.
KVANTA5 (KV5) is
classified as a commodity under proof-of-work legislation. It carries no
staking yield. Users are responsible for their own tax and regulatory
obligations in their jurisdiction.
A KV5 wallet address
is generated from your private key using the ML-DSA-87 key derivation
process. You can create a wallet using the KVANTA5 Core desktop client.
Never share your private key with anyone.
KVANTA5 addresses
include a checksum that catches most typos. However, if you send to a
valid but unintended address, the funds are permanently gone. Always
copy and paste addresses and confirm the first and last 4 characters
before confirming.
Support
Need Assistance?
Our settlement specialists are available to
assist qualified clients with onboarding, large transfers, and technical
integration.
For node operators, pool operators, miners & infrastructure partners
Infrastructure Requirements
KVANTA5 was built to move large value at high
throughput with post-quantum signatures — not to run comfortably on a
leftover box. This is what real participation actually costs in compute,
memory, storage, and bandwidth, and why.
STATUS · ACTIVE — MAINNETAUDIENCE · OPERATORS / MINERS / POOLSSIGNATURE · ML-DSA-87
Block Interval
60s
fixed target
Max Block Size
32 MB
vs ~1 MB, comparable PoW chains
Signature Scheme
ML-DSA-87
Dilithium · FIPS 204 Level 5
Signing Cost / TX
1–5ms
≈10–100× heavier than ECDSA chains
01 — THE CLOCK
The 60-Second Budget
Every block has sixty seconds to be built,
fragmented, encrypted, transmitted, reassembled, validated, and
rebroadcast network-wide before the next one is due. This is the
constraint everything else here is sized against.
Block propagation cycle, single hop
window: 60.0s target · margin matters more than average case
FRAGMENT
ENCRYPT ×5
TRANSMIT
REASSEMBLE
VALIDATE
REBROADCAST
01
Sender splits the assembled block into 5 chunks
02
Each chunk is encrypted independently
03
All 5 encrypted chunks transmit to each peer
04
Receiver decrypts and reassembles into one block
05
Full ML-DSA-87 signature validation, every input
06
Validated block relays onward to the next peer set
Bitcoin-class chains broadcast a block as a single message and
validate with ECDSA at sub-millisecond cost per signature. KVANTA5 does
five times the message handling per hop and roughly 10–100× the per-signature compute at up to 32× the payload size. None of those multipliers are optional, and none of them shrink the clock.
02 — COMPARISON
Why This Isn't Bitcoin-Class Hardware
Three design decisions compound against each
other. Each one alone would be manageable. Together, they define a
different class of machine.
Factor
Bitcoin-class PoW chain
KVANTA5
Max block size
~1–4 MB effective
32 MB
Block interval
600s (10 min)
60s
Signature scheme
ECDSA (secp256k1)
ML-DSA-87 (Dilithium, FIPS 204 L5)
Sign time, single input
~0.05–0.30 ms
~1–5 ms
Bytes per signed input
~108 bytes
~7,219 bytes (≈67×)
Block transmission
single message
5-chunk fragment / encrypt / reassemble
Third-party software
Bitcoin forks generally work
must be purpose-built for KV5
03 — DEPLOYMENT
Infrastructure Tiers
Not every role on the network carries the same
load. A wallet checking a balance and a relay node propagating max-size
blocks to forty peers are not the same hardware problem. Pick the tier
that matches what you're actually running.
This tier is in the direct path of "did the
block reach the network in time." No shared-tenant virtualization, no
exceptions. Dedicated, bare-metal-class hardware only.
CPU
1× minimum, 2× preferred — 12+ core, AMD preferred, large L1/L2/L3 cache. 2nd-gen EPYC as a starting baseline.
Memory
32 GB DDR4 minimum. Required for signature verification handling and batch transaction signing under load.
Storage
1 TB SSD minimum. Multi-TB RAID arrays preferred, and required by month 6 of operation.
Network
1 Gbps+ low-latency fiber minimum, 10 Gbps+ preferred. Burst-shaped or contended bandwidth is disqualifying.
Hosting class
Dedicated
/ bare-metal only. No shared-core cloud VMs — CPU steal and
noisy-neighbor jitter directly threatens the propagation window.
Why it matters here
This
tier absorbs the full fragment / encrypt / transmit / reassemble /
validate / rebroadcast cycle on every block, on every peer connection,
with no slack in the clock.
Full relay node
Pool block-template source
Network seeders
RPC + ZMQ (internal only)
Heavy, sustained compute — but with slightly
more tolerance for jitter than the propagation-critical path. Still
dedicated CPU. Storage and network can flex with scale.
CPU
Dedicated cores required — high single-thread performance matters for CKpool share validation; multi-core matters for indexing.
Memory
32 GB+ recommended. RocksDB block-cache performance scales directly with available RAM for range queries and pagination.
Storage
NVMe,
SSD sized to chain growth — a single fanout transaction can add
hundreds of thousands of index entries. Plan growth in months, not
years.
Network
Stable, low-latency connection to the Tier 1 node — private network strongly preferred over public RPC exposure.
Hosting class
Dedicated-vCPU cloud acceptable; bare-metal preferred at scale.
Why it matters here
Mining pool payout batching must account for ML-DSA-87 signature weight directly — naive batch sizes produce unminable blocks.
CKpool (solo / PPLNS)
RocksDB chain indexer
Exchange / custodial nodes
P2QR multisig vault infrastructure
Read-heavy, cacheable, and not on a 60-second clock. This is where general-purpose hosting is genuinely fine.
CPU
2–4 vCPU, shared-tenant acceptable for low-to-moderate traffic.
Memory
4–8 GB typical, more if serving high explorer traffic with large result sets.
Storage
Standard SSD — this tier holds no chain data of its own; it queries Tier 2 via API.
Network
Standard hosting bandwidth, CDN-fronted for public traffic where possible.
Hosting class
Any reputable VPS or static/edge hosting. This is the one tier where a low-cost box is a legitimate choice, not a compromise.
Why it matters here
Isolating this tier means a traffic spike on the public explorer can never threaten block propagation or pool reliability.
Block explorer UI
Pool front-end (miner dashboard)
Wallet interfaces
Light / SPV clients
04 — STORAGE ENGINE
RocksDB, Mandated
This is not a recommendation among several
reasonable options. It is a requirement for any indexer, explorer
backend, or chainstate implementation built against KVANTA5.
Why RocksDB
Built for exactly this problem
RocksDB was built at Facebook because
no existing database was fast enough to handle their content at scale —
they designed and built their own rather than force-fit one that wasn't
built for the job. KV5's indexing load is the same kind of problem:
high-volume, high-throughput, write-heavy at a scale general-purpose
databases weren't designed for.
Ruled Out
BerkeleyDB, SQLite, and similar
Tested directly against KV5's actual
load — fanout transactions with hundreds of thousands of outputs, 30MB+
blocks landing every 60 seconds. Nowhere near fast enough. This isn't a
theoretical concern; it's a result.
Engine
Status for KV5
Notes
RocksDB
Mandated
Required for indexers, explorers, and the planned wallet/chainstate migration.
BerkeleyDB
Ruled out
Tested. Throughput insufficient for KV5 block/transaction volume.
SQLite
Ruled out
Tested. Write throughput insufficient at fanout-transaction scale.
Generic relational (Postgres/MySQL)
Not evaluated for this role
Not the target use case — column-family key/value access pattern fits RocksDB, not row-oriented relational storage.
Looking ahead, RocksDB is also the planned
target for KV5 wallet storage and node chainstate, not just third-party
indexing. Any infrastructure built on a different engine today should
plan for that migration path rather than treating the current
architecture as a permanent branch point.
05 — KNOWN FAILURE MODES
What Will Not Work
Specific mistakes we expect operators to make, because they're the same mistakes Bitcoin-class assumptions naturally lead to.
Failure Mode
Forking Bitcoin-derivative software
Explorers, wallets, and pool software
built by forking Bitcoin-ish codebases will not handle 32 MB blocks,
ML-DSA-87 signatures, or P2QR script types correctly. Third-party
software must be purpose-built for KV5.
Failure Mode
Sizing for empty blocks
A low-end box will run fine while
traffic is light. That is not the same thing as production
infrastructure. Size for the network doing its actual job, not for the
demo.
Failure Mode
Shared-core cloud VMs for Tier 1
CPU steal and bandwidth contention on
shared-tenant virtualization directly threaten the 60-second propagation
window. This is disqualifying for relay nodes and pool block sources,
not a matter of preference.
Failure Mode
Naive payout batching
KVANTA5 can support very large P2QR
fanout transactions, but payout software cannot assume Bitcoin-sized
spends later. P2QR outputs are compact to create; spending them requires
ML-DSA-87 authorization data. Pools, exchanges, and custodians must
size fees, consolidation windows, and block-policy behavior against
KV5’s P2QR spend model, not legacy ECDSA input assumptions
06 — QUICK REFERENCE
Find Your Role
A quick reference for which tier applies to what you're actually planning to run.
Runs the network
Relay node operator
Validates and propagates blocks to peers. Directly in the
path of the 60-second budget. The fragment/encrypt/reassemble cycle runs
on every connection.
Required: Tier 1
Serves miners
Pool operator
Block template sourcing sits at Tier 1. CKpool itself, share
validation, and payout batching sit at Tier 2. Most pool operators need
both.
Required: Tier 1 + Tier 2
Serves users
Explorer / indexer operator
The indexer doing RocksDB writes on every block is Tier 2. The public-facing explorer UI querying that indexer is Tier 3.
Required: Tier 2 + Tier 3
Holds custody
Exchange / custodial operator
Full validation, multisig vault infrastructure, and
high-reliability uptime expectations. No tolerance for the shortcuts a
hobby node can take.
Required: Tier 1 + Tier 2
Mines
Solo / pool miner
Mining hardware itself isn't covered here — but if you're
solo mining with your own node rather than pointing at a pool, that node
is Tier 1.
Solo: Tier 1 · Pooled: no node required
Holds coins
Wallet user
Light and SPV wallet usage is Tier 3 — any reasonable
consumer device or basic hosting. This is the one role this document is
not trying to scare off.
The institutional-grade quantum-resistant settlement chain
KVANTA5 is a live SHA-256 proof-of-work
blockchain engineered for post-quantum settlement from genesis. Its
native P2QR output system uses ML-DSA-87 spend authorization,
eliminating ECDSA exposure from the transaction path while preserving
wrapped P2SH compatibility for pool and exchange infrastructure. With
60-second target blocks, KVANTA5 is designed for rapid probabilistic
settlement: six confirmations target approximately six minutes, and
confidence deepens with every additional block of accumulated
proof-of-work. KV5 has a fixed 231,000,000 coin supply, consisting of a
transparent 21,000,000 KV5 Block #1 Development Fund allocation with
Network Consensus scheduled and controlled unlock and 210,000,000 KV5
distributed to the public through proof-of-work mining.
Ticker
KV5
Total Supply
231,000,000 KV5
PQ Security
NIST Level 5
Block Time
60 Seconds
Consensus
SHA-256 PoW
Status
Mainnet Live
00 // KEY PERFORMANCE INDICATORS
At A Glance
Settlement Finality
~6
minutes — 6 confirmations
Security Level
5
NIST FIPS 204 — AES-256 eq.
Total Supply
231M
KV5 — hard cap
Staking
0%
proof-of-work only
Attack Neutralization
5
blocks — ~5 minutes
DAA Response
±300%
per block cap
vs Bitcoin Settlement
10×
faster confirmation
Legal Classification
Commodity
PoW — no staking yield
01 // ARCHITECTURE
Technical Foundation
KVANTA5 is built on battle-tested components:
Bitcoin's SHA-256 proof-of-work, the Dark Gravity Wave difficulty
algorithm proven on live networks since 2014, and the ML-DSA-87 P2QR
quantum-resistant signature primitive — assembled into a single
institutional-grade settlement chain. No novel consensus mechanism. No
unproven cryptographic assumptions at the chain layer. Proven
components, new combination.
⛏ Consensus Layer
AlgorithmSHA-256 Proof of Work
Block time target60 seconds
DAADGW-style per-block adjustment
DAA window24-block history
Adjustment cadenceEvery block
Design goalResponsive hashrate tracking
ASIC compatibleYes — standard SHA-256 hardware
🔐 Signature Layer
SchemeML-DSA-87 (Dilithium)
StandardNIST FIPS 204
Security levelLevel 5 — AES-256 equivalent
Output typeNative P2QR
Signature size4,627 bytes per input
Public key size2,592 bytes
PQ fromBlock #1
⚡ Settlement Layer
Target block time60 seconds
6 confirmations~6 minutes
vs Bitcoin10× faster
vs Ethereum PoSComparable
Finality modelProbabilistic PoW
Legal classCommodity
Staking yieldNone — no securities risk
🛡 Attack Profile
Attack neutralized in5 blocks (~5 min)
Max extraction~250 KV5 per attack
Recovery min1–4 blocks
Recovery max~24 blocks
Strip-mine epochsNone — no epoch boundaries
Testnet validatedMay 30, 2026
Attack tested1 PH/s vs 8 TH/s
Why three proven components: KVANTA5 deliberately
avoids experimental consensus design. Its foundation combines
established proof-of-work, a production-tested difficulty adjustment
approach, and a custom quantum-resistant transaction-output layer built
specifically for this chain.
The consensus foundation is SHA-256 proof-of-work, the same mining
primitive that has secured Bitcoin since 2009. Difficulty adjustment
uses a DGW-style per-block mechanism, derived from an approach that has
operated in production networks since 2014. The signature foundation is
ML-DSA-87, implemented from the CRYSTALS / ML-DSA reference lineage. The
cryptography is standardized; the custom engineering is KVANTA5’s P2QR
output scheme, address handling, wallet integration, script
classification, relay policy, mining policy, and validation path.
Native P2QR outputs use KVANTA5’s consensus-defined marker:
`OP_KVANTA5_P2QR <32-byte program>`
At the script byte level, `OP_KVANTA5_P2QR` is KVANTA5’s named use of
opcode `0x50`, historically `OP_RESERVED` in Bitcoin script. Native P2QR
outputs are classified as `TxoutType::KVANTA5_P2QR` and validated under
the explicit `SCRIPT_VERIFY_KVANTA5_P2QR` flag. This gives KVANTA5 a
native quantum-resistant output class rather than a convention layered
on top of legacy ECDSA templates.
The integration has already been demonstrated on mainnet under live
SHA-256 proof-of-work. Block #21797 created a P2QR fanout transaction
with 4,001 P2QR outputs totaling 179,536 bytes. Block #21798 then
consolidated 4,000 P2QR inputs in a single 29,072,055-byte transaction,
averaging approximately 7,268 bytes per input. A separate 2-input
transaction of 14,632 bytes independently confirmed the same per-input
sizing behavior at a radically different scale, averaging approximately
7,253 bytes per input.
KVANTA5 also completed a large-scale architectural demonstration on
mainnet. Block #24521, mined June 19, 2026, included a single
transaction creating 715,001 P2QR outputs inside a 29.34 MB block,
approaching KVANTA5’s 32 MB maximum serialized block size. This was not a
simulated benchmark or private test harness; it was a live
proof-of-work block demonstrating the chain’s ability to support extreme
P2QR output fanout within the configured block-size envelope.
KVANTA5’s test coverage includes a complete sighash mutation harness,
validating that transaction-critical mutations invalidate the signature
commitment as expected. For institutional due diligence, the separation
is clear: SHA-256 proof-of-work is inherited, DGW-style adjustment is
production-tested, ML-DSA-87 is standardized, and P2QR is the
KVANTA5-native transaction-output and validation layer proven through
live mainnet operation.
02 // QUANTUM SECURITY
Level 5 Protection
KVANTA5 addresses both quantum attack surfaces
that existing proposals leave partially or fully unresolved. No ECDSA
key exists anywhere in the signing path — not at broadcast, not
historically, not retroactively.
✓ Short Exposure — Eliminated
The mempool attack window:
when a transaction is broadcast, the ECDSA public key is visible for
approximately 9 minutes before confirmation. Google estimates a CRQC can
break ECDSA in under 9 minutes. P2QR has no ECDSA key to harvest from
the mempool.
✓ Long Exposure — Eliminated
Any address that has made
an outgoing transaction has its public key permanently on-chain. A CRQC
can retroactively derive the private key. KVANTA5 has no ECDSA history —
every coin mined, every transaction confirmed, uses ML-DSA-87
exclusively.
→ BIP-360 Comparison
Bitcoin's BIP-360 partially
mitigates short exposure by hiding keys in tapscript leaves. It does
not address long exposure attacks against historically exposed keys.
KVANTA5's P2QR eliminates both surfaces by removing ECDSA from the
protocol entirely.
Max block P2QR outputs715,001 outputs — mainnet block #24521, June 19, 2026
Block size with 715K outputs29.34 MB — single transaction, under live PoW
Mainnet validation4,000-input consolidation (29MB) · 4,001-output fanout · 715,001-output transaction in 29.34M B block — June 18–19, 2026
Verification ledgerAll claims verified on KV5 explorer — kvanta5.org/explorer — "EVERY CLAIM VERIFIED" section
03 // TOKENOMICS
Supply Architecture
231,000,000 KV5 hard cap. 210,000,000 KV5 mineable
exclusively through SHA-256 proof-of-work. 21,000,000 KV5 created at
block #1 as a transparent development reserve, locked by consensus and
released only when scheduled unlock heights are reached: 1,000,000 KV5
every six months over 10.5 years. No ICO. No presale.
Total Supply
231M
KV5 hard cap
Mineable
210M
KV5 — PoW only
Block #1
21M
KV5 — 10.5yr vest
Block Reward
50
KV5 per block (Era 1)
Halving Interval
2.1M
blocks (~4 years)
Daily Emission
72K
KV5/day
Emission Schedule
LIVE HEIGHT 89,305 · ERA 1
EraRewardEra ProgressMinedLeft to Mine
Era 1
50 KV5
4.25%
4,465,200
100,534,800
Era 2
25 KV5
0%
0
52,500,000
Era 3
12.5 KV5
0%
0
26,250,000
Era 4
6.25 KV5
0%
0
13,125,000
Era 5
3.125 KV5
0%
0
6,562,500
Era 6
1.5625 KV5
0%
0
3,281,250
Era 7
0.78125 KV5
0%
0
1,640,625
Era 8
0.390625 KV5
0%
0
820,312.5
Era 9
0.1953125 KV5
0%
0
410,156.25
Era 10
0.09765625 KV5
0%
0
205,078.125
MinedRemaining·
Eras 1–10 represent 99.902344% of the nominal
210M KV5 PoW emission.
Development Fund — 21,000,000 KV5
40%
Core Development
8,400,000 KV5
25%
Security Audits
5,250,000 KV5
20%
Infrastructure
4,200,000 KV5
15%
Legal & Compliance
3,150,000 KV5
Development Funding Allocation: 21,000,000 KV5 was
created at block #1 as a transparent development reserve. The reserve is
locked by KVANTA5 consensus rules and unlocks in scheduled tranches of
1,000,000 KV5 every six months over 10.5 years. Locked tranches cannot
be spent early by any wallet, signer, developer, company, or third
party. Before each required unlock height is reached, nodes reject
attempted spends as invalid. All unlocks and movements are publicly
verifiable in the source code and on-chain.
05 // INSTITUTIONAL TARGETS
Why Institutions Need This
Bitcoin's institutional holders face a hard
choice: wait years for governance consensus that may never arrive, or
move to a chain that was quantum-resistant from day one. KVANTA5 is that
chain — purpose-built for settlement security, SHA-256 PoW, and NIST
Level 5 signatures from Genesis. Three unresolved problems, one clean
migration path.
THIRD-PARTY VALIDATION
BIS Project Leap — Central Bank Proof of Concept
In
2025, the Bank for International Settlements' Innovation Hub ran Project
Leap: a proof-of-concept demonstrating that NIST post-quantum
algorithms (including ML-DSA) can protect central bank RTGS and
cross-border payment systems from quantum attack. Participating central
banks confirmed feasibility, performance, and compliance with the same
NIST FIPS 204 standard that underpins every KV5 transaction. What
central banks proved in a controlled lab environment, KVANTA5 has
deployed in production from block #0.
Problem 01
Quantum Vulnerability of Holdings
Every institutional Bitcoin address that
has made an outgoing transaction has its public key on-chain. A CRQC
derives the private key. BlackRock's ETF holdings are in permanently
exposed addresses. No insurance policy covers this. KVANTA5 has no ECDSA
history.
Problem 02
Governance Paralysis on Migration
BIP-361 proposes freezing Satoshi's
coins. The Bitcoin community is fractured. Institutions cannot force
governance outcomes — they are passengers. KVANTA5 made the quantum
migration decision at genesis. No debate required.
Problem 03
Regulatory Exposure Timeline
Canada's April 2026 PQC mandate. NIST
NSM-10. EU quantum readiness framework. By 2028, compliance officers
will ask: are our digital asset holdings quantum-resistant? KVANTA5
answers yes with an audited implementation.
KVANTA5 Answer
The Quantum-Resistant Bridge Asset
KVANTA5 is not a Bitcoin replacement — it
is a quantum-resistant parallel reserve asset for institutions that
hold Bitcoin and need a provably secure alternative as quantum computing
timelines accelerate. Level 5 security. Commodity classification.
Audited code.
Entry Point 01
Compliance Infrastructure First
Chainalysis, Elliptic, TRM Labs — the
compliance infrastructure every regulated institution uses. KVANTA5
integration with these platforms precedes institutional conversations.
When an institution's compliance team asks "can we monitor KV5?" the
answer is already yes.
Entry Point 02
Regulated Crypto Firms
Galaxy Digital, Grayscale, Arca, Bitwise —
regulated firms that move faster than banks. One research note from
Galaxy Digital's research team reaches every digital asset desk on Wall
Street simultaneously. Target: Q3 2027.
All security claims are sourced from peer-reviewed
publications, official NIST standards, or empirical testnet data.
Nothing here requires trust.
MILESTONE · BLOCK #283 · JUNE 2026
First Native Spent P2QR Transaction in History
TXID: 62572d2127da3d42afb0b20757edb844b0820851f4d8340cbc7e26954ae6272c · 7,388 bytes · Wrapped P2SH → native P2QR address. The first spent
P2QR transaction on a live PoW mainnet — P2QR output types exist from
block #1, but Block #283 marks the first time one was spent. Permanently
recorded on-chain by contributor KV5 DevTeam.
P2QR Output Scalability — 715,001 Outputs in Single Block
TXID: abb67b2c05c965080cc19b6d4dcf23d501888e1d87bf4cf4122a50bcee2e6cf8
· Single transaction with 715,001 P2QR outputs (1 payment + 715,000
micro-outputs) confirmed in a 29 MB block under live PoW. Routine
mainnet operation, not a stress test. Demonstrates output-side
scalability at production scale — the chain handles ultra-large output
counts with no special handling or performance degradation.
Single
transaction with 715,001 P2QR outputs confirmed in a 29.34 MB block
under live PoW. Architecture Demonstration on live Mainnet. Not a
"TestNet Maybe", a Mainnet Fact. Demonstrates output-side scalability at
production scale.
// Press & Media Resources · KV5 · Updated August 2026
KVANTA5 MEDIA KIT
Everything a journalist, analyst, or
researcher needs to cover the world's first SHA-256 proof-of-work
post-quantum settlement chain.
KVANTA5 (KV5) is the world's first SHA-256
proof-of-work settlement chain secured by ML-DSA-87 (CRYSTALS-Dilithium,
NIST FIPS 204 Security Level 5) quantum-resistant signatures from
genesis. Every transaction ever confirmed on KV5 — from block 1 on June
1, 2026 — uses ML-DSA-87. No ECDSA key exists anywhere in the signing
path, historically or retroactively.
The chain features a 231,000,000 KV5 hard supply cap, 60-second
block times enforced by a Dark Gravity Wave difficulty adjustment
algorithm, up to 32 MB blocks with V2_FRAGMENT propagation, and
~6-minute settlement finality. KV5 is SHA-256d compatible with all
standard ASIC mining hardware. The project is open-source with a
zero-premine fair launch. A consensus-enforced 21,000,000 KV5
development fund is distributed via 21 time-locked tranches over ~10
years, hardcoded in protocol consensus rules. KV5 is classified as a
proof-of-work commodity with no staking yield.
// Verified, citable claims
What You Can State Accurately
✓
KVANTA5 is the world's first SHA-256
proof-of-work chain to use ML-DSA-87 (NIST FIPS 204, Level 5) as its
sole signature scheme from genesis.
Source: Genesis block June 1, 2026 · github.com/Kvanta-Organization/Kvanta5-Core
✓
The first non-coinbase P2QR spend was
confirmed at block #283 on June 2, 2026 — the first deliberate
ML-DSA-87-signed transfer between addresses on any live proof-of-work
mainnet.
Block #24521 contained 715,001 P2QR
outputs in a single transaction — the world's largest known post-quantum
signed UTXO transaction on any live proof-of-work chain.
A 4,000-input P2QR consolidation at
block #21798 produced a 29,072,055-byte transaction (weight 116,288,220
wu) — approximately 29× the weight of a maximally full Bitcoin block.
Each ML-DSA-87 input on KV5 is ~7,268
bytes — approximately 67× larger than a comparable ECDSA input (~108
bytes). The raw signature is exactly 4,627 bytes (OP_PUSHDATA2 0x1312
LE).
Measured: 29,072,055 ÷ 4,000 inputs · Confirmed in Delving Bitcoin post Jul 3, 2026
✓
On June 22, 2026 — 21 days after KV5's
genesis — the US government issued an executive order requiring all
federal agencies to migrate to ML-DSA by 2030. KV5 has used ML-DSA since
block 1.
US Federal PQC Executive Order, June 22, 2026
✓
KV5 empirical data was cited by Protocol
Watch (Christine D. Kim) in Issue 47 of "BTC Before Light" covering the
Bitcoin BIP-360 post-quantum signature debate.
christinedkim.substack.com · Issue 47, July 2026
// Technical specifications
Chain Parameters
Parameter
Value
Notes
Ticker
KV5
Native settlement coin
Algorithm
SHA-256d (PoW)
ASIC-compatible — any standard SHA-256 miner
Signature scheme
ML-DSA-87
CRYSTALS-Dilithium · NIST FIPS 204 · Level 5 (2024)
30.77 MB block · largest known PQ UTXO TX on any live PoW chain abb67b2c…e2e6cf8
// Protocol-enforced — not a promise
Development Fund
21,000,000 KV5 (9.09% of total supply) — allocated at block 1 across
21 P2QR addresses. Time-locked via consensus code: each tranche unlocks
every 262,800 blocks (~6 months). Full vest takes ~10.5 years. The
distribution is enforced by Kvanta5DevFundCoinbaseIsExpected() — called by every full node. Any miner producing a non-conforming block 1 is rejected by the network.
"Every chain in production today uses ECDSA.
A sufficiently large quantum computer breaks ECDSA. We didn't build a
patch or a migration plan. We built the chain where that problem doesn't
exist — not as a future upgrade, but from block 1."
— KVANTA5 Core Development Team
"KV5 is the only live PoW chain running the
algorithm the US government just mandated for all federal systems — with
a known team, a consensus-enforced audit fund, and on-chain proof of
production-scale ML-DSA-87 transactions."
— KVANTA5 Core Development Team · July 2026
"KVANTA5's contribution to the Delving
Bitcoin thread on hybrid Schnorr + ML-DSA-87 construction — specifically
the observation that the Schnorr R component (32 bytes) is rounding
error relative to the post-quantum blob — provided real production data
to an ongoing Bitcoin developer debate."
— Protocol Watch, Issue 47 · Christine D. Kim · July 2026
// Brand identity
Logos & Visual Identity
// Full brand asset package
All logos, variants, and source files — download as a zip from GitHub.
The KVANTA5 mark has three elements: speed-lines (three horizontal bars with a diagonal break — quantum-speed settlement), a blue orb (the quantum dot), and the wordmark
(spaced-cap sans-serif, silver metallic, "5" in electric blue). Do not
separate the speed-lines from the orb. Do not recolour the K, V or the 5
independently.
Christine D. Kim cited KV5 empirical ML-DSA-87 data in Bitcoin PQ coverage
// For miners and pool operators
Mining
Stratum connection
Algorithm: SHA-256d — compatible with any standard SHA-256d ASIC miner
Username: your KV5 wallet address (kvqr1… native P2QR, or 3… Wrapped P2SH)
Password: x (unless noted)
Worker: append worker name with a dot — e.g. 3YourAddress.rig1
⚠ Mine to a personal wallet address, not an exchange deposit address.
Get a mining address: Qt wallet → Receive → Wrapped P2SH (Mining Compatibility)
Or via CLI: kvanta5-cli getnewkvanta5p2qrminingaddress
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
BADGERS DEN — https://www.badgersden.tech
SOLO stratum+tcp://mrbadgers.ddns.net:3333
PPLNS stratum+tcp://mrbadgers.ddns.net:3334
SOLO HIGH stratum+tcp://mrbadgers.ddns.net:3335
Username: Kvanta5 P2SH wallet address (3… format)
Password: x
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
BLACKSHIRT POOL — https://www.blkshirtpool.com
STANDARD stratum+tcp://blkshirtpool.com:3333 (home miners, Bitaxe, Nano)
HIGH DIFF stratum+tcp://blkshirtpool.com:3433 (ASICs / rentals >100 TH/s)
Username: Kvanta5 P2SH wallet address (3… format)
Password: x
Note: VarDiff active on both ports. High diff port avoids low-diff
warnings on rental platforms.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1MINER — https://1miner.net
ASIC stratum+tcp://1miner.net:9838 (diff 1024, range 64→∞, VarDiff)
INDUSTRIAL ASIC stratum+tcp://1miner.net:9839 (diff 1,000,000, VarDiff)
Region: US-TX (North America) — latency ~43ms
Username: Kvanta5 P2SH wallet address (3… format)
Password: (none required)
Fee: 1% | Scheme: PPLNS | Min payout: 1 KV5
Auto-payouts every 2h
Pool wallet: 325Aj2cuzviUvFxtpT2bgyMy58xnbpCSjJ
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
NITROPOOL — https://nitropool.net
AU stratum+tcp://au.nitropool.net:3339
EU stratum+tcp://eu.nitropool.net:3339
US stratum+tcp://us.nitropool.net:3339
Username: Kvanta5 P2SH wallet address (3… format)
Password: x
Modes: PROP & SOLO
Optimised for Bitaxe, Nano, Antminer, Lucky, Magic & more
KVANTA5 (KV5) — the world's first SHA-256 PoW chain using ML-DSA-87 quantum-resistant signatures from genesis. Mainnet live since June 1, 2026.
Short paragraph (article intro / listing)
KVANTA5 (KV5) is a post-quantum settlement chain — the world's first SHA-256 proof-of-work blockchain secured by ML-DSA-87 (CRYSTALS-Dilithium, NIST FIPS 204 Level 5) quantum-resistant signatures from genesis. Every transaction carries a full ML-DSA-87 signature. No ECDSA key exists anywhere in the signing path. 231M hard supply cap. 60-second blocks. ~6-minute finality. Zero premine. Live on mainnet since June 1, 2026. Listed on SafeTrade (KV5/USDT).
