ZyronChain wolf and Z mark in a blue ring

ZyronChain · Layer 1

ZyronChain Verifiable Layer-1 infrastructure

  • Local keys
  • Deterministic execution
  • Authenticated state
  • Quorum finality
  • Fixed supply design

What it is

An open-source Layer-1 you can inspect and run yourself.

ZyronChain is a TypeScript/Node.js Layer-1: secp256k1 accounts, signed transfers, a deterministic state machine, authenticated state commitments and validator-quorum finality. The canonical implementation is l1/. This site is documentation and local tooling, not a custody service, exchange or RPC.

Is it live?
No public network yet. The public testnet is authorized by governance but not activated; mainnet is not activated.
Can I use ZYN today?
No. There are no balances, transfers on a public network, token sale or market.
Can I create a wallet?
Yes, locally. Keys are created and kept on your device. Wallet options
Can I run a validator?
You can prepare one locally. Public validator enrollment is not active. Validator Launchpad
Where is the code?
github.com/zyron249/-zyronchain (canonical L1 in l1/).
What should I test?
A local two-validator devnet: cd l1 && npm ci && npm run devnet. See docs/PUBLIC_TEST.md.

How the protocol works

From a local key to a finalized block.

  1. Keys

    A secp256k1 key is created on your device. The address is ZYN + the first 40 hex characters of SHA-256 of the public key.

    Read crypto.ts
  2. Transactions

    A transfer commits to chain ID, nonce, sender, receiver, amount, fee and timestamp, and is signed locally. Wrong chain or nonce is rejected.

    Read transaction.ts
  3. Execution

    Every node applies the same ordered transactions with the same rules and must reach the same state. Ambiguous input fails closed.

    Read chain.ts
  4. Authenticated state

    Accounts and protocol state are committed to a sparse Merkle root, so checkpoints and light clients verify roots instead of trusting a server.

    Read state-v2.ts
  5. Quorum finality

    A block is final only with more than two-thirds of the configured validator set. Without quorum the chain halts rather than finalize conflicting history.

    Read p2p-consensus.ts

Whitepaper · Canonical L1 source

Security principles

What this project commits to.

  • Verify, don't trust.Claims on this site link to source, specs or tests. Run them yourself.
  • Local keys.Keys are generated and used on your device. The site never asks for a phrase, key or password.
  • Open source.Node, wallets, website and CI live in one public repository.
  • Explicit network state.Governance authorized ≠ network activated. Local devnet ≠ hosted public testnet. Can sign ≠ can broadcast.
  • No fake metrics, market or mainnet.No price, volume, TVL, block height or user counts are shown, because none are real yet.
  • No secret uploads.Nothing secret is sent anywhere. No analytics cookies, no telemetry.

Security policy (SECURITY.md) · Phone Wallet security model

ZYN tokenomics

50M ZYN maximum supply. Allocation under review.

Final protocol fact

50,000,000 ZYN cap

The consensus constant MAX_SUPPLY_ATOMS = 50_000_000 * ATOMS_PER_ZYN, with 1 ZYN = 100,000,000 atoms. No balance can exceed it.

Read types.ts

Proposed · under review

Launch allocation

  • Founder5M10% · 12-month cliff, 36-month linear vesting design
  • Public distribution20M40%
  • Permanent liquidity reserve20M40%
  • Ecosystem / community5M10%
Review the open proposal (PR #913)

Pending governance

Not decided yet

  • Consensus-enforced founder vesting
  • Quote asset and on-chain liquidity model
  • Mining retired: Mining has been shut down by owner decision (2026-09-30). Consensus rejection of all mining claims is under review and not yet merged to the main branch.

No price, order book, volume or market cap exists, so none is shown.

Validator path

Prepare a validator locally.

The Validator Launchpad generates local scripts: verify the canonical repository and genesis, create the validator identity on your machine, configure peers and a firewall, and keep consensus RPC private. Public validator enrollment is not active.

Open Validator Launchpad
  • Hardware and OS baseline
  • Identity created locally, never uploaded
  • Genesis and repository verification
  • Peers, bootstrap and firewall
  • Consensus RPC on 127.0.0.1 only
  • Backup and recovery plan

Developer path

Clone, build, run, inspect.

Local devnet
git clone https://github.com/zyron249/-zyronchain.git
cd ./-zyronchain/l1
npm ci
npm test
npm run devnet

npm run devnet starts a disposable two-validator chain on 127.0.0.1 with a random chain ID and port, then sends a verified 1 ZYN transfer. It is not a hosted testnet.

Local devnet · inspect
curl -s http://127.0.0.1:<PORT>/status
curl -s http://127.0.0.1:<PORT>/protocol
curl -s http://127.0.0.1:<PORT>/balance/ZYN<40-hex>
npm run devnet:check

Use the port printed by the launcher. devnet:check also proves one validator alone cannot finalize.

Public testnet

Not activated

No public chain ID, genesis hash, RPC, explorer or faucet is published. Do not trust anyone who offers one.

Public tester guide (docs/PUBLIC_TEST.md)

Network status

Static, published with this build from the repository. Not a live feed; this page never contacts validator RPC.

ZyronChain network capabilities as of this build
Governance AuthorizedPublic testnet and mainnet authorized by governance. Activation is not allowed yet.
Public testnet Not activatedAuthorized ≠ activated. A local devnet is not a hosted public testnet.
Public RPC UnavailableNo public wallet RPC is published.
Explorer UnavailableNo public block explorer is published.
Wallet creation Available locallyKeys are created on your own device.
Offline signing AvailableCan sign ≠ can broadcast.
Broadcasting Unavailable until activationSigned transfers cannot be submitted to a public network yet.
Mining RetiredShut down on 2026-09-30. Do not run miner software.
Token sale NoneNo sale, no price, no market.

Source: docs/l1-launch-authorization.json (publicTestnetActivationAllowed=false, mainnetActivationAllowed=false).