height 23698 of 23698 on the network. 9 peer(s) connected, 77 in its peer directory; 994 block(s) followed and 824 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.
Priority support
There are no tiers, no hours and no escalation path set anywhere in this software. A page that printed any of those would be the first thing a paying reader found to be untrue. What is below is what is genuinely available today.
What is available today
- The published corpus
- Fifty documents published beside the installers, each with a SHA-256 so you can check what you downloaded. They include runbooks for backup, restart, upgrade, rollback, incident and custody — written to be followed under pressure rather than read in advance. The knowledge base says which one to start with.
- The audit record
- Dated audit documents stating what was examined, by what method, what was found, what was fixed and what is still open. A finding that is still open is published as open.
- The gate suite
- The repository re-reads its own documentation’s claims against the code, re-checks every citation in the deep volumes against the tree, and refuses a build where the two disagree. It is the reason a sentence in a document can be trusted to be about the current code.
- A person
- support@sourceless.net, which is the support and technical address. No queue and no promised response time. Contact says what else is not set.
- A security finding
- Bug bounty, which states plainly that there is no reward and that findings are wanted regardless.
If you are running a node and something is wrong
Two things are worth doing before writing to anybody. First, Network status on the surface served by your own node: it says what that node has verified and whether it believes it is caught up, which separates my node is behind from the chain has stopped. Those have completely different remedies and they look identical from the outside.
Second, the banner at the top of every page, which says how the surface obtained its chain. A surprising number of reports turn out to be a page served from a synthetic chain or from a follower that never reached a peer, and the banner says both.
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.
- [WHETHER PRIORITY SUPPORT IS OFFERED AT ALL — to be supplied]
- [THE TIERS, AND WHAT EACH ONE INCLUDES — to be supplied]
- [FIRST-RESPONSE AND RESOLUTION TARGETS PER SEVERITY — to be supplied]
- [HOURS OF COVER, AND THE TIME ZONE THEY ARE IN — to be supplied]
- [THE CHANNEL: A TICKET SYSTEM, AN ADDRESS, OR SOMETHING ELSE — to be supplied]
- [PRICING, AND THE TERM IT IS SOLD FOR — to be supplied]
- [WHAT IS OUT OF SCOPE, INCLUDING THIRD-PARTY SOFTWARE — to be supplied]
- [WHO PROVIDES THE COVER, AND WHAT HAPPENS OUTSIDE HOURS — to be supplied]