TRANSPARENCY / DOCUMENTATION

How the observer works.

Measurements, attribution rules and limitations are intentionally separated. No central service can infer every public pool from the blockchain alone.

Node measurements

Network hashrate, height and difficulty are sourced from the locally authenticated VMESH Core RPC. Private RPC is never made public.

Pool metrics

Miner counts, workers and pool hashrates are read only from configured operator APIs. Unavailable data stays unavailable.

Verified attribution

A recognized block is assigned to a named pool only when an explicit, independently checked coinbase tag or payout rule is configured.

Source candidates

Unknown blocks can be grouped by exact coinbase payout addresses or scripts. Groupings do not identify individual miners, public pools or ownership.

Sampling limits

Only indexed blocks count. Backfill progresses separately from the latest tip; a scan window may initially be incomplete. Historical API metrics begin when monitoring is activated.

Security and privacy

All public endpoints are read-only. API secrets and RPC access remain local. No visitor accounts or tracking cookies are needed.

OPEN DATA / JSON

Public read-only API

/api/v1/healthJSON ↗/api/v1/summaryJSON ↗/api/v1/poolsJSON ↗/api/v1/blocksJSON ↗/api/v1/network/history?days=7JSON ↗/api/v1/attribution?days=7JSON ↗/api/v1/discoveries?days=90JSON ↗/api/v1/charts/blocks?days=30JSON ↗