Common Foundry v1.0.6

Common Foundry v1.0.6

Node and wallet update, recommended for everyone running a node or the desktop wallet: initial sync and catch-up are many times faster. 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

Much faster sync

• A sync session now moves up to 16 blocks instead of one. Every session used to stop after a single 12 MB block because blocks were counted against the session's 32 MB message budget, so a syncing node reconnected for every block and managed about five blocks a minute. Block frames now have their own per-session allowance; everything else keeps the old budget.
• A block the node already downloaded is no longer thrown away when the proof verifier is busy; it is offered again instead of being fetched a second time.
• The proofs of a downloaded batch are checked on several CPU cores (all but one, at most four) before the blocks are applied in order. Blocks that peers push unasked keep the single verifier slot and its limits.
• Older nodes keep working with v1.0.6 peers: they take only as many blocks per session as their own budget allows, as before.

Desktop wallet no longer stalls its own sync

• Every 4 seconds the wallet rebuilt its transaction history by re-reading and re-hashing every block of the chain from disk while holding the node's lock, which starved its own sync (about 0.6 blocks a minute on a full chain) and kept one CPU core busy. The history is now cached and extended with only the new blocks; reorganisations are still handled exactly. Right after starting, the history list can stay empty for a few minutes while the first scan runs in the background; balances are unaffected.
• Measured with the wallet's 4-second refresh running: 18.7 blocks a minute before this fix, 70.7 after, at a low chain height where the old cost was still small.

More bootstrap peers

• New nodes and wallets dial the seed, the St. Louis relay and a new Singapore relay (13.140.66.6:29444) from their first round.

Smaller fixes

• After a compressed session to a peer ends early, a node waits 10 minutes (was an hour) before trying compressed frames with it again, and the log line no longer calls it a rejection.

Fastest start: the chain bootstrap

A signed copy of the chain (height 2637) is on Cloudflare: https://downloads.commonfoundry.ai/chain-bootstrap/mainnet-2026-10-05-h2637/. See the chain-bootstrap-2026-10-05 release for the steps.

Packages

Package	File
Windows runtime (node + wallet)	commonfoundry-mainnet-runtime-windows-x86_64-v1.0.6.zip
Windows miner	commonfoundry-mainnet-miner-windows-x86_64-v1.0.6.zip
Linux runtime (node + wallet)	commonfoundry-mainnet-runtime-linux-x86_64-v1.0.6.tar.gz
Linux miner	commonfoundry-mainnet-miner-linux-x86_64-v1.0.6.tar.gz
HiveOS	commonfoundry-mainnet-hiveos-1.0.6.tar.gz

HiveOS flight sheet custom URL: https://github.com/JustAResearcher/CommonFoundry-Binaries/releases/download/v1.0.6/commonfoundry-mainnet-hiveos-1.0.6.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.5 (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 baa7dd0b…).

Qualification limits: CI run 37272040997 on the final commit was in progress at signing and was not used as a gate (rust-base 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 (15.526 s and 11.257 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.