Common Foundry v1.0.9

Common Foundry v1.0.9

Exchange integration update. Exchanges and integrators get offline key and withdrawal-signing commands and a complete integration guide. Wallets, miners and other nodes behave as in v1.0.8 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

Offline keys and withdrawals for exchanges

• cmfd-node exchange-key-new --output <file> creates a deposit or hot-wallet key and prints its address; exchange-key-show --key <file> prints the address of an existing key.
• cmfd-node exchange-tx-sign --request <file> builds and signs a withdrawal from a JSON request (inputs from getaddressutxos, payments, change address, fee) and prints the transaction for sendrawtransaction. It refuses keys that do not own their input, fees below 0.1 CMFD, requests for another network and any leftover amount without a change address. None of these commands needs a running node.

Exchange RPC

• Resending a transaction that is already mined now returns transaction_already_confirmed instead of a missing-input error.
• The conformance check in the exchange kit now expects the transaction and address query methods, so it passes against current nodes.

Documentation

• exchange-kit/INTEGRATION-GUIDE.md: deposit addresses, deposit events and confirmations, sweeps, withdrawals, fees and error handling, for both the hosted endpoint and your own node.

Packages

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

HiveOS flight sheet custom URL: https://github.com/JustAResearcher/CommonFoundry-Binaries/releases/download/v1.0.9/commonfoundry-mainnet-hiveos-1.0.9.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.8 (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. Because the qualified verifier scripts changed, the preserved proof was re-qualified for this source (qualification record db257c3b…), and the owner approved the unchanged mainnet plan for it (approval manifest 44d653ae…).

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