SourceLessExplorer · SourceLess AsgardSourceLess Asgard · chain 1313
LiveHeight23,715Head age21 sLast interval1 minFinality23,704Behind−11Pending0 / 8,192Tx in head0
XPlorer following the chain as its own read-only node

height 23715 of 23715 on the network. 9 peer(s) connected, 77 in its peer directory; 1011 block(s) followed and 840 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.

Contact us

support@sourceless.net is the address for support, technical questions, security findings and anything operational. It is the one to use unless your question is about licensing.

alex@strlabs.io is the rights holder’s and is for LICENSING ONLY — rights, the grant, written consent. It appears in the notice at the head of every source file, which is the only reason it is published at all.

A postal address for legal notice is not set anywhere in this build. Rather than print a plausible one, it is listed at the foot of this page as a gap.

There is no account to contact us about

This surface performs no sign-in, no registration and no profile. Where the header carries a Sign in with your STR.domain link, it leads out to a separate login surface, and nothing here receives what you do there. This surface answers GET and HEAD and nothing else, it never reads a request body, and it keeps two browser-storage keys at most: sourceless-appearance, the appearance you picked, and shell-rail, whether you collapsed the sidebar. Neither is ever transmitted. So there is no password to reset here, no account to close and no data export to ask for. Terms and privacy sets out exactly what the page does, measured from the code rather than promised.

Two things that do often need a human are worth naming, because both have a page of their own that explains what is and is not in place today: a security finding (Bug bounty) and an operational problem with a node or this surface (Network status).

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.

  • [A POSTAL ADDRESS FOR LEGAL NOTICE — to be supplied]
  • [A PRESS AND PARTNERSHIP ADDRESS — to be supplied]
  • [EXPECTED RESPONSE TIME, OR A STATEMENT THAT NONE IS PROMISED — to be supplied]
  • [WHICH COMMUNITY CHANNELS ARE OFFICIAL, IF ANY — to be supplied]
  • [THE LANGUAGES CORRESPONDENCE IS ACCEPTED IN — to be supplied]