Right now when a chain is added we have to manually update HTML to include the chain in the dropdown on the query page and on the account page. Now that the config table is in the frontend's database, we can dynamically populate this data.
We might also consider conduit's use case. If someone provisions an indexer from conduit, they might not want to share access to the data. In which case we should not show it in the UI.
Right now when a chain is added we have to manually update HTML to include the chain in the dropdown on the query page and on the account page. Now that the config table is in the frontend's database, we can dynamically populate this data.
We might also consider conduit's use case. If someone provisions an indexer from conduit, they might not want to share access to the data. In which case we should not show it in the UI.