Skip to content

Releases: JustAResearcher/CommonFoundry-Binaries

Common Foundry pool miner 2 - RTX 40/50 performance

Choose a tag to compare

@JustAResearcher JustAResearcher released this 06 Sep 20:23
d2a1cad

Common Foundry pool miner 2 - RTX 40/50 performance

Standalone pool-mining update for RCNet-1, built on RC5. Improved GPU batching
and CPU activation hashing increase measured mining throughput. This is a miner-only prerelease. Wallets,
nodes, consensus rules, the model bank and existing signed RC5 assets remain
unchanged; no coordinated network upgrade or chain reset is required.

Download and start

Download the Windows/WSL2 ZIP or Linux tar.gz and extract the complete archive
into a new directory. Use the attached miner packages, not GitHub's automatic
Source code archives.

  • Windows: WSL2 Ubuntu 22.04 with NVIDIA CUDA support; double-click
    START-MINER.bat.
  • Linux: a compatible NVIDIA driver and CUDA support; run ./start-miner.sh.
  • Supply your RCNet wallet's public receive address and the pool operator's
    complete certificate-pinned cmfd+tls://IP:PORT?pin=... URL.

The first run downloads and authenticates approximately 6.4 GB of model data.
Allow about 14 GB free disk during first setup because downloaded parts and
the assembled bank temporarily coexist. Existing miners can reuse their model
bank; the included README explains how. Pool clients do not download the
full solo prover. Stop the previous miner before starting this package.

Measured performance

These are bounded console-rate comparisons against the preceding software
configurations on the same hardware, with clocks and power caps unchanged.

GPU Before After Improvement
RTX 4070 Ti SUPER 8.33 FW/s 20.285 FW/s 2.44x
RTX 5070 Ti 11.29 FW/s 27.59 FW/s 2.44x
RTX 5090 29.535 FW/s 34.84 FW/s 18%

The 4070 Ti SUPER measurement qualifies the Ada GPU change before the added
CPU hashing improvement. The 5090 continued sharing its GPU with the local
pool/proof workload. These figures are not promises for other configurations.

Final 5090 pool qualification recorded 29 accepted shares and zero rejected or
stale shares. The 5070 Ti recorded 26 accepted shares and one stale rejection,
plus one unclassified console rejection. Full intermediate replay outputs and
final activations matched the previous worker byte-for-byte; CPU hashing tests
matched unchanged consensus digests and retained canonical-value checks.
The included performance records give methodology and limitations.

Native worker images cover SM 7.5, 8.6, 8.9 and 12.0, plus compute-7.5 PTX.
Physical checks cover RTX 4070 Ti SUPER, RTX 5070 Ti and RTX 5090. Physical RTX
20/30-series and 8 GB testing remain pending. Build targets are not hardware
qualification, and pool-search checks do not broaden solo-prover support.

Verification

Compare downloads with SHA256SUMS.txt and authenticate its detached OpenSSH
signature against the established Common Foundry release key using namespace
commonfoundry-release. A checksum alone does not authenticate a publisher;
these packages are not Windows Authenticode signed. BUILDINFO.json records
source and binary identities, build tools, and qualification scope. This
bounded miner update does not claim independent reproducible-build evidence.

RCNet-1 is a testing network, not mainnet; its coins have no intended monetary
value. The wallet, node and original signed RC5 release assets are unchanged.

Common Foundry pool miner - cross-GPU preview 1

Choose a tag to compare

@JustAResearcher JustAResearcher released this 05 Sep 11:46
d2a1cad

Community pool launch — September 6, 2026

The Common Foundry community pool started Sunday, September 6 at 17:00 UTC / 12:00 noon US Central (CDT).

Launch verification — September 6, 13:04 CDT: Public TLS access, the certificate pin, and actual mining over an Internet connection are verified. The pool has two active workers, 211 total accepted shares, and 6 canonical pool blocks, including a block from the external worker. The external seed confirms the same height and tip. Two rejected shares are recorded as stale. Automatic payouts remain unverified while rewards mature.

View live workers, shares, blocks, and payouts on the public pool dashboard.

Copy the entire pool URL, including the certificate pin:

cmfd+tls://107.214.187.2:19445?pin=a4868a78e9d4d46bbb3c7867bd43bacbb4e8bb0a0ac61e54444b16250d525dc0
  1. Download the Windows/WSL2 or Linux pool miner and extract the whole archive. Follow its checksum and signature verification instructions.
  2. Have your RCNet wallet's public receive address ready. Use the same address consistently; never enter a private key, recovery secret, or wallet password into the pool-address field.
  3. Windows requires WSL2 Ubuntu 22.04 and NVIDIA CUDA support; use START-MINER.bat. Linux uses ./start-miner.sh.
  4. Supply your receive address and the complete pool URL. First use downloads and verifies approximately 6.4 GB of model data. Follow the included README for input preparation.

