CacheCoin (CCCN) 0.2.1 for Windows

CacheCoin (CCCN) 0.2.1 for Windows

Published 2026-10-09. This is the eighth portable Windows package of CacheCoin:
cachecoind.exe and cachecoin-cli.exe from the tagged tree, the PowerShell
launcher, the window (CacheCoin.exe), the documentation and the pinned Tor
Expert Bundle.

The binaries are unsigned and this build is not reproducible. Read the whole
note before running.

Why 0.2.1 exists

A minor packaging fix. The two node executables in this ZIP are the ones CI
built; they carry the project's product name and icon in their Windows version
resources, and the CI job now fails if that metadata is missing. The 0.2.0 ZIP
was assembled from a locally built set where that step had not run, and its
PROVENANCE.txt described the package as if it had. Source, patch fingerprint and
consensus behavior are unchanged.

0.2.0 is frozen as published.

Files

• CacheCoin-Windows-0.2.1.zip
  sha256: 4cd664b9bcb6ca0319e8bdf895e93815f74508d6bd69d6260afdf0cd5e7ee1f7
• SHA256SUMS.windows.txt (sha256 of every file in the package)
• SHA256SUMS.windows.txt.asc (detached GPG signature of the checksum file)
• raw executables for direct hashing: cachecoind.exe
7f933882ee632c09347dd5bede51c9251c1976e3868a9df754329db4f9265200,
  cachecoin-cli.exe
8cb5098b9f65736025357a7dc408e0a058dba027321c763f4ef4448084da725b,
  CacheCoin.exe
68e1f30d742bd55e4bbf0c52fb648c771cba1d54ffb371d5e92ace1cd0d30267
• PROVENANCE.txt, TOR-PIN.txt (also inside the package)

Signing key fingerprint:
7D85B6F364CC47BA9209BB54F750900C7C911728
(CacheCoin (CCCN) Releases releases@cachecoin.org; public key also in the
repository as release-key.asc and in doc/release.md).

Provenance

• Base pins: Bitcoin Core v31.1, commit
  9be056a8a72b624dae9623b2f7bded92c2a21c91; RandomX commit
  7607fb2faed24d5a679e139a9828d194bbc644a4.
• Patch fingerprint: 6a89aa144620ea2c019f2678ea80ae8b2de45544bc64d871cd3bb2fefcf1ddda
  (cat patches/*.patch | sha256sum). Compare it with doc/verification.md.
• The release tag windows-0.2.1 is a signed Git tag; verify it with
  git tag -v windows-0.2.1 after importing release-key.asc. Commit
  ca67356 (full hash on the tag page).
• Tor Expert Bundle 15.0.24 (tor 0.4.9.13); its files are hashed in
  version.json; TOR-PIN.txt carries the archive, its sha256 and the key.

Verify before running

Get-FileHash CacheCoin-Windows-0.2.1.zip -Algorithm SHA256

Unpack it, then:

gpg --import release-key.asc          # from the repository or the release page
gpg --verify SHA256SUMS.windows.txt.asc SHA256SUMS.windows.txt
sha256sum -c SHA256SUMS.windows.txt

The gpg --verify output must name the fingerprint above. The sha256 values
prove the files arrived unchanged; the signature proves the checksum file came
from that key. Neither proves the binaries can be rebuilt from source.
Verify Download.cmd performs the same three checks in one step.

What this is

A portable Windows package. The node is Tor-only; the launcher starts a bundled
Tor if none is running. Data lives in %APPDATA%\CacheCoin, not ~/.cachecoin.
Start Node.cmd runs the node; Start Mining.cmd runs node + CPU miner + peer;
CacheCoin App.cmd opens the window; Check Status.cmd reports height, peers
and disk (needs a running node); Create New Wallet.cmd makes a wallet offline.
New users should read README-Windows.txt and docs\START_HERE.txt. Mining
also accepts incoming Tor connections (default cap: 32 connections, about 5 GB
uploaded per day). There is no daemon mode.

Version strings: the package is 0.2.1; the node executables report the upstream
31.1.0; the window reports 0.2.0 because it did not change in this release.

Honest limits

• Not reproducible. The sha256 values prove only that the files arrived
  unchanged in transit; the GPG signature proves the checksum file came from the
  CacheCoin release key. Nobody can yet rebuild the exact bytes; compare the
  patch fingerprint, not the binary hash, when you rebuild.
• The executables are unsigned at the OS level (no Authenticode).
• SmartScreen. Windows will show "Windows protected your PC" on first
  launch; choose More info, then Run anyway, after checking the sha256.
• Outside the suites. The Windows .exe files are not covered by the
  repository's automated test suites. CI starts the node in regtest, verifies
  the genesis, mines one block and runs the wallet flow with a clean PATH.
• Integrity check scope. The fail-closed check covers a swapped file inside
  a genuine package. It cannot cover a fully forged package that also replaces
  version.json; only the ZIP hash and the GPG signature catch that. The
  remaining accepted limits are listed in SECURITY.md, section "The Windows
  package"; the file-hash check cannot see a TOCTOU swap or an alternate data
  stream.
• No daemon mode. cachecoind -daemon does not exist on Windows (MinGW has
  no fork()); run it in a window or under Task Scheduler. cachecoin-cli -rpcwait still works.
• Mining is a lottery. Expect weeks without a block; it may never pay. The
  PER ticket system shares fees only when fees exist. Mining costs electricity
  whether or not it pays, and mining publishes this computer's .onion address.
• No financial advice. This is open-source software provided as is under the
  MIT license; nothing here is financial advice, an offer or a promise of return.