tl;dr - celo.blockscout.com is the new hotness, explorer.celo.org is going away (but redirects will exist to (hopefully) make it seamless)
Hey all,
the Blockscout instance at explorer.celo.org has been running for some time with an out of date revision and database schema. Due to staffing issues and expenses, we’ve not been able to prioritise updating this or giving it the attention it needs to continue working. With the migration to an L2 happening this year we will need a new service that supports the OP stack as a first class citizen.
Fortunately the upstream blockscout project already supports this, and the Blockscout team is hosting an instance at https://celo.blockscout.com at this moment. In the best case this means that due to the shared project history, requests and queries can be pointed at the blockscout.com instance without significant API incompatibility.
As with any significant migration there may be hiccups and issues - we ask for your patience and please reach out to us with any feedback or problems encountered during the switch over.
What this means
- The cLabs hosted blockscout service at explorer.celo.org will be retired
- We aim to have this done by Feb 1st 2025
- There is an existing replacement service at celo.blockscout.com hosted by the blockscout team
- Redirects will be set up to rewrite requests to point to celo.blockscout.com with a 301 redirect
- Both services are instances of the same project, and we expect functionality to persist throughout
- celo.blockscout.com is much newer however, and there may be teething problems
- We will be testing this functionality over the next few weeks
Once again, feel free to reach out to us with queries, concerns or issues around this service.
Thanks,
- cLabs DevOpsRE