Just wrote a very simple Solana account for claiming SPL tokens with an secp256k1 signature.

Nearly died.

What can be done under 5 minutes and 73 lines in very readable Solidity has been bloated to 300+ lines of Rust Anchor code that took more than 20 hours.

I’m not even sure if it’s correct without spending weeks to write tests.

In Solidity, Signatures / Merkle Trees are considered beginner stuff.

In Anchor, Signatures / Merkle Tress are considered advanced stuff.

And the compilation times… fuck. It’s 10x slower than —via-ir on even the most hardcore Solidity codebases.

This makes me understand why they are mostly pushing UX and relabeled memecoins.

Solidity Engineer | Researcher | Onchain Degen | DMs Open | https://github.com/0xCooki

Dang. DAMM!

Only possible on Solana I guess.

the thing that really shocked me is the deployment costs on Solana are wild - something like 10 SOL to deploy a pretty simple program iirc

design trade-offs all the way down

Full-time builder. @pimlico | @33bits | @66bits | farcaster-solidity | x.com/potekhin_sergey. Zero-knowledge and asynchronous transactions evangelist.

this is actually low key friggin genius. Make devX so hard that people contribute to your TPS.

Are there libraries like oz/solady/... for Anchor? I don't know much about Solana, but given that Merkle tree implementation takes so much hassle, I guess their tps may be solely created by people doing the airdrops the old way 😮

I thought i was dumb for not grokking it ty for this 😭