Privacy

Last updated · 10 August 2026

bip110.run ("Running BIP-110") is a free public observatory on BIP-110 miner signaling and related public-node telemetry. This page explains what your browser connects to and what this site stores.

What this site is

Mostly static pages and JSON snapshots on Cloudflare Pages, plus a few browser-side calls to public services so the instrument can stay fresh. There are no accounts, no login, and no user profiles on bip110.run itself.

What we load in your browser

This site’s files — HTML, CSS, JSON snapshots (signal, nodes, node-client mix), images, and inline icons from Cloudflare.
mempool.space - a public WebSocket from your browser accelerates new-block arrivals. Initial load, manual refresh, and recovery use a bounded same-origin endpoint: your browser contacts bip110.run, and our Cloudflare edge requests the public chain tip or block detail from mempool.space without sending it a visitor identifier or house-node credential. The block explorer may also request public block detail directly.
Mapbox - map tiles and the Mapbox GL library for the interactive BIP-110 peers map. Mapbox receives standard map requests from your browser under its terms and privacy policy.
Public node snapshot - the archived Coin Dance summary is baked into this site's JSON. Its user agents are self-reported; visiting this site does not contact Coin Dance.
Market ratio - the MSTR/BTCUSD chart uses a baked adjusted-close history plus a short-lived, same-origin minute endpoint sourced from Yahoo Finance. Your browser contacts bip110.run; our Cloudflare edge contacts Yahoo Finance and does not send it a visitor identifier, TradingView credential, or account data. The source may be delayed or revised.
Node-runner census - a build-time snapshot joins self-identified public X profiles discovered through house records and consensus.health. The published census JSON and avatar copies are served by bip110.run; visiting the page does not contact X or consensus.health.
Equipment census - voluntary anonymous hardware profiles. Visible native commands report proof-of-work-relevant component classes and capacities; they do not ask for a name, handle, hostname, username, network address, hardware serial, UUID, files, processes, or keys.

Local preferences

The dashboard may store small preferences in your browser’s localStorage (for example the last SMA window you picked). That data stays on your device; we do not read it on a server. Clearing site data in your browser removes it.

Visitors and "reading now"

A small on-page chip shows two anonymous public counts. Visitors is the full public total: a floor taken from Cloudflare edge analytics for page views on this site's zone, plus ongoing browser sessions after that floor. Your browser keeps a random visit id in localStorage (never a cookie); after 30 minutes of inactivity the next visit can add to the live portion. That is not a verified unique-person census. Reading now counts open tabs seen in about the last 150 seconds using a throwaway sessionStorage id. We store no IP address, no name, and no location. Clearing site data removes the ids from your browser.

Coalition requests (optional)

On the Coalition page, you may send a public X/Twitter handle to request a listing, add one role, or improve one Bitcoin-class receipt. A role or class request may include one public post or page URL. The site may send the handle or public post id to public profile and post readers such as FxTwitter, then store the public profile fields, post text, timestamp, and attached public media needed to evaluate that claim. We do not request or read private messages, email, passwords, or private evidence. Do not submit another person's evidence without their knowledge.

Node-runner census corrections (optional)

The Census publishes public X display names, handles, avatars, self-identification evidence, and public BIP-110 stance receipts. It is not an account system or an X login. If a record is missing or wrong, the existing suggestion form stores the public profile or stance receipt you choose to provide for private operator review.

Equipment census (optional)

The Equipment page analyzes terminal output entirely inside your browser. The pasted text is cleared after it becomes an editable profile and is never sent to or stored by bip110.run. Only the normalized hardware profile you review, correct, and submit is stored and published. No name or social handle is requested. An opaque first-party HttpOnly cookie privately limits one browser to three rig submissions; it is not displayed or included in the public census. Clearing browser data can reset that self-policed limit. We do not build a user-agent fingerprint. Standard Cloudflare request handling may process an IP address transiently under Cloudflare's service terms, but the equipment census does not store a raw IP address as a profile identity. Optional ASIC and FPGA descriptions are public. Do not paste secrets, addresses, serial numbers, or another person's information.

Meme tips (optional)

Submit a meme stores only the public links you choose to paste and the submission time so the operator can review them. The links are not published automatically. Do not submit private links or material you are not entitled to share.

Error reports and feature ideas (optional)

Report an error (footer or continuous-improvement notice) stores what you typed, a technical environment card from your browser (user agent, window size, device pixel ratio, and similar layout measurements), and an optional screenshot only if you attach or paste one. Suggest what to show next (notice link, ballot strip, or idea control) stores only what you typed and an optional sketch or screenshot - no browser environment card. These notes are for improving the site. We do not ask for your name or email. Screenshots are not published on the public pages. A copy of the report may also be emailed to the site operator so it is seen promptly; that message stays private. Do not put secrets or private keys in either form.

Chatroom (optional)

When the chat room is available, posts you send include the message text, an optional display nick you choose (or a short random anon-… label), and a random visit id used only for rate limiting. Accepted messages are archived permanently; the live window may show only a bounded recent conversation without deleting its archive. We do not store IP addresses, emails, or accounts for chat. Clearing site data removes the handle and visit id from your browser, but not a public message you already sent.

What we do not collect here

No account registration or passwords on bip110.run.
No advertising pixels, no cross-site tracking, and no marketing cookies. The only first-party signals above are the anonymous visitor session tally, the "reading now" count, and optional chat posts you choose to send.
No mailing list signup form on this site.

Your browser and network still create ordinary server logs at the host and at any third party you contact (Cloudflare, mempool.space, Mapbox, FxTwitter, or CDNs). We do not sell that information.

Children

This site is not directed at children under 13. We do not knowingly collect their information.

Contact

Privacy questions about this site: reach the operator via public channels linked from Running BIP-110 / About.

Changes

If this policy changes in a material way - including a new third-party load or payment rail - we will update the date at the top of this page.