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.