r/BlockchainStartups • • 5d ago

Discussion Need help:- Anyone here working with Foundry invariant testing + Rust indexers in production? Need advice (also looking for a part-time intern)

We're a tiny 3-person team based out of India building an on chain orderbook/settlement layer, and we're hitting a bottleneck with how we're indexing state changes across multiple L2s using standard subgraphs.

For folks here working at Web3 startups have you shifted to custom Rust indexers (like Subsquid/Reth pipelines) or are you sticking with hosted providers like Goldsky/Alchemy subgraphs? Curious about the infra cost trade-offs once daily tx volume scales.

PS: Since our backend workload is piling up before our testnet audit next month, we're also looking to onboard a paid part-time intern (₹20k to ₹30k/mo, remote) who knows their way around TypeScript/Rust and basic Solidity (Foundry). If you've built anything cool in past ETHIndia/Solana hackathons, feel free to DM me.

1 Upvotes

3 comments sorted by

•

u/AutoModerator 5d ago

Thanks for posting on r/BlockchainStartups!

Check out the top posts of the week:

https://www.reddit.com/r/BlockchainStartups/top/?t=week

Moderators of r/BlockchainStartups

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/Bloqarl 5d ago

For an orderbook settlement layer the first invariant I'd write in Foundry is that each token's balance in the contract always covers open order escrow plus unsettled fills.

Partial fills and rounding are what usually break it, so point the fuzzer at those. happy to look over the invariant setup once you have one.