Common Foundry v1.0.13

Common Foundry v1.0.13

Faster restarts, and the desktop wallet stops storing old proofs. Network, launch plan, beacon round, wallets, consensus and monetary policy are unchanged; keep your chain data and wallet.

What changes

Fast restarts (nodes and the desktop wallet)

• A restart no longer re-reads the whole chain. The node keeps an index next to its startup snapshot and reads only blocks newer than it, so it starts in seconds however long the chain is.
• Older history is re-checked in the background after startup. If a stored block no longer matches, the node stops serving, sets storage to unhealthy and rebuilds from the block log on the next start. status shows history_scrub_complete.
• The first start after upgrading checks the chain once, as before, and writes the index; later starts are fast.

Desktop wallet: old proofs pruned by default

• The wallet keeps full blocks for the newest 720 blocks (about 12 hours) and drops the roughly 12 MB proof of older blocks, keeping their transactions. Balances, history and payments are unchanged; the chain stops growing by about 12 GB a day.
• The first prune happens about 720 blocks after the first start of v1.0.13. --prune-keep-blocks <n> (at least 288) sets the window; --no-prune keeps every proof.
• A prune waits until the disk has room for it, and stops at once if the wallet closes. Details: docs/proof-pruning.md.

Packages

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

HiveOS flight sheet custom URL: https://github.com/JustAResearcher/CommonFoundry-Binaries/releases/download/v1.0.13/commonfoundry-mainnet-hiveos-1.0.13.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.12 (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 219661e1…).

Qualification limits: CI run 37517888987 on the final commit was completed at signing and was not used as a gate (explorer completed/failure; node-shutdown completed/failure; rust completed/failure; rust-base completed/failure). 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.479 s and 11.097 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 Windows. The explorer CI job fails only at npm audit, on the sharp advisory pulled in by Cloudflare's wrangler development tool, as in v1.0.12. The Ubuntu node-shutdown job failed on the same timing-sensitive peer-sync test that failed on the Windows runner for v1.0.12 (one extra retry of a deliberately stalled peer); that code did not change in this release, and the test passed 15 of 15 runs on Windows and 15 of 15 on Linux on the final source. The rust-base job fails one size-budget test of an experimental proof bridge that the node does not use (a 157,343-byte proof against a 157,000-byte budget); it failed the same way on v1.0.12 and that code is unchanged. The rust job only summarizes the Rust jobs. Fast startup was checked with the real node on a development network: a 200-block restart used the snapshot and index (0.55 s), the background check verified every older record, and a byte flipped in an older record was caught, the caches were moved aside and the next start refused the damaged log. Desktop-wallet pruning shares the relays' prune path; the St. Louis relay's first mainnet prune was checked before this release was signed.

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.

Common Foundry v1.0.11

Common Foundry v1.0.11

Storage update for node operators: opt-in proof pruning. Nothing changes unless you turn it on. Network, launch plan, beacon round, wallets, consensus and monetary policy are unchanged; keep your chain data and wallet.

What changes

Proof pruning (opt-in)

• cmfd-node run --prune-keep-blocks <N> (N of at least 288) keeps full blocks only for the newest N blocks. Older blocks keep their header, coinbase and transactions but drop their roughly 12 MB proof, so each takes a few KB.
• Balances, wallet history, the explorer, deposits and verbose getblock are unchanged. Raw getblock <hash> 0 on a pruned block returns block_proof_pruned; getblockchaininfo reports pruned and pruneheight.
• A pruned node does not serve old blocks to peers and cannot follow a reorganization deeper than its window. The first prune happens about N blocks after the flag is first turned on, and pruning cannot be undone.
• Back up prune-anchor-<height>.bin together with blocks.log; a pruned node does not start without it. Details: docs/proof-pruning.md.

Packages

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

HiveOS flight sheet custom URL: https://github.com/JustAResearcher/CommonFoundry-Binaries/releases/download/v1.0.11/commonfoundry-mainnet-hiveos-1.0.11.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.10 (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 efc5a504…).

