Content pfp
Content
@
https://onchainsummer.xyz
0 reply
26 recasts
26 reactions

Max Branzburg pfp
Max Branzburg
@max
You're building an app and can use: 1. Privy, et al that enable a simple, segregated wallet for your app alone 2. Single sign-on w/ unified wallet that enables users to bring their assets/identity everywhere Assume for a moment they both offer seamless UX w/o janky app-switching, gas fees, etc. Which do you choose?
7 replies
7 recasts
38 reactions

BRG pfp
BRG
@brg
This is an interesting question. And an interesting trade-off consideration. The idea of ending up with 10s of single-purpose embedded wallets kinda beats down parts of the original “onchain identity” value prop, no?
1 reply
0 recast
2 reactions

Bethany - countessellis.eth🎩 pfp
Bethany - countessellis.eth🎩
@ellis
I’d include both as options to users. Give an option, both during signup and as a later option, to bring your own wallet, but also have a built in one for those who don’t have one or don’t want to link it. Adding your own wallet later would have the option to send existing funds in the built in to the linked one.
2 replies
0 recast
1 reaction

Eric Kuhn pfp
Eric Kuhn
@ekuhn.eth
do you have a swift sdk on the roadmap?
1 reply
0 recast
0 reaction

Adam pfp
Adam
@rhynotic
Guessing #2 wouldn't have headless? Pro for privy is that the app can control all the transactions for a wallet
2 replies
0 recast
1 reaction

Henri Stern Ꙫ pfp
Henri Stern Ꙫ
@henri
How about 3. Privy with global wallets enabled :D https://www.privy.io/blog/global-embedded-wallets
1 reply
0 recast
2 reactions

Nitya pfp
Nitya
@nitya
Why not both! usecapsule.com :)
0 reply
0 recast
1 reaction

‏ pfp
@maxbr
3. Particle Network and ERC-4337 Accounts Create your own validator or module to perform functions on your contracts. All they have to do is enable it the first time. Then you can do whatever you desire on the backend, sponsor their gas, submit batch transactions, etc. Can also do custodial 4337 accounts w/ pks
0 reply
0 recast
0 reaction