Files
observer/web
rob thijssen adaf00e1f5
All checks were successful
deploy / build (push) Successful in 1m1s
deploy / deploy-api (push) Has been skipped
deploy / deploy-web (push) Successful in 5s
ui: separate mainnet from testnets in the chain nav
`Quantus` and `Heisenberg` sat side by side, identically styled. One is the real
network. Somebody reading a balance, a reward or a transfer had no way to tell
from the chrome whether the number meant anything, and Planck makes it two
testnets against one mainnet.

Two labelled groups rather than a styling difference alone, because a lone
visual difference reads as decoration to anyone who has not been told what it
means:

    MAINNET  [ Quantus 329 ]    TESTNETS  [ Planck 110 ] [ Heisenberg 4 ]

The dashed border on a testnet chip is a second channel behind the heading
rather than the only one, and every chip's tooltip now says outright that a
testnet's balances and rewards are not real.

No backend work: `ChainInfo.mainnet` has been on the wire since the registry was
written and the frontend simply ignored it. It stays operator-asserted and is
never inferred from the name — a chain publishing itself as "Quantus Staging
Mainnet" must not collect the heading by having the word in its title.

A chain list with no mainnet in it renders one `TESTNETS` group rather than an
empty `MAINNET` heading.

Closes #5

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Jp6a8EDar9ueEhAxzep4V5
2026-09-10 11:05:38 +03:00
..