Connecting
POOL OVERVIEW
Every share counts.
Live work, rewards, and the chain behind them.
Waiting for live data
Pool hashrate
Persistent accepted-work history
Latest plotted—
Range average—
Minimum—
Peak—
Loading recorded history…
Hover or tap the chart to inspect a sample.
Hashrate estimates are stored independently of mining services and survive restarts.
Loading history…
More control.
More of your reward.
0%Direct DATUM pool fee
3%Public Stratum fee
Two percentage points of Stratum rewards are shared with eligible DATUM work. One goes to the pool.
Connect a DATUM gateway ↗Miners in the TIDES window
Work is tracked separately for each connection path.
| Payout address | Connection path | Hashrate | Window share | Next block allocation |
|---|---|---|---|---|
| Waiting for pool data. | ||||
PAYOUTS & INCENTIVES
Paid in the block.
TIDES rewards follow accepted work in the rolling payout window.
Block found
Miner allocations and eligible DATUM bonuses are included directly in the coinbase transaction.
Reward allocated, then held
A direct block payout is recorded immediately, but cannot be spent until maturity. See the activation heights and current wallet policy below.
Spendable rewards
Paperclip settles pool-owed amounts and mature carry-forward daily, using funds its node allows it to spend.
How the TIDES window works
Rolling work · 8× network difficultyYour share of rewards follows your accepted work in the most recent eight network difficulties of pool work. This is a work target, not eight blocks found or a fixed number of days. Shares are weighted by their assigned difficulty, not counted equally.
The window does not reset when a block is found. It moves forward as new shares arrive and resizes when network difficulty changes. Share history is retained so older work can re-enter after a difficulty increase. There is no fixed share-count cap on the active window.
While the pool has less recorded work than the target, allocations use all available work. The oldest share crossing the target remains included in full. Direct coinbase allocations are fixed in the payout split supplied for the mining job; the next-block estimates shown here continue to change with new work. The Community Bounty uses its separately recorded window when the block is found, as described below.
Block rewards: current maturity
Active since block 973,440The temporary network rule is active and began at block 973,440. Network rules determine which transactions can go into a valid block; wallet and relay policy can impose a longer wait.
| Block height | Network maturity rule |
|---|---|
| Rewards mined before 973,440 | Keep the ordinary 100-block maturity rule, including during the temporary period. |
| 973,440 through 979,919 | While this rule is active, rewards mined at or after 973,440 require a depth of 6,480 blocks before they can be spent. |
| From 979,920 | The temporary network restriction ends under this release. Ordinary 100-block maturity applies again unless a later upgrade changes it. |
Current Paperclip payout maturity: our wallet and relay policy now require 6,481 confirmations for unspent coinbase rewards: the reward block plus 6,480 additional blocks. This is roughly 45 days at a 10-minute block interval; actual time varies. The pre-activation 101-confirmation spending policy has ended.
The maturity countdowns and reserve balances follow this wallet policy. Older unspent coinbase rewards are also subject to this longer wallet policy, even though their network maturity rule remains 100 blocks. Already confirmed payments are not reversed; pending payments may have to wait. This patch retains the longer wallet policy after height 979,920, even though the temporary network restriction ends then. Ordinary confirmed, spendable deposits can still fund Community Bounty payouts.
Where the 3% goes
Illustration · not live earnings- Stratum miner · 97%
- 97,000 sats
- DATUM incentive · 2%
- 2,000 sats
- Pool · 1%
- 1,000 sats
Bonus allocations are proportional to eligible direct DATUM work, not divided equally between users. Whole-satoshi rounding applies.
Daily 00:00 UTC
No eligible DATUM work? The 2% allocation stays in the reserve for future DATUM users. It is separate from pool income.
- Reserve awaiting maturity
- —
- Mature reserve
- —
- Pool-owed rewards
- —
- Next settlement check
- —
Checking settlement service.
Direct coinbase payouts do not wait for the daily run. Network fees for settlement are paid by the pool. Small amounts remain owed until they can be paid.
COMMUNITY FUNDED · DATUM ONLY
0% pool cutDATUM Community Bounty
Help bring more independent templates to Paperclip. Contributions reward eligible DATUM miners alongside the existing Stratum-funded incentive, with a separate wallet and balance.
- Confirmed bounty balance
- —
- Available for new allocations
- —
- Reserved for miner carry-over
- —
- Awaiting coinbase maturity
- —
- Unconfirmed funds (including change)
- —
- Bounty payments in flight
- —
- Bounties paid (after fees)
- —
- Community-funded network fees
- —
Contribute to the bounty
Send Bitcoin Blake2b only. Contributions are voluntary and committed to DATUM miner rewards.
bc1qh0sx4gprk2wmuxrnzfsatzheanuqqmlghke4eg
Paid automatically after each pool block. Confirmed, spendable contributions are distributed proportionally to DATUM work in the frozen TIDES window recorded when that block was found. This does not change direct TIDES block payouts or the 97/2/1 allocation.
Payable miner balances are sent without waiting for smaller allocations. Amounts below the 546-sat payment minimum stay credited to the same address, then combine with its new allocation in the next block where it has DATUM work in the frozen TIDES window. Payment occurs once the combined amount reaches the minimum and funds cover fees. Saved credits are never redistributed to other miners. Without eligible DATUM work, unallocated funds carry forward.
Coinbase contributions now require 6,481 confirmations under the wallet policy above. Ordinary confirmed, spendable deposits can still fund per-block bounties. Network fees are paid from community contributions at 1 sat/vbyte; newly allocated funds after fees are shared proportionally among eligible DATUM miners. A small unallocated change buffer may remain to keep the transaction standard; it becomes available for a later block. If this fee rate is not accepted, payouts wait rather than increasing fees. There is no bounty amount cap. Each block can trigger one distribution, with network fees deducted from the bounty.
Loading bounty status.
| Bounty transaction | Created | Amount | Status |
|---|---|---|---|
| No bounty distributions yet. | |||
Found blocks & maturity
Countdowns follow Paperclip's wallet policy above| Block | Found | Miner allocation | Wallet maturity |
|---|---|---|---|
| No blocks found yet. | |||
Settlement history
Reserve and pool-owed payments| Transaction | Created | Recipients | Status |
|---|---|---|---|
| No settlement transactions yet. | |||
CONNECT TO PAPERCLIP
Bring your own template.
Connect a BLAKE2b-compatible DATUM gateway or use our public Stratum endpoint.
Checking mining readiness.
Direct DATUM
0% pool fee + incentiveRun a compatible gateway beside your own Bitcoin node with BLAKE2b support. Add these pool settings to your gateway configuration.
DATUM gateway requirements
DATUM protocol v3 is required. Your gateway must support the v3 / DRS handshake and Bitcoin BLAKE2b mining. Protocol v1 connections are rejected.
Soft fork active since block 973,440: independent DATUM operators must run their own updated Knots node using 29.4.2 rc2 or a compatible successor. Updating Paperclip does not update your local block templates. Confirm your gateway supports the node's changed difficulty RPC fields.
- RATUM Gateway by iohzrd: use a build with v3 support and set
datum.protocol_v3totrue, as shown below. - CONVOY DATUM Gateway: use an updated build that includes the DRS/v3 handshake. Older builds may report the same
v0.4.1-betaversion label while using protocol v1; the label alone does not establish compatibility. Follow Convoy's configuration instructions; the explicitprotocol_v3switch below is for RATUM.
Run a synchronized Bitcoin node with BLAKE2b support and working getblocktemplate RPC. Connect the gateway to pool.paperclippool.xyz:28915 with the pool public key below. Retain your own node RPC credentials and payout address.
Seeing “Not Ready”? Check gateway logs, node readiness, the pool host/port and public key. A “version 1 protocol” or “requires version 3” rejection means you must enable v3 in RATUM or update your gateway build. With pooled-only mining enabled, the gateway waits for a pool connection before serving work.
DATUM v3 describes gateway-to-pool communication. Your ASIC miners can still use Stratum V1 to connect to the gateway.
Waiting for pool configuration.
Keep your own node RPC settings and payout address. Miners attached to your gateway use their Bitcoin payout address as their username.
Public Stratum V1
3% feePoint your compatible Sia miner at our hosted gateway.
- Pool URL
stratum+tcp://pool.paperclippool.xyz:3333- Username
YOUR_BITCOIN_ADDRESS.worker- Password
x
97% of your gross allocation goes to your address. The other 3% funds the DATUM incentive and pool operation.
YOUR MINING ACTIVITY
Address dashboard
Monitor all accepted work credited to your Bitcoin payout address.
Enter an address to see its mining activity.
Address information
- Mining route
- —
- Payout eligibility
- —
- Latest gateway tag
- —
- DATUM window work
- —
- Stratum window work
- —
- Total window work
- —
Hashrate estimates combine accepted shares credited to this exact address. Work values are cumulative difficulty units within the TIDES window, not share counts. Individual device names, temperatures, rejected shares and online status are not exposed by the pool. A gateway using its own payout address aggregates its miners under that address.
Block reward history
| Block | Found | Address allocation | Payment type | Status |
|---|
Direct block rewards and separate settlement allocations are listed separately for available recent pool blocks. A direct reward is already paid, even while immature; it is not part of the unsettled allocation above. Community bounty payments are shown separately on the pool payouts page. The soft fork is active. Paperclip now requires 6,481 confirmations (6,480 additional blocks) for all unspent coinbase rewards, including older rewards. The pre-activation 101-confirmation policy has ended. The temporary consensus restriction applies from block 973440 through 979919; wallet and relay policy can remain stricter after that interval. Orphaned rewards are not payable.