A place for talking about the Ethereum Virtual Machine on Farcaster.

I've got integration tests that rely on goerli and Alchemy stopped supporting it a month earlier than promised. I tried using a Tenderly fork but their reliability is awful. Does anyone have a recommendation besides telling me to write new tests?

Any ideas for maintaining tests that depend on goerli node RPCs now that goerli is unreliable and will soon be dead?

Head of Engineering at Courtyard.io, bringing physical collectibles onchain. nf.td/joe /courtyard /backend

I don't know best practices since I've done little work that requires a chain.
When I did, I just relied on spinning up my own geth, getting it to the state needed for the tests and then running them.

The open web is dead, long live the open web. ⌐◨-◨

Building Farcaster

I think this makes sense if you're developing smart contracts; it's what we do in our solidity repo. But I'm testing an indexer, and I need data that comes from quite a few places - Seaport, Gelato, payment providers, and our own contracts.

You know what, you're making me realize there's a good argument for directly mirroring the on chain stuff I care about in the DB, and then indexing that, because then I can test the layers separately. Whereas today I do some transformation of the onchain data before storing it... Maybe time to look at shovel again

I see. For the indexer I worked on, I just stubbed everything and returned test data.
My use case wasn't very complicated though.

Also, because we mirrored the state in spanner, each indexing layer read spanner more than the chain.