Pool terms: 3% operator fee, automatic one-block PPLNS window, 10 test CMFD minimum payout, and 0.1 CMFD transaction burn per payout transaction. Payouts require mature block rewards and confirmation; they are not immediate after a share.

This is RCNet-1 testing, not mainnet. Test coins have no intended monetary value. The network's virtual-genesis field still displays September 7; the operational community-pool start above is September 6. This notice does not change network parameters or signed release packages.

The preview includes NVIDIA RTX 20/30/40/50-series worker targets. Physical RTX 20/30-series and 8 GB qualification remains pending; consult the preview release for the tested hardware scope. Wallet solo-mining compatibility is separate.

Watch the RCNet explorer for confirmed chain progress. Report setup or mining problems in the testing repository's Issues.

Windows startup fix: If startup reports ProductionV4 input manifests disagree about FORGEMATRIX-V4-FIXED-BANK-0.tree, the packaged input manifest contains a one-character checksum typo. In the extracted production-v4-rcnet-1-inputs.json, find the FORGEMATRIX-V4-FIXED-BANK-0.tree entry and set its sha256 to:

6f55b1ddc9bc15426dbf23a662ab205e2f5396d92c7298c34885a22e34380085

This matches both V4-INPUT-CHUNKS.json and the independently hashed tree artifact. Save the file and rerun START-MINER.bat; keep the integrity checks enabled. This correction applies to the extracted JSON file; the existing signed release assets have not been replaced.


Common Foundry pool miner - cross-GPU preview 1

Standalone pool-mining update for RCNet-1, built on RC5. The pool handles the
full block proof; this package performs GPU search and submits shares.
This is a miner-only prerelease, not a wallet, node or consensus upgrade.

Download and start

Download the Windows/WSL2 ZIP or Linux tar.gz below and extract the entire
archive into a new directory. Do not use GitHub's automatic Source code archives.

  • Windows: use WSL2 Ubuntu 22.04 with NVIDIA CUDA support, then double-click
    START-MINER.bat.
  • Linux: run ./start-miner.sh with a compatible NVIDIA driver and CUDA support.
  • Supply your RCNet wallet's public receive address and the pool operator's
    complete certificate-pinned cmfd+tls://IP:PORT?pin=... URL.

The included downloader prepares and authenticates approximately 6.4 GB of
model data on first use. Pool clients do not download the full solo prover.
The included README covers setup. CANDIDATE.md records the pre-publication
build and test checkpoint; this release supplies the signed download manifest.

GPU compatibility checkpoint

  • Native worker images: RTX 20, 30, 40 and 50 series, plus a PTX fallback.
  • RTX 4070 Ti SUPER 16 GB: full-model offline search and forced PTX checks
    passed, with output matching the original RTX 5090 worker exactly.
  • RTX 5090: updated-worker regression passed.
  • Physical RTX 20/30-series and 8 GB testing, and live accepted-share
    verification, remain pending. Build targets are not hardware qualification.

Twenty focused tests passed. The pool-search changes do not broaden solo
proof-generator compatibility. RCNet-1 is a testing network, not mainnet;
its coins have no intended monetary value.

Verification

Compare each download with SHA256SUMS.txt. Authenticate that manifest's
detached OpenSSH signature using the established Common Foundry release key
and the commonfoundry-release namespace. A checksum alone does not
authenticate a publisher. This is not Windows Authenticode signing.

The wallet, node, network identity and existing signed RC5 release assets
are unchanged. Build provenance and qualification scope are in BUILDINFO.json.

Common Foundry v0.1.0-rc.5 - wallet usability and GPU mining

Choose a tag to compare

@JustAResearcher JustAResearcher released this 05 Sep 05:06
v0.1.0-rc.5
d2a1cad

RTX 40/50 miner update - September 6, 2026: Miner 2 improved tested RTX 4070 Ti SUPER and RTX 5070 Ti rates by about 2.44x, and RTX 5090 by 18%, without changing clocks or power limits. See that release for test conditions and limitations. RC5 wallet/node and signed assets are unchanged.

Community pool launch — September 6, 2026

The Common Foundry community pool started Sunday, September 6 at 17:00 UTC / 12:00 noon US Central (CDT).

Launch verification — September 6, 13:04 CDT: Public TLS access, the certificate pin, and actual mining over an Internet connection are verified. The pool has two active workers, 211 total accepted shares, and 6 canonical pool blocks, including a block from the external worker. The external seed confirms the same height and tip. Two rejected shares are recorded as stale. Automatic payouts remain unverified while rewards mature.

View live workers, shares, blocks, and payouts on the public pool dashboard.

Copy the entire pool URL, including the certificate pin:

