A little clarity goes a long way.

PapoPool is an independent mining pool being prepared for the Common Foundry native Mainnet. It brings miners together around ForgeMatrix GPU proof of work. It is not the official Common Foundry pool. The website is ready to display pool data, but the mining service has not been announced as open.

ForgeMatrix is Common Foundry’s matrix-based proof of work. FW/s measures complete ForgeMatrix nonce evaluations per second. It is not GPU TOPS or a conventional hash rate measured in MH/s. Mining secures the chain; customer-paid AI inference is a separate service layer.

Use a compatible GPU and the official Mainnet mining package. Official NVIDIA miners support the documented CUDA architectures. An AMD ROCm/HIP pool miner for Linux is available from release 1.0.16; Windows/WSL2 support is experimental. Hardware qualification varies by package, so check the current release notes before installing.

A worker identifies one mining process, GPU or rig under your payout address. Use a unique, recognizable name for each one, such as rig-01.gpu0. The official pool protocol binds a worker label to the authenticated payout key for the session.

The miner checks the SHA-256 fingerprint of the pool’s exact TLS leaf certificate before sending authenticated work. Copy both the numeric IP and the published pin. If the certificate changes, verify the new fingerprint before reconnecting. The website’s HTTPS address and the miner’s TLS endpoint serve different purposes.

Pay Per Last N Shares distributes a mature block’s eligible mining reward among work in a recent share window. The official implementation weights contributions by exact share work. Your share of that work determines your allocation after the operator fee. Rewards depend on blocks found by the pool; there is no guaranteed daily return. The dashboard shows the current window reported by the pool.

The operator fee reported by the pool API applies to eligible mining rewards. It supports pool operation and is separate from blockchain payout transaction fees. See the dashboard for the current rate.

Common Foundry mined rewards require 100 confirmations before becoming spendable. A discovered block may therefore appear as immature before rewards can be credited. Confirmation progress depends on the chain; a fixed wall-clock payout time is not guaranteed.

Eligible balances follow the settlement settings reported by the pool API. See the dashboard for the minimum payout, fees and any accounting holds. Settings absent from the API are unavailable. The website shows actual payout transactions and does not sign or send payments.

Accepted shares passed the pool’s checks. Rejected shares failed acceptance. A stale share usually refers to work on a job that is no longer current; stale shares may also be counted among rejected shares, depending on the backend’s counters. They should not be added together without checking that definition.

An orphaned pool block is no longer on the canonical chain. Its reward is not distributed as a mature canonical block reward. The pool must follow the active chain and its accounting rules when a reorganization occurs.

The website is available before its separate pool backend is connected. Unavailable means the API has not reported this value. No miners, work rates, balances, blocks or payouts are simulated. Pool connection details will be published only when the operator has verified them.

No. Looking up statistics only requires your public receiving address. Your payout key is handled locally by the official miner or wallet. The website never asks for a seed phrase, private key or wallet file.

Visit Common Foundry’s official website ↗ and Mainnet explorer ↗. When pool records are connected, block and payout rows can link to their official explorer pages.