Reading the Network Stats Dashboard: The Milestones Now Check Out, and Two Tiles Should Not Exist
What this page checked, and what it did not
The stats page was fetched with no account and its markup read directly.
In that markup every metric renders as a dash placeholder, which is what a client-hydrated page looks like when you read it as a document. That is not evidence a browser shows nothing, and this page makes no claim about the values a visitor sees.
What is readable, and therefore checkable, is the set of labels. A label is a claim about what kind of quantity exists, and it makes that claim before any number arrives.
Two tiles assert something this project has fenced against
One tile is labelled for a token price.
It has no market, no listing and no price. A tile reserved for a price asserts that the quantity exists and is merely unavailable right now, which is a different and stronger statement than "there is no such thing".
Another tile is labelled for throughput.
This estate does not publish throughput figures, and the one benchmark that exists was produced on a single laptop in a different repository and is not this network's capacity. A tile shaped to receive that number is an invitation to put it there.
And the fix that already happened is the reason this matters
A fabricated price value was removed from this page in an earlier clean-up, along with fabricated milestones.
The value went. The tile stayed.
That is the shape this estate keeps finding: the number gets corrected and the noun that asked for it survives, so the next person to wire the page up has a labelled slot waiting. Removing a wrong value fixes today. Removing the tile fixes the class.
The milestones, checked one at a time, and all four hold
Selective disclosure, May 2026. Matches when that work shipped.
Registered in the W3C DID Method Registry, July 2026. The wording is exactly right, a registry listing described as a listing rather than as a standard, and the date matches a merged request anybody can fetch.
Associate membership of the Decentralized Identity Foundation, May 2026. Matches the confirmation.
Four for four, on a page whose milestones were previously fabricated. That is a real repair and it deserves saying as plainly as the two tiles that were missed.
What to read instead, if you want a number you can trust
Ask the chain. The tip, the chain identifier and the validator set are all one request each, with no account:
solidus_blockNumber·solidus_chainInfo·solidus_getValidators
The tip when this page was written was 83,688. Yours will differ, which is the point: a number you fetched is worth more than a number we rendered.
And be careful with the validator count, because the registry and the producing committee are different sets.
What a dashboard on a testnet should probably show
Height, chain identifier, block interval against its target, and the size of the producing committee. All four are facts about a running system.
Not price. Not throughput. Not supply-shaped tiles for a unit with no market, because each of those is a slot that can only be filled with something misleading.