cmfd+tls://107.214.187.2:19445?pin=a4868a78e9d4d46bbb3c7867bd43bacbb4e8bb0a0ac61e54444b16250d525dc0
  1. Download the Windows/WSL2 or Linux pool miner and extract the whole archive. Follow its checksum and signature verification instructions.
  2. Have your RCNet wallet's public receive address ready. Use the same address consistently; never enter a private key, recovery secret, or wallet password into the pool-address field.
  3. Windows requires WSL2 Ubuntu 22.04 and NVIDIA CUDA support; use START-MINER.bat. Linux uses ./start-miner.sh.
  4. Supply your receive address and the complete pool URL. First use downloads and verifies approximately 6.4 GB of model data. Follow the included README for input preparation.

Pool terms: 3% operator fee, automatic one-block PPLNS window, 10 test CMFD minimum payout, and 0.1 CMFD transaction burn per payout transaction. Payouts require mature block rewards and confirmation; they are not immediate after a share.

This is RCNet-1 testing, not mainnet. Test coins have no intended monetary value. The network's virtual-genesis field still displays September 7; the operational community-pool start above is September 6. This notice does not change network parameters or signed release packages.

The preview includes NVIDIA RTX 20/30/40/50-series worker targets. Physical RTX 20/30-series and 8 GB qualification remains pending; consult the preview release for the tested hardware scope. Wallet solo-mining compatibility is separate.

Watch the RCNet explorer for confirmed chain progress. Report setup or mining problems in the testing repository's Issues.

Windows startup fix: If startup reports ProductionV4 input manifests disagree about FORGEMATRIX-V4-FIXED-BANK-0.tree, the packaged input manifest contains a one-character checksum typo. In the extracted production-v4-rcnet-1-inputs.json, find the FORGEMATRIX-V4-FIXED-BANK-0.tree entry and set its sha256 to:

6f55b1ddc9bc15426dbf23a662ab205e2f5396d92c7298c34885a22e34380085

This matches both V4-INPUT-CHUNKS.json and the independently hashed tree artifact. Save the file and rerun START-MINER.bat; keep the integrity checks enabled. This correction applies to the extracted JSON file; the existing signed release assets have not been replaced.


Common Foundry v0.1.0-rc.5 — wallet usability and GPU mining

RCNet-1 release candidate, not mainnet. RCNet coins have no intended monetary value.

  • Send and consolidation default to, and enforce, a minimum transaction burn of
    0.1 CMFD (10,000,000 atoms). Nodes enforce the same minimum for each normal
    spend and channel close; pool payout defaults also match.
  • Backup and restore use native Save As/Open dialogs, including paths containing
    spaces. Existing backups cannot be overwritten, and cancellation does not
    perform a wallet operation.
  • The Mining tab connects solo mining to the persistent ProductionV4 GPU
    replay/proof workers and normal embedded-node consensus verification. Opening
    the tab does not start mining or downloads.
  • The complete runtime package includes optional authenticated mining setup:
    PREPARE-MINING.bat (Windows) or prepare-mining.sh (Linux). Wallet-only setup
    remains about 6.4 GB; solo mining needs about 61 GB of inputs plus scratch space.

Upgrade

All RCNet nodes and pools must upgrade together because the fee rule changes
the consensus fingerprint. Empty RC4 chain directories receive a narrow metadata
upgrade, preserving the wallet key and an original network.meta.rc4 copy.
Existing block histories are not automatically reset or rewritten.

The initial packaged mining workers target NVIDIA RTX 50-series (CUDA SM 12.0).
Windows requires WSL2 Ubuntu-22.04 with CUDA 12.8; Linux requires CUDA 12.8.
Other GPU architectures are not qualified by this package. The community pool
follows the launch schedule above. Stop waits for the current GPU operation
to finish and prevents subsequent work or submissions.

Use the complete runtime archive and its launcher, not a bare executable.
Back up the encrypted wallet before upgrading. Release-manifest signatures
authenticate the download; they are not Windows Authenticode signatures.

Common Foundry v0.1.0-rc.4 - complete RCNet runtime setup

Choose a tag to compare

@JustAResearcher JustAResearcher released this 05 Sep 02:14

Common Foundry v0.1.0-rc.4 — complete RCNet runtime setup

RC4 includes the Windows installer, Linux desktop builds, portable wallet/node
runtime bootstrap packages, and Windows/Linux miners. No earlier RC installation
is required. RCNet-1 is experimental, is not mainnet, and its coins have no
intended monetary value.

