accounts across profiles from one mnemonic, and addresses refused by name #37

New Issue

grenade · 2026-09-15T12:40:18Z

grenade commented

2026-09-15 12:40:18 +00:00

Parent: #6

Scope

Derive accounts for every enabled profile from the one seed (coin type from the profile; Quantus chains share 189189 and therefore share keys, which is correct and must be shown as such). Address validation decodes any ss58 prefix the registry knows and refuses a foreign one by naming its chain; a prefix it does not know reads as invalid.

Acceptance

Mainnet and Heisenberg accounts appear side by side with their own balances. Pasting a Polkadot address into the send form says "that is a Polkadot address" rather than "invalid".

Depends on

#14 (key schemes), the asset registry, the app shell.

Parent: #6 ## Scope Derive accounts for every enabled profile from the one seed (coin type from the profile; Quantus chains share 189189 and therefore share keys, which is correct and must be shown as such). Address validation decodes any ss58 prefix the registry knows and refuses a foreign one by naming its chain; a prefix it does not know reads as invalid. ## Acceptance Mainnet and Heisenberg accounts appear side by side with their own balances. Pasting a Polkadot address into the send form says "that is a Polkadot address" rather than "invalid". ## Depends on #14 (key schemes), the asset registry, the app shell.

grenade added the child label 2026-09-15 12:41:48 +00:00

grenade referenced this issue

2026-09-15 12:42:40 +00:00

epic: multi-chain asset model #6

grenade referenced this issue from a commit

2026-09-16 06:22:47 +00:00

feat(core): a foreign address is refused by the name of its chain

grenade referenced this issue from a commit

2026-09-16 06:26:47 +00:00

feat(ui): the same accounts on every other network, side by side

grenade closed this issue

2026-09-16 06:26:47 +00:00