The first published build. The public testnet is live and mining.
Which file do I want?
| your machine | to join the testnet and mine | to verify the source builds |
|---|---|---|
| Linux, Intel/AMD | zycord-0.1.0-linux-amd64-randomx.tar.gz |
zycord-0.1.0-linux-amd64.tar.gz |
| Linux, ARM | zycord-0.1.0-linux-arm64-randomx.tar.gz |
zycord-0.1.0-linux-arm64.tar.gz |
| macOS, Apple Silicon (M1–M4) | zycord-0.1.0-darwin-arm64-randomx.tar.gz |
zycord-0.1.0-darwin-arm64.tar.gz |
| macOS, Intel | not in this release — see below | zycord-0.1.0-darwin-amd64.tar.gz |
| Windows, Intel/AMD | not in this release — see below | zycord-0.1.0-windows-amd64.zip |
| Windows, ARM | not in this release — see below | zycord-0.1.0-windows-arm64.zip |
Not sure which Mac you have? Apple menu → About This Mac. "Apple M1/M2/M3/M4" is
Apple Silicon; "Intel" is Intel.
There is also a desktop wallet — zycord-wallet-0.1.0-* — for Linux, Windows
and Apple Silicon. You do not need it: zcd ui opens the same wallet in your
browser and ships in every archive above.
Why two archives per platform
The -randomx one is the client. It carries the proof-of-work engine, so it
can verify blocks, join the testnet and mine.
The plain one cannot join a network at all, and that is by design rather
than an omission. It is pure Go and byte-for-byte identical no matter who builds
it, which is what lets a stranger rebuild this tag from source and compare
hashes. That property is impossible with the C++ engine compiled in. So the
reproducible archive exists to be checked, and it runs --devnet only.
If you take the wrong one, the node tells you so at startup and names the file
you wanted. It does not fail silently.
zcd version # the engine this binary carries
zcd params # the engine the network requires
Windows and Intel macOS have no -randomx build in this release. Windows
because the release pipeline has no leg for it yet; Intel macOS because GitHub
stopped serving the runner image this release's matrix asked for. Both are being
fixed. Until then those two platforms can build one locally with
make build-randomx, or run the devnet.
Verifying what you downloaded
The strongest check here needs no keys and no keyring: rebuild it yourself.
The plain archives are pure Go and byte-for-byte identical no matter who
compiles them. SHA256SUMS.binaries lists the hash of each binary inside each
archive, so you can compare against your own build:
git clone <this repository> && cd zycord && git checkout v0.1.0
make build
sha256sum bin/zcd bin/zycorddThose two hashes appear in SHA256SUMS.binaries under your platform. If they
match, the archive contains this source and nothing else — a stronger statement
than any certificate makes. A certificate says some legal entity paid for
this; a reproducible build says this is what the source compiles to, and
anyone can check.
The archive checksums are published as well:
sha256sum --check --ignore-missing SHA256SUMS # the reproducible tier
sha256sum --check --ignore-missing SHA256SUMS.randomx # the client tier--ignore-missing is not leniency: each list covers every archive in the
release and you downloaded one of them.
What this release does not have, stated plainly. The -randomx archives are
cgo builds, so nothing can reproduce them byte for byte — the check above does
not reach them. From the next release onward every archive also carries a
GitHub build-provenance attestation, verifiable with gh attestation verify,
which closes exactly that gap. This release predates it: the workflow that
produces it landed after this tag was cut, and a tag builds from its own
workflow. For v0.1.0 the checksums are what you have for that tier.
Your operating system will warn you
An unsigned executable is blocked by SmartScreen on Windows and by Gatekeeper on
macOS. There is no certificate here and there will not be one: an Authenticode
or Apple Developer ID certificate is a certificate authority attesting to a
verified legal identity, and this project is published pseudonymously.
Buying one would undo that in a single step.
Windows — SmartScreen shows "Windows protected your PC". Click More info,
then Run anyway.
macOS — Gatekeeper refuses the first launch. Right-click the binary and
choose Open, then confirm; or clear the download flag with
xattr -d com.apple.quarantine <file>.
Neither warning is about the file being damaged or unsafe. It is about the
absence of a paid identity attestation. Check the attestation or the checksum
above instead — those tell you something a certificate never does, which is what
the bytes actually are.
Running from a terminal, which is how a node is run anyway, avoids the dialog on
both systems.
The public testnet
Live since 2026-08-30T00:00:00Z. Rebuild these values yourself with
zcd genesis --testnet — they are a property of the binary, not of this page.
network zycord-testnet
chain id 2
params hash 0xce415e2d992c44d60adc0ae0b75775901b26c29e4acba081728e9ed3b505915a
genesis id 0x0c3cdc8b74cd65eae9604f49ee206a952a089b2c025d4f04a90fa38072738935
state root 0x3c8f97c8ef50991522feb4f89cd15e8fe1e0b98cec5adb1a2344ee64115a0df8
genesis time 1788048000
allocations 0
allocations 0 is the fair-launch claim, and it is checkable rather than
asserted: block 0 credits nobody, not even the treasury. No premine, no founder
allocation, no investor round.
Start it whenever you like. A node started before a network's first block
waits for it and begins on its own — nothing to schedule, nothing to restart.
tar xzf zycord-0.1.0-linux-amd64-randomx.tar.gz
cd zycord-0.1.0-linux-amd64-randomx
./zcd wallet new --out miner.json
./zycordd --testnet --dir ./data --mine --payout $(./zcd wallet address --key miner.json)It finds the network on its own; no peer address to copy.
Mainnet has not launched
Chain id 1 is pre-genesis and its parameters are not frozen. There is no
coin. Anyone selling you ZCD today is scamming you.
Known limitations
- No
-randomxbuild for Windows or Intel macOS, as above. - No Homebrew tap or Scoop bucket yet.
- The multi-day chaos soak has not been run against this build; it is the
thinnest evidence in the project anddocs/DEFERRED.mdsays so. - The public testnet has a single bootstrap seed, and it is project
infrastructure. That is recorded as a standing exception rather than as a
solved problem.