What to download

  • Windows wallet: commonfoundry-wallet-v0.1.0-rc.4-windows-x86_64-setup.exe.
    First startup opens a progress window to download and authenticate the missing
    approximately 6.4 GB runtime, then continues startup. Keep that window open.
  • Linux first installation:
    commonfoundry-rc-runtime-bootstrap-linux-x86_64-v0.1.0-rc.4.tar.gz.
    Extract it and run ./start-wallet.sh. The wallet needs GTK/WebKitGTK desktop
    libraries; the downloader needs curl and Python 3. The separate AppImage and
    deb builds require manual runtime preparation and placement.
  • Portable Windows wallet/node:
    commonfoundry-rc-runtime-bootstrap-windows-x86_64-v0.1.0-rc.4.zip.
    Extract it and run START-WALLET.bat.
  • Miners: select the commonfoundry-miner-v0.1.0-rc.4 archive for your
    platform and follow its included README. Windows mining requires WSL2; mining
    requires a compatible NVIDIA GPU and a certificate-pinned pool connection.

Reserve at least 16 GB free during runtime preparation. The downloaded
chunks and assembled bank temporarily coexist; this supersedes the older 8 GB
estimate in the bundled runtime README. Interrupted downloads can resume.
The small bootstrap archives include the complete downloader and pinned
manifests, not a duplicate of the large model bank. The RC1 label on model-data
URLs identifies the unchanged immutable input set, not an older wallet that
must be installed.

Fixes and verification

This fixes the Windows installer starting without its authenticated ProductionV4
runtime. The RCNet-1 network identity, consensus rules and encrypted-backup
format are unchanged from RC3. Complete release assets include native runtime
identity evidence, build metadata, source dependency inventory, activation
qualification, SHA-256 checksums and their detached OpenSSH signature.

Verify downloads against the authenticated SHA256SUMS.txt. The release signer
fingerprint is SHA256:nmSmxosb/kAkfPf3cQy1te3rLlUQ13fTc/39FDzadaM; authenticate
that key through an independently trusted channel. Windows executables are not
Authenticode-signed and may show an unknown-publisher prompt. This release does
not claim an external audit or independent cryptographic reproduction.

Preserve your encrypted wallet backup and its passphrase separately before
upgrading. Never share private keys, recovery material or passwords in reports.

Common Foundry v0.1.0-rc.3

Pre-release

Choose a tag to compare

@JustAResearcher JustAResearcher released this 03 Sep 03:24
0140526

Common Foundry v0.1.0-rc.3 — RCNet runtime bootstrap

This RCNet-1 release candidate adds the complete wallet runtime bootstrap
package and makes missing ProductionV4 files actionable in the desktop wallet.
It is not mainnet, and RCNet coins have no intended monetary value.

Fixed

  • Missing authenticated ProductionV4 runtime files now identify the exact files
    required instead of surfacing as a generic node-storage failure.
  • The release includes Windows and Linux runtime bootstrap archives. Each
    archive contains the native node and wallet binaries, the pinned manifests,
    the fixed artifact record, and a resumable downloader for the approximately
    6.4 GB model bank.
  • The downloader verifies every part and the assembled bank with SHA-256 before
    the wallet or node can use it.

The RCNet-1 network identity, consensus rules, bootstrap endpoint, wallet data
format, and encrypted-backup format are unchanged from v0.1.0-rc.2.

Common Foundry v0.1.0-rc.2 — Wallet input hotfix

Choose a tag to compare

@JustAResearcher JustAResearcher released this 03 Sep 00:51
0140526

Common Foundry v0.1.0-rc.2 — Wallet input hotfix

RCNet-1 wallet-only hotfix. Not mainnet; RCNet coins have no intended monetary value.

  • Source commit: 673b3d1a5fe0003bea70ed1d8cb231b2449d8d80
  • Network identity, consensus, bootstrap, wallet data, and encrypted-backup formats are unchanged from v0.1.0-rc.1.
  • Fixes desktop passphrase focus loss during background polling.
  • User-facing minimum is 12 characters; internal UTF-8 safety limits remain enforced.
  • Node/miner/runtime packages remain the v0.1.0-rc.1 artifacts.

Downloads

Verify SHA256SUMS.txt with the attached OpenSSH signature and release signer fingerprint SHA256:nmSmxosb/kAkfPf3cQy1te3rLlUQ13fTc/39FDzadaM.

Common Foundry v0.1.0-rc.1 — RCNet-1

Pre-release

Choose a tag to compare

@JustAResearcher JustAResearcher released this 01 Sep 23:21
0140526

Common Foundry v0.1.0-rc.1 — RCNet-1

RCNet-1 release candidate.

Main packages

Verification

Release signer fingerprint: SHA256:nmSmxosb/kAkfPf3cQy1te3rLlUQ13fTc/39FDzadaM. The signer policy, checksums, signature, provenance, SBOM, runtime attestations, activation approval, and network metadata are attached below or available at the complete-downloads link.

Common Foundry v0.1.0-devnet.16 — ProductionV4 Testnet-1

Choose a tag to compare

@JustAResearcher JustAResearcher released this 28 Aug 03:34
0140526

Common Foundry v0.1.0-devnet.16 — ProductionV4 Testnet-1

This binary-only prerelease activates the isolated ProductionV4 transparent
BaseFold proof network. It is incompatible with ProductionV3 Devnet-15 and
uses RPC/P2P ports 22443/22444 and separate chain and wallet storage.

