Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

UI: Ropsten/custom chain considered as Mainnet #3578

Closed
chevdor opened this issue Nov 23, 2016 · 2 comments
Closed

UI: Ropsten/custom chain considered as Mainnet #3578

chevdor opened this issue Nov 23, 2016 · 2 comments
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue.

Comments

@chevdor
Copy link

chevdor commented Nov 23, 2016

I am running parity using --chain ropsten.json

In the UI, parity shows a green label that usually means MAIN net.
In the contracts and accounts tab, I can now see a mix of accounts/contracts from Homestead and Ropsten => the Ropsten accounts/contracts do show up, but the Homestead ones as well.

screen shot 2016-11-23 at 12 20 38

The Network ID should probably be used to identify the network and store/filter the accounts/contracts.

I think the color code for the network is a good idea and I would propose to extend it as follow:

  • Homestead / mainnet => green (unchanged)
  • Morden / Ropsten / testnet => cyan (red is a contradiction, red = risk, testnet = no risk )
  • other / unknown networkd id => yellow
@derhuerst derhuerst added F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M7-ui labels Nov 23, 2016
@jacogr
Copy link
Contributor

jacogr commented Nov 23, 2016

Fixed in master yesterday.

@jacogr
Copy link
Contributor

jacogr commented Nov 24, 2016

Still happens when using a chain file, but not using --chain ropsten (or --testnet)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue.
Projects
None yet
Development

No branches or pull requests

3 participants