Mainnet · since version 1.0.0

Helix Post-quantum blockchain

A layer-1 blockchain secured by NIST-standardised post-quantum cryptography — every signature ML-⁠DSA-⁠65, from the very first block.

Block height
—
Block time (target)
≈ 2 s
Validators
—
Signatures
ML-DSA-65
  • ML-DSA-65 on every signature
  • Mainnet since 1.0.0
  • BFT finality
  • ≈ 2 s per block
  • ZK-STARKs
  • alice.hlx
  • Open source · MIT

01Live

The chain, block by block.

Every new block shows up here as soon as the public node reports it — with its height, hash and transactions. A click opens it in the explorer.

Helix MainnetConnecting …
Validators
—
Accounts
—
Issued
—
Burned
—
Peers
—
Version
—
Open the explorer

02Post-quantum from the ground up

Not retrofitted. Built from the ground up.

Instead of migrating an existing chain to post-quantum later, Helix is designed for it from the first line of code: ML-⁠DSA-⁠65 on every transaction, block and validator vote — no transition period, no classical signature schemes to swap out down the line.

Signature
ML-DSA-65 · FIPS 204
Backup
SLH-DSA-SHA2-192s · FIPS 205
Hash
BLAKE3
Proofs
ZK-STARK
Transport
Noise · X25519 · classical

03Why Helix

What existing blockchains leave open.

Six problems Helix does not leave for later, but has solved since its first line of code.

In existing blockchainsHelix
A large quantum computer can break ECDSA and Ed25519 signaturesML-⁠DSA-⁠65 (NIST FIPS 204) on every transaction, block and vote
Stake buys voting power without limitEach validator’s voting power capped at 1% of total stake
Hex addresses; a lost key is lost for goodalice.hlx names and recovery through guardians
No plan for the next cryptographic migrationThe signature scheme is versioned in every transaction
Zero-knowledge proofs resting on elliptic curves (SNARKs)ZK-STARKs only — purely hash-based
A contract that runs forever stalls the chainWASM VM, fuel-metered per transaction and per block, no floating point

04Architecture

Eight decisions, block by block

What the protocol is made of — and where to read it in the code.

  1. ML-⁠DSA-⁠65 everywhere

    Every transaction, every block, every validator vote. No classical scheme with a migration plan attached.

  2. Crypto agility built in

    The signature scheme is versioned in every transaction; SLH-⁠DSA (FIPS 205) stands by as a hash-based reserve.

  3. Final in about two seconds

    Tendermint-style BFT consensus: a block stands once more than two thirds of the vote is behind it — and, as long as less than a third of the vote is faulty, is never reverted.

  4. Voting power capped

    Each validator’s voting power is capped at 1% of total stake — capital alone buys no majority. That only means at most 1% of the vote once there are 100 validators; today the set is far smaller.

  5. Names and recovery

    alice.hlx instead of a hex address — and social recovery through guardians when a key is lost.

  6. WASM contracts without reentrancy

    Fuel-metered, no floating point, no calls between contracts: the best-known attack surface simply is not there.

  7. ZK-STARKs

    Zero-knowledge proofs built on hashes alone — no elliptic curves for a quantum computer to break.

  8. Upgrades by governance

    Protocol changes are voted on-chain and activate at a height announced in advance. No more resets since 1.0.0.

05Supply

Capped, traceable, with a disclosed genesis allocation.

Every number is in the code. More than 99% of all HLX only come into being by producing blocks.

HLX supply over time — upper bound, before burned fees

010M20M30MGenesisY5Y10Y15Y20Y25Y30Hard cap: 33M HLX≈ 31.7M

Computed from the protocol parameters: 1 HLX per block, halved every 15,768,000 blocks (≈ 1 year at 2 s). Burned fees are not subtracted. Issuance approaches about 31.7M HLX; the 33M cap sits above it and is fixed in code.
Show as a table
YearNewly issued (HLX)Total supply (HLX)
Genesis0.00161,000
115,768,000.0015,929,000
27,884,000.0023,813,000
33,942,000.0027,755,000
41,971,000.0029,726,000
5985,500.0030,711,500
6492,750.0031,204,250
7246,375.0031,450,625
8123,187.5031,573,813
961,593.7531,635,406
1030,796.8831,666,203
1115,398.4331,681,602
127,699.2131,689,301
133,849.6031,693,150
141,924.8031,695,075
15962.4031,696,038
16481.1931,696,519
17240.5931,696,759
18120.2931,696,880
1960.1431,696,940
2030.0731,696,970
2115.0331,696,985
227.5131,696,992
233.7531,696,996
241.8831,696,998
250.9331,696,999
260.4631,696,999
270.2231,697,000
280.1131,697,000
290.0531,697,000
300.0231,697,000
hard cap
33M
HLX at genesis (~0.5%)
161,000
block reward, halved yearly
1 HLX
of the base fee is burned
100%
HLX minimum validator stake
10,000
slashed for double-signing
5%
unbonding period
7 days
default commission, at most 50%
10%