The release contains standalone node, GUI-wallet, and GPU-miner packages for
Windows and Linux. Nodes and wallets download the 6.4 GB model bank. Miners
download 61.2 GB of model and preprocessed prover inputs on first launch.
Launchers fetch parts concurrently, resume interrupted downloads, and require
the pinned byte count and SHA-256 identity for every part and assembled input.
Versioned inputs are served from downloads.commonfoundry.ai on Cloudflare R2,
with the GitHub binary release retained as an automatic fallback. This gives
testers a faster primary path without changing any authenticated input bytes.
Assembly now computes that final identity while writing instead of rereading
the completed file, and up to 16 parts download concurrently. Later launches
authenticate the 6.4 GB model and three Merkle trees once, while the 48 GiB of
row-major proving data is reused as an explicitly untrusted cache. Every row
opened from that cache is checked against a record-pinned tree, and every
finished proof still passes mandatory CPU self-verification before submission.
The Windows miner has a tester-ready START-MINER.bat that prompts for a
receive address. Windows launchers work with the built-in Windows PowerShell
5.1 or PowerShell 7. The Linux packages require curl and Python 3; the GUI
wallet also requires WebKitGTK 4.1.

The release now also includes self-contained reference-pool packages for
Windows/WSL2 and native Linux. Pool operators get durable share, block, credit,
and payout accounting; authenticated automatic Devnet payouts; bounded replay
admission; TLS certificate pinning; a polished loopback dashboard; and the same
resumable authenticated input bootstrap used by the miner. The pool defaults
to a seven-leading-zero-bit share target, one bit easier than the Devnet block
target.

Pool rewards now use exact-work-weighted PPLNS accounting. Each discovered
block freezes its rolling share window and operator fee, waits for the 100-block
coinbase maturity, then distributes every atom remaining after the fee. The
operator fee defaults to 3% and is configurable from both Windows and Linux
launchers; the automatic window represents one expected block of share work.
The dashboard discloses the current policy, per-block split, maturity progress,
and matured operator fees.

Pool packages now include a separate local operator console for Windows and
Linux. It presents live service health and accounting, the latest pool log,
guarded start, graceful-stop, and restart controls, and editable operator-fee
and PPLNS-window settings for future blocks. The console binds only to
127.0.0.1:22448; every state-changing request is same-origin protected, and
stop or restart always uses the pool's authenticated ledger-preserving shutdown
path.

The GUI wallet can mine those ProductionV4 pool jobs directly. It keeps the
payout key inside the wallet, searches server-issued work with the persistent
32-lane CUDA replay worker, and submits only the qualifying nonce. The pool
independently replays each submission before crediting it. Share-result waits
now tolerate normal short socket polling intervals while retaining a bounded,
interruptible five-minute response deadline, so an honest GPU verification no
longer causes the wallet to reconnect or resubmit stale work.

The Windows standalone miner can also mine to a pool using only its payout
address. The official test pool and its certificate pin are prefilled; edit
WALLET_ADDRESS and WORKER_NAME at the top of START-POOL-MINING.bat, then
double-click it. The certificate-pinned pool connection credits accepted work
to that receive address, while the pool still replays and verifies every
submitted nonce independently.

Windows mining now keeps authenticated hot inputs in the WSL-native filesystem
and creates each attempt's temporary trace in native Linux storage. Windows and
Linux launchers keep the replay and proof workers alive across blocks, so model
loading, artifact authentication, memory mapping, and CUDA setup are reused.
Nonce search runs continuously in a 6.021 GiB search-only replay mode, and only
a qualifying nonce is replayed with full traces. Dynamic commitment generation
is fused into the proof worker, which reuses the uploaded traces for relations
and openings. These changes preserve the proof transcript, mandatory CPU
verification, and all authenticated input bytes.

Windows and Linux miner consoles show compact session statistics only. Hashrate
is reported as Forge Work per second (FW/s), where one Forge Work is one
complete ProductionV4 nonce evaluation. Compute is the corresponding TMAC/s
at the fixed consensus geometry of 0.824633720832 trillion multiply-accumulates
per Forge Work. The same line includes accepted and rejected submissions,
average GPU wattage, accepted blocks per kWh, peak GPU temperature, and
last-attempt time. Full prover diagnostics are retained under work/logs and
are printed only when an unexpected failure stops mining.

Nodes now exchange bounded peer lists after the network and consensus
handshake. Newly advertised addresses are connect-back verified before they
are cached or shared, while total, per-IP, retry, and message limits keep
discovery lightweight. The community bootstrap provides first contact, and
compatible nodes can then discover one another automatically.

Wallet transactions now propagate outward to configured and discovered peers
through bounded inventory comparison and the node's normal transaction
validation policy. This lets a standalone miner connected to the community
bootstrap include transactions created by a separately running wallet, while
duplicate, invalid, and over-capacity submissions remain fail-closed.

