Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not all top coins are listed #27

Open
passcombo opened this issue Jan 9, 2019 · 0 comments
Open

Not all top coins are listed #27

passcombo opened this issue Jan 9, 2019 · 0 comments

Comments

@passcombo
Copy link

passcombo commented Jan 9, 2019

Hi, very useful project!

However I've found not all tokens are listed, for example KMD is not there, probably due to dPOW usage.

I believe it's perfect to display all top coins from CMC with a proper info rather then hide some information. Reason - your site viewers will see that you did not skip any and analysed all interesting tokens. Informative reason.

As I understand currently some projects may be "hidden" due to marking as "not relevant" while applying additional 51% protection layers. But this way some information is hidden to site user. User does not know why the information is missing, either relevant, site owner forgot to analyse it or was lazy or paid by some conspiracies to avoid some :)

What I mean - hiding information is not useful and counter productive, even if the information shows the item is not exactly relevant in the list, it's better to put it there and explain why not exactly relevant, or that currently it's not possible to estimate it precisely.

So what I propose? - List all analysed coins that can be attacked with proper info. Proper info I mean - even if it is not possible to exactly estimate the number - it can be for sure estimated other ways, or at least marked as not estimated yet or "not apply" in terms of POS coins ?

Taking example of dPOW protected coins it could be simplified to have > BTC 1h attack cost. IF you also consider 1 minute cost - it could be different, as first 10 minute cost is only cost of attacking the orig token chain, and > 10 minutes it will be + BTC attack. But keeping the original site notation (considering 1h attack) simply putting "> BTC" cost would be fair estimation to me. In general it seems the important knowledge is not the exact cost but the "level of cost" - is it level of 1 000 000 $ or 1 000 $ or 10 $. So just rough estimation gives user good enough information if the chain is basically safe to use.

Another possibility is just putting "?" with a * where * (or number) in the bottom of the page could explain the details.

Hope these ideas will help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant