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.