Common Foundry v1.0.5

Common Foundry v1.0.5

Node and wallet update, recommended for wallet users: a fresh install now syncs from the relay and the seed together instead of the seed alone. 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

New installs sync from two sources from the start

• A mainnet node or desktop wallet without explicit --peer arguments now dials the relay (209.145.48.36:29444) next to the bootstrap seed from its first round, instead of learning about the relay only through discovery. RCNet and devnet keep their single seed, and an explicit --peer list still replaces every default.
• The desktop wallet's Network view lists both as community bootstrap peers, and Reset restores both. A wallet whose peer list was never edited picks this up automatically; if you edited yours, press Reset in the Network view to get both.

Packages

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

HiveOS flight sheet custom URL: https://github.com/JustAResearcher/CommonFoundry-Binaries/releases/download/v1.0.5/commonfoundry-mainnet-hiveos-1.0.5.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.4 (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 fcfdfe14…).

Qualification limits: CI run 37263277269 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 (14.416 s and 11.518 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.