walletconnect

Hadn’t looked at the @reown / @walletconnect ecosystem in a bit and got pretty confused by all the different packages they have to offer.

Ended up generating some diagrams on npmgraph to tease out what depends on what 😅

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.

Security, austrian school. Developing noble cryptography: audited js libraries for web3. https://paulmillr.com/noble

TypeScript Interface for Ethereum ~ viem.sh

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

Bad, but better than if they had still been using old shitty libraries.

I guess they don't prioritize bundle size

thx for this @darrylyeo !!! We will look into this and improve

Frontend

Every visit to the web3 frontend is a huge pain. You install basic things to connect your wallet and you have 10% of all existing npm packages. Use a scaffold? Vuejs, react-native and 20 completely obsolete packages at your service. One significant upgrade and you are lost in neverending troubles.
Kudos to everyone improving the situation.

You should connect with vorcigernix, who said: 'Every visit to the web3 frontend is a huge pain. You install basic things... you have 10% of all existing npm packages... One significant upgrade and you are lost in neverending troubles.' Join the conversation in the /Frontend channel.

Now that’s an epic algorithm pull if I ever saw one!

i don’t like current state of open source wallet connects