Inspect the work.
Keep the limits visible.

Shared-address watch

Automatically compares exact positive coinbase recipients across original explorer labels and coinbase tags. Refreshes every 30 seconds using retained chain observations; no pool submission needed.

Shared recipients can be miners switching pools, fees, or collection addresses. A changing tag does not mean a new pool. Matches do not establish ownership, proxying or template control, and never merge pool identities. First/last seen dates cover retained block timestamps, not lifetime history or the time a pool launched. Reorganizations and retention can remove findings.

Reward-share filters require one matching block, not every block. Unclassified does not mean miner-owned. Search covers all retained matches; matching labels/tags appear first in each result.

Loading shared recipients…

Download current matches (JSON) → · Previously documented AlphaPool finding →

What we discovered

Loading the published snapshot…

Download the dated results (JSON) → · Method, source and reproduction →

Why there is no “proxy” verdict

A BLAKE2b job may expose a short work commitment rather than a full coinbase transaction. We do not turn that commitment into a payout address. If a full transaction can be decoded, shared payout scripts still do not establish common ownership or who selected the transactions.

A public Stratum connection also says nothing conclusive about the same pool's separate miner-controlled DATUM connections. A refusal or timeout can reflect the test client, network path or authentication requirements. It is not a downtime or misconduct finding.

Each check uses a fresh throwaway payout identifier, sends subscribe and authorize messages, waits for jobs, and disconnects. No hashing, shares, payouts, account creation or private credentials are involved. This pilot is a dated snapshot, not continuous monitoring.

Beyond the endpoint: inspect actual rewards

Multiple recipients do not prove miner-controlled templates. One PyBLOCK-attributed example has three positive recipients, yet one receives about 98% of its coinbase value. Lazarus-attributed examples range from one to 97 recipients. These are useful questions to investigate, not verdicts about operators.

Below we separate published claims from selected block observations and the evidence still needed. The explorer checks use the same source as our chain index, not an independent full node. Examples deliberately show contrasting payout shapes and are not a representative sample.

Pool operators: help fill the gaps.

We recommend submitting your pool for a transparency review. Explain your published endpoints, who builds templates on each path, any upstream routing or failover, payout rules and the scope of your telemetry. Sources and a reproducible explanation are more useful than a badge.

You can correct an endpoint or observation through our existing submission process. Participation is optional and does not automatically change an assessment. Operators have not been contacted through this pilot.