Common Foundry v1.0.0 — Mainnet

Common Foundry v1.0.0 — Mainnet software

Planned source and packages: October 2, 2026, noon Central (CDT; 17:00 UTC).
Planned mainnet mining: October 3, 2026, noon Central (CDT; 17:00 UTC).

Downloading or installing the software does not start the chain. The launch
helper authenticates the scheduled beacon before activation. Keep your clock
accurate; do not change the launch plan, target, or beacon round to bypass the
wait. Earlier RC balances and chain data do not transfer to mainnet.

Verify before running

Frozen implementation source: 033d41e45edf35033dfd4c9bf5f6f0774caf154b.
This is the exact compiled and tested source. Both complete 23-asset sets passed
source-bound and source-free signature verification with the single approved
release signer. The reviewed-source approval is a separate attestation.

Obtain the release policy independently from
commonfoundry.ai/mainnet-release-key.txt.
The owner replaced the pending mainnet signer before the first mainnet release;
the previous key did not cross-sign this replacement.

Fingerprint: SHA256:cA1Tsf8hL/pxDV5WpOE3iPW3b4uDQosu1dOh//4a/fk
Policy SHA-256: 9c5be92681092801d89687823837823d0966055c03a84e64551e26387da179d2

The policy is packaging/mainnet/MAINNET-RELEASE.allowed_signers in the final
source. It authorizes commonfoundry-mainnet-owner under the
commonfoundry-release OpenSSH signature namespace. The producer-approval
policy has a different purpose and namespace; do not substitute it.

Download the complete 23-asset release set, including all five archives,
SHA256SUMS.txt, SHA256SUMS.txt.sig, and the release metadata. Follow
docs/mainnet-release-verification.md from the exact final source and require
the verifier's source commit to match the one announced above. Stop on any
signature, inventory, identity, or checksum mismatch. Keep these notes and the
independently obtained policy outside the download directory: the verifier
rejects missing or extra files.

The binary repository's automatic source ZIP is not the implementation source.
Use the announced Common-Foundry-1/CommonFoundry implementation commit; do not
substitute an old candidate or the binaries metadata repository.

Choose a package

Use	Archive
Windows wallet + node	commonfoundry-mainnet-runtime-windows-x86_64-v1.0.0.zip
Linux wallet + node	commonfoundry-mainnet-runtime-linux-x86_64-v1.0.0.tar.gz
Windows pool miner	commonfoundry-mainnet-miner-windows-x86_64-v1.0.0.zip
Linux pool miner	commonfoundry-mainnet-miner-linux-x86_64-v1.0.0.tar.gz
HiveOS NVIDIA custom miner	commonfoundry-mainnet-hiveos-1.0.0.tar.gz

Use the package's README and platform launchers. Wallet/node verification runs
on the CPU and does not require a mining GPU. Windows GPU mining requires
WSL2 Ubuntu-22.04 with NVIDIA support; Linux/HiveOS mining requires a compatible
NVIDIA driver. Compiler targets are not a claim that every card and driver has
been physically tested: follow the final release's actual hardware evidence.
Pool search and full solo/pool proof generation have different requirements.

Use fresh mainnet configuration and chain/pool data, not RC databases, ledgers,
launch plans, or RC receiving addresses. Create and separately back up the
encrypted mainnet wallet before mining. Never send keys or passphrases to
support. Keep the previous encrypted backups and release artifacts for recovery.

HiveOS setup

In a flight sheet, select Custom, using the installation URL for the exact
HiveOS archive in the verified official release. HiveOS is included in the
October 2 release; there is no early separate HiveOS publication.

• Wallet template: %WAL%, your 64-character mainnet destination public key.
• Pool URL: the complete pool-supplied cmfd+tls://IP:PORT?pin=... URL.
• Algorithm: forgematrix_v4.
• Optional extra configuration: JSON such as {"gpus":[0,2]}.

The installer places files directly in
/hive/miners/custom/commonfoundry-mainnet-hiveos/, with no version
subdirectory. The default model and scratch directories are outside that
replaceable directory, under /hive/miners/custom/commonfoundry-data/.
Allow at least 15 GB of free storage for the pool-miner model and download
staging. The wrapper verifies model hashes, starts one native worker per
selected NVIDIA GPU, and uses the native .gpuN worker suffix.

The package requires python3, curl, jq, and compatible NVIDIA drivers;
the CUDA runtime is bundled, not the driver. Logs are under
/var/log/miner/commonfoundry-mainnet-hiveos/. Configure watchdogs to tolerate
initial model preparation and the authenticated launch wait. Follow the included
HiveOS README for the complete options and installation procedure.

Qualification status and limits

Completed for these exact bytes: all 16 final-source CI jobs; separate
Windows/Linux native builds and clean rebuilds; a newly compiled and
byte-reproduced network-bound proof worker; and full content/byte comparison
of both five-archive sets, including HiveOS.

The new worker produced a complete production-size proof on a physical RTX
4090 using the preserved offline fixture. Its native verification and five
malformed-proof checks passed. The separate current-source Python verifier
accepted the full proof and strict candidate claims and rejected eight
fresh-process mutation variants. This does not constitute an external audit
or a live mainnet block, and does not qualify untested physical GPU models.

Actual packaged Windows/Linux programs each passed 16 prelaunch checks,
including refusal to start before the authenticated launch and rejection of
altered launch data. HiveOS's official installer installed and force-upgraded
the actual archive in an isolated Ubuntu-22.04 environment, preserving model
and state caches and validating packaged binaries/configuration. This is not
a physical HiveOS mining test or proof of compatibility with older images.

Both operator hosts have the exact signed runtime selected. Isolated service
checks using the installed service settings reached the genuine launch wait,
created no mainnet listener or chain state, and stopped cleanly. Production
launch holds remained installed, and the existing running services were
preserved. The older Linux pool service required the separately qualified
systemd-249 credential adapter; the raw template was not treated as compatible.

Launch-time acceptance remains separate. Publication of these files is not
a claim that mainnet is already running. Mainnet connectivity, transfers, reward
maturity and payouts must be observed on the live network after activation;
they are not inferred from prelaunch tests.

ForgeMatrix uses 12,025,320-byte transparent proofs (about 11.47 MiB) for the
current mainnet profile. CPU verification checks the committed computation and
work relation; it is not hardware attestation or proof of physical GPU/VRAM
use. Internal clean rebuilds are not independent-party reproduction, and
verification is not an external cryptographic audit or a guarantee of zero
cheating. Prelaunch tests cannot demonstrate future mainnet blocks, transfers,
reward maturity, or payouts.

Dedicated Linux pool service files are templates, not automatically installed
services. Qualify their credentials, sandbox, NVIDIA device access, and systemd
compatibility on the actual host before enabling them. In particular, the
packaged %d credential-copy commands must not be assumed compatible with
systemd 249; any host adapter needs qualification with the final replacement
runtime. An old service-compatibility supplement is not carried forward here.

The operator's launch pool is configured with a 0% operator fee, a
10 CMFD minimum payout, and a 0.1 CMFD network burn per payout. These
are pool operating settings, not guaranteed earnings or a change to the
chain's monetary rules.

Visit commonfoundry.ai for the project and its
official Discord community. Publication and activation remain separate gates.