Valentin Rodygin

Hey @kopeboy! We're about to release a set of API and UI changes to surface this data, it should be available mid-September.

Hey @divine-comedian, could you attach the files so we could debug? As a workaround, you could verify on https://sourcify.dev, the explorer pulls from there.

@divine-comedian Both Explorer and sourcify don't support verification via flattened sources. I used https://legacy.sourcify.dev/ in the past, if you have the separated files still, you could try it out.

I've updated the blockchain client to match the upstream format in this [PR](https://github.com/celo-org/celo-blockchain/pull/2254), it's already deployed to `rc1staging`. I also updated the blockscout's code to match the previous expectations of...

> Hey @carterqw2 , this requires archive nodes to be deployed at [1fc347330](https://github.com/celo-org/celo-blockchain/commit/1fc34733020cef6666d46ac67c86bfe6e1df2b40) - correct? Yeah, I updated them on `rc1staging` for testing but not on other envs yet.

Related to https://github.com/celo-org/celo-blockchain/issues/1613

Gonna test with Blockscout on staging.

Celo is compatible with Ethers.js since December. Announcement [here](https://forum.celo.org/t/developer-experience-update/4978). If you’d like to share any feedback feel free to post it in this [Github discussion](https://github.com/celo-org/celo-monorepo/discussions/9922).

Should be fixed here https://github.com/celo-org/celo-blockchain/pull/2010

We'll open a specific one for the block format.