CacheCoinCCCN Mainnet genesis block 25 September 2026, 18:25 UTC
CacheCoin is a CPU-mined proof-of-work coin, with no premine and no central operator. It mines with RandomX on ordinary processors, puts half of every fee into a reservoir for small miners, holds back re-organizations deeper than five blocks and relays transactions over Tor. Every figure here is reproducible from the repository.
Scroll or drag to follow the chain
25 September 2026, 18:25:18 UTC. The supply starts here, at zero. Every coin that will ever exist is mined after this block.
1bc3387d50988b4b653389516f1d2b3672cffef48f124a3b8ff7b1ac3c1e3efa
The launch record lists the first blocks and the public seed.
The first 720 blocks pay 5 CCCN each, twelve hours at the one-minute target. Blocks 1–60 are mined at minimum difficulty. From then on LWMA-1 retargets every block over a 60-block window.
From here the reward is 10 CCCN. Every block is proof of work in RandomX v1 with one fixed key, an algorithm built around the large caches and fast memory of desktop CPUs. Nodes verify each header once, in light mode, in about 20 ms.
The miner who finds a block keeps its reward and half of its fees. The other half settles into a reservoir, and anyone mining can claim a share of it with an entropy ticket, a proof sixteen times easier than a block.
A miner that never finds a block can still earn a share, in any epoch that collected fees.
A node will rewrite up to five of its own blocks to follow a heavier chain, and no more. A branch it turned away is taken back once that branch runs more than thirty-five blocks past the fork. The count is taken on the branch itself, so every node lets go of a split at the same height.
Every 40,320 blocks, about four weeks, the reservoir is shared equally among the tickets of the epoch just ended. Each ticket is paid in the block exactly one epoch after the one that carried it, so payouts arrive one block at a time across the next four weeks.
The reference node speaks over Tor and carries no DNS seeds. With shunkobroadcast, a signed payment is handed to two unrelated nodes over single-use connections, and they announce it as their own.
This hides which node first announced a payment from anyone watching for the first announcer. It claims no protection against a global observer, and amounts and addresses stay public.
About two years in, the reward falls to 5 CCCN, and it halves again every 1,051,200 blocks after that. By then 10,508,405 CCCN will have been mined, 49.99% of the final supply.
After thirty halvings the reward reaches zero, some sixty years from genesis. The supply stops at 21,020,399.86334400 CCCN, a fraction of a coin under the cap.
From there the chain runs on fees alone, half to the miner and half through the reservoir.
Research
The test suites settle what one machine can check. These questions need a running network, outside review, or both.
No external audit has been done. SECURITY.md lists what the suites do not cover: transaction and signature validation, power loss mid-flush and chainstate corruption, and independent verification of the proof of work.
At an exact 50/50 split each side mines at half rate, so one reaches 36 blocks past the fork in about 72 minutes on average, with a longer tail when the split is uneven. An operator can end it sooner with invalidateblock. Until this has been observed on the live network, treat a payment as final after 10 confirmations, and 60 or more for large amounts.
Consensus enforces the accounting: payouts never exceed collected fees. Ticket grinding, fee gaming and payout edge cases have not had an external monetary review.
A miner holding the full 2 GiB RandomX dataset is several times faster per core than the built-in light-mode miner, and a fixed key makes specialized hardware easier to build than a rotating one would.
Shunko hides the first announcer, not the payment. Amounts, addresses and timing stay on the ledger, so a fresh address for every payment still matters.
Two routes in
On Windows, a portable package bundles the node, Tor, a launcher and a window. On Linux, or on Windows through WSL2, you build from source, which is the route the repository’s test suites cover.
Take the package, SHA256SUMS.windows.txt and its .asc signature from the Releases page. The checksums are signed with the release key, fingerprint 7D85 B6F3 64CC 47BA 9209 BB54 F750 900C 7C91 1728, published as release-key.asc. A matching hash shows the download arrived unchanged, and the signature shows who signed the checksums. Verify Download.cmd inside the package runs these checks in one step.
Get-FileHash .\CacheCoin-Windows-*.zip -Algorithm SHA256 gpg --import release-key.asc gpg --fingerprint releases@cachecoin.org gpg --verify SHA256SUMS.windows.txt.asc SHA256SUMS.windows.txt
The executables are unsigned, so SmartScreen shows “Windows protected your PC” on first launch. Choose More info, then Run anyway, only after the hash matches.
Unzip to a folder of your own and double-click Start Node.cmd for the node alone, or CacheCoin App.cmd for the window. If Tor isn’t already running, the bundled copy starts. The first start takes a few minutes while the node finds peers over Tor. Chain data and the wallet live in %APPDATA%\CacheCoin.
Which entry point you open sets the mode: Start Node.cmd runs the node alone, the safe default, and Start Mining.cmd runs the node, the miner and a peer that accepts incoming Tor connections, capped at 32 connections and about 5 GB a day. Node-only mode offers the same incoming option as a choice. Stop it from the tray icon with Stop CacheCoin, because closing the window can leave the node running.
Make the wallet first: Create New Wallet.cmd runs offline and writes a new address and its private key to Wallet\ (or shows it for you to copy down). Start Mining.cmd then asks how many processors to use and where the coins go, either that wallet or a pasted cccn1 address the node checks first; mining never uses the node’s wallet. There is no seed phrase: the file is the wallet, so keep it offline and away from the app’s disk. Whoever holds it can spend the coins, and nobody can recover them for you.
The Windows package is outside the repository’s automated test suites (CI smoke-tests it in regtest) and the build is not reproducible. Verify Download.cmd checks the manifest, every file hash and the checksum list in one step, and PROVENANCE.txt and TOR-PIN.txt record where every file came from. Verifying a download and how the package is built are written up in the repository.
The build takes thirty to sixty minutes. The script checks that it is building Bitcoin Core v31.1 and RandomX at the exact commits it expects, applies the change series in patches/ to that base, stops on any mismatch, and installs cachecoind and cachecoin-cli to /usr/local/bin.
git clone https://github.com/triplecN/CacheCoin cd CacheCoin bash scripts/build_linux.sh
The test suites run on throwaway data directories and never mine on mainnet. Run them one at a time, because they share ports. Without a running node, scripts/reproduce_genesis.py rebuilds the genesis header and checks its hash.
B=~/cachecoin-build/cachecoin-v31.1 python3 tests/functional_regtest.py $B/build/bin/bitcoind python3 tests/per_regtest.py $B/build/bin/bitcoind python3 scripts/reproduce_genesis.py
The node connects through Tor at 127.0.0.1:9050. Tor Browser listens on 9150 instead. If the ports don’t match, the node stays at zero peers without saying why.
No seeds are compiled in. The shipped config already routes everything through Tor; add the community seeds, relays that do not mine. A connection count of 1 or more means the node has reached the network. If the seeds ever change, the README lists the current ones.
mkdir -p ~/.cachecoin cp config/cachecoin.conf ~/.cachecoin/cachecoin.conf SEED1=ag7rydtma6dt5fonz76sdbecrbugq3uln7cc6ddvg2c2jngio4lw6mid.onion:29333 SEED2=7uodchunfsykltytzwhpq6plvlxsulhtawjisrvcxzhljfdsmwnjbead.onion:29333 echo "addnode=$SEED1" >> ~/.cachecoin/cachecoin.conf echo "addnode=$SEED2" >> ~/.cachecoin/cachecoin.conf cachecoind -daemon cachecoin-cli getconnectioncount cachecoin-cli getblockchaininfo
Create a wallet and back it up offline before mining; the wallet guide shows how, and losing the descriptors loses the coins. The built-in miner runs RandomX in light mode, one core per call. Keep ticket searches bounded: the default of 1,000,000 tries can outlive the CLI timeout. scripts/ticket_loop.sh runs the search in a loop.
cachecoin-cli createwallet "main" ADDR=$(cachecoin-cli -rpcwallet=main getnewaddress "" bech32) cachecoin-cli validateaddress "$ADDR" cachecoin-cli generatetoaddress 1 "$ADDR" cachecoin-cli -rpcclienttimeout=0 generateperticket "$ADDR" 20000
At the 60-second target, a miner with 1% of the network’s hash rate finds a block about every 100 minutes on average, and one with 0.1% about every 17 hours. A day or two without a block is normal.
There is no seed phrase, so the wallet file and its descriptors are the only copy of your coins; back them up offline before mining. A ticket pays the address it names one epoch later and cannot be redirected, so mine one to a fresh address and confirm it with validateaddress before running a loop.
Official sources
The official sources are this site and the GitHub repository. The project sells nothing and takes no payments; anything presented otherwise does not come from it. Release files are signed with the key published as release-key.asc, and its fingerprint is recorded in doc/release.md.
The node is Bitcoin Core v31.1 with the CacheCoin changes in patches/; the patch fingerprint recorded in doc/verification.md is the anchor for a verified build.
Questions and security reports go to the repository’s public issues, where anyone can read and answer them.
CacheCoin is provided as is. Nothing on this site is financial advice, an offer or a promise of return.