Repository navigation
v1.1.0-testnet — Shielded bridge activation (public testnet)
Pre-releaseCoinCync v1.1.0-testnet — Shielded bridge activation (public testnet)
⚠️ EXPERIMENTAL TESTNET PRE-RELEASE. This is not a mainnet launch.
This software runs on the CoinCync testnet only. Testnet coins have no
monetary value and the network may be reset. The code has not completed a
third-party security audit and has not been reviewed for legal or
regulatory compliance in any jurisdiction. It is provided as‑is, with no
warranty, as non‑custodial software you run at your own risk. Nothing here
is financial, legal, or tax advice. Do not use it to hold anything you value.
Mainnet remains parked pending a security audit and counsel review.
What this release does
Activates the Option‑B shielded bridge on the public testnet at a fixed
height — a coordinated testnet hard fork:
SHIELDED_TESTNET_ACTIVATION_HEIGHT = 29000
Below block 29000 the node is byte‑identical to the previous testnet build.
At/after 29000, the shielded operations become valid on testnet:
- shield‑in — move transparent funds into the shielded (Spark) pool
- shielded‑send — spend within the shielded pool
- unshield — exit the shielded pool back to a transparent output
Transparent CLSAG ring privacy is unchanged. The shielded pool is the new piece
being exercised live on testnet ahead of audit.
Consensus identity
- testnet consensus fingerprint:
fc428e8673379f07cc213b9a7aceb4c05d5433387113a02b818ba3e0ab3664ca - built from tag
v1.1.0-testnet(commit23dc8d7b)
A node whose coincync-node --version prints the fingerprint above is running
the canonical cutover build.
Assets (Linux x86‑64)
coincync-node— the full node (run one to join / relay / validate the testnet)coincync-wallet— CLI wallet (transparent + shielded operations)coincync-rig— optional solo miner (RandomX)SHA256SUMS— checksums for the three binaries
SHA‑256 (contents of SHA256SUMS):
2d055b9eb8ddfd0ea9e5c15622048235ef4a5a7cc7588c416f1e25c06db95fd9 coincync-node
c5d5499bee7f92d597d4347a1cbf11929ac83c139beee7f2e26cc9a4171da66b coincync-wallet
688c209c23eafcb17f5d3d7aea1cd30f0e88d3d011c59e08445f4417ff770ebc coincync-rig
The coincync-node hash above is byte‑identical to the node binary running
on the public testnet fleet — the release build is reproducible from the tag.
Signed checksums. SHA256SUMS is signed with the project's SSH key
(SHA256SUMS.sig). To verify the signature with the included allowed_signers:
ssh-keygen -Y verify -f allowed_signers \
-I 192831449+ghostrider1092@users.noreply.github.com \
-n file -s SHA256SUMS.sig < SHA256SUMS
# then: sha256sum -c SHA256SUMSVerify before you run
sha256sum -c SHA256SUMS
./coincync-node --version # expect testnet fingerprint fc428e86…64caJoin the testnet
./coincync-node --network testnet --data-dir ./cync-data \
--addnode 2.29.34.197:28080RPC binds to loopback (127.0.0.1:28081) by default — keep it there unless you
know your exposure model. The node will sync from genesis and mesh with the
public fleet. Upgrade to this build before block 29000 or you will fork off
the canonical chain at activation.
Build from source (if you'd rather not trust the binary)
git clone -b v1.1.0-testnet https://github.com/ghostrider1092/CoinCync.git
cd CoinCync
cargo build --release --features testnet --bin coincync-node --bin coincync-wallet
cargo build --release -p coincync-rig
./target/release/coincync-node --version # should match the fingerprint aboveThe same source is also published as the branch release/v1.1.0-testnet on the
testnet mirror.
Known scope / caveats
- Testnet only; no external audit yet; interfaces may change.
- Block timing can be bursty (low‑hashrate difficulty oscillation); this does not
affect safety. - Report issues on the repo.