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
The backend currently doesn't work with multiple blockchains. Since multi-chain is an important feature of Aergo, we need to improve this.
There are two approaches:
Have one instance of backend+frontend per chain (optionally reuse same db, with index prefix)
Have multiple chains in one instance (more flexible with UX, e.g. we can have a dropdown to switch between networks and also analyze cross-network traffic)
The text was updated successfully, but these errors were encountered:
It would really help to have the indexer be part of the node (aergoio/aergo#14). That way it would be really easy to setup indexing multiple chains into one database and have just one unified backend and frontend.
Update: The indexer is now a standalone go program (https://github.com/aergoio/aergo-esindexer) which supports syncing multiple chains. The aergoscan backend is now only an API to access the data in the database.
We can still go both routes mentioned in the intro, it really is just a UX decision now.
The backend currently doesn't work with multiple blockchains. Since multi-chain is an important feature of Aergo, we need to improve this.
There are two approaches:
The text was updated successfully, but these errors were encountered: