Mainnet and testnets have equal weight in the chain nav #5

New Issue

grenade · 2026-09-10T08:04:16Z

grenade commented

2026-09-10 08:04:16 +00:00

What

Quantus and Heisenberg sit side by side, identically styled. One is the real
network and one is a testnet, and nothing on the page says which. Planck makes
it three, and two of the three will be testnets.

Somebody reading a balance, a reward or a transfer has no way to know from the
chrome whether the number means anything.

What already exists

ChainInfo.mainnet is on the wire and reaches the browser today — the frontend
ignores it. registry.rs sets it from the operator-asserted [[chains]] entry
and never infers it from the name, deliberately: a chain calling itself
"Quantus Staging Mainnet" must not get the badge by having the word in its
title.

So this is a render change with no backend work.

Shape

Two labelled groups rather than a styling difference alone:

MAINNET   [ Quantus 320 ]     TESTNETS   [ Heisenberg 3 ]  [ Planck 12 ]

The nav already carries a CHAINS eyebrow; splitting it into two says which is
which without a legend, and without the reader having to know a convention.

Dashed borders on testnet chips as a second channel, per the rule already in
force elsewhere in this file — "not colour-alone: the disabled chains carry a
word", because a single visual channel reads as decoration to anyone who has not
been told what it means.

Degrade sensibly when there is only one group: a chain list with no mainnet in
it should say TESTNETS and not render an empty MAINNET heading.

## What `Quantus` and `Heisenberg` sit side by side, identically styled. One is the real network and one is a testnet, and nothing on the page says which. Planck makes it three, and two of the three will be testnets. Somebody reading a balance, a reward or a transfer has no way to know from the chrome whether the number means anything. ## What already exists `ChainInfo.mainnet` is on the wire and reaches the browser today — the frontend ignores it. `registry.rs` sets it from the operator-asserted `[[chains]]` entry and never infers it from the name, deliberately: a chain calling itself "Quantus Staging Mainnet" must not get the badge by having the word in its title. So this is a render change with no backend work. ## Shape Two labelled groups rather than a styling difference alone: ``` MAINNET [ Quantus 320 ] TESTNETS [ Heisenberg 3 ] [ Planck 12 ] ``` The nav already carries a `CHAINS` eyebrow; splitting it into two says which is which without a legend, and without the reader having to know a convention. Dashed borders on testnet chips as a **second** channel, per the rule already in force elsewhere in this file — "not colour-alone: the disabled chains carry a word", because a single visual channel reads as decoration to anyone who has not been told what it means. Degrade sensibly when there is only one group: a chain list with no mainnet in it should say `TESTNETS` and not render an empty `MAINNET` heading.

grenade referenced this issue from a commit

2026-09-10 08:05:42 +00:00

ui: separate mainnet from testnets in the chain nav

grenade closed this issue

2026-09-10 08:05:42 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: blackbeard/observer#5