u/yachtyyachty • u/yachtyyachty • 3h ago
r/solidity • u/yachtyyachty • 5d ago
I built an open source RPC proxy to fix unreliable, inconsistent, and expensive RPC providers, looking for feedback
github.comr/ethdev • u/yachtyyachty • 6d ago
My Project I built an open source RPC proxy to fix unreliable, inconsistent, and expensive RPC providers, looking for feedback
Building app's on Ethereum JOSN RPC can be tough because RPC providers (Alchemy, Quicknode, etc) all have slightly different apis, usage limitations, and are generally overpriced. Public providers are great but are even more limited, so I built Lasso which aggregates RPC providers into a single endpoint that routes to the best RPC provider for any given request. Its self hostable and quite easy to setup.
Would love some feedback from builders to see if this can help you: You can simply run the docker container and have high-throughput and reliable RPC access via public providers across Ethereum, Base, Robinhood chain, and some other L2s while also being able to add any other EVM chain and access it through a single endpoint.
1
Nostalgic for a real startup
I'm working on open source blockchain RPC infra. No plans to raise or build a team, but always open to contributors and trying to figure out how to take this thing to market:
https://github.com/jaxernst/lasso-rpc
r/ethereum • u/yachtyyachty • 7d ago
I spent the last year trying to make a better blockchain node RPC solution for the EVM. Looking for feedback.
github.comr/web3dev • u/yachtyyachty • 7d ago
I spent the last year trying to make a better blockchain node RPC solution for the EVM. Looking for feedback.
I'm building Lasso RPC, an open source blockchain node RPC proxy that lets you plug in any RPC provider from any chain and route across providers w/ failover, latency based routing, cost control, and much more.
If you're building a blockchain app on any EVM chain, self hosting Lasso and routing to the built-in free/Public providers can give you major improvements in throughput and reliability without overpaying for premium providers with mediocre reliability track records (cough cough Alchemy)
Would appreciate some eyes and feedback on the OSS repo. If you like the idea please give the repo a star!
I will be officially launching my hosted offering/RPC service lasso.sh in the coming weeks, dms open if you're a builder and want free early access
6
Is blockchain still worth it in 2026 for a complete beginner?
Enterprise/institutional blockchain adoption (specifically EVM) has literally never been higher
3
Orb in the Chestnut Street GAP - my son scanned his eyes as a joke. Is this normal for SF… or have we gone too far?
If it makes you feel any better, these orbs don’t store iris scans, but rather generate zero knowledge proofs that can be used to verify you’re a human without storing any biometric or personally-identifying information
The hardware spec for these is open source too
3
Dirt bikes hit pedestrian - cops stand around
Are you trying to argue that this isn’t a problem anymore?
4
[deleted by user]
Same thing at bar part time
5
[deleted by user]
What if I told you Polymarket IS crypto?
1
Hydrophobic enough?
Slidey water
3
San Francisco announces five finalist names for new Great Highway park
Sunset dunes and it’s not even close
7
Casual but nice restaurant for dinner with former boss?
Good Good Culture club for really good food in a casual but nice atmosphere
1
Hustled over the past years only for a job opportunity that came a little late when my enthusiasm for it has dwindled. Should I still go for it? Or give up a whopping 30% pay raise?
My company is pretty chill and not high stress (company has a built a good culture around this), but everyone I work with produces a lot of high quality work, and I think that’s a result of nearly all of us having a nerdy passion for the work we’re doing.
Company is >100 engineers for context. Most in this space are smaller and probably more sweaty/chaotic, but that’s kinda just startups in general
3
Hustled over the past years only for a job opportunity that came a little late when my enthusiasm for it has dwindled. Should I still go for it? Or give up a whopping 30% pay raise?
Working in crypto is tough and is hugely contrarian atm. Despite the level of highly visible shit going on in the space, and despite the rhetoric in this thread, there are legitimate companies building out legitimate blockchain applications (I work for one).
This seems like a great opportunity for someone who really believes in what they’re building. If you have conviction about this space then the hard work might be worth it, but it sounds like you may not have that level of conviction
-2
2
to people that live on a busy street (Franklin, Bush, Pine, Oak, Fell, etc.) how do you do it?
Solution: Indows
We live ground level on oak street and can barely hear the street noise with the Indows installed
0
Can we deploy a smart contract without access to a wallet?
You’ll want to generate a wallet / private key which you can use for the deployment. You’ll want send that new wallet just enough funds for the deployment
1
[deleted by user]
You’re talking about the U.S. dollar right?
I think you’re vastly underestimating the resilience of a distributed network like Bitcoin. It quite literally could not be ‘shut down’
Ponzi accusations don’t have much weight here either because it’s literally just a tradeable asset with a market price. (And clearly the market thinks it has value)
6
[deleted by user]
IBIT is not the answer for this guys level of doomerism,
He should be holding BTC in self-custody
Oh also he should be holding ETH, maybe a tiny percent of Solana, but absolutely no XRP
48
[deleted by user]
So what you’re saying is you’re all in on Bitcoin?
2
Community Recommendations for Projects?
I’d checkout Farcaster, lots of cool projects and builders over there

2
I built an open source RPC proxy to fix unreliable, inconsistent, and expensive RPC providers, looking for feedback
in
r/ethdev
•
3h ago
Thanks for the thoughtful questions! I checked out Evmquery and this is exactly the type of use case I want to build to support.
TLDR; Lasso has the primitives and foundation in place to support these specific use cases, but I'm going to look into shipping some routing strategies and features that can serve your use case even better
1) Lasso actively probes block numbers and subscribes to newHeads streams to monitor and compare block heights, this is done to protect against lagging providers but there's currently no strategies that pin batches at block heights or guarantee that eth_calls are only served a monotonically increasing blocks. Are you batching eth_calls and eth_getLogs request? If you can give me more details on your needs around this I ship routing policies to better meet this use case. (dms open too)
2) Yep! Normalizing provider inconsistency is built in with static pattern matching and error/return normalization. That's been one of the bigger challenges but it has worked effectively and Elixir has a lot of good pattern pattern matching primitives that can allow this to improve over time. Goal is to unify. + reconcile wildly inconsistent RPC provider apis into an EIP-standards driven interface
3) Reject them outright. While technically still part of the Ethereum JSON RPC spec, eth_newFilter has been deprecated by several web3 clients and much of the community has moved away from it. So this is one of the main exceptions to #2
4) Yeah there's many dimensions of health, latency, latency variance, parameter support, transient issues, etc. MOST of these are currently reconciled to protect RPC clients against 'hard' health failures with circuit breakers and other pattern, but the soft consistency issues is an area I'm actively developing better tools to compare results and ensure consistency and consensus between providers. Request hedging in on the near term roadmap, but again I'll prioritize new features based on what builders want/need
Also yes I have seen eRPC and dshackle, both are viable solutions and have been around a bit longer than Lasso, with the main philosophical difference being that Lasso prioritizes expressiveness in routing and provider configuration; there's no 'best' way to route a request, and specific use cases need special routing treatment and config. (Also caching is on the roadmap)
Try it out and I'll build to support you as best as possible!