CoinCync (CYNC)
A private-by-default proof-of-work chain, built from scratch in Rust.
Public testnet is live — and we want node operators and testers.
What it isCoinCync is a privacy cryptocurrency written from scratch in Rust. Every transaction is private
by default — not opt-in: ring signatures (CLSAG), confidential amounts (Bulletproofs+) and one-time stealth addresses are mandatory at the protocol level. The aim isn't to be the first privacy coin — it's to be a carefully built, independently verifiable one, and to ship the layers others stop at: a zero-knowledge shielded pool, selective-disclosure proofs, and open experiments on the proof-of-work itself.
This is our first public call for help. The testnet is running, and we want people to
run nodes, mine, and break things before we go anywhere near mainnet.
Why test it- Private by default — stress real ring / stealth / Bulletproofs+ privacy on a live network, not a whitepaper.
- CPU-mineable (RandomX) — no ASICs, no GPUs. No premine, no dev tax.
- A live PoW experiment — we're running Bobtail, a multi-sample PoW (K=20 shares/block) that should sharply cut block-time variance. It runs in read-only Observe mode on our fleet right now — measuring what it would do on real traffic, changing nothing about consensus. It's compiled out of the public release, so mining is unaffected; we'll publish the Observe results. Want to run the experimental build and join in? Ask in Discord.
Run a node in ~2 minutesGrab
coincync-linux-x86_64.tar.gz (or
coincync-windows-x64.tar.gz) from the
releases page, then:
mkdir coincync && tar xzf coincync-linux-x86_64.tar.gz -C coincync && cd coincync
chmod +x coincync-node coincync-wallet coincync-rig cyncswap
# run a node — auto-connects via built-in seeds, syncs from genesis
./coincync-node --network testnet
It finds peers and starts syncing immediately. Optional manual seed:
--addnode 2.29.34.197:28080Mine (two ways — both CPU / RandomX)Make a payout address first:
./coincync-wallet --network testnet create
./coincync-wallet --network testnet address # your tCYNC address
Simplest — the built-in node miner:
./coincync-node --network testnet --mine <your-tCYNC-address>
Full miner — the tunable rig against your own local node:
./coincync-node --network testnet & # keep a node running
./coincync-rig run-solo --node http://127.0.0.1:28081 \
--address <your-tCYNC-address> --network testnet --threads 8
[b]How you can help (what we're looking for)[/b]
[list]
[li][b]Node operators[/b] — run a full node, ideally inbound-reachable (forward P2P port [tt]28080[/tt]). Reliable community nodes get listed as seeds.[/li]
[li][b]Miners[/b] — CPU-mine and tell us about hashrate, stability, and block-time behavior.[/li]
[li][b]Privacy testers[/b] — send transactions, try the wallet, poke at the ring / stealth / range-proof paths.[/li]
[li][b]Bug reports[/b] — crashes, sync stalls, reorg weirdness, anything surprising. GitHub issues or Discord.[/li]
[/list]
[spoiler=Specs]
[code]
Ticker CYNC
Algorithm RandomX (CPU-friendly)
Block time 120 s target
Difficulty ASERT (dual-window)
Max supply 100,000,000 CYNC
Emission smooth decay, NO halvings — ~50 CYNC first block,
tapering to a 0.6 CYNC tail emission
Decimals 12 (1 CYNC = 1,000,000,000,000 atomic)
Ring size 16 (11 during bootstrap < block 10,000; max 32)
Premine/dev tax NONE — 0%, enforced in code
Shielded pool Lelantus-Spark — live on testnet since block 29,000
P2P / RPC ports 28080 / 28081
Release v1.1.4-testnet
[/spoiler]
[spoiler=Don't trust — verify]
# your binary matches the published build:
sha256sum -c SHA256SUMS.txt
# you're on the same consensus rules as the network:
./coincync-node --version
# → consensus-fingerprint testnet: fc428e86...
[/spoiler]
Links
This is a testnet. Coins have no value and the chain may be reset. Everything here is experimental and pre-mainnet — Bobtail is measuring, not enforced. The code is open and the chain is independently verifiable: run your own node and check. Mainnet is targeted for March 2027 — we'd rather ship it right than ship it early.
Come run a node, mine a few blocks, and tell us what breaks. That's exactly the point.[/code]