Peer-to-peer network · Self-certifying certificates · Zero premine

Verifying a transaction shouldn't require the whole network.

Zycord is a peer-to-peer network where every transaction carries the state it read and the state it wrote. No node has to replay the history to check one — just the transaction's own bytes, checkable by any machine, in parallel. Proof-of-work mining with RandomX, solo or in a pool: no premine, no ICO, no admin keys. Mainnet has been running since 7 October 2026.

0% premined or sold
before launch
883K state operations per second,
per CPU core
~2s to validate and apply a whole
block of certificates
RandomX CPU mining

Zycord (ZCD) — how the network works

Assembled off-chain.
Verified in parallel.
Committed in order.

Every large blockchain makes every node re-execute every transaction against a global state. Zycord takes execution off the chain: a payment is built by the wallet, a contract call is executed by the contract's sequencer from the user's signed intent, and either way the result arrives complete with everything it read and wrote. Any machine checks it from the bytes alone, and a single loop commits it — or skips it, and bills whoever deposited for it.

Three phases: construction by sequencers, parallel verification, sequential fold Construction — off-chain Sequencers execute the intent and co-sign one fill Wallet Sequencer contract A Sequencer contract B Sequencer contract C Verification — parallel, stateless Every node checks every certificate, on every core Fold — sequential One loop, compares and adds apply or skip, never execute

// 01 — The problem

Every fast blockchain gets heavier as the network grows

Most blockchains make every computer on the network replay every transaction against the same global state. It works — until the network really grows: then every node has to become a bigger machine, and fewer and fewer people can keep up. Zycord exists to solve that specific problem, not to promise being generically "faster".

The core idea: every transaction — called a certificate here — already carries what it read and what it wrote of the network's state. Checking whether it's valid becomes a matter of checking its own bytes, without consulting the whole history. Any machine can do that check on its own, in parallel, using several processor cores at once.

The only step that has to happen in order, one at a time, is applying the final result to the ledger — and that step is simple enough to run almost for free: comparing and writing values, with no signature checks, no code execution, no heavy cryptography along the way.

Two certificates that race for the same value are both valid; the first in the block applies and the other is skipped, a fixed fee is burned from the deposit it named, and the block stays valid. Payments never race at all: they declare “balance at least x” and add or subtract, so any number of them land in one block in any order.

No premine

No coin exists before block 0, and every coin is mined. The founder is paid the way miners are: 3% of each block, written into consensus, for three years.

Accessible mining

RandomX runs well on ordinary CPUs — no ASIC farm to compete with you.

Parallel processing

Validation depends only on the transaction's own bytes — never on the whole network history. That's what opens room to run in parallel, with no queue.

// 02 — Launch

Launch, milestones and eras

Mainnet launched on 7 October 2026. Every milestone after that is a height or an epoch fixed in consensus, or a condition measured on chain, never a calendar date or a vote. An epoch is one day; the dates below are estimates at 30 seconds a block.

Mainnet · live

7 October 2026 — 00:00 UTC

Block 0, chain id 1. No premine, no ICO, no admin keys. Block 1 revealed the launch commitment, and mining runs on a 30-day reward ramp.

Public testnet · live

5 October 2026 — 00:00 UTC

The same binary, started two days before mainnet to rehearse the launch. Its machine opened at height 2,880, so the cEVM, sequencers and the forced path can be tried there before mainnet reaches height 80,640. To learn more, join the Discord.

Milestones

Height or epoch~DateMilestone
07 Oct 2026Launch: mining starts on the 30-day reward ramp
80,6404 Nov 2026Era 1: the cEVM, sequencers and the forced path turn on
86,4006 Nov 2026Ramp ends: full block reward
259,2005 Jan 2027Earliest a spend path for the treasury can arrive, by upgrade
524,1607 Apr 2027Era 2: stake bonding opens (epoch 182)
786,2407 Jul 2027Latest start of the proof-of-stake ramp (epoch 273)
1,045,4405 Oct 2027Latest switch to proof of stake, if the ramp never pauses (epoch 363)
Epoch 1,0956 Oct 2029Founder share ends; the treasury goes to 6%
Epoch 4,376Sep 2038Perpetual tail emission

Eras 0 and 1 are in the launch binary: era 0 has been live since block 0, and era 1 opens at height 80,640 with nothing to install. Eras 2 and S are in development, and each ships as its own release, by hard fork; what lies past full verification is only a direction.

Era 0 block 0 · live since 7 October 2026

Mine and pay

RandomX mining, solo or in a pool, on a 30-day reward ramp. Native assets — issue, mint, transfer, retire — with no virtual machine involved; one-shot and persistent addresses; the two fee markets; the 94/3/3 subsidy split, with the treasury accruing and no certificate able to debit it. Ten thousand tips to one address in one block: zero conflicts.

Era 1 height 80,640 · in the launch binary

