Technology

A Layer-1 that is parallel, private, and provable

One binary, four chainspecs. A DAG that includes honest parallel work instead of orphaning it, transfers that are shielded by default, three virtual machines, and an onion Sphinx mixnet — with a single external audit standing between the code and mainnet.

01 · Consensus

GhostDAG + TriStream

PYRAX orders a DAG, not a single chain. GhostDAG's k-cluster rule selects a "blue set" of well-connected blocks and orders everything relative to a selected-parent chain — so honest blocks mined in parallel are included and rewarded, not orphaned. That is what lets throughput scale without sacrificing the security of proof-of-work.

Three streams · five seal lanes
StreamSeal laneHardware
A BLAKE3 PoW ASIC / specialized
A double-SHA-256 ASIC
B kHeavyHash Commodity GPU
B Argon2id (memory-hard) Commodity CPU
C BLS proof-of-stake Staked validators

BLS-aggregated PoS finality

Proof-of-work gives probabilistic ordering; Stream C adds deterministic finality. Validators bond a minimum 32 PYRX and vote with BLS12-381 signatures that aggregate — hundreds compress to one. A block is final once attestations cover > 2/3 of staked weight, and finality overrides work.

51%-resistance across three resources

Rewriting history would require a majority of ASIC and GPU+CPU hashpower and a staked supermajority — three uncorrelated supply chains at once — while GhostDAG colors withheld branches red and reverting a finalized block is a slashable offense (5% burn + 10% reporter bounty).

02 · Privacy

Shielded by default

On every production network the default transfer is Shielded — transparent is the explicit special case, enforced at the type level. A shielded transaction reveals no sender, no receiver, and no per-note amount.

Notes, not balances

State is a set of notes in a depth-32 note-commitment Merkle tree plus a nullifier set. Spending reveals a nullifier — never which commitment it came from.

No trusted setup

Poseidon-over-Goldilocks proofs with a plonky2-style backend. There is no toxic-waste ceremony to trust, and the circuit is default-on today.

Auditable by choice

Viewing keys grant read-only visibility to an auditor or regulator without ever exposing the ability to spend — private for users, provable for oversight.

Recursive aggregation reconciles privacy with scale: thousands of shielded proofs fold into one recursive proof, so a validator performs roughly a single verification per batch. A flat 100-base-unit shielded fee is burned per transfer as anti-DoS.

03 · Virtual machines

Three VMs, cross-VM calls, one chain

Deploy in the language and toolchain you already know. All three virtual machines share one state, one gas market, and can call each other — and a recursive ZK-rollup layer folds thousands of proofs into one.

EVM revm

Full Ethereum equivalence — Solidity/Vyper, the complete eth_* JSON-RPC, filters, subscriptions, precompiles, CREATE2, and EIP-1559.

WASM wasmtime

Rust-first smart contracts compiled to WebAssembly — sandboxed, fast, and metered by the same gas market.

Cairo STARK-provable

The Cairo VM for provable computation, so heavy logic can be proven off-chain and verified on-chain.

Six transaction types, one ledger
ShieldedTransparentEthereumEscrowStakeGovernance

Escrow (Lock / Refund / Release / Drip / Split), Stake (Bond / Unbond / Withdraw / Slash), and Governance (Propose / Vote) are first-class transaction kinds — not bolted-on contracts.

04 · Network

Bootstrapless & ISP-resistant

There is no company-run starter server that can be seized or blocked. Peers discover each other through a decentralized mesh, and traffic can ride an onion Sphinx mixnet so an on-path observer — including an ISP — sees only uniform, encrypted flows.

No bootstrap authority

Discovery is peer-to-peer with a relay directory and Kademlia routing. Nothing central to shut off.

Onion Sphinx mixnet

Layered encryption with cover traffic hides who is talking to whom — metadata privacy, not just payload privacy.

Anonymous carriage

A pull-based want/have engine moves files and media over the mixnet with reply-route loop guards and bounded reassembly.

05 · Security

Audit-gated to mainnet

PYRAX is open-core: the protocol, node, and SDK are public. The supply cap is enforced in consensus, the fee split is frozen, and a single external audit of consensus, ZK, and the bridge stands between the code and PYRAX One.

Formal invariants

Supply, finality, and nullifier-set invariants asserted in code and tested.

Documented threat model

51% across three resources, rogue-key defense, DoS bounds, mempool caps.

External audit gate

Consensus + ZK + bridge audited by an independent firm before mainnet.

Open-core

Apache-2.0 protocol — verify the claims on this page in the source.