XPlorer following the chain as its own read-only node

height 23697 of 23697 on the network. 9 peer(s) connected, 77 in its peer directory; 993 block(s) followed and 823 pulled in by sync since this follower started. Caught up: this follower holds every block any peer has claimed, so every panel below is the whole chain. Genesis 1cf8655125cc1bbb…, producers genesis.

What this follower is, locally

Following 7 seed(s) — their addresses are not published here, for the reason the peer table gives. Its store is held under its own Cerberus lease — no other node’s store is opened, touched or stopped.

Terms and privacy

There are no published terms of service for this surface yet.

Five legal documents are drafted in this repository — terms, a privacy notice, a GDPR statement, a cookie statement and validator terms — and every one of them is a draft that may not be published until the operating entity, the governing law and 25 other items are supplied. They carry visible blanks rather than guesses, for the same reason this page does. Nothing below is a contract.

What can be stated exactly, and is stated below, is what this page does to the machine reading it. None of it is a promise: all of it is readable in the response headers you received with this page and in the one script it loads.

What this surface does with a visitor

Requests it answers: GET and HEAD. Anything else is refused with 405 before any handler runs, and no handler on this surface reads a request body — there is nowhere for one to go.
Cookies: None. This surface sets no cookie of any kind.
Browser storage: Two keys at most: sourceless-appearance, holding the name of the appearance you picked, and shell-rail, whether you collapsed the sidebar. Each is written only when you choose, read only by this page, and never sent anywhere. With storage blocked the choice holds for the page you made it on.
Third-party requests: None, and the policy forbids them rather than merely avoiding them. The two typefaces, the stylesheet, the script and both brand marks are served by this node. There is no analytics, no tag manager and no font CDN.
The policy sent with this page: default-src 'none'; style-src 'self'; script-src 'self'; img-src 'self' data:; font-src 'self'; connect-src 'self'; form-action 'self'; frame-ancestors 'none'; base-uri 'none'
Referrers: referrer-policy: no-referrer. Following a link off this page does not tell the destination where you came from.
Framing: Refused: x-frame-options: DENY and frame-ancestors 'none'. This page cannot be embedded in somebody else’s site.
The search box: A GET to this node. What you type arrives in the URL, so it may appear in whatever request log the operator of this host keeps.

What the chain holds, which is a different question

This page is a window. The chain behind it is a permanent public record, and that is not a property any privacy notice can soften: an address, a domain name, a transaction and every record a block carries are readable by anybody with a node, forever, and nothing on the chain can be deleted or corrected after the fact. A name is chosen by its holder and is readable — that is what makes it useful and it is also what makes it public.

The drafted GDPR statement in this repository flags the tension between that and a right to erasure as unresolved rather than answering it with a clause. That is the honest position and it is repeated here.

Separately, the machine serving this page is a web server: whoever operates it may be keeping an access log with your IP address in it. This code sets no retention period for such a log, and the deployment bounds its log by volume rather than by time, so how long an entry survives depends on traffic. The period is a gap below, not a figure.

Read on

Contact — the one published address, and the ones that are not set
Network status — what this node has verified, and the caveat on reading it
Bug bounty — how a security finding reaches somebody, today

Not answered here

Each of these is a decision rather than a measurement, so nothing in this build could supply one. They are listed here, and again at the JSON mirror of this page, rather than filled with something that would read as true.

[OPERATING ENTITY, AND WHETHER IT IS THE DATA CONTROLLER — to be supplied]
[REGISTERED ADDRESS AND COUNTRY OF ESTABLISHMENT — to be supplied]
[GOVERNING LAW, FORUM AND DISPUTE RESOLUTION — to be supplied]
[THE DATA PROTECTION CONTACT — to be supplied]
[WHERE THE PUBLISHED LEGAL DOCUMENTS WILL LIVE — to be supplied]
[ACCESS LOG RETENTION PERIOD, IN TIME RATHER THAN IN VOLUME — to be supplied]
[HOSTING, DNS AND EMAIL PROVIDERS, NAMED AS PROCESSORS — to be supplied]
[MINIMUM AGE, AND THE EFFECTIVE DATE THE DOCUMENTS CARRY — to be supplied]
[WHETHER A CONSENT STEP IS NEEDED FOR THE THEME PREFERENCE — to be supplied]
[THE REMAINING ITEMS IN LEGAL/README.MD, WHICH LISTS 27 — to be supplied]