Wallet and node startup now keep the authenticated fast-start checkpoint
current whenever the canonical chain advances. On the live Windows Devnet
wallet, a warm restart with a 6.25 GB block log reached its ready node listener
in 9.5 seconds, compared with about 8 minutes 40 seconds for the one-time full
historical replay used to establish the checkpoint. The append-only block log
remains authoritative, and deterministic replay remains available whenever a
checkpoint cannot be used.

P2P ingress now includes bounded per-source reputation, temporary bans for
repeated objective protocol failures, and connection-attempt and concurrency
limits. IPv4 addresses and IPv6 /64 prefixes are tracked consistently, while
ordinary outbound outages do not reduce a peer's reputation. These controls
make public nodes more resilient without changing consensus behavior.

ProductionV4 replaces the multi-hour BLS12-381 transition proof with a
KoalaBear-native GPU proof. The complete proof is exactly 12,025,320 bytes
inside the ProductionV4-only 16 MiB block bound; older networks retain their
existing limits.

A live RTX 5090 acceptance run with 32-nonce search batching produced block
236 in 13.8 seconds from snapshot through node acceptance. The batch evaluated
32 complete candidates in 2.421 seconds of GPU time and 2.935 seconds of search
wall time. It reported 10.90 FW/s and 8.99 TMAC/s, up from 4.39 FW/s on the
single-nonce stacked path. Search reached 100% GPU utilization and 570 W during
the batched kernel, while the complete search, replay, proof, CPU verification,
and submission cycle averaged 192.8 W. The winning full replay took 0.132
seconds, fused proof construction took 7.547 seconds, mandatory CPU
self-verification took 0.296 seconds inside that proof phase, and submission
took 0.584 seconds. The finished 12,025,320-byte proof verified and all required
mutation checks were rejected.

Batching changes only search throughput. Candidates share the resident model,
then the first qualifying nonce in canonical nonce order is rebound and replayed
through the unchanged full-trace path. Its final activation must match the
batched result byte for byte before proof construction. An eight-nonce
differential test matched every coefficient stream and every complete final
activation against separate single-nonce replays. Batch size 32 was selected
after testing 1, 2, 4, 8, 16, 32, and 64 candidates; 64 used more memory without
improving throughput. The 32-lane search allocation is 6.445 GiB, preserving
the memory-conserving 16 GB GPU path.

Physical RTX 5070 Ti 16 GB qualification produced and CPU-verified the exact
proof on the prior process path. The new launchers automatically use a
memory-conserving schedule below 20 GB: the replay model is evicted before
proving and restored for the next search. The measured persistent proof and
full-replay allocations total 14.576 GiB at their conservative overlap bound,
keeping the supported 16 GB tier while larger cards retain the model for lower
latency.

An accepted height-2 block was produced through normal P2P admission and was
downloaded, verified, and persisted by an independent second node. This is an
experimental low-difficulty test network. Coinbase rewards remain immature
for 100 blocks before becoming spendable. Coins have no value.

Common Foundry v0.1.0-devnet.15 — ProductionV3 Devnet RC1

Choose a tag to compare

@JustAResearcher JustAResearcher released this 26 Aug 20:33
0140526

Test candidate. ProductionV3 Testnet-1 is a private, low-difficulty test
network. It is not RCNet and not mainnet, and its coins have no value.
No complete ProductionV3 block has been mined and verified end to end yet —
that is exactly what this prerelease asks testers to do.

Which download do I need?

I want to... Download
Run a node commonfoundry-node-v0.1.0-devnet.15-<platform>
Send and receive CMFD commonfoundry-wallet-v0.1.0-devnet.15-<platform>
Mine commonfoundry-miner-v0.1.0-devnet.15-<platform> (fetches the model bank itself on first run)

Nodes and wallets are self-contained: they ship the platform proof worker and
the ceremony-authenticated Record V2, and need no GPU and no model bank.

Miners: set your address and start

Extract the miner package, open its launcher (START-MINER.bat on Windows,
start-miner.sh on Linux), and set PAYOUT_ADDRESS to your wallet's
64-character receive address. Then run it. The first run downloads the
6.4 GB model bank automatically as four verified parts, checks every
SHA-256, assembles MODEL-V2.bank, and starts mining; later runs start
immediately. Point LOCAL_PEER at your own node or wallet if you run one;
otherwise the public bootstrap issues your work.

The bank ships as four split assets only because GitHub caps a release
asset at 2 GiB. For offline preparation, the .part files and
REASSEMBLE-MODEL-BANK scripts remain downloadable and produce the same
verified MODEL-V2.bank in the miner's production-v3 folder.

Network

