ZyronChain
Source ↗ Create wallet
PUBLIC TESTNET AUTHORIZED · ACTIVATION GATED

OPEN-SOURCE · SELF-CUSTODIAL · VERIFIABLE

Own your keys.
Verify the chain.

ZyronChain is a Layer-1 built around deterministic execution, authenticated state and quorum finality. Wallet keys stay on your device, protocol claims stay tied to evidence, and launch status stays explicit.

Create a wallet → See how ZyronChain works
No presale 50M ZYN hard cap Public source No analytics cookies
ZYRON / PROTOCOL CONSOLE Verification surface
STATIC DEMO
EXECUTIONDETERMINISTICexact integer accounting
STATEAUTHENTICATEDState-v2 commitments
KEYSLOCALencrypted keystore
FAILURE MODEFAIL-CLOSEDsafety before liveness
PUBLIC TESTNETGovernance authorizedActivation evidence still required
MAINNETGovernance authorizedNot value-bearing / not activated
PUBLIC WALLET RPCNot publishedValidator RPC remains private
EXPLORERGateway pendingRead-only boundary planned

Public testnet governance authorized. Authorized does not mean activated. The current hosted profiles remain rehearsal/private and non-value-bearing.

01 / START

One network.
Three ways in.

Whether you want to hold ZYN, operate infrastructure or build on the protocol, the first step should be obvious. Choose a path and follow a security-bounded workflow.

SELF-CUSTODY PATH

Create your first ZYN address locally.

The canonical wallet flow generates a secp256k1 key on your own machine, derives a ZYN… address and stores the private key inside an authenticated encrypted keystore. The browser never receives your password or private key.

Create local wallet → Understand ZYN
  1. 01
    CreateGenerate an encrypted local keystore.
  2. 02
    Back upKeep keystore and password backup separated.
  3. 03
    ConnectPublic wallet endpoint appears only after activation.
  4. 04
    TransactSign transfers locally and submit bounded RPC requests.
02 / WALLET

Your wallet starts
on your device.

A ZyronChain wallet is not an account on this website. It is a secp256k1 keypair whose address is derived from the public key. New local keystores use scrypt + AES-256-GCM and include the public key and ZYN… address for identity checks.

✓ Private key generated locally ✓ Password requested only in your terminal ✓ No browser storage ✓ No remote JavaScript dependencies
Open Wallet Setup →
03 / PROTOCOL

Security boundaries
are protocol features.

ZyronChain is designed so the rules that protect consensus, state, networking and upgrades are visible and testable rather than hidden behind a product claim.

01
CONSENSUS

Quorum finality.

Finalization requires a strictly-greater-than-two-thirds validator quorum. If quorum disappears, the protocol gives up liveness before it accepts conflicting finalized history.

V1SIGNED
V2SIGNED
V3SIGNED
V4ONLINE
02
STATE

Authenticated State-v2.

Deterministic state roots, checkpoints, restart validation and content-addressed portable state make replay and corruption checks part of the operating model.

03
NETWORKING

Authenticated native P2P.

Noise-authenticated libp2p sessions bind PeerId, node identity, chain ID and exact genesis before consensus, sync or gossip traffic is accepted.

04
EXECUTION

Exact, replayable accounting.

Integer atom balances, nonces, canonical transaction identities and deterministic state transitions avoid floating-point monetary ambiguity.

05
UPGRADES

Quorum-authorized changes.

Validator-set changes and protocol upgrades require active-validator quorum and a minimum 100-block activation delay. Unsupported versions fail-stop instead of silently forking.

04 / ZYN

Finite by protocol.
Not by promise.

ZYN accounting is defined in atoms and enforced by the canonical L1. The website does not publish price targets, yield claims or investment promises.

HARD SUPPLY CEILING50M ZYN5,000,000,000,000,000 atoms maximum
01100,000,000 atoms

One ZYN is exactly one hundred million integer atoms.

02Fees are burned

The sender pays amount + fee; the receiver gets the amount; the fee does not create new supply.

03No presale

The public website does not offer tokens, allocations, investment contracts or guaranteed returns.

04No activity minting

Proof-of-Activity settlement can distribute only atoms already allocated to its configured pool.

Distribution policy

Any value-bearing distribution, public wallet endpoint and network parameters must be published before activation and must match the canonical genesis and launch evidence. A website button cannot activate supply.

05 / SECURITY

Evidence before
confidence.

A green build is not the same as a safe network launch. ZyronChain keeps synthetic regression evidence separate from real operator independence, production key custody and external audit evidence.

Readiness report ↗ Threat model ↗ Security policy ↗
01
Adversarial CI

Mixed-version rehearsal, disaster recovery, native P2P recovery, gateway red-team and State-v2 scale evidence.

VERIFIED
02
Artifact-only operator rehearsal

Canonical release artifacts are exercised independently of the repository source tree.

VERIFIED
03
Independent operators

Genuine non-founder infrastructure evidence remains a launch gate.

GATED
04
Production key custody

HSM/KMS or audited remote-signer operations remain separate from local development keystores.

GATED
05
External audit / retest

External findings and remediation evidence remain explicit activation evidence.

GATED
06 / DEVELOPERS

Inspect the chain.
Then build.

The canonical Layer-1 is TypeScript and targets Node.js 22+. CI covers Node.js 22 and 24 along with protocol-specific recovery and adversarial workflows.

quick-start.sh
# clone the canonical source
git clone https://github.com/zyron249/-zyronchain.git
cd -zyronchain/l1

# install and verify
npm ci
npm run typecheck
npm test
npm audit --omit=dev

# build the CLI + node
npm run build
RPCBalances, nonces, blocks, transaction submission
P2PNoise + yamux, PeerId-pinned admission
CLIENTIndependent light-client verification core
GOVERNANCEValidator rotation + delayed protocol upgrades
STATEAuthenticated State-v2 + checkpoint recovery
Technical paperArchitecture and protocol model↗ L1 sourceCanonical implementation↗ Validator LaunchpadGenerate local operator scripts→ Wallet SetupCreate a local encrypted keystore→
07 / NETWORK

Launch status should never be ambiguous.

Governance has authorized public-testnet and mainnet network classes, but activation is still evidence-gated. Until a public wallet gateway and canonical network parameters are explicitly published, do not treat rehearsal endpoints as a public value-bearing network.

Governance authorizationCOMPLETE
Public testnet activationGATED
Public wallet RPCNOT PUBLISHED
Value-bearing mainnetNOT ACTIVE
08 / FAQ

Know what
you are using.

Does the website create or store my private key?

No. The Wallet Setup page generates local terminal instructions/scripts. The password and private key are created on your machine and are not submitted to this website.

Can I buy ZYN here?

No. This site does not sell ZYN, run a presale, promise returns or provide an investment contract. Network distribution must match the canonical activation and genesis process.

Is the public testnet live?

No public value-bearing activation is claimed here. Governance authorization exists, but activation remains gated by the readiness evidence described in the repository.

Why is validator RPC not exposed directly to browsers?

Consensus RPC and public wallet/read-only traffic are different security surfaces. Validator RPC is designed to stay private or behind a separately controlled proxy/gateway boundary.

What format is a ZyronChain address?

The canonical L1 derives the address from a secp256k1 public key and encodes it as ZYN followed by 40 lowercase hexadecimal characters.

START WITH SELF-CUSTODY

Create your first
ZyronChain wallet.

No sign-up. No browser-held secret. Generate the encrypted keystore locally and keep control of the key.

Create wallet →