Hashly / public method
Every claim
needs a trail.
Every figure in the catalog names its source and its time, and every radar event and author credit passed an editor. What we cannot verify is left blank rather than estimated.
Catalog data
Public sources, named
Network figures come from public explorers and node statistics; pool figures from each operator’s public API or statistics page. The source and the time of each reading are listed on the project or pool page. Where no feed can be verified, an editor checks the operator’s documentation and enters the value by hand, with its own check date.
Readings, not live feeds
Automatic sources are read about every 15 minutes. A reading that fails its checks is rejected and the last valid one stays visible, marked as delayed. Manually verified terms such as pool fees, reward schemes and connection examples keep the date they were checked. Refresh a page to see new readings.
A share is a ratio of two estimates
A pool’s share of a network is its reported hashrate divided by the network’s estimated hashrate. The two numbers can be measured at different times over different windows, so a share is an estimate. A 24-hour trend is shown only when comparable readings exist.
Sums are indicative
Pool lists are partial. The sum of listed shares can fall short of 100% because some pools are missing or do not publish figures, and it can exceed 100% because independent estimates overlap. Shares are never rescaled to fit, and the unexplained remainder is never assigned to a pool.
A dash is not a zero
When an operator does not publish a value — a pool fee, a reward scheme, a miner count, a connection address — the page shows a dash or “Not reported”. Conditional or contractual fees are described in words instead of being forced into one percentage. Values are never copied from another project or from the operator’s global totals.
Merged mining and several algorithms
Some Dogecoin estimates come from shared Scrypt work merged with Litecoin; they are labelled as shared-work estimates and never added to Litecoin figures. Tari is shown per algorithm, because hashrates of different algorithms cannot be added together.
Radar and callouts
Three dates, three meanings
The event date is when the reported launch or update happened. The source check date is when an editor checked the linked source. The Hashly publication date is when the event entered the public Radar. Adding a historical event today does not make its launch new today.
Published with a source
Each public event names and links a checked source. A linked post may have started the review, but Radar publication is a separate editorial decision. For an anonymous author, editors require an independent source outside X or Twitter and omit any link back to the post. A source supports a specific statement; it does not certify every project claim.
A link starts review
Anyone can submit their own or someone else’s public X or Twitter post about a listed project or suggest one we have not listed yet, without a Hashly account. The receipt confirms only that the submission was received. It does not show the review outcome, original post or author. Editors check the post, its author, the project reference and the time before admitting evidence.
Earliest among public evidence
For each project, eligible independent public posts are ordered by verified post time, with its precision shown. Private evidence is omitted from this ranking. Credit belongs to the verified post author, not the submitter. An official announcement can provide context but does not earn independent credit. Shared rank means the evidence cannot distinguish an order. This does not establish who first mentioned a project on the Internet.
Review before public credit
A submission can request privacy for the post author. That is a request for manual review, not an anonymity guarantee. Until it is resolved, the evidence is not publicly attributed. Anonymous authors appear only in aggregate leaderboard rows, without their post or project evidence. Editors can see the original source; prior publications, screenshots and outside links can remain identifiable.
A published snapshot
Editors choose which approved callouts and Radar events to publish together with the leaderboard. Unselected drafts stay private; new submissions do not update scores automatically. A project callout counts once per author and project with eligible verified independent evidence. Radar count reflects linked published events with eligible evidence. Equal counts share a rank. These are editorial activity counts, not a financial score or win rate.
Decisions can change
Attributions can remain provisional or be confirmed. Disputed and withdrawn public posts keep their correction history but lose their current rank. A privacy change can also remove a public credit and invalidate a leaderboard snapshot. Review does not prove that a submitter owns the source account.
None of this is financial or investment advice. Questions about a figure: see the FAQ or write to us from the about page.