ProductionV3 Testnet-1 uses RPC 21443 and P2P 21444. These are deliberately
different from Devnet-14's ports, and the chain data lives in a separate
directory, so the two networks cannot be mixed.

Verifying your download

SHA256SUMS.txt covers every asset, and BUILDINFO.json records the exact
source commit and tree the binaries were built from.


Common Foundry v0.1.0-devnet.15 — ProductionV3 Devnet RC1

Devnet-15 is the first tester build that selects the intended ProductionV3
proof path rather than the tiny ForgeMatrix-v2 reference profile. It is a new
test network and is not chain-compatible with Devnet-14.

Consensus and proof path

  • Selects the production geometry: batch 128, dimension 4096, and 384 layers.
  • Requires a succinct ProductionV3 proof before a block can be accepted,
    replayed, or adopted from a side branch.
  • Binds the final activation table, model identity, block statement, and work
    digest into the proof transcript.
  • Uses the fixed-width compressed WHIR transport and rejects proofs above the
    network proof-size limit.
  • Verifies proofs in a persistent, hash-pinned worker process. A worker crash,
    timeout, identity mismatch, or malformed proof fails closed.
  • Loads the ceremony-authenticated Record V2 at nodes and wallets. The full
    model bank and manifest are miner-only inputs.

Mining

  • The standalone miner uses the real ProductionV3 model bank and proof
    generator; it does not use the Devnet-14 reference proof.
  • CUDA packages target Volta and NVIDIA 20-, 30-, 40-, and 50-series GPUs and
    enumerate all supported GPUs in a rig.
  • One immutable node template is retained while its long proof is generated,
    then the exact completed block is submitted to the issuing node.
  • The miner reports per-GPU rate, power, efficiency, temperature, fan, clocks,
    VRAM, accepted blocks, stale jobs, and proof activity.

Node and wallet packaging

  • Nodes and wallets ship with the platform proof worker and authenticated
    Record V2. They do not need a GPU or the 6.4 GB model bank to synchronize,
    send, receive, or verify blocks.
  • On first run the miner launcher downloads the model bank's four split
    release assets, verifies every SHA-256, and assembles the bank beside the
    miner automatically; standalone reassembly scripts remain available for
    offline preparation. The split exists because no single release asset may
    exceed GitHub's upload limit.
  • The wallet keeps its peer editor, automatic bootstrap peer, public-testnet
    opt-in, local-only RPC, and two-decimal CMFD display.
  • ProductionV3 uses a separate data directory and network identity, preventing
    accidental reuse of the Devnet-14 chain.

Operational notes for Windows testers

  • Stop a node with Ctrl+C in its console window so the verifier sandbox can
    clean up after itself.
  • ProductionV3 refuses to reuse verifier-sandbox state whose owning process
    died without cleaning up. If a node or wallet was force-killed (Task
    Manager, a crash, or power loss), the next start reports a "stale
    AppContainer cleanup session ... manual remediation is required" error.
    With every Common Foundry process stopped, delete the leftover folders
    under %LOCALAPPDATA%\CommonFoundry\AppContainerProfileCleanupV1 and
    start again. Never delete them while a node, wallet, or miner is running.

Tester acceptance targets

This prerelease is ready for community validation, not a mainnet declaration.
The requested test is deliberately end to end:

  1. Start two or more packaged nodes or wallets and confirm they complete the
    ProductionV3 handshake and synchronize.
  2. Set a payout address in the miner launcher, start it (the first run
    fetches and verifies the model bank automatically), and generate one
    complete ProductionV3 proof.
  3. Confirm the issuing node accepts the block and every other node advances to
    the same height and tip.
  4. Restart a node and confirm block-log replay verifies the proof again.
  5. Send CMFD between two tester wallets and confirm both balances after sync.
  6. Report proof time, proof size, peak miner memory, verifier time, GPU model,
    power, and any worker restart or rejection messages.

All release assets are accompanied by SHA-256 checksums and build information.

SHA-256

