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
Once we've implemented everything in the codebase to be able to scrape Cosmos chains, we'll want to deploy the scraper with this change
Solution
Some minor changes to infra / helm charts are probably required, e.g. making sure that GRPC URLs are properly passed into the scraper, configuring the correct non-EVM chains on the scraper, etc
We'll want to be cautious about this breaking prod services that depend on the scraper, e.g. the explorer UI, because this involves a DB schema change (e.g. Scraper: addresses in DB should always be 32 bytes #3330). Instead of rolling this out straight to prod on the existing scraper, I think it may be better to deploy this new scraper alongside the old one, with the intent of eventually shutting down the old scraper and moving over to this new one. This way we'll continue to have the explorer UI work well & give Rossy / others the opportunity to move over to this new DB
The text was updated successfully, but these errors were encountered:
tkporter
changed the title
Deploy scraper with Cosmos chains like Neutron / Injective
Deploy scraper with Cosmos chains like Neutron / Injective in mainnet3
Aug 8, 2024
Problem
Once we've implemented everything in the codebase to be able to scrape Cosmos chains, we'll want to deploy the scraper with this change
Solution
The text was updated successfully, but these errors were encountered: