privy

walletconnect

Looks like the current latest version of @reown AppKit comes with two different versions of @viem, and in turn FOUR different versions of two libraries from @paulm’s Noble Cryptography suite.

Fun stuff.

TIL @privy’s `@privy-io/react-auth` package straight up depends on @reown AppKit.

That’s... a LOT of node_modules 😵

Would like to see this slimmed down significantly. Dependency minimalism, pretty please.

The easiest way to bring all your users onchain, regardless of whether they already have wallets | Customer love at privy.io/love

Toolkits to build onchain UX → /reown. Builders of the WalletConnect Network. For the WalletConnect Network, please visit @walletconnect

/frontend dev (HTML/CSS)・founder/decentralized data wrangler /blockhead・contributor /ethglobal /walletbeat・hackathon bounty hunter・music maker・dropout・nomad・25

Yes yes yes. Please!

Adding the “crypto web3” stack in general, and all the 10K things that get willy-nilly dragged along with it is a real smell - not to mention the attach surface on all that.

🐵 ← 🙈🙉🙊 → /phil →  phil.cockfield.net, db.team →  
ƒ(🌳) →  🧫 /sys  ←  @cell <T> 🧠🐦‍⬛, 100% human cartoon, waiheke

One of the biggest impediments to FC "clients" not taking off as a programming substrate in earlier times, I think can be attributed to just what a shit-show the underlying bramble of libraries required make this work is.  

It's hard though - unwinding an unwieldy large dependency graph is not easy feat.  Can't the whole thing be done with one instance of Viem? (I say, intentionally naively)