252e639bdeb3ade739a695fe63f8e74d8572981ad0a924e972a5c42ff7861a2b  BUILDINFO.json
ac00f4df8ecb0702628197fc71fb161a46fd734cce7a89f748d09d692089b3c8  RCNET1-MODEL-RECORD-V2.json
3af0fd15bf0377bab42f2c59d8337f4f82e87e32c5f8c4f27ebfc21681450254  RCNET1-MODEL-V2.bank.part01
9d4f2547dc632c1c5f74ace84d26ca2ce38be50bea01ed93542fc5ab56aed6cf  RCNET1-MODEL-V2.bank.part02
a1bf1ac3230a54006039b3ce2add912e4c6f94065afad322bbaebee15b089602  RCNET1-MODEL-V2.bank.part03
5af1c6de16f5d48032aa9b37a5d48abd5d6c6e22b24935476faddb9af2cf7069  RCNET1-MODEL-V2.bank.part04
0365b818080dcd48f37a9a8b8d1ef4ce400fa391b54acfbd0c15841b47ccc19e  RCNET1-MODEL-V2.manifest.json
9a2104c683324fc77234567ef523105e4f9dbf511433483ac7611e03a52c29aa  REASSEMBLE-MODEL-BANK.bat
f93d120402ab435a7a1a8ae418090060bb1a77ab4561ac91178bf0b794f93efd  REASSEMBLE-MODEL-BANK.sh
85080cb63f29ad0f9fc4ec8d4e52dc9253c03a7cd0c294744c20acc35ae6735b  RELEASE_NOTES.md
ef95da3cdc1cea7910fbddc5c3dfb04814b8a229bcdf12107cd89249fe51cc3b  commonfoundry-miner-v0.1.0-devnet.15-linux-x86_64-gnu.tar.gz
b73ac0a931048c42ccd8a63cd5dd50e7f8727525ba38a99bf7253767be6cb875  commonfoundry-miner-v0.1.0-devnet.15-windows-x86_64.zip
241372848b8b05bc7a9863d42666a53685f55d80966027acc3cd6c5831cb8884  commonfoundry-node-v0.1.0-devnet.15-linux-x86_64.tar.gz
fac225403c633ff708fd31968a9caa3864e674bc827eafe4a170d1a26bda54bc  commonfoundry-node-v0.1.0-devnet.15-windows-x86_64.zip
627d873e3949e29b18a1efc32131816b59db43d41bb6df25ea03a223b9945e0c  commonfoundry-wallet-v0.1.0-devnet.15-linux-x86_64.tar.gz
f2522e9d8970855b01e74f6ef6e69055b8ad04508100b3fa2efa1698e90624a9  commonfoundry-wallet-v0.1.0-devnet.15-windows-x86_64.zip

Common Foundry v0.1.0-devnet.14 - Integration Devnet

Choose a tag to compare

@JustAResearcher JustAResearcher released this 25 Aug 20:10
v0.1.0-devnet.14
0140526

Common Foundry v0.1.0-devnet.14

Status clarification - August 25, 2026: This release validates the Devnet integration stack using the tiny ForgeMatrix v2 reference profile. It is not the production/mainnet RC1 and does not represent final GPU utilization, power, proof size, or performance.

Peer-settings hotfix — refreshed August 25, 2026: the packaged wallet
capability policy is corrected, so the Network screen can add, remove, reset,
and persist configured peers on Windows and Linux.

Devnet-14 is the public binary integration test release for the existing Common
Foundry Devnet-0 network. Production and mainnet activation remain disabled.

This download repository intentionally contains no application source code.
GitHub's automatically generated Source code archives contain only the
repository's distribution metadata, not the Common Foundry implementation.

Highlights

  • Persistent wallet peer management with add, remove, reset, restart
    persistence, and clearer diagnostics.
  • Windows and Linux wallet, node, and standalone-miner packages.
  • CUDA support for Volta and NVIDIA RTX 20-, 30-, 40-, and 50-series GPUs,
    including multi-GPU controls.
  • Runtime-loaded OpenCL support for Intel Arc.
  • Graceful node shutdown and stalled-session regression coverage on Windows and
    Linux.
  • Stronger build-identity, archive-safety, reproducibility, and
    release-provenance checks.
  • Continued production-proof research behind dormant, fail-closed feature
    gates; Devnet consensus still uses its existing reference profile.

Recommended downloads

Windows

  • GUI wallet installer: Common.Foundry.Wallet_0.1.0-devnet.14_x64-setup.exe
  • Node package: commonfoundry-node-v0.1.0-devnet.14-windows-x86_64.zip
  • Standalone miner:
    commonfoundry-miner-v0.1.0-devnet.14-windows-x86_64.zip

Linux x86-64

  • GUI wallet: Common.Foundry.Wallet_0.1.0-devnet.14_amd64.AppImage
  • Debian/Ubuntu wallet: Common.Foundry.Wallet_0.1.0-devnet.14_amd64.deb
  • Node package: commonfoundry-node-v0.1.0-devnet.14-linux-x86_64.tar.gz
  • Standalone miner:
    commonfoundry-miner-v0.1.0-devnet.14-linux-x86_64-gnu.tar.gz

The individual node and wallet executables are also attached for advanced
testers.

Upgrade and verification

  • Preserve existing wallet data; replace only the application binaries.
  • Devnet-14 remains compatible with the current Devnet-0 chain and P2P port
    18444.
  • Verify every download against SHA256SUMS.txt before running it.
  • BUILDINFO.json records the exact build identity and artifact inventory.
  • Windows executables are not code-signed and may display an unknown-publisher
    warning.

See the attached RELEASE_NOTES.md for the complete technical change and
qualification notes. Please report reproducible problems through this
repository's Issues section without posting wallet recovery material, private
keys, passwords, or tokens.