OPEN-SOURCE · SELF-CUSTODIAL · VERIFIABLE
ZyronChain is a Layer-1 designed around deterministic execution, authenticated state, permissionless ZYN issuance and validator quorum finality. The rules are public, the wallet stays yours, and network activation stays explicit.
Introduction
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
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 SetupZYN ISSUANCE
Protocol-v5 mining introduces permissionless Proof-of-Work claims for ZYN issuance. A valid miner searches for a tip-bound SHA-256 solution, signs the claim locally and submits the public transaction. The current engineering target is a fixed 20-bit SHA-256 target. Proof-of-Work issuance does not select the canonical chain; validator quorum finality remains separate.
CONSENSUS
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 sourceAUTHENTICATED STATE
State-v2 commits accounts, governance schedules and protocol-owned mining 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
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 policyGLOBAL BY DESIGN
ZyronChain nodes, wallets and miners 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
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.
git clone https://github.com/zyron249/-zyronchain.git
cd ./-zyronchain/l1
npm ci
npm run build
npm testGetting started
Create an encrypted local wallet and understand the self-custody boundary before the public network activates.
Create a wallet → 02Prepare a validator identity, verify genesis and peer data, and keep validator RPC off the public Internet.
Validator Launchpad → 03Inspect consensus, state, networking, mining and release tooling directly in the public repository.
Developer source ↗Network status
The software can contain production-oriented capabilities before a public network is safe to activate. ZyronChain keeps those two facts separate.
Public testnet governance authorized. Authorized does not mean activated. Current hosted rehearsal/private profiles remain non-value-bearing.
Start with custody
The website prepares reproducible local commands. Your password and private key never need to enter zyronchain.com.