Common Foundry v1.0.8

Common Foundry v1.0.8

Exchange RPC update. Recommended for exchanges and integrators that run a node with --exchange-rpc-bind. Wallets, miners and other nodes behave as in v1.0.7 and 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

Exchange RPC no longer scans the whole chain

• gettransaction and getrawtransaction without a block hash now find the block through the node's transaction index and read only that block. On v1.0.7 they rescanned the full chain and gave up whenever a new block arrived during the scan, so at current mainnet height they rarely completed and could leave the endpoint busy (HTTP 503).
• registerwatchdestination(s) reads only the blocks that already pay or spend the new keys; a freshly generated deposit key reads none. Deposit events are unchanged.

Packages

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

HiveOS flight sheet custom URL: https://github.com/JustAResearcher/CommonFoundry-Binaries/releases/download/v1.0.8/commonfoundry-mainnet-hiveos-1.0.8.tar.gz

Upgrading: extract the new archive to a new folder. Desktop wallet data lives in %LOCALAPPDATA%\org.commonfoundry.wallet.mainnet and is picked up automatically; headless START-NODE.bat users keep their data-mainnet folder. Copy the old folder's production-v4 directory into the new one to skip re-downloading the model files.

Pool operators: if you upgrade, update expected_node_sha256, expected_launch_sha256 and expected_proof_worker_sha256 in your pool config to the values in the new package's MAINNET-PACKAGE.json. The dashboard, replay worker and CUDA runtime are unchanged.

Verification

SHA256SUMS.txt is signed by the same release key as v1.0.0–v1.0.7 (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 d3cdb282…).

Qualification limits: CI run 37364888987 on the final commit was queued at signing and was not used as a gate (desktop in_progress/; desktop in_progress/; explorer queued/; msrv queued/; node-shutdown in_progress/; node-shutdown queued/; pool-dashboard queued/; proof-codec in_progress/; proof-codec in_progress/; rust-base queued/; rust-proof in_progress/; rust-proof in_progress/; rust-proof in_progress/; rust-v4 in_progress/; wallet queued/). 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.156 s and 11.451 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.