Qualification limits: CI run 37471625690 on the final commit was in progress at signing and was not used as a gate (explorer completed/failure; pool-dashboard completed/failure; rust-base in_progress/; rust-proof in_progress/; rust-proof in_progress/; wallet completed/failure). 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 (17.108 s and 11.22 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 jobs on Windows and Ubuntu. The explorer, pool-dashboard and wallet CI jobs failed only at npm audit, which now flags a new advisory for source-map-js (GHSA-68fv-2mgg-jv7q); it is a build-time development dependency, unchanged since v1.0.10, and the shipped dashboard files are identical to v1.0.10. Pruning was tested on Windows and Linux and end to end on a development network with the real node (startup and background pruning under concurrent reads, following a full peer, refusing a fresh peer, offline storage inspection, restarts, and turning pruning off); the first mainnet prune happens on the relays after this release.

Common Foundry v1.0.10

Common Foundry v1.0.10

Exchange integration update. Exchanges can now integrate Common Foundry the way they integrate Bitcoin. Wallets, miners and other nodes behave as in v1.0.9 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 wallet

• cmfd-node exchange-wallet --wallet-dir <dir> runs a wallet daemon that speaks Bitcoin Core's wallet JSON-RPC: getnewaddress, listsinceblock, gettransaction, getbalance, sendtoaddress, sendmany, encryptwallet, walletpassphrase, backupwallet and the usual chain and status calls, with Bitcoin Core's error codes. An exchange's existing Bitcoin integration, or bitcoin-cli, works against it.
• Keys stay on the exchange's server in wallet.json; one backup covers every address the wallet will hand out. The chain is read from the hosted exchange endpoint or the exchange's own node, so no chain is stored.
• Settings come from cmfd-wallet.conf in the wallet directory (rpcuser, rpcpassword, upstream, upstreamuser, upstreampassword, optional rpcbind, rpcport, rpcallowip).

Documentation

• exchange-kit/INTEGRATION-GUIDE.md describes the exchange wallet as the recommended integration, lists where it differs from Bitcoin Core, and asks exchanges to credit deposits after at least 60 confirmations.

Packages

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

HiveOS flight sheet custom URL: https://github.com/JustAResearcher/CommonFoundry-Binaries/releases/download/v1.0.10/commonfoundry-mainnet-hiveos-1.0.10.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.9 (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 eebf65df…).

Qualification limits: CI run 37396239691 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 (14.959 s and 11.201 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 jobs on Windows and Ubuntu. The exchange wallet was tested end to end against a development-network node (deposits, payments, reorganization, restore, encryption, endpoint outage, Bitcoin Core's bitcoin-cli) and on mainnet through the hosted endpoint, where it received a deposit, sent a payment that was mined, and restored an encrypted backup by rescanning.

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.

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.

Common Foundry v1.0.7

Common Foundry v1.0.7

Node and wallet update, recommended for everyone running a node or the desktop wallet: catching up no longer stalls on slow or distant peers. 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

Catch-up stops waiting on slow peers

• A sync session stops asking a peer for more blocks after 30 seconds, keeps every block that already arrived and ends normally. A slow or far-away peer can no longer hold a node for a whole batch of 12 MB blocks.
• While catching up, the peer that delivered blocks fastest in the last round gets the first turn and most of the extra sessions; the others are still used in turn.

A fourth bootstrap peer

• New nodes and wallets dial the seed and three relays from their first round: St. Louis, Singapore and a new 1 Gbit/s relay in Falkenstein, Germany (88.198.110.195:29444).

Fastest start: the chain bootstrap

New wallet, or far behind? Start from a signed copy of the chain (height 3201) instead of downloading and verifying every block from peers. The wallet then only syncs the newest blocks.

Windows wallet (needs about 40 GB free on C:):

1. Install or upgrade the wallet to v1.0.7, open it once (create or unlock your wallet), then close it.
2. Open PowerShell and run these two lines:

   curl.exe -fLO https://github.com/JustAResearcher/CommonFoundry-Binaries/releases/download/chain-bootstrap-2026-10-05/bootstrap.ps1
   powershell -ExecutionPolicy Bypass -File .\bootstrap.ps1

3. When it prints Done, open the wallet. It starts at block 3201 and syncs the rest in minutes.

The script downloads from Cloudflare (https://downloads.commonfoundry.ai/chain-bootstrap/mainnet-2026-10-05-h3201/), checks the release-key signature and every checksum, and replaces only the chain files. Your wallet and coins are not touched. If the download is interrupted, run the second line again to resume.

Linux node: stop the node, then run curl -fLO https://github.com/JustAResearcher/CommonFoundry-Binaries/releases/download/chain-bootstrap-2026-10-05/bootstrap.sh and bash bootstrap.sh <data directory>. Manual download and details: the chain-bootstrap-2026-10-05 release.

Already synced, or only a few hundred blocks behind? Just upgrade; v1.0.7 catches up at roughly 30 blocks a minute.

Packages

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

HiveOS flight sheet custom URL: https://github.com/JustAResearcher/CommonFoundry-Binaries/releases/download/v1.0.7/commonfoundry-mainnet-hiveos-1.0.7.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.6 (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 32c197f0…).

Qualification limits: CI run 37333775048 on the final commit was in progress at signing and was not used as a gate (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.381 s and 11.61 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.

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.

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.

Common Foundry v1.0.4

Common Foundry v1.0.4

Node and pool-operator update, recommended for wallet users too: the wallet runs a full node, and this release is what lets it sync from the new relay and other peers instead of only the seed, so initial sync becomes much 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

Relay nodes get used for initial sync

• Peer discovery polled the due peers of each round in address order, so once a round outlasted the 10 s retry interval the same lowest addresses won every round and a discovered peer with a high address (such as a relay) was never synced from. Due peers are now polled least-recently-scheduled first.

Compressed frames and older peers

• A v1.0.3 node opened sessions to its static peers with version-5 frames and only fell back after two refusals; a v1.0.1/v1.0.2 peer closes on the first such frame and counts each as a protocol violation, so the second one got the newer node banned there for five minutes. One refused version-5 handshake now pauses compression toward that peer for an hour, before a ban can happen.
• A node no longer remembers "accepts compressed frames" per address. Several nodes may share one address (NAT), and a v1.0.3 node that learned it from one of them answered every connection from that address with version 5. A session that is greeted with version 5 now answers in version 5 for that session only; static peers are still opened with version 5.

Packages

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

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

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.3 (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 83d9d275…).

Qualification limits: CI run 37230030728 on the final commit was in progress at signing and was not used as a gate (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 (16.07 s and 13.875 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.