You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are different watchers being developed by @ashwinphatak now, that we are going to have to consume to build the above pages.
To move in the direction of consuming these watchers, a new explorer-watcher-ts "parent" watcher should be created, which then is consuming child watchers such as eth-watcher-ts, erc20-watcher, address-watcher, etc.
The purpose of this epic is to re-architect the system as necessary to begin consuming botheth-watcher-ts and erc20-watcher in an elegant manner, with the goal that in future sprints we can integrate with additional watchers as they are completed (such as address watcher).
Acceptance criteria
IPLD Block Explorer can work with multiple watchers in an elegant manner
IPLD Block Explorer is integrated with eth-watcher-ts using the multi-watcher design
IPLD Block Explorer is integrated with erc20-watcher using the multi-watcher design
The text was updated successfully, but these errors were encountered:
Not sure I understand how "parent" watcher explorer-watcher-ts will interact with child watchers. Will it have its own database and pull all data from the child's database to its local? Or just proxy graphql requests?
I tried to run erc20-watcher, followed the instruction in README and after I ran it get errors:
what is expected to be running on port 5000? Am I missing something in instruction?
3. How to get Token list like this https://www.ethvm.com/tokens from watcher-ts?
4. How to get basic erc20 token information in case storage layout will be different than default?
5. How to get Transfers and Holders information by token?
6. Hot to get Total ERC20 Tokens and Transaction History by address?
At the moment, the IPLD Block Explorer is just relying on a single watcher,
eth-watcher-ts
But this watcher does not have all of the functionality required to build out the missing pages such as:
There are different watchers being developed by @ashwinphatak now, that we are going to have to consume to build the above pages.
To move in the direction of consuming these watchers, a new
explorer-watcher-ts
"parent" watcher should be created, which then is consuming child watchers such aseth-watcher-ts
,erc20-watcher
,address-watcher
, etc.The purpose of this epic is to re-architect the system as necessary to begin consuming both
eth-watcher-ts
anderc20-watcher
in an elegant manner, with the goal that in future sprints we can integrate with additional watchers as they are completed (such as address watcher).Acceptance criteria
eth-watcher-ts
using the multi-watcher designerc20-watcher
using the multi-watcher designThe text was updated successfully, but these errors were encountered: