OBSERVED BLOCKS
—No indexed blocks yetKnow your pool. Make your own choice.
Independent evidence for informed XBT mining choices. Understand miner control, pool transparency and what the data can tell you.
Loading exchange quotes…
Recent changes · Loading…
RECORDED LIVE HISTORY · SEPARATE FROM SAMPLE MODE
Loading recorded changes…
Up to four recorded profile updates from the last 30 days and two share shifts of at least 5 percentage points between consecutive complete UTC days with 100+ blocks each. Share shifts can reflect ordinary mining variance or attribution changes. Profile dates show when we recorded a change, not when the operator made it; website terms are reviewed snapshots.
All trends & changes →
Waiting for observationsData delayed
LARGEST ATTRIBUTED POOL
—Attribution pendingUNKNOWN BLOCK SHARE
—Kept visible, never redistributedBLOCK PRODUCTION
Where blocks come from
Largest first · clockwise
—blocks observed
Pool attribution groups blocks using explorer labels and documented evidence.
Explore shared payout addresses →Auto-refreshes every 30 seconds. Mining share is estimated from blocks in the selected observation window.
CONCENTRATION WATCH
Signals worth a closer look
Crossing a watch level is a concentration signal, not evidence of an attack.
Pools to consider
Below 15% observed block share in the selected window. Public options advertising miner-built templates with your own node and DATUM gateway. Options to research—not ratings or endorsements.
Choosing a pool: Start with control of your own templates, understandable payout rules and a smaller observed mining share. Compare the evidence, check the unknowns, then follow the operator’s setup guide. The reasons below summarize dated operator claims; they are not certifications.
Checking network share…
Bitcoin Xor →
Observed share: loading…
Why consider it: Advertises own-node DATUM and shared payouts directly in the coinbase.
Fees: 1% own-template DATUM; 2% pool-built templates.
Terms source · Sep 18, 2026 ↗What to check before connecting
Choose the own-template connection; confirm current fees and whether the payout terms apply to the service you use.
Review recent block evidence and operational history. A smaller observed share does not establish independent ownership or reliable payouts.
DATUM connection details
Set these in your gateway’s datum configuration. Run your own synced BLAKE2b node; connect ASICs to your gateway’s Stratum address.
pool_host: datum.xorpool.com
pool_port: 28915
Regional alternatives: eu.datum.xorpool.com (Europe), hk.datum.xorpool.com (Hong Kong). Same port and key; default host is US.
pool_pubkey:b83aedbba54ba2aa605c76859d97aebd16dece3284402b9fc874778a974da4acbb449f6ccda61625d700036f0487a05f5184f79a07abf2880da77352f4cc487e
Operator source ↗ · checked Sep 24, 2026. Published settings, not a connection test. Confirm the key and current settings with the setup guide before use.
Historical luck · optional context
Luck (7 days): 107% · pool-reported
Shared DATUM service only · snapshot checked Sep 24, 2026; not live or independently verified.
Past luck does not improve the odds of future work. It is not a selection criterion.
CONVOY →
Observed share: loading…
Why consider it: Its recorded setup guide makes your own node and DATUM gateway the primary mining path.
Fees: 1% own-node DATUM; 2% Stratum failover.
Terms source · Sep 17, 2026 ↗What to check before connecting
Confirm payout method and minimums. Direct Stratum failover gives up your own-template control.
Review recent block evidence and operational history. A smaller observed share does not establish independent ownership or reliable payouts.
DATUM connection details
Set these in your gateway’s datum configuration. Run your own synced BLAKE2b node; connect ASICs to your gateway’s Stratum address.
pool_host: datum-beta1.mine.convoy.xyz
pool_port: 28915
pool_pubkey:dbb11fa0c2b5403e4f798fa6071bb97e6079d219598366032fdf2ae01962b13c5e66e2be7d6b008f0b2603f3e6f6fc64768fa786c8129c46d3e30a5867734b62
Operator source ↗ · checked Sep 24, 2026. Published settings, not a connection test. Confirm the key and current settings with the setup guide before use.
Historical luck · optional context
Luck: Not available
No comparable, verified source recorded.
Past luck does not improve the odds of future work. It is not a selection criterion.
RIPTIDE →
Observed share: loading…
Why consider it: Advertises an own-node DATUM path with a recorded 0% DATUM fee.
Fees: 0% DATUM; variable SV1, last recorded at 1%.
Terms source · Sep 17, 2026 ↗What to check before connecting
Confirm current fees, payout minimums and when payments are coinbase versus manual; public SV1 is a separate path.
Review recent block evidence and operational history. A smaller observed share does not establish independent ownership or reliable payouts.
DATUM connection details
Set these in your gateway’s datum configuration. Run your own synced BLAKE2b node; connect ASICs to your gateway’s Stratum address.
pool_host: riptide.maveth.ca
pool_port: 29120
Default 0% DATUM port, minimum difficulty 1024. The guide also lists port 29121 for minimum difficulty 8192. Follow its worker-name setting: pool_pass_full_users: false.
pool_pubkey:b95abf4a11050c5164d09e9d3c4a18a4df735c5d670e3e974fc146794efa4ed9fbc78e7cd4b6abcd3fcc0e0619543d60004fdb49e9d2974582ae11988a03d743
Operator source ↗ · checked Sep 24, 2026. Published settings, not a connection test. Confirm the key and current settings with the setup guide before use.
Historical luck · optional context
Luck: Not available
No comparable, verified source recorded.
Past luck does not improve the odds of future work. It is not a selection criterion.
Compare these pools →
How these options were selected
Luck compares actual blocks with expected blocks from mining work over the same period and service. Using actual / expected, 100% is expectation; above 100% means more blocks than expected. Past luck does not improve future odds. The dated pool-reported figure uses its own seven-day period, not the selected network-block window; shared-service luck may cover less than the explorer attribution. Observed block share alone cannot establish luck. Missing luck is not zero.
A starting shortlist with published public connection guides and an advertised own-node DATUM path, listed alphabetically. Telemetry participation is not required. This is not an exhaustive list, ranking or endorsement; omitted pools may also qualify. Template-control statements are operator claims, not independent assessments. Terms are dated snapshots; confirm fees and availability with the pool before connecting. Only pools with available, fresh observed block share strictly below 15% in the selected window appear. Sample data and missing attribution do not qualify. Observed block share estimates network hashrate; it cannot guarantee a pool is below 15% of actual hashrate.
ATTRIBUTION REGISTER
Pool distribution
| Pool / attribution | Blocks | Observed share | Details |
|---|
Ratings are in draft. “Not assessed” is not a failing grade.
Read the framework →
AlphaPool includes a documented collection-address grouping across changing tags. Evidence and research credit ↗. This identifies payout collection, not template control.
LATEST OBSERVATIONS
The block feed
FOLLOW THE COINBASE
Payout-address activity
Recipients of block rewards. An address is not automatically a pool or an independent miner.
| Recipient address / script | Blocks appearing in | Coinbase amount (XBT) | Documented role |
|---|
A block may pay multiple recipients. These amounts describe coinbase outputs, not current balances or spendable funds.
— · No participating sources yet
SEPARATE POOL SIZE FROM TEMPLATE CONTROL
Who chooses the work?
Cooperating gateways can share difficulty-weighted work and block outcomes.
Accepted-work telemetry is not connected
Accepted-work reports describe participating providers only. Work-only feeds cannot establish block outcomes or template control.
How participation and decentralization ratings work →
01 Identify the template operator02 Measure work, not template counts03 Compare block outcomes
SHOW THE EVIDENCE
What these numbers can tell you
Observed share, with uncertainty
Pool share is attributed blocks divided by all observed blocks in the selected window. Unknown blocks remain in the denominator. The 95% Wilson interval describes sampling uncertainty under an approximately stable block-finding share; it cannot capture attribution mistakes or rapidly changing hashrate.
Attribution is evidence, not identity
Pool tags and documented collection or fee addresses support attribution. Tags can be copied, addresses can rotate, and conflicting matches stay unknown. Ordinary miner payout addresses are never used to infer pool ownership automatically.
Templates are not mining work
Refreshing a template does not add hashrate. Expected blocks are the sum of accepted share difficulty divided by the contemporaneous network difficulty, using the same difficulty convention. Template-control share requires work measurements and operator attribution.
Signals do not prove attacks
Threshold crossings flag concentration. A shortfall in blocks may reflect luck, accounting errors, stale work, or submission failures. Stratum V1 may connect ASICs to a DATUM gateway; a protocol label alone does not establish centralized template control.
Coverage and chain changes
Only the indexed sample is measured. The collector checks the canonical chain and rebuilds its retained window after a detected reorganization. Reorg observations depend on this node's view and are not a complete record of every competing block.
Independent public infrastructure
XBT Pulse reads chain data using a dedicated source. It needs no wallet keys and does not connect to a private mining pool. Telemetry remains unavailable until authenticated participating operators supply it. Sample mode is illustrative and never used for live alerts.
Optional operator contributions
Public data powers XBT Pulse. Operators can add context, corrections and telemetry.
The data source is delayed. Showing the last indexed observations; check the chart’s update time before interpreting changes.