The machine

The Solidity-compatible cEVM with a delta-first standard library. Contracts choose a sequencer, which executes users’ signed intents and confirms them in milliseconds; one call can span several sequencers atomically; a directory says where each one answers. The forced path: any user reaches any contract without a sequencer. Same binary as block 0.

Era 2 epoch 182 · in development

Proof of stake: bonding and ramp

Bonding opens at epoch 182, about 7 April 2027: stake is bonded, unbonded or delegated to a pool, and a delegator’s coin never leaves its owner. Once active stake holds 10% of supply for 30 epochs, and at the latest from epoch 273, a ramp of 90 epochs begins: blocks are still mined but also carry the signature of a staker drawn by stake, whose share of the reward rises to one half.

Era 2 when the ramp completes

Proof of stake: the switch

Mining ends and stake alone produces blocks, in slots of 5 seconds; a day pays the same subsidy and holds the same capacity as before. At the latest epoch 363, about 5 October 2027, if the ramp never pauses. A block is final 120 blocks deep, ten minutes. Only signing two blocks for one slot is punished, and never a delegator.

Era S in development

Confidential payments

Hidden amounts and one-time addresses, under a specification of their own — they are not part of the v2 protocol — and only after independent audits and an adversarial public testnet. It doesn't switch on before it's ready.

Later a direction, not a specification

Past full verification

Until then every node verifies every certificate. When daily volume nears what an ordinary node can verify, a later era may draw a subset of stakes to verify each certificate instead, so capacity grows with every node that joins, while the state and the fold stay one.

Issuance with no cliffs

The reward climbs from near zero to full over the first 30 days, then drops gradually, in small steps each epoch — no sudden cut like Bitcoin's halving. After about 12 years it settles into a small, permanent tail that pays for security forever.

Founder share and treasury

Of every block subsidy, 94% goes to the block's producer, 3% to the founder until epoch 1,095 (three years) and 3% to the treasury. The treasury is held by the protocol with no key, and no certificate can debit it: a spend path, if any, comes by a later upgrade, not before height 259,200. Once the founder share ends, it receives 6%.

// 03 — Differentiators

What already runs from block 0 — and what comes later

Each card shows which era of the protocol turns that feature on. Nothing here is sold as ready before it's ready.

Era 0

Genuinely parallel processing

Every certificate already arrives proving on its own that it's valid — no need to consult the network's history. Hundreds of payments to the same wallet process at the same time, with no queue and nobody blocking anybody.

Era 0

Capacity that grows with real usage

The ceiling isn't fixed or decided by vote: the sequential target moves once a day with the gas that actually applied, at most doubling in a year of full, healthy blocks, and never below its genesis value. Within an era it stops at 3.2× genesis (8 MB blocks); only an era boundary moves that wall. The structural limit, set at genesis, is about 1.1 million certificates per second.

Era 0

Fair fees

Two separate markets — one for state changes, one for verification — adjust on their own as usage rises or falls, with no fixed auction. The fee of a certificate that is skipped is burned, never kept by whoever assembles the block, so a producer earns only from what applies.

Era 0

No-surprise launch

Zero premine, zero ICO, zero admin key. The block subsidy split — 94% miner, 3% founder, 3% treasury — is a consensus rule, and the genesis block was public and reproducible before the network existed.

Era 0

Being first counts for little

The block reward climbs from near zero to full over the first 30 days. Pointing a rented farm at the first hours earns little; the coin goes to whoever keeps mining.

Height 80,640

Censorship resistance

If a contract's sequencer ignores you, sign an open intent instead: any block producer can execute it at the end of its block and is paid to. Inclusion is application — no queue, no lease, no waiting period — and a sequencer can never spend your funds or change what your intent does. Arrives at height 80,640, about four weeks after block 0, alongside the Solidity-compatible machine.

Era 0

Mine with what you already have

Mining uses RandomX, built to run well on an ordinary processor — the same one already in your computer. No specialized hardware needed to start participating from block 0.

Height 80,640

Solidity-compatible

Anyone who already writes contracts on Ethereum can port them to the cEVM with few changes — same language, same tools, same auditors. A ported contract runs correctly in all-exact mode, serialized by its sequencer; parallelism is opt-in, slot by slot. It ships inside the genesis binary and turns on at height 80,640, with no fork and nothing new to install.

Era S

Privacy in payments

Each payment's value stays hidden, and whoever receives it gets a new address every transaction — nothing to trace by repetition. It is not part of the v2 protocol: it comes under its own specification, and only after independent audits are published. Privacy that arrives ready, not privacy that arrives fast.

Height 80,640

Room for heavy cryptography

A heavy proof — zero-knowledge, post-quantum signature — never competes for space with a simple payment: it pays in a market of its own. What doesn't fit in a contract on an ordinary chain today fits here.

Era 0

