height 23716 of 23716 on the network. 9 peer(s) connected, 77 in its peer directory; 1012 block(s) followed and 841 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.
SourceScan
SourceScan does not exist in this software. There is no component, no route, no record and no stored data by that name, and nothing on this page describes a feature anybody can use. It is published here because the owner named it as an intended product and a footer link was asked for; it is marked this plainly so that it cannot be read as a release.
As the owner describes it, SourceScan is intended to be a cross-chain identity and analytics product. That is the whole of what has been stated about it. The rest of what a product page would carry — what it does, for whom, on which chains, and whether it will be built at all — is not decided, and is listed at the foot rather than filled in.
What exists in this chain today, which is not SourceScan
Named so the distinction is concrete. These are real pages on this surface, they are not a product, and none of them is cross-chain:
- Identity — STR.domains and the wNFTs that prove them, on this chain only
- Organisations — master domains that have opened departments, and what each holds
- Delegations — who may move whose money, under what cap, until what height
- Bridge — cross-chain value, which is a chain mechanism and not an index of other chains
- Throughput — what this chain has actually done over a named window — the analytics that exist
What none of them does is look at another chain. There is no cross-chain index here, no identity graph spanning networks, and no analytics over anything but the chain the node serving this page holds.
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 SOURCESCAN WILL BE BUILT AT ALL — to be supplied]
- [WHAT IT DOES, IN ONE SENTENCE THE OWNER WOULD STAND BEHIND — to be supplied]
- [WHAT “IDENTITY” MEANS ACROSS CHAINS THAT DO NOT SHARE A NAMESPACE — to be supplied]
- [WHICH CHAINS, AND HOW EACH WOULD BE READ — to be supplied]
- [WHICH ANALYTICS, AND WHETHER THEY WOULD BE MEASURED OR ESTIMATED — to be supplied]
- [WHO IT IS FOR, AND WHETHER IT IS PAID — to be supplied]
- [WHAT A PRIVACY POSITION WOULD BE FOR A CROSS-CHAIN IDENTITY INDEX — to be supplied]
- [WHETHER THE NAME IS CLEAR TO USE — to be supplied]