Common Foundry v1.0.12

Common Foundry v1.0.12

Total supply for exchanges and listing sites. Network, launch plan, beacon round, wallets, consensus and monetary policy are unchanged; keep your chain data and wallet.

What changes

• Exchange RPC gettxoutsetinfo (Bitcoin Core's method) returns the height, best block, number of unspent outputs and total_amount_atoms, the total supply: every CMFD minted so far minus burned fees.
• The exchange wallet answers gettxoutsetinfo like Bitcoin Core, with total_amount in CMFD.
• The explorer snapshot reports total_supply_atoms, used by the public endpoints https://explorer.commonfoundry.ai/api/supply (JSON) and https://explorer.commonfoundry.ai/api/supply/total (plain number).
• Build-time update of source-map-js (GHSA-68fv-2mgg-jv7q) in the web frontends' lockfiles.

Packages

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

HiveOS flight sheet custom URL: https://github.com/JustAResearcher/CommonFoundry-Binaries/releases/download/v1.0.12/commonfoundry-mainnet-hiveos-1.0.12.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.11 (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 approved the unchanged mainnet plan for this source (approval manifest 54db0b1f…).

Qualification limits: CI run 37498241497 on the final commit was in progress at signing and was not used as a gate (explorer completed/failure; 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.209 s and 11.213 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; they passed in CI's node-shutdown job on Ubuntu. The explorer CI job fails only at npm audit, now on an advisory for sharp pulled in by Cloudflare's wrangler development tool; the wallet and pool-dashboard jobs pass again. The Windows node-shutdown job failed on a timing-sensitive peer-sync test (one extra retry of a deliberately stalled peer on the CI runner) and a runner PowerShell that lacked Get-FileHash; neither area changed in this release, and that test passed 15 of 15 runs on the final source. The total supply was checked on a development network against an independent total (every address balance; minted coins minus the burned fee) through the exchange RPC, the explorer snapshot, the exchange wallet with Bitcoin Core's bitcoin-cli, and the explorer endpoints.