HELIXIUM PROTOCOL SPECIFICATION

Helixium Protocol Specification v1.0

Frozen baseline for the proof-native Layer-1 evidence protocol: Create -> Prove -> Verify, enforced through Authorize -> Transfer -> Certify -> Guard.

Open Full Specification Read Whitepaper View Testnet

POSITIONING

Layer-1 for Verifiable Digital Evidence

Helixium is not positioned as only a fast chain or another generic token network. The protocol is built around evidence anchoring, proof lifecycle enforcement, validator role accountability, and external verification.

User Model Create -> Prove -> Verify

Runtime Model A -> T -> C -> G

Supply Policy 46,000,000 HLX

FREEZE RULES

Core Invariants

The protocol lifecycle is Authorize, Transfer, Certify, Guard.
A/T/C/G are Nukleoid validator roles, not only UI stage labels.
ProofLifecycleFinalized finalizes proof state only; it does not claim block consensus finality.
Portable Proof Bundle is the standard export format for off-chain and cross-system verification.
Challenge, fraud proof, invalidation, and slashing intent belong to the Guard layer.
Public wording must not use C as Consensus in the protocol lifecycle.

NUKLEOID STANDARD

A/T/C/G Role Definitions

Role	Protocol meaning	Runtime evidence
A: Authorization	Confirms signer authority, origin context, and permission boundary for the proof.	Authorization vote/state, validator identity, event trail.
T: Transfer	Confirms payload movement, transaction propagation, and bundle delivery context.	Transfer vote/state, anchor reference, digest continuity.
C: Certification	Confirms validator attestation and lifecycle certification after required evidence is present.	Certification vote/state, quorum record, certified proof marker.
G: Guard	Confirms digest integrity, challenge status, fraud evidence, invalidation, and slash intent.	Guard vote/state, challenge record, fraud proof status.

STATE MACHINE

Proof Lifecycle

The chain records a proof as a sequence of explicit lifecycle states. A finalized proof means the proof lifecycle has completed; it is not a replacement for Substrate block finality.

01Anchor Proof

02Authorization

03Transfer

04Certification

05Guard

06ProofLifecycleFinalized

SAFETY MODEL

Quorum Boundary

Testnet Liveness

Adaptive quorum can reduce requirements when validators are offline. This keeps the public demo testable and prevents development stalls.

Production Safety Floor

Production policy must define minimum independent validators for proof finalization. Solo fallback is a testnet behavior, not a default mainnet security claim.

DISPUTE LAYER

Guard, Fraud Proof, and Invalidation

Guard is the protocol layer for integrity review. It records challenges, evaluates fraud evidence, marks invalid proof states, and prepares slash intent for a validator staking registry.

GuardChallengeOpened -> FraudProofSubmitted -> ProofInvalidated | ProofLifecycleFinalized

EXTERNAL VERIFICATION

Portable Proof Bundle

Portable Proof Bundle is the verifier-readable export format. It contains the digest, anchor reference, lifecycle votes, Nukleoid role records, checksum data, and challenge status needed to verify a proof without reading the full chain state manually.

GET /proof/:id/bundle
GET /proof/:id/verify
GET /proof/:id/audit
GET /validators
GET /challenges/:id