______ _______ ___ ____ ____
|__ / \ / / ___/ _ \| _ \| _ \
/ / \ V / | | | | | |_) | | | |
/ /_ | || |__| |_| | _ <| |_| |
/____| |_| \____\___/|_| \_\____/
without choking, and without betraying whoever showed up first.Testnet: 30 August 2026, 00:00 UTC — LIVEMainnet: 15 September 2026, 00:00 UTC — block 0, open to anyoneWebsite |
Source |
Whitepaper |
Explorer |
DownloadsZycord — a peer-to-peer network of self-certifying state transitions.
⚡ REAL SCALABILITYBorn doing 90 transactions per second and grows, with real usage, past 1,000,000. No architecture swap along the way, no "sharding in 2029", no committee deciding. The engine that carries the top of that curve already runs today on an ordinary desktop — measured, and re-measurable by you.
⚙ PARALLEL EVM — the first real oneOther chains parallelize execution
inside each computer, but every computer still re-executes everything, all of them at once. Here the
network itself is parallel: each machine verifies a share, none has to redo the others' work. Your Solidity contracts port with few changes.
🔒 PRIVACY AND FREEDOMPayments with hidden value and a disposable address every transaction. Censorship resistance. An EVM where heavy cryptography is usable in a way never seen before — ZKPs, post-quantum algorithms, schemes not yet invented. The network where the next decade's cryptography already has its seat reserved.
⚖ FAIR LAUNCH — actually, not as marketingZero premine, zero founder allocation, zero ICO, zero admin keys. Not one coin exists before block 0, and the only way to get one is to mine it on an ordinary CPU.
WHY MINE ZYCORD▸ You enter at block 0 — and nobody entered before you. No premine, no allocation, no ICO, no admin key. The fairest launch a network can have: the only way to hold the coin is the same work that is open to you today.
▸ The computer you already own is competitive. RandomX mining — the same algorithm securing Monero — built for ordinary CPUs. No ASIC farm to crush you, no top-shelf GPU as the price of entry.
▸ 97% of every block goes to whoever secures the network. No halving cliffs: emission steps down smoothly, a tiny fraction per day, and after ~12 years becomes a perpetual tail — mining never stops paying. (The other 3% sits sealed in a treasury with no owner and no key, which only a future community can open — or nobody ever does.)
▸ Miners are not disposable here. When the network evolves to proof of stake, whoever mined and bonded their rewards from Era 0 gets
priority in the first operator slots. On every other chain the miner is discarded at the transition. Here he becomes the backbone of the next phase.
▸ You are mining the right network early. The value of a chain that scales 12,000x without choking, runs the first genuinely parallel EVM, and ships audited privacy is not in what it does today at 90 TPS — it is in who showed up before the rest of the world noticed. Block 0 is the earliest "before" there is.
HOW IT WORKSEvery fast blockchain today has a hidden ceiling. The more people use it, the bigger the machine every node has to be — until only a datacenter can keep up, and the "decentralized network" is half a dozen servers. That is not an engineering failure; it is the model. As long as every computer on the network must redo the work of all the others, growing means evicting the small.
What Zycord fixes: it breaks that coupling. Every transaction arrives with its own receipt stapled to it — it declares "I read this, I wrote that" and carries the proof. Checking whether it is valid never requires consulting the network's history: the transaction's own bytes are enough. And whatever depends on nothing else can be checked
in parallel — a thousand transactions, a thousand cores, each checking its own, and it can even be accelerated on a GPU. The more machines join the network, the more verification capacity exists. For free.
Only one thing has to happen in a queue:
writing the result into the ledger. After the parallel checking, one sequential step remains — walk the list and apply whatever still holds, skipping whatever conflicted. No signatures, no code execution, no cryptography: comparing and adding numbers in memory. A single core of an ordinary desktop handles the equivalent of
294,000 transactions per second at that step — 9.9 milliseconds inside a ~2-second block. The bottleneck that stalls every other chain measures under 1% of block time here.
And because checking and writing are different jobs, they carry
different prices: two gas markets. Writing to the ledger — scarce, sequential — has one price. Verifying — abundant, growing with every core that joins — has another, far cheaper one. That is where everything in the pillars above comes from: the scaling without a choke point, the parallel EVM, and cheap heavy cryptography. They are not four loose features — they are four consequences of a single decision.
Conflicts stall nothing: the late transaction is skipped and its insurance pays the bill — spam is expensive by construction. And the network is born proof-of-work so the launch is fair, migrating gradually to proof of stake with the first-hour miners at the front of the queue.
MEASURED ON AN ORDINARY DESKTOPSequential fold 883,000 ops/sec on ONE core (~294K certs/sec)
Block of 2,900 certs 1,963 ms to verify (parallel) | 9.9 ms to apply
Parallel share 99.5% of block time
Reference implementation, ten-core x86, source published. Rebuild it, re-run it, and post your figures in this thread — including if they are worse.
The genesis network ships that capacity throttled to ~90 certificates/second on purpose. The ceiling is a consensus function of measured demand: it can at most double per year of full, healthy blocks, toward the structural ~1.1M/sec. No vote, no governance event, no lever for anyone to pull — and no way to raise it except sustained real usage.
SPECIFICATIONSTicker ZCD
Distribution 100% proof-of-work mined. Nothing else.
Algorithm RandomX (CPU)
Consensus Proof of work, Nakamoto rules
Block time 30 seconds
Epoch 2,880 blocks (~1 day)
Genesis block reward 21 ZCD
Emission E(n) = max(tail, E(n-1) - E(n-1)/1054) per epoch
Rate halves every 2 years - exactly, no cliffs
Tail emission 0.33 ZCD/block, perpetual, from ~year 12
(height 12,602,880; ~0.55%/yr of supply, falling)
Supply at tail 62,744,838.47 ZCD scheduled
62,744,817.47 issued: genesis pays no coinbase
Premine None
Founder allocation None
ICO / investor round None
Admin keys None
Treasury 3% of subsidy, sealed until Era 2
No key, no address, no quorum at genesis
Block size 2.5 MB at genesis, elastic
Genesis throughput ~90 certificates/second, elastic
Certificate TTL 240 blocks (~2 hours)
No halving cliffs: the reward steps down once per epoch by a fraction too small for any single block to feel. The tail exists because security is a permanent expense. The 21 ZCD gap between scheduled and issued is the genesis block itself — a reproducible genesis must credit no address, so block 0 pays no one.
THE ERASEra 0 is deliberately small. With no admin keys there is no pause button, so every line in the genesis binary is a line that could kill the network with no remedy. Nothing ships whose only caller is a future era.
Block 0: RandomX mining. Native assets — ISSUE, MINT, TRANSFER, RETIRE — with no VM involved. Tips as a protocol primitive: ten thousand tips to one address in one block are ten thousand commutative additions, zero conflicts, zero skips. Every certificate self-insured, so you can transact with no counterparty from the first block.
Era 1 — height, then bonded stake ≥ 1% sustained: the parallel EVM (Solidity ports at source level), bonded underwriters, application sequencers, forced-inclusion queue, checkpoint finality.
Era 2 — height AND stake ≥ 10% sustained for 30 epochs: PoS block production; the PoW reward retires on a ~90-day ramp that pauses if finality stalls. Treasury opens under a 3-of-5 pinned by hard fork.
Era S — two independent published audits plus an adversarial public testnet: confidential payments. It does not switch on before it is ready.
Thresholds are measured on-chain — never calendar dates, never a vote.
ON THE LAUNCHI am not raising funds. There is no ICO, no sale, no reserved tokens.
Nothing stays with the creator — I mine block 0 in the same queue as you. This network is being handed to the world, and what I want to build on top of it is not a treasury: it is a community that takes it further than I can alone.
Genesis is reproducible from the published source — the absence of privilege is not a promise, it is a line you check. Published with the code is the complete, unedited adversarial review history of this design: the attacks that changed the rules, the ones that were refuted, and why.
The mainnet date is public two weeks ahead so block 0 is reachable by anyone who wants it. Same binary: a mainnet node started early waits for genesis exactly as the testnet one does today.
On the treasury, since this is where projects usually lie: 3% of every block subsidy accrues to a cell sealed until Era 2. At genesis there is no key, no address, no quorum, no emergency path. A premine is coins, an address, and a key that exist at genesis and belong to someone — genesis here contains none of the three. If no community ever arrives to pin a 3-of-5 by hard fork, the cell never opens and those coins are simply never issued. Whether that day comes is not the author's call.
COMMUNITY, DONATIONS, AND A REQUESTI am an anonymous developer. I will launch this network and maintain it for as long as it takes — but it was designed from day one not to depend on me, and the goal is for the community to take over every part of it.
Donations fund development (Eras 0 and 1 are donation-funded only — public proposals, open budget, unspent amounts returned). I take no allocation and hold no privilege over any other user; these addresses are the only way I am paid for this work:
BTC: bc1q99k4mfydge2glhwa3wf2nmjwc67xrtfqjvygwc
ETH: 0x14825761bf3F2D53165F3aD6EbEFFECDbb33a097
ZCD: published after mainnet genesis
to run community channels (Telegram, Discord, Reddit — community-run and explicitly unofficial, see the FAQ), translations, documentation, pools, and above all people willing to attack the design and publish what they find. Post in this thread.
Official announcements live here and only here, signed:
GPG: E724 39CE DD85 11F9 D607 550B 87FD 60D5 EB4A 0B29
FAQQ: When exchange?Never asked for, never paid for, never announced here. Testnet coins are worth nothing by design. Where the mainnet coin trades is the market's business, not the author's — there is no company to sign a listing deal and no fund to pay for one.
Q: Pools?None exist at launch and none are official. The node solo-mines out of the box, and at genesis difficulty that is the sensible way in. If pools appear they are third parties; apply the skepticism you would anywhere.
Q: Bounties? Airdrop? Signature campaign?No, no, and no. Nothing here pays for promotion. If someone offers you Zycord for shilling, it is not coming from this project.
Q: Is this another "1M TPS" chain?The claim is narrower and falsifiable: verification needs no state, therefore it parallelizes without bound, therefore per-node cost can fall as the network grows. The network ships at ~90 certs/sec and the ceiling only rises on sustained real usage — nobody, including me, can raise it by decree. The measured numbers are in §15 of the whitepaper with the source to re-run them. If your box disagrees, post the figures.
Q: How is this different from Monad, Sei, or any other "parallel EVM"?Those parallelize execution inside a node — every node still re-executes every transaction, so the state-I/O wall stays exactly where it was. Here validity is a pure function of a transaction's bytes, so verification splits across the whole network instead of being repeated by all of it, and the only sequential stage touches memory rather than a database. Different wall, not a faster car into the same one.
Q: Why RandomX? Botnets will come.They will; every CPU-minable coin has fought them and we do not expect to be the exception. The trade is taken with open eyes: a distribution skewed by botnets is still broader than one decided in a sale, and keeping the laptop you already own competitive is the entire reason RandomX exists.
Q: What happens when transactions conflict?The later one in fold order is skipped, its fee is burned, and the block stays valid — nothing ever "fails" halfway. Payments, mints, and tips use commutative deltas and cannot conflict at all; only exact-read contract state (order books, AMMs) contends, and that is what application sequencers exist to serialize off-chain in Era 1.
Q: Smart contracts at launch?No — Era 0 is native assets plus mining, on purpose: no admin keys means no pause button, so the genesis surface is kept small enough to audit completely. The parallel EVM arrives in Era 1 with a delta-first standard library pre-deployed. Solidity, its compilers and auditors carry over; raw wallet compatibility is not claimed and we do not pretend otherwise.
Q: Known problems?Named in the whitepaper rather than left for you to discover: the spent-address registry grows forever (shared with every nullifier-set design, and the binding constraint at high throughput); bodies are chain data, so a block producer at the top of the capacity curve is datacenter-class on bandwidth alone; sequencers see their own application's order flow first — its MEV is captured by the application, explicitly; verification sampling is roadmap, not launch; and §12 lists the confidential-payment open questions by name.
Q: Discord? Telegram?Community channels are welcome and will be built
by the community — I am looking for volunteers for exactly that. But none of them is official, by design: a chat has an admin, and an admin can silence people and erase history. Every official announcement goes in this thread, signed with the key above, and nowhere else. If someone in a chat says "official announcement" without a signed post here, it is a lie.
Q: Who are you?Simstoshi. That is the whole answer, and it is the point: nothing in this design requires trusting me. No admin keys to abuse, no allocation to dump, no operator load-bearing for safety — and a forced-inclusion path that keeps the network alive even if every operator disappears, author included. Every official release and announcement is signed with the key above.
SIGNED ATTESTATIONThe facts an impersonator would alter — the donation addresses and the canonical URLs above all — are pinned below and signed with the project key. Copy the block verbatim (it sits in a code box so the forum preserves it byte for byte) and run
gpg --verify on it. If a repost of this announcement anywhere shows different addresses or different domains, this block is what proves which set is real.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
ZYCORD — OFFICIAL LAUNCH ATTESTATION
Simstoshi
Ticker: ZCD
Testnet genesis: 2026-08-30T00:00:00Z
Mainnet genesis: 2026-09-15T00:00:00Z
Both instants are the genesis_time in the published parameter file. They are
consensus values, not announcements: a node that disagrees is on a different
chain.
Release signing key (all binaries, all announcements):
E724 39CE DD85 11F9 D607 550B 87FD 60D5 EB4A 0B29
Canonical locations. Anything outside this list is not this project:
Site: https://zycord.com/
Source: https://github.com/thesimstoshi/zycord
Releases: https://github.com/thesimstoshi/zycord/releases
Whitepaper: https://doi.org/10.5281/zenodo.22167490
Explorer, testnet: https://testnet.zycord.com/
Explorer, mainnet: https://explorer.zycord.com/
Donation addresses. These are the only two. There are no others, in any
currency, on any platform:
BTC: bc1q99k4mfydge2glhwa3wf2nmjwc67xrtfqjvygwc
ETH: 0x14825761bf3F2D53165F3aD6EbEFFECDbb33a097
There is no ICO, no presale, no token sale, no premine, no founder allocation,
and no admin key. Nobody is authorised to collect funds on behalf of this
project. Any address that is not one of the two above is fraudulent.
No official chat channel exists on any platform. Community channels are
community property and are not official. Every official announcement is a post
signed with the key above; anything else is fraudulent regardless of where it
appears or who appears to be saying it.
-----BEGIN PGP SIGNATURE-----
iHUEARYKAB0WIQTnJDnO3YUR+dYHVQuH/WDV60oLKQUCapOZBQAKCRCH/WDV60oL
Kfu0AP91jRk/8W0MfkW2pMYoOrVa4rnWJZ6ucPltBambZrQp9gD/US8kDznDQrlh
oPiXn4Op7d5ZRblCb63OYvsscGKnkAA=
=Si6n
-----END PGP SIGNATURE-----
Vires in numeris. Strength in numbers, not in name.
— Simstoshi