Genesis allocation (1.0.0)

launch reserve on an offline key
100,000 HLX
liquid, one for each of the three operators
3 × 15,000 HLX
bootstrap validator: staked + liquid
15,000 + 1,000 HLX

Genesis hashf318dcdeffe93a45e8f7233b2048bedf1d544410028dafaec46a5461d4ef8540Query the genesis from the node (opens in a new tab)

HLX is not an investment, and nothing here promises it is worth anything. Every parameter — and the open question of what pays for security once issuance ends — is in TOKENOMICS.md (opens in a new tab).

06Get started

Three ways in.

You do not need a node of your own to use Helix: the wallet and the command line talk to the public network with no setup.

A

Desktop wallet

For Linux, macOS and Windows — everything the command line does, without a terminal.

  • Balance, send, receive, history
  • Staking, delegation and governance
  • .hlx names and recovery
  • A validator node in one click
  • The key stays on your machine; locks after 10 minutes
Download the wallet (opens in a new tab)
B

Command line

One binary for everything: helix runs a node or talks to the network as a client.

helix
# 1. Create a wallet
helix wallet new -o alice.json --passphrase

# 2. Look at the chain
helix chain status

# 3. Send HLX
helix tx send <address> 10 --key alice.json
Read the CLI docs (opens in a new tab)
C

Validate or delegate

Help secure the network — with a node of your own or through an existing validator.

  • Validate from 10,000 HLX stake
  • Delegate without running a node
  • Works behind NAT, firewalls or proxies
  • Linux, macOS, Windows or Docker

07Known limits

A young network with known limits.

  • The validator set is still smallWith n validators the network survives ⌊(n−1)/3⌋ failures: four survive one, seven survive two — three or fewer survive none. When too many are missing, the chain stops and waits; it does not fork. Active right now: —.
  • HLX is not an investmentSince 1.0.0 nothing is reset any more. That does not mean HLX is worth anything — and we do not claim it is.
  • The transport uses classical encryptionNodes connect over libp2p Noise (X25519). What they exchange is public and ML-⁠DSA-signed: a quantum computer could read along but forge nothing.
  • Consensus at scale: shown in tests, not yet in productionVote locking, re-proposals and double-sign detection are exercised in fault-injection and chaos tests — including with a third of all messages lost, with no fork. The live network is still small.
  • Reviewed continuously from an attacker’s point of view — AI-assistedThe review runs alongside development with Claude (Anthropic), as the README describes. Every finding is first reproduced as a test, then fixed; as a cross-check, reverting the fix must make the test fail again. No independent external audit has been published so far.

We would rather say this up front than have to explain it afterwards.

08Questions

Questions about Helix

Do I need my own node?

No. The wallet and the command line talk to the public network with no setup. A node of your own is worth it if you want to validate or verify the chain independently.

How do I become a validator?

With at least 10,000 HLX staked and a running node — from the command line or in one click from the desktop wallet, behind NAT or a proxy too. The guide is in the documentation under “Running a Node”.

Can I take part without running a node?

Yes, by delegating: you put your stake behind a validator and receive a share of its earnings, less commission (10% by default, at most 50%).

What happens when validators go down?

With n validators the network survives ⌊(n−1)/3⌋ failures. With more missing, the chain stops and waits — it does not fork. A validator that stops signing is suspended for a while. Under protocol 1, active today, that costs no stake; from protocol 2, once stakers vote it in, it does.

What does a transaction cost?

A base fee per byte, burned in full, plus a tip for the validator. The base fee follows demand (at most ±12.5% per block); the wallet never pays more than 1 HLX on its own.

Is HLX an investment?

No. The network is young, and nothing here promises it is worth anything.

The other side of Silvra

Silvra Messenger

Chats, calls, feed and points account in one app — the chats end-to-end encrypted, from Europe.

Go to the messenger