A Layer-1 that is parallel private and provable
One binary across four network chainspecs. A DAG that includes honest parallel work instead of orphaning it, opt-in shielded transfers with viewing keys, three virtual machines, and a verifiable compute market — advancing through testnet toward audited mainnet deployment.
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.
| Stream | Seal lane | Hardware |
|---|---|---|
| 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).
Opt-in shielded transfers
Transfers on PYRAX are transparent by default for native liquidity and regulatory clarity. Users and institutions can seamlessly opt into Shielded transfers — concealing sender, receiver, and amount with zero-knowledge proofs, while viewing keys enable selective disclosure for compliance and audits.
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 privacy circuits are available on demand.
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.
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.
Full Ethereum equivalence — Solidity/Vyper, the complete eth_* JSON-RPC, filters, subscriptions, precompiles, CREATE2, and EIP-1559.
Rust-first smart contracts compiled to WebAssembly — sandboxed, fast, and metered by the same gas market.
The Cairo VM for provable computation, so heavy logic can be proven off-chain and verified on-chain.
Escrow (Lock / Refund / Release / Drip / Split), Stake (Bond / Unbond / Withdraw / Slash), and Governance (Propose / Vote) are first-class transaction kinds — not bolted-on contracts.
Verifiable AI & GPU compute
The same GPUs that mine Stream B can run paid AI and compute jobs, funded by on-chain escrow and settled on-demand. Instead of trusting a provider's word, results climb a four-rung verification ladder.
Redundant execution
Independent providers cross-check outputs to eliminate silent calculation errors
Fraud proofs
Cryptographic state proofs pin the exact divergent execution step
Interactive dispute
On-chain bisection game isolates and slashes cheating compute nodes
TEE attestation
Hardware-enforced secure enclaves protect confidential model weights and data
Multi-layer protocol security
PYRAX is open-core and security-first: consensus rules are enforced cryptographically, the 50B supply cap is frozen, and multi-resource 51% resistance protects the chain as it advances toward audited mainnet deployment.
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.
Rigorous audit readiness
Consensus, multi-VM execution, and bridge contracts prepared for comprehensive external audits.
Open-core
Apache-2.0 protocol — verify all claims and cryptographic primitives in the open source.