01 / BLOCK REWARDS
Rewards begin with valid blocks.
The network validates the block subsidy and transaction fees. Miners and pools work within those rules.
| RUB block height | Ordinary subsidy per block |
|---|---|
| 2–499,999 | 100 RUB |
| 500,000–999,999 | 50 RUB |
| 1,000,000–1,499,999 | 25 RUB |
These early eras are separated by 500,000-block intervals. Transaction fees are added to the block subsidy. A pool’s allocation method divides earned rewards among participants.
02 / POOL ACCOUNTING
Understand what each number means.
- Shares
- Accepted shares measure contributed mining work. They are used by the pool’s allocation method.
- Block rewards
- A valid block creates a reward on its own network. RUB and BTC block results are recorded separately.
- Allocations
- The pool calculates each miner’s share of an earned reward under the selected mining profile.
- Payments
- A payment is an on-chain transaction sent to a receiving address. Its transaction ID can be checked in the corresponding explorer.
03 / MATURITY & PAYMENTS
From earned reward to spendable RUB.
Mined RUB outputs require 100 blocks of coinbase maturity before they can be spent. Block maturity, pool accounting and payment processing are separate stages, so an earned or allocated amount may appear before a payment transaction.
PPLNS distributes rewards according to accepted work in a defined window. Solo uses a different reward method. Current fees and payment conditions are published by the pool.
Check your miner account →04 / BITCOIN REWARDS
The extra result has its own conditions.
In merged mining, RUB work can produce RUB blocks without a Bitcoin block being found. Bitcoin is the additional opportunity: a BTC reward exists only when a Bitcoin block is found and accepted.
For that reason, a RUB reward does not imply a BTC reward, and a RUB block count is not a Bitcoin block count. The dashboard keeps the two networks’ rewards and payments separate.
View merged mining results →