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 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 both eth-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
At the moment, the IPLD Block Explorer is just relying on a single watcher,
eth-watcher-tsBut 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-tsanderc20-watcherin 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-tsusing the multi-watcher designerc20-watcherusing the multi-watcher design