A place for developers to talk about building on Farcaster.

/dev

1/ With the rise of embedded wallets, a vital topic to think through is interoperability. That is, how do siloed wallets turn into global wallets.

In this thread, I explore a few paths to consider. 🧵👇

Note: approaches 1-3 are simpler; 4-7 more complex; Please consider this a draft for community discussion 🙂

Building dynamic.xyz | @dynamic | Craft magical onchain sign up experiences  - embedded wallets, login, user mgnt, authz and more | Demo: demo.dynamic.xyz

Fantastic thread!

One potential sticking point for 1 & 4 is that unless the embedded wallet platform purges the PK and/or has permissions revoked at time of export, they maintain the ability to sign, initiate txns, etc. on behalf of users. This gets dicey when the wallet exits the walled garden + holds more assets

Thanks for the thoughtful reply!! I guess that depends on whether the implementation is custodial/not-custodial. In a non-custodial model, the dapp shouldn't be able to sign on behalf of the user, meaning even if the embedded wallet holds the key, unless the user initiates an action it should be somewhat limited.

Hm, not sure I agree there. A big value prop for embedded wallets is abstraction of technical processes and full white-label UI customization. I don’t think either of those things necessary require the platform or service provider to custody assets.