2

I found the following in the eosjs docs:

eos.getCurrencyStats(code, symbol) ⇒ getCurrencyStatsResult

I was able to receive all stats for

eos.getCurrencyStats('EOS', 'eosio.token')

as well as all self created tokens on my local test node. I was looking for symbols on the main net and found RIDL, POOR and WIZZ. Using their symbols just returned an empty object. So either these tokens aren't really published yet or using 'eosio.token' is the wrong contract.

Was anybody successful getting stats for main net tokens?

Improve this question
1
  • using 'eosio.token' is the wrong contract This can be true, I think. Try deploying a contract on local and verify whether this is the reason. Meanwhile, will check for these tokens on mainnet too.
    – Rajat Chaudhary
    Commented Aug 16, 2018 at 4:55

2 Answers 2

Reset to default
1

This one worked: Using contracts from https://github.com/eoscafe/eos-airdrops

So all wallet providers need to have access to all contract names or even their own little database. Is there a package in development to get the most recent ones?

Improve this answer
0

This npm package works: eos-token-info

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.