HLX is the native coin of a Substrate-based Layer-1 runtime, not an ERC-20 token.
Proof-Native Layer-1 Network
Helixium
Verifiable digital evidence with runtime-visible proof lifecycles, portable proof bundles, accountable validator roles, and a fixed HLX supply.
What is Helixium?
HLX is a proof-native Layer-1 coin for compact, portable verification.
Proof objects retain authorization, transfer, certification, Guard, and challenge context.
Compact receipts and proof bundles can be verified outside the originating application.
The mainnet genesis policy targets a maximum supply of 46,000,000 HLX with zero inflation.
Helixium is not an ERC-20 token. HLX is designed as a native coin with its own validator network, fixed supply policy, Substrate runtime, proof anchors, and Helix-native verification logic.
The core idea is simple: Helixium does not store everything on-chain. It proves what matters. Large operational data can remain off-chain while compact proof anchors, receipts, checkpoints, and Helix Proof bundles make the record independently verifiable.
coin: HLX
max_supply: 46,000,000 HLX
public_sale_community: 9,200,000 HLX
smallest_unit: nucleo
1 HLX: 1,000,000,000,000 nucleo
model: proof-native Layer-1
| Classic Blockchain Limitation | Helixium Contribution |
|---|---|
| Full history becomes heavy for users, wallets, and small devices. | Compact receipts, signed checkpoints, and portable proof bundles support light verification. |
| Hashes are useful but often lack user-friendly proof context. | Helix Proof packages digest, primary strand, complementary strand, checksum, anchor, and receipt. |
| Fast systems cannot wait for every action to be written directly on-chain. | Events can happen off-chain while important outcomes are anchored as verifiable proofs. |
| Supply chain and operational records are hard to verify without trusting a database owner. | Farm-to-table product traceability can use QR-linked Helix Proofs without exposing private raw data. |
A-T-C-G Proof Lifecycle
Verification is a governed sequence, not a one-time timestamp.
A proof moves through four runtime-visible verification roles. Validators may evaluate the full pipeline locally, but only assigned, signed role attestations can contribute to the network decision.
Verifies signer identity, permission, signature, nonce, and request validity.
Verifies payload movement, routing context, delivery integrity, and transfer state.
Certifies that the required protocol evidence and attestations are present; it does not claim real-world truth.
Applies deterministic policy, challenge, integrity, quorum, and risk checks before the final decision.
Full Engine Availability does not equal Full Decision Authority.
Local computation creates a verification receipt. Network state changes only after role assignment, signed attestation, quorum, and lifecycle transition rules are satisfied.
Live Testnet Evidence
Read the network, runtime, validators, and latest proof directly.
Node Status
Checking gateway
Waiting for Substrate RPC response.
Open Explorer
Chain helixium-public-testnet-1
Block cadence measuring
Finality Aura + GRANDPA
Storage Substrate
Guard & Security Architecture
A deterministic security pipeline with explicit failure reasons.
Guard does not make absolute security claims. It is designed to detect and reject unauthorized, altered, conflicting, or suspicious proof transitions under protocol-defined rules.
Schema, field, size, and canonical encoding checks.
Signature, digest, checksum, and evidence integrity.
Nonce reuse, replay, double-spend, and lifecycle conflict checks.
Eligibility, permissions, limits, and network policy.
Assigned role attestations and independent validator thresholds.
Accept, reject, or review with machine-readable reason codes.
Replay nonce + state comparison
Tampering signature + digest
Double spend ledger + lifecycle state
Malicious validator quorum + challenge + slash intent
Use Cases
One proof lifecycle, multiple evidence domains.
Model output, source, approval, transfer, and integrity evidence.
Authorization and certification trails for institutional records.
QR-linked production, custody, inspection, and delivery checkpoints.
Portable receipts with validator actions and challenge history.
Proof-backed asset lifecycle records without exposing private raw data.
Compact anchors for high-volume systems that retain data off-chain.
Nucleotide Validators
Full local evaluation, separated network authority.
Full A-T-C-G engine availability and assigned-role attestation.
Full A-T-C-G engine availability and independent network identity.
Full A-T-C-G engine availability and signed role receipts.
Full A-T-C-G engine availability and Guard quorum participation.
Planned expansion: 4 → 8 → 12 independent validators
New validators require identity, eligibility, stake/bond policy, peer proof, heartbeat, controlled authority activation, and conformance checks. Expansion must not require rewriting the proof lifecycle.
Tokenomics
Planned 46,000,000 HLX mainnet genesis allocation.
status: published genesis policy
policy_version: HLX-TOKENOMICS-LOCK-2026-05-11
max_supply: 46,000,000 HLX
inflation: 0
public_manifest: /assets/locked-tokenomics.json
changes: versioned public amendment required
| Allocation Category | Share | HLX Amount | Planned Control |
|---|---|---|---|
| Ecosystem and Grants | 30% | 13,800,000 HLX | Milestone releases, treasury multisig, and public reporting. |
| Validator Incentives | 20% | 9,200,000 HLX | Protocol-defined reward vault; not discretionary treasury spending. |
| Public Sale & Community | 20% | 9,200,000 HLX | Separate distribution vault, compliance review, and published schedule. |
| Treasury and Reserve | 15% | 6,900,000 HLX | Planned multisig + timelock, progressing to on-chain governance. |
| Founding Team | 10% | 4,600,000 HLX | Dedicated long-term vesting; no unilateral treasury access. |
| Advisors & Partners | 5% | 2,300,000 HLX | Separate vesting and milestone-based agreements. |
These allocations describe the planned mainnet genesis distribution. Current testnet balances are technical test balances and do not represent this economic allocation. No single individual is intended to have unilateral control over the allocation vaults.
Roadmap
From working testnet to independently secured mainnet.
Protocol Foundation
Substrate runtime, native HLX, proof anchors, portable bundles, and A-T-C-G state machine.
Four-Validator Testnet
Multi-node authority set, wallet transfers, proof lifecycle roles, Guard quorum, and public APIs.
Independent Expansion
Validator admission, 8- and 12-validator growth, staking policy, slashing, monitoring, and stress tests.
Mainnet Candidate
External audit, economic security floor, governance controls, genesis signing, and launch readiness.
Join HLX Testnet
Independent validator and early developer applications will open soon.
Helixium is now in public testnet. The next focus is independent validators, fast RPC, wallet access, and open verification tooling.