Defi renaissance

The Angstrom testnet will be live soon. If you're a liquidity provider, market maker, solver, router, or protocol dev, fill out this form to apply for early access or connect with our team.

I was playing around with a Solana side project this weekend, and my god am I thankful for all the tooling from Alloy and Reth. My intro to Ethereum and rust was ~2/3 years ago by reading through the entire Reth codebase (at the time) over the course of 6 months. The process was smooth - building small tools with ethers-rs accelerated my learning timeframe. Since then, I have spent the large majority of my waking hours building, following the good practices I learned from these libraries and others like them. I could not imagine doing the same on Solana. At all. Here are some of the issues I had with the rust-sol space this past weekend: ⁃There is no unification of the tooling. Every core/sdk library seems to be using a different version of each other, all with their deps locked. You do not need 10 versions of the same crate in your Cargo.lock, just saying. ⁃Where are the docs? I’m convinced there are more docs in reth and alloy than every single public rust-sol library combined. ⁃Bad/annoying code practices: ⁃I’m honestly surprised that one of, if not the, major DEXs feels the need to call unwrap() everywhere in their sdk - a little bit of error handling goes a long way (@RaydiumProtocol). ⁃Any reason the core Sol sdk has to have functions that take referenced arguments even when they impl Copy? No, it’s ugly. This is why I’m bullish on Ethereum - being able to elucidate complex topics with good tooling and docs will allow for building to progress faster. Without that, you are left with a small subset of people who know the code well because they wrote it, and it becomes a tall task to onboard new devs. Maybe it’s better in other languages, but if not, do better Solana, otherwise you will just be left with your memecoins. Sorry for the rant. Go birds.

I'm ready to see it go down!🥤🍿