Use ThirdWeb SDK for local wallets

neatonk commented 8 months ago

neatonk commented 8 months ago

Process Notes:

These are some of the options I considered. Option 4 is the one I implemented.

1. Use LocalWallets with supabase Auth

Store password to decrypt wallet in DB
Register UUID for each device, only 1 active. 2. Use Embedded Wallet with Super base Auth - install ThirdWeb @ nightly release - use embeddedWallet.authenticate(strategy: "jwt", jwt) - dead end because supabase does not support JWKS yet.
1. Use EmbeddedWallet with Thirdweb Connect modal.
The connect modal loads in an iframe and aacts as it's own app for oauth via google and email OTP.
Email OTP never showed up.
Feels janky, not very customizable.
1. Use LocalWallet with client/server secret exchange
send client secret to server to exchange for deterministically generated password
combine client and server secret can hash result to create password
client cannot recreate password without server.
server will not generate password unless user is authenticated.
server cannot access encrypted wallet store on client.

neatonk commented 8 months ago

TODO:

[ ] send generated wallet address to server (with payload?) to link to user account.

neatonk commented 7 months ago

Done. See #31 for potential improvements.