ZyronChain
Source Create a wallet

THE ZYRONCHAIN PROTOCOL / LAYER 01

Fixed supply.
Open rules.

An open-source Layer-1 built around verifiable state, local key custody and a transparent 50,000,000 ZYN launch design now under review.

Local wallet setup Explore the protocol

Public network not activated · Trading not active · Fixed-supply launch design under review · Authorized ≠ activated

50M ZYNfixed maximum supply
10% foundervesting design: 12m cliff + 36m linear
40% liquiditypermanent-liquidity reserve design
Open sourceinspect every launch assumption

Introduction

ZyronChain puts verification before promises.

The project is built so the important claims can be checked in code: who controls a wallet, how state is committed, how blocks reach finality, how ZYN can enter circulation, and which network capabilities are actually active.

SELF-CUSTODY

Your wallet is yours.

A ZyronChain wallet is a cryptographic identity, not an account stored on this website. The canonical setup creates a secp256k1 key on your own machine and protects new local keystores with scrypt and AES-256-GCM. The browser never asks for your private key or wallet password.

Open Wallet Setup

ZYN SUPPLY

A fixed 50M launch design is under review.

The proposed fixed-supply launch allocates the complete 50,000,000 ZYN ceiling at genesis: 5M founder, 20M public distribution, 20M permanent-liquidity reserve and 5M ecosystem/community. If adopted exactly, the existing consensus supply ceiling leaves no issuance headroom beyond genesis.

Mining retired: Mining has been shut down by owner decision (2026-09-30). Do not mine or run miner software. A change that makes consensus reject every mining claim is under review and is not yet merged to the main branch; until it is, legacy protocol-v5 mining code remains in the repository.

50M ZYN proposed full-genesis supply 0 ZYN mining issuance (mining retired) Trading not activated
Review fixed-supply PR #913

CONSENSUS

Finality requires validator quorum.

Finalized blocks require a strictly greater than two-thirds quorum of the configured validator set. If the quorum disappears, the protocol is designed to sacrifice liveness before accepting conflicting finalized history. Protocol upgrades and validator-set rotations are delayed, authenticated and fail-closed.

Inspect the canonical L1 source

AUTHENTICATED STATE

State can be independently checked.

State-v2 commits accounts, governance schedules and protocol-owned state into an authenticated sparse Merkle structure. Checkpoint recovery, portable state sync and independent light-client verification are designed around explicit roots rather than trusting a serving node's narrative.

SECURITY BOUNDARIES

Fail closed when evidence is missing.

Consensus, persistence, signer responses, checkpoint restoration, RPC admission and release provenance are treated as security boundaries. A failed or ambiguous durability step does not silently advance live state. Unsupported protocol activation intentionally fail-stops instead of guessing.

Read the security policy

GLOBAL BY DESIGN

Open-source infrastructure without a website account.

ZyronChain nodes and wallets are designed to operate from public source and reproducible local tooling. The website is an onboarding and documentation surface—not a custody service, exchange, bank or privileged signing coordinator.

DEVELOPERS

Clone it. Build it. Test the boundaries.

The canonical Layer-1 is TypeScript/Node.js. Development and release workflows cover Node.js 22 and 24, reproducible package checks, dependency audits, recovery rehearsals, mixed-version behavior, adversarial soak and an independent Python light-client verifier.

The honest public-test path today is local, not a hosted testnet: cd l1 && npm ci && npm run devnet. That starts a disposable two-validator loopback chain. No public RPC, explorer or faucet is published.

QUICK START
git clone https://github.com/zyron249/-zyronchain.git
cd ./-zyronchain/l1
npm ci
npm run build
npm test
LOCAL PUBLIC TEST
cd l1
npm ci
npm run devnet
Read the public tester guide (docs/PUBLIC_TEST.md)

Fixed-supply launch design

Every ZYN has a disclosed role before launch.

This is a design under review, not a token sale. The website does not accept money, custody purchaser funds or route orders. The quote asset and production AMM are intentionally unset until their trust model is frozen and independently reviewed.

FOUNDER5M10% · 12-month cliff + 36-month linear vesting design
PUBLIC20M40% · future public-distribution reserve
LIQUIDITY20M40% · permanent-liquidity reserve design
ECOSYSTEM5M10% · community and ecosystem reserve
No hidden mint key No founder withdrawal path for permanent liquidity No live quote asset yet No real-money trading yet

Getting started

Find your place in the protocol.

01

Use ZyronChain

Create an encrypted local wallet and understand the self-custody boundary before the public network activates.

Local wallet setup → 02

Run infrastructure

Prepare a validator identity, verify genesis and peer data, and keep validator RPC off the public Internet.

Validator Launchpad → 03

Build on the protocol

Inspect consensus, state, networking and release tooling directly in the public repository.

Developer source ↗

Network status

Authorization is not activation.

A transparent view of launch readiness. These are published activation states, not a live feed from the local development network.

Public testnetGovernance authorizedActivation evidence still required
MainnetGovernance authorizedNot value-bearing / not activated
Public wallet RPCNot publishedValidator RPC remains a separate protected surface
Fixed-supply launchUnder review50M full-genesis allocation design is not activated
Token tradingNot activatedNo quote asset, production AMM or live Buy/Sell surface
MiningRetiredShut down by owner decision; consensus-level rejection is under review, not yet on main
Local public testLoopback onlycd l1 && npm ci && npm run devnet — not a hosted testnet

Public testnet governance authorized. Authorized does not mean activated. Current hosted rehearsal/private profiles remain non-value-bearing. Testers should follow docs/PUBLIC_TEST.md instead of looking for a public RPC, explorer or faucet.

Start with custody

Your first step starts locally.

The website prepares reproducible local commands. Your password and private key never need to enter zyronchain.com.

Create a wallet