ETHRome - 4-6th Oct

pov: @privy announced their new smart wallet feature and u decided to build a next.js starter kit for it

this is the fastest way to start building a user friendly dApp: no more signatures and gas-fees for your users⚡️

a gift for /ethrome hackers building on AA tracks in two weeks

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

pov: @privy announced their new smart wallet feature and u decided to build a next.js starter kit for it

this is the fastest way to start building a user friendly dApp: no more signatures and gas-fees for your users⚡️

a gift for /ethrome hackers building on AA tracks in two weeks

https://privy-aa.builders.garden

a lemon 🍋 building onchain products and communities w/ @builders-garden 🌳 /urbe-eth & /ethrome 🐺

https://limone.lol

Rome, Metropolitan City of Rome Capital, Italy

While this is cool and super useful. I wonder about the UX a bit. The obfuscation is good for the onboarding, but if user minted an NFT for example using smart wallet (unknowingly), then signed in with his EOA on opensea, he will be puzzled why his NFT is not appearing (as it's owned by smart wallet instead). This is not a new problem and nothing specific to Privy, but just in general a pain point that takes a lot of effort to improve atm 🤔

CTO & Full Stack Developer at @rmrk. Building modular NFTs with truly on-chain composability JS maxi, tea, advaita vedanta, psychonaut
https://x.com/Yuripetusko

Sure. You are right, the ux issue I described is only an issue in particular slice of use cases. Still super cool feature, especially in cases where transactions are sent by the server, just need user to sign typed data to validate that it's him, but server's PK would send tx and pay for everything