Fees and rewards

How SoloMining fees and Bitcoin rewards work

SoloMining's published policy allocates 1% of mining work to the platform and 99% to the user. Under that policy, a valid block found on user-assigned work is directed to the configured Bitcoin address through the coinbase transaction, with no second block-reward fee. This page describes the published model; it does not independently inspect a live job or payout.

A fee paid through work allocation

Enter a connected hashrate to see the intended long-run split. Short periods need not show an exact split because submissions are discrete and probabilistic.

Connected hashrate
100 TH/s
User allocation (99%)
99 TH/s
Platform allocation (1%)
1 TH/s

A long-run allocation illustration, not a promise about every short dashboard window. The fee applies through mining work even if no block is found.

Hashrate fees and reward deductions are different

With a hashrate allocation, some work is assigned to the platform and the rest to the user. With a reward-deduction model, an operator takes a stated portion of a successful reward. Compare the basis and timing, not just the headline percentage. Receiving an undeducted user-block reward does not erase the opportunity cost of the platform's work allocation.

  • At 100 TH/s, the intended long-run equivalent is 99 TH/s for the user and 1 TH/s for the platform.
  • The platform allocation is not user-assigned work, even if that allocation finds a block.
  • Do not apply this 1% again to a probability input that already represents the user's effective hashrate.

What the published reward model says

SoloMining's published policy says the reward destination for a valid block found on user-assigned work is your configured Bitcoin address in the coinbase transaction. The block's subsidy and included transaction fees are assigned to that address under the stated model. This page does not independently verify a live job or payout. Ordinary accepted shares do not create a shared daily balance.

  • The subsidy and included transaction fees are separate parts of a block reward.
  • No block found by your allocation means no block reward from that allocation.
  • Check the complete service terms for conditions beyond this allocation illustration.

How to evaluate a reward path

A receiving address in a settings form and a statement about private keys are not complete proof of the job's payout destination. Technical verification examines the coinbase transaction reconstructed from the actual mining job and the resulting outputs. A source-code feature or another pool's transaction does not establish how a particular live service constructs your jobs.

  • Inspect the job actually received by the miner with compatible verification tooling.
  • Compare the resulting payout script with the intended receiving address and the allocation being inspected.
  • For a historical claim, verify the block identity and coinbase outputs on an independent explorer.

The stated reward destination and spendable balance are different stages

The published model identifies a reward destination; it does not prove that a live job or payout followed that route. The block must be accepted on the Bitcoin main chain, and its coinbase reward must satisfy Bitcoin's maturity rules before spending. A stale candidate or a block removed by a reorganization is not the same as a mature main-chain reward.

  • A coinbase reward must satisfy Bitcoin's maturity rules before it can be spent.
  • A reported candidate is not the same as a block accepted in the eventual main chain.
  • Address-format validation cannot recover a lost key or prove control of the address.

Check the receiving address before you connect

Under the published model, the address saved on the miner is intended as the destination for a user-assigned block reward. Check it after pasting and after firmware or configuration changes. Once a block is found, its coinbase outputs can show the on-chain reward destination; an actual payout claim also needs evidence linking that job and block to the service and allocation.

Content updated: 3 October 2026 · Policy and sources checked: 6 September 2026

Fee and reward questions

Is SoloMining free if it does not deduct my block reward?

No. The published service fee is a 1% allocation of mining work to the platform. The remaining 99% is the user's effective allocation under that policy. A user-assigned block reward is not charged again, but the work allocation still applies during periods without any block discovery.

Do I keep the transaction fees if my allocation finds a block?

SoloMining's published policy says the subsidy and transaction fees in a valid block found on user-assigned work are assigned to the configured Bitcoin address through the coinbase transaction. This page does not independently verify a live job or payout. The 1% service fee is described separately as mining-work allocation; coinbase maturity rules govern when a reward can be spent.

Does my block reward pass through a SoloMining.xyz wallet?

SoloMining's published policy says the subsidy and transaction fees for a valid block found on user-assigned work are assigned to the configured Bitcoin address through the coinbase transaction. This page does not independently verify a live job or payout. Bitcoin's coinbase maturity rules still apply before a reward can be spent.

Can I use the Blocks page as proof of this pool's payouts?

The existing Blocks page displays recent Bitcoin mainnet blocks from Bitcoin Core. It is not an attributed record of this service's discoveries or payments. A payout claim needs a correctly identified block and its coinbase outputs, linked to the service and allocation in question. Network-wide activity does not supply that attribution.

Will a short dashboard window always show exactly 1% and 99%?

No. The illustration describes an intended long-run allocation. Shares arrive discretely and probabilistically, and dashboard windows are limited. Do not infer a precise split from a handful of submissions or treat ordinary rejected counts as fee accounting. Questions about a specific allocation require the relevant operational records.