Repository navigation
Common Foundry v1.0.7
Common Foundry v1.0.7
Node and wallet update, recommended for everyone running a node or the desktop wallet: catching up no longer stalls on slow or distant peers. Pool miners do not need to update. Network, launch plan, beacon round, wallets, consensus and monetary policy are unchanged; keep your chain data and wallet.
What changes
Catch-up stops waiting on slow peers
- A sync session stops asking a peer for more blocks after 30 seconds, keeps every block that already arrived and ends normally. A slow or far-away peer can no longer hold a node for a whole batch of 12 MB blocks.
- While catching up, the peer that delivered blocks fastest in the last round gets the first turn and most of the extra sessions; the others are still used in turn.
A fourth bootstrap peer
- New nodes and wallets dial the seed and three relays from their first round: St. Louis, Singapore and a new 1 Gbit/s relay in Falkenstein, Germany (
88.198.110.195:29444).
Fastest start: the chain bootstrap
New wallet, or far behind? Start from a signed copy of the chain (height 3201) instead of downloading and verifying every block from peers. The wallet then only syncs the newest blocks.
Windows wallet (needs about 40 GB free on C:):
- Install or upgrade the wallet to v1.0.7, open it once (create or unlock your wallet), then close it.
- Open PowerShell and run these two lines:
curl.exe -fLO https://github.com/JustAResearcher/CommonFoundry-Binaries/releases/download/chain-bootstrap-2026-10-05/bootstrap.ps1 powershell -ExecutionPolicy Bypass -File .\bootstrap.ps1
- When it prints
Done, open the wallet. It starts at block 3201 and syncs the rest in minutes.
The script downloads from Cloudflare (https://downloads.commonfoundry.ai/chain-bootstrap/mainnet-2026-10-05-h3201/), checks the release-key signature and every checksum, and replaces only the chain files. Your wallet and coins are not touched. If the download is interrupted, run the second line again to resume.
Linux node: stop the node, then run curl -fLO https://github.com/JustAResearcher/CommonFoundry-Binaries/releases/download/chain-bootstrap-2026-10-05/bootstrap.sh and bash bootstrap.sh <data directory>. Manual download and details: the chain-bootstrap-2026-10-05 release.
Already synced, or only a few hundred blocks behind? Just upgrade; v1.0.7 catches up at roughly 30 blocks a minute.
Packages
| Package | File |
|---|---|
| Windows runtime (node + wallet) | commonfoundry-mainnet-runtime-windows-x86_64-v1.0.7.zip |
| Windows miner | commonfoundry-mainnet-miner-windows-x86_64-v1.0.7.zip |
| Linux runtime (node + wallet) | commonfoundry-mainnet-runtime-linux-x86_64-v1.0.7.tar.gz |
| Linux miner | commonfoundry-mainnet-miner-linux-x86_64-v1.0.7.tar.gz |
| HiveOS | commonfoundry-mainnet-hiveos-1.0.7.tar.gz |
HiveOS flight sheet custom URL: https://github.com/JustAResearcher/CommonFoundry-Binaries/releases/download/v1.0.7/commonfoundry-mainnet-hiveos-1.0.7.tar.gz
Upgrading the desktop wallet: close it, extract the new archive to a new folder and start START-WALLET.bat. Your wallet and chain data live in %LOCALAPPDATA%\org.commonfoundry.wallet.mainnet and are picked up automatically. Copy the old folder's production-v4 directory into the new one to skip re-downloading the model files. Headless START-NODE.bat users also keep their data-mainnet folder.
Pool operators: update expected_node_sha256, expected_launch_sha256, expected_proof_worker_sha256 and expected_dashboard_index_sha256 in your pool config to the values in the new package's MAINNET-PACKAGE.json. The replay worker and CUDA runtime are unchanged.
Verification
SHA256SUMS.txt is signed by the same release key as v1.0.0–v1.0.6 (commonfoundry-mainnet-owner, SHA256:cA1Tsf8hL/pxDV5WpOE3iPW3b4uDQosu1dOh//4a/fk), policy MAINNET-RELEASE.allowed_signers SHA-256 9c5be92681092801d89687823837823d0966055c03a84e64551e26387da179d2. Follow docs/mainnet-release-verification.md.
All five archives were built twice from clean and are byte-identical, as are every native binary and the proof worker. The owner re-approved the unchanged mainnet plan for this source (approval manifest 32c197f0…).
Qualification limits: CI run 37333775048 on the final commit was in progress at signing and was not used as a gate (node-shutdown completed/failure; rust-base in_progress/; rust-proof in_progress/; rust-proof in_progress/). The new proof worker was checked on an RTX 4090 against the preserved RCNet-1 fixture: replay traces identical, one-shot proof with the worker's complete self-verification, and server-mode proofs with and without the preload (13.381 s and 11.61 s request-to-done); all three proofs passed the independent verifier and agree up to the grinding offset. The RTX 50-series path was built but not separately re-qualified. The console-interrupt shutdown tests cannot run in the build harness and were not re-run on a console.