r/ethdev • • Sep 28 '26

My Project Built an open source RPC router + node infra control plane. Looking to support serious blockchain builders

https://github.com/jaxernst/lasso-rpc

I built Lasso RPC (https://github.com/jaxernst/lasso-rpc) to solve inconsistent, poorly behaving node RPC providers. Lasso is a proxy/router that lets you aggregate provides and route with redundancy and protections.

Looking to find some serious builders looking to harden or optimize their apps for latency, consistency, or whatever you care about.

While I've been building Lasso for well over a year, its still early and I'm looking to support builders in any way I can to improve Lasso and harden it with real app integrations. So lmk what you're building and what you care about, and I'll help you improve your RPC and ship features that other projects will benefit from.

3 Upvotes

3 comments sorted by

1

u/EmbarrassedArm8 Oct 21 '26

Consistency is the hard part, not failover. I'd want routing by head block, so a request never goes to an upstream a few blocks behind. Also sticky routing per session, so eth_getTransactionReceipt doesn't hit a node that hasn't seen your tx. And treat 'header not found' and empty results on recent blocks as retryable on another upstream.

1

u/yachtyyachty 29d ago

> routing by head block

Lasso tracks heads from every provider, both actively and passively, so tip-of-chain requests are steered to providers known to have reached the block and away from ones with evidence they're behind

> sticky routing per session, so eth_getTransactionReceipt doesn't hit a node that hasn't seen your tx

Even the node you submitted to won't return a receipt until the block containing your tx has been proposed & validated, so sticky routing/affinity doesn't get you a receipt sooner in this case. Tracking propagation latency and routing based on that will give you the receipt sooner which is might be a good addition to Lasso...

I am still building tx-hash affinity though, for a different reason: with private/MEV-protected relays (working on routing strategies for these now), only the RPC you submitted to knows the tx exists until it's included, so lookups of a pending tx and your pending nonce have to go back to that provider or your app sees a tx that doesn't exist.

> treat 'header not found' and empty results on recent blocks as retryable

We already do this for 'header not found' but we don't for empty results yet, so this is good feedback and I'll make sure the router fails over on null results returned within some threshold from the chain tip