Mark account only for testnet
We can mark account only use for certain networks. It will useful to mark account only use for development. i.e. network with prefix 42
I feel this might end up looking convoluted for users if we mix "testnet" with network names.
How about add Generic Substrate?
I have some accounts are strictly for development purpose only (shared private key) and will want to avoid accidentally use them in mainnet.
I totally understand your point, I do have such accounts allowed on any chain as well, I name them "TEST *" to make sure I don't mess up. "Substrate generic (testnet)" could indeed by a good middle ground IMO. I'd add this depending on @jacogr opinion.
The above dropdown add the genesisHash for the selected account, i.e. so it is only useful on that network. There is no "generic substrate genesisHash" and actually the extension is completely oblivious to what may or may not be a test network.
In that case is there a way to mark an account not to be used by a known network?
Like this
- [ ] Any
- [ ] Polkadot
- [ ] Kusama
- [ ] Crab
- [x] Others
No, however both genesisHash-allowed/blocked (as a list, not just a single) is interesting for the keyring component.
Able to block a list of known networks will work as well.
One thing that I've missed recently, is the ability to set the network for an account for Westend, which I have the metadata for, but that doesn't appear in the list still. Adding in the list, all the networks for which you have the metadata, might solve at least part of your issue.