294K TPS measured. Only 90 released at genesis.

The system's one sequential step — the one that decides what actually counts — ran at 294,000 TPS on a single core of an ordinary desktop, measured on the reference implementation for whitepaper v1.0. At launch, the network releases about 90: the ceiling grows only with sustained, applied use on a healthy network, not with hardware limits. The bottleneck was never the machine.

Era 0

99.5% of block time runs in parallel

Out of roughly 2 seconds to validate and apply a block of 2,900 certificates, only 9.9 milliseconds is the part that can't be parallelized (measured on the reference implementation for whitepaper v1.0). The system's real bottleneck measures under 1% of total time — the rest is verification, and verification scales with hardware.

// 04 — Why

Trust that doesn't ask you to trust anyone

Four reasons to take this launch seriously — and none of them ask you to take a promise on faith.

  • 01

    Why trust without trusting anyone

    The whitepaper doesn't hide its weak points — it lists its accepted risks, one by one, and is signed with a public key. You don't need to take a promise on faith: you can check the code, and run the test vectors against it yourself.

  • 02

    Why now, and not later

    The chain is days old. Its start was announced in the open and fixed in the published parameter file, so anyone could be there at block 0, and the 30-day reward ramp paid little to whoever arrived first. There was no silent presale and no privileged waitlist.

  • 03

    Why mine here

    RandomX was designed to keep ordinary hardware competitive — CPU, not an ASIC farm. Mine solo or in a pool, from the same release: 94% of every block subsidy goes to the miner, and so do the priority fees of every certificate that applies.

  • 04

    Why this solves a real problem

    Every fast blockchain today makes every computer on the network replay every transaction against the same state. The more people use it, the bigger the machine every node has to be — and the fewer people can run one. Here, verifying a transaction doesn't require the whole history — just the transaction's own bytes.

// 05 — See for yourself

Don't take our word for it. Check it.

Documentation and the complete source code — all published for anyone to audit before trusting it.

Read the whitepaper

Self-certifying certificates, the fold, typed state access, sequencers, the forced path, two fee markets and proof of stake — the v2 paper, with its companion on launch, eras and parameters, and the references the design leans on.

Document · v2.0

Check the protocol against its vectors

The parameter files and the golden vectors are the protocol: every fold, block and validity rule has its case, positive and negative. Run them against this implementation — or against one you write yourself, which is what they are for.

Spec · vectors

Official announcements live on Bitcointalk

The community is being built on Discord and Telegram, run by the community itself. Official announcements are different: every one is signed with the project key and posted in one public forum thread, with dated, ownerless posts, the way anonymous projects have done it since 2009. When in doubt, check the thread.

Forum · official

Watch mainnet produce blocks

The block explorer for mainnet, from block 0. Block 1 opens the launch commitment; every block after it, every certificate, and whether each was applied or skipped and billed.

Mainnet · live

Watch the testnet produce blocks

The block explorer for the running testnet. Every block, every certificate, and — the page no other chain's explorer can render — whether each certificate was applied, or skipped and billed, and which declared read stopped holding.

Testnet · live

Source code & testnet

Reference implementation, golden test vectors, and instructions to run your own node — published before launch, under the MIT licence.

Public · MIT

// 06 — Join

Run your own node, no permission needed

Reference client, RandomX mining binary, and a light wallet — one release, for mainnet and the public testnet alike.

Download it, start it, and leave it running. Era 1 is already inside the same binary and opens at height 80,640 on its own — there is nothing to schedule, restart or reconfigure when the height arrives.

🟢Mainnet

Each release ships two sets of archives and they are not interchangeable. The -randomx builds are the ones that join a network, and they are published for Linux, macOS and Windows on x86-64. The plain builds are byte-for-byte reproducible so that anyone can rebuild the tag and compare — they carry no mining engine and run only a local devnet, which is all that Windows on ARM has. The downloads page names which is which.

// 07 — Community

Built in the open, with the community

I am an anonymous developer. I launched this network and will maintain it for as long as it takes.

I am looking for volunteers

Every part of this is work the community can own, and most of it is work I cannot do alone or should not do at all:

  • Community channels — the Discord and the Telegram are run by the community, and that is where it is being built. Help moderate them, welcome newcomers, or start one on Reddit.
  • Translations of the documentation and the whitepaper.
  • Documentation — guides, corrections, and anything that makes the docs easier to arrive at cold.
  • Pools. None exist and none are official; if you build one, it is a third party and should say so.
  • Above all, people willing to attack the design and publish what they find. Post it in the thread or open an issue — neither can be deleted, and a defect found before era 1 opens costs far less than one found after.

Post in the announcement thread. It is not self-moderated, so nothing in it can be deleted — including criticism of me.

Follow the project by e-mail

Releases, era activations and testnet resets, sent by hand and not often. One address, no tracking, no mailing service.

Get Updates by E-mail