Temporary Browser Wallet

[0x4007]

Temporary Browser Wallet

Fingerprinting

Before going to sleep yesterday I was also researching browser fingerprinting and generating a temporary wallet in the client to immediately accept the payout. Like if a bounty hunter opens it on their phone and doesn't want to deal with the tedious mobile wallet experience to handle an instant/quick payout. Checking things like IP, timezone, locale, screen resolution, browser, hardware.

The private key could be saved in browser localStorage with the warning that its temporary and must be backed up or transferred out as soon as possible.

The inspiration behind this is:

1. to re-think the current (arduous) status-quo of crypto payments. I'm really keen on making the experience as seamless and pleasant as possible.
2. to onboard non crypto native developers to the DevPool. If they can accept a payment without having a wallet setup as a prerequisite, it could lure them to finally set up a wallet (import their private key) to continue participating!

Password / OAuth

We could also let a non-crypto payee generate a seed with a password or authentication with another OAuth provider.

Appendix

This makes gasless transactions (relayers) needs much more apparent if we allow users to generate temporary payment wallets.