Tudor π£π‘
@tudorizer
have we talked about composability? apps with embedded wallets inside apps with embedded wallets so you won the big pot on a @ponder prediction market. Well done! are you withdrawing the funds to your Warplet? are you withdrawing funds from your Warplet to Rainbow? are you doing the copy-paste dance across apps and devices? @vitalik.eth βs βone address per appβ statement was in the right direction, but issues of account management (beyond asset holding) become obvious. throw the new @coinbasewallet in the mix and UX friction increases. Iβd be keen to hear @dwr.eth and @henri take on how is Alice navigating all this. (thoughts inspired after hanging our with @sheldrake and @accountless.eth today)
9 replies
10 recasts
19 reactions
Tako Unik
@tako-unik
Can we export warplets to rainbows and vice versa?
1 reply
0 recast
1 reaction
Tudor π£π‘
@tudorizer
on some platforms you can, on others not. the degrees to which this is implemented varies you are thinking in right direction thiugh, cypherpunk-style
1 reply
0 recast
1 reaction
Tako Unik
@tako-unik
Whatβs your take on this?
1 reply
0 recast
0 reaction
Tudor π£π‘
@tudorizer
as a wholistic view: in web2 we ended up with the likes of Visa and Stripe being ubiquitous, although still manageable because we donβt have a credit to top up in each and every app imagine having credit it every app installed on your phone sure, you βownβ where this is stored and you could withdraw it, but the withdrawal would happen to Apple first and then to your bank account. obviously, each app will also have on/off ramp, right? riiight?! this exercise of imagination tackles only the financial aspect. identity (not identifiers) is a whole other ordeal. the real answer is to have these discussions in a d/acc manner and build the stack to prepare Alice for all of this. even beyond Alice, the devs will not have a good time. wdyt @stephancill ?
2 replies
0 recast
3 reactions