Content
@
0 reply
0 recast
2 reactions
andrew
@boop
Been getting questions on how this works. Under the hood, it was important for us to use tried-and-true systems and not reinvent the wheel as we help users access their embedded wallets through RainbowKit, ConnectKit, and many other connector libraries 1/
1 reply
4 recasts
7 reactions
andrew
@boop
We use @coinbase's Mobile Wallet Protocol, which is typically used for connecting to external wallets. We implement the connect handshake, which does a Diffie Hellman cryptographic key exchange to generate a shared secret between an app and the wallet and establish the connection. 2/
1 reply
0 recast
2 reactions
andrew
@boop
Then, at transaction time, the transaction contents are encrypted by the secret before sending to the wallet UI for the user to approve. The wallet will only allow the user to act on these requests if they were encrypted with the shared secret established in the connection handshake. 3/
1 reply
0 recast
1 reaction
andrew
@boop
@mads367 goes into more detail in today's blog post! If you want to learn more or set up a cross-app experience, DC me! We're always available to help. https://www.privy.io/blog/wallet-connector-deep-dive /fin
2 replies
0 recast
2 reactions
Thibauld
@thibauld
That's super cool!! Quick 2cents feedback: You should explicitely mention here that to test the demo, the user needs to select the Strawberry Fields wallet :) It got me puzzled when I initially looked at it. #My2cents
2 replies
0 recast
1 reaction
Thibauld
@thibauld
Follow-up question: I suppose that "Strawberry fields" is not a global privy wallet but the privy wallet tied to another organization. Hence my question: Who decides which Privy wallet appears here in the rainbow kit window? Can only 1 wallet show or several?
1 reply
0 recast
1 reaction
andrew
@boop
The developer (whoever integrates rainbowkit) can choose - you can add any or all the possible public Privy cross-app applications!
0 reply
0 recast
1 reaction
