opscan.co is down

[bap2pecs]

tho i can still open https://opscan.co/tx/0xff441f57d28c4d03c3542cf3cb708d5b37f8fda9da0a067096bb16944dc13eae

[mazurroman]

hey @bap2pecs thank you for reporting and apologies for the delay in our response

the site is up again, accessible at opscan.co

FYI we also just announced Milestone 3 completion, and the explorer is finally getting into a usable state. Can you share what's your intention with it? Do you plan to start using it?

[bap2pecs]

Can you share what's your intention with it? Do you plan to start using it?

we are building a finality gadget to OP stack (ethereum-optimism/specs#218) and have started a demo testnet for it.

and we are looking for some lightweight explorer for this demonet. we have experience with blockscout integration but if opscan is easier to integrate, we are happy to try it out.

[mazurroman]

@bap2pecs, thank you for the info. The project looks super interesting.

Feel free to reach out for help with the integration; we would be glad to support. I will also comment here once Milestone 4 is out (expected in ~2–3 weeks from now).

Note: The opscan.co is currently just a snapshot of the chain from a few weeks ago. It’s not running the indexer, so it doesn’t live update and doesn’t contain fresh data. However, it should still give you a good glimpse of the UI/UX.

[bap2pecs]

It’s not running the indexer, so it doesn’t live update and doesn’t contain fresh data

ah that's good to know. Does that imply it's not ready yet for live debugging if we use it for our demonet? most times, we will send a test tx on our OP demonet and want to see it immediately showing up on the explorer

[mazurroman]

@bap2pecs It is ready for live syncing and the setup is fairly simple: you just need to host the database, indexer and the frontend. There is a how-to guide in readme. We will be revisiting the guide in the next weeks as part of Milestone 4 to ensure it's as simple as possible.

To simplify the self-hosting process even further, we are also looking into adding an update API route to the next.js explorer webapp, which you could call every couple of seconds to sync with the head of your chain. This would not require you to host your own indexer and would allow a super simple setup with services like Vercel. Please let me know if this route would be interesting to you.