-
Notifications
You must be signed in to change notification settings - Fork 56
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
478bb91
commit 31d55a7
Showing
2 changed files
with
19 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
31d55a7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the symbol is "PAC": https://github.com/cipig/coins/blob/master/coins#L51
31d55a7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not according to CMC https://coinmarketcap.com/currencies/paccoin/
31d55a7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Half of the exchanges also use PAC as symbol, it is PAC in jl's repo and i use it on my LPs too. $ is a special character and using it can cause problems in scripts.
31d55a7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't feel strongly about it, but it's kinda weird to not use the official symbol name. We would also have to do a workaround since our CMC fetching would not match
PAC
. @lukechilds Thoughts?31d55a7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
autoprice call in mm (which uses CMC v1 API) uses part of the URL to identify the coins on CMC, not the coin symbols. CMC v2 API and CMC paid API use ids to identify the coins. I have collected this ids: https://github.com/cipig/mmtools/blob/master/setprices/margins.conf and use them for my own price update script for CMC paid API.
31d55a7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cipig If we use a different coin name does that mean we won't be able to match with your LPs?
If so, we should always use whatever is in the jl777/coins repo to ensure we match with the rest of the network.
@sindresorhus I know it's a bit dirty but we could add a
symbol
property to the coin object and use that for all visual stuff but usecoin
for all mm related stuff. That way the user always see's the ticker they expect.I already considered implementing that to fix: #289
31d55a7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the same coin symbols must be used across all nodes, else it won't match. We should use the same symbols across all apps. Problem is that coin symbols are not consistent on exchanges/CMC, eg look up BTM on CMC (it is used twice). I would recommend using other things to uniquely identify a coin, eg the id on CMC.
31d55a7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, thanks for the info @cipig.
@sindresorhus yeah I definitely think we should do that then.