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

Cater for non-ETH chain currency symbols #4123

Closed
cseberino opened this issue Jan 10, 2017 · 6 comments
Closed

Cater for non-ETH chain currency symbols #4123

cseberino opened this issue Jan 10, 2017 · 6 comments
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M2-config 📂 Chain specifications and node configurations. P7-nicetohave 🐕 Issue is worth doing eventually.
Projects
User Interface
Milestone
2.1 Whatever

Comments

@cseberino
Copy link

When submitting contracts and other things that require payments, Parity labels
currency as ETH even when should be ETC.

Possible to somehow add a conditional instruction in code to adjust when "--chain classic"
switch used?
@jacogr
Copy link
Contributor

jacogr commented Jan 10, 2017 •
edited

Affects -

  1. Dapps
  2. UI naming
  3. UI icons

To consider (test & live networks) -

  1. ETC
  2. Expanse
  3. Private chains (?)

(Non-shared code for ETH naming currently in existence)

@jacogr jacogr added F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M7-ui P7-nicetohave 🐕 Issue is worth doing eventually. labels Jan 10, 2017
@cseberino
Copy link
Author

cseberino commented Jan 10, 2017 via email

@cseberino
Copy link
Author

ETC currency is always officially called ETC so this is definitely a bug rather than just
an annoyance.

@jacogr jacogr changed the title Currency symbol always ETH even when using ETC chain! Cater for non-ETH chain currency symbols Jan 10, 2017
@jacogr jacogr mentioned this issue Jan 20, 2017
Merged
@tomusdrw tomusdrw mentioned this issue Feb 3, 2017
Closed
@5chdn
Copy link
Contributor

5chdn commented May 10, 2017

This issue is labelled with annoyance: The client behaves within expectations, however this "expected behaviour" itself is at issue. It's inactive since January, neither assigned nor linked to any milestone.

@paritytech/ui-devs @paritytech/dapp-devs Please, decide within 7 days on a deadline and add an assignee or close it otherwise. Thanks.

@5chdn 5chdn mentioned this issue May 10, 2017
Closed
@5chdn 5chdn mentioned this issue Jul 31, 2017
Closed
@keorn
Copy link

keorn commented Jul 31, 2017

Either based on a contract lookup or a chain spec file.

@5chdn 5chdn mentioned this issue Aug 4, 2017
Closed
@5chdn 5chdn added the M2-config 📂 Chain specifications and node configurations. label Aug 4, 2017
This was referenced Aug 22, 2017
Closed
Closed
@5chdn 5chdn added this to the 1.9 milestone Oct 5, 2017
@5chdn 5chdn modified the milestones: 1.9, 1.10 Oct 17, 2017
@jacogr jacogr moved this from Icebox to Icebox 2 in User Interface Nov 21, 2017
@5chdn 5chdn modified the milestones: 1.10, 1.11 Jan 23, 2018
@5chdn 5chdn modified the milestones: 1.11, 1.12 Mar 1, 2018
@5chdn 5chdn modified the milestones: 1.12, 1.13 Apr 24, 2018
@Tbaut Tbaut mentioned this issue Apr 25, 2018
Open
@Tbaut
Copy link
Contributor

Tbaut commented Apr 25, 2018

Moved to parity-js/shell#77

@Tbaut Tbaut closed this as completed Apr 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M2-config 📂 Chain specifications and node configurations. P7-nicetohave 🐕 Issue is worth doing eventually.
Projects
No open projects
User Interface
Icebox
Milestone
2.1 Whatever
Development

No branches or pull requests
5 participants
@jacogr @cseberino @keorn @5chdn @Tbaut