Nexus Pool logoNEXUS POOL
Pool transparency

Clear terms for every hash.

Nexus Pool is designed so miners can understand where their work goes, how a successful block is handled, which statistics are public and what the pool retains.

1% transparent feeBTC & BCH solo miningUS · EU · Asia
Fee

A visible 1% pool fee

Nexus Pool charges a 1% fee on a successfully mined block. The split is constructed in the coinbase transaction: the configured miner payout address receives the miner portion and the configured Nexus Pool address receives the fee portion.

There is no hidden withdrawal fee or accumulated pool balance for ordinary solo mining.

Payout model

Solo rewards, not proportional shares

Submitted shares measure work and help monitor miners, but they do not create a proportional payout balance. A miner earns the configured miner portion only when its work produces a valid network block accepted by the applicable blockchain.

Mining is probabilistic. Hashrate, shares and best difficulty do not guarantee a block or reward.

Block handling

Permanent, verifiable block records

When CKPool reports a solve, Nexus Pool records the coin, height, block hash, timestamp, region, share and network difficulty, reward information and confirmation state. Public block history links to an independent blockchain explorer when a hash is available.

A candidate can remain pending or become orphaned according to network consensus. Nexus Pool does not control confirmation outcomes.

Architecture

Regional access, centralized accounting

Public Stratum endpoints in the United States, Europe and Asia reduce network distance for miners. The regional edge proxies forward Stratum traffic to the core pool; they do not change Bitcoin or Bitcoin Cash consensus rules.

Core nodes validate current mainnet work, while centralized accounting keeps wallet, worker and best-difficulty records consistent across regions.

Public statistics

What appears on the dashboard

  • Pool and regional availability, workers, users, hashrate and best difficulty
  • Wallet and worker hashrate, accepted work, last share and difficulty records
  • Worker health, recent history and the regional endpoint used by an active session
  • Pool-wide accepted, rejected and rejection-rate counters for the current CKPool processes
  • Confirmed and pending blocks found by Nexus Pool
Finder privacy

Miners control public credit

After looking up an active wallet, a miner can choose a recognizable worker name, an anonymized worker name or “Anonymous Miner” for public block history and Discord celebrations.

The preference is protected by a private management key retained in the miner's browser. Nexus Pool stores only a one-way hash of that key.

Data retained

Operational mining data

  • Payout addresses and submitted worker names
  • Share counts, timestamps, hashrate samples and difficulty records
  • Regional session labels and block-discovery metadata
  • Short-term operational and security logs, which may include network addresses
  • Encrypted configuration backups and monitoring records

Hashrate history is compacted and retained for dashboard chart ranges, with storage limits designed to prevent uncontrolled growth.

Not collected

No custodial or account data

  • No Nexus Pool user account is required for mining
  • No wallet private keys or recovery phrases are requested or retained
  • No custodial reward balance is maintained for the solo pool
  • No identity document, payment-card profile or exact physical location is required
  • Friendly worker labels, hidden rows and recent wallet lookups remain local to the miner's browser
Share-quality limits

Exact where possible, explicit where not

CKPool provides exact accepted and rejected totals at the pool-process level, and exact accepted work in persistent wallet and worker records. It does not expose rejected or stale counters per worker, and stale submissions are included within the pool rejection stream. Nexus Pool labels these limitations instead of presenting estimates as exact statistics.