Public testnet governance authorized. Activation remains evidence-gated. View launch gates →
GitHub Run a validator
Open-source canonical Layer-1

Finality you can verify.

ZyronChain is an account-based Layer-1 designed around deterministic execution, authenticated state, explicit protocol upgrades and quorum finality. Every launch claim is separated from the evidence required to justify it.

Launch a validator Read technical paper
Consensus>2/3 validator quorum
Supply ceiling50M ZYN
RuntimeNode.js 22+
V1signed
V2signed
V3signed
V4online
3 / 4 quorum · finalized
100kState-v2 account regression
22 / 24Required Node.js CI runtimes
4Validator rehearsal profile
0Investment promises
Protocol

Security boundaries are part of the protocol.

ZyronChain separates consensus, state, execution, networking and upgrades into explicit boundaries with deterministic checks and fail-closed behavior.

01 · CONSENSUS
V1signed
V2signed
V3signed
V4offline

Quorum finality

Finality requires a strictly greater-than-two-thirds validator quorum. When quorum disappears, the network sacrifices liveness rather than accepting conflicting finalized history.

safety > livenessdeterministic quorumanti-double-sign
02 · STATE

Authenticated State-v2

Content-addressed authenticated state with checkpoint, pruning, restart and corruption-recovery controls.

checkpointedcontent-addressed
03 · EXECUTION

Deterministic execution

Exact integer accounting, canonical transaction identities and replayable state transitions.

integer accountingreplayable
04 · NETWORKING

Authenticated native P2P

Noise-authenticated libp2p sessions bind PeerId, node identity, chain ID and exact genesis before consensus traffic.

NoisePeerId pinned
05 · UPGRADES

Fail-closed upgrades

Protocol upgrades, rollback boundaries and validator-set changes are delayed and quorum-authorized.

versionedquorum authorized
Security

Evidence before claims.

Readiness is not inferred from a green build alone. ZyronChain separates synthetic regression evidence from genuine operator, hosting, custody and external-audit evidence.

Open readiness report ↗
01
Adversarial CI

Mixed-version, disaster recovery, multiprocess recovery, gateway red-team and State-v2 scale evidence.

✓
02
Artifact-only operator rehearsal

Canonical release artifacts run independently of the repository source tree.

✓
03
Independent operators

Genuine non-founder operator evidence remains required for activation.

GATED
04
Audit & key custody

Independent audit/retest and production HSM or audited remote-signer custody remain external gates.

GATED
Validator Launchpad

Turn the website into your validator control point.

Use the ZyronChain launchpad to create a local encrypted validator identity, package a shared genesis, pin explicit peers and download a deterministic start script. Private keys never touch the website.

Open Validator Launchpad → Operator guide
zyron-validator-start.sh
$ ./zyron-validator-start.sh
release: a3512f26…
chain:   zyron-friends-testnet-1
rpc:     127.0.0.1:9137
p2p:     0.0.0.0:9140

✓ encrypted key stays local
✓ genesis verified locally
✓ PeerId-pinned P2P
✓ validator starting…
Developers

Clone. Build. Verify.

The canonical TypeScript L1 is public. Node.js 22+ is required and Node.js 24 is the preferred test runtime.

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

# Install, build and verify
npm ci
npm run build
npm test
Operator guideInstall and run the canonical L1↗ Technical paperProtocol model and design choices↗ Security policyReport vulnerabilities responsibly↗ Launch policyAuthorization and activation boundaries↗
Explorer

Observable state without exposing consensus RPC.

The production explorer will expose finalized blocks, transactions, balances and validator state through a bounded read-only gateway. Browser access to validator consensus RPC remains intentionally prohibited.

explorer.zyronchain.comREAD-ONLY PREVIEW
FINALIZED HEIGHT27
VALIDATORS4
QUORUM3 / 4
#0278f2c…a71dFinalized
#0261ae9…0c44Finalized
#02571bd…d39fFinalized
Launch discipline

Authorized does not mean activated.

Public testnet and mainnet governance classes are authorized. Actual activation remains closed until external evidence and irreversible launch specifications are complete.

01
Independent operatorsNon-founder operators and independent failure domains.
GATED
02
External auditConsensus, cryptography and network review with independent retest.
GATED
03
Always-on real Internet soakReviewed sustained uptime and restart evidence.
GATED
04
Production custody & release policyHSM/audited signer, protected release process and succession evidence.
GATED
05
Mainnet specification freezeImmutable genesis, economics, validator governance and launch bundle.
GATED