You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like the extension onboard to have fewer steps the user must complete.
In the alpha 1 release, the user must copy a public key from the extension and paste it into the wallet provider's website.
2024-05-30.alpha1.clip.share.mp4
Describe the solution you would like
User enters wallet address and taps connect.
Extension opens the wallet provider's website with the extension's public key as a URL parameter.
Wallet provider authenticates the user and saves the extension's public key when the user confirms they want to authorize the amount to use from the wallet.
Additional context
I'm not sure if additional information can be passed along with the grant approval. If not, then the desired solution would be to first confirm the user wants to use this browser for Web Monetization (as a way to approve saving the public key) and then the grant approval for the budget is a second approval.
While Interledger does not control the wallet provider website, but it could define a URI scheme as part of the wallet provider specification. Something like https:// (walletProvider.example/usersWalletAddress) /keys/add?key= (public key contents here). Because the key is a public key, it's fine for it to be passed as a URL parameter, where it might be included in server access logs.
The text was updated successfully, but these errors were encountered:
Describe the feature you would like to request
I would like the extension onboard to have fewer steps the user must complete.
In the alpha 1 release, the user must copy a public key from the extension and paste it into the wallet provider's website.
2024-05-30.alpha1.clip.share.mp4
Describe the solution you would like
Additional context
I'm not sure if additional information can be passed along with the grant approval. If not, then the desired solution would be to first confirm the user wants to use this browser for Web Monetization (as a way to approve saving the public key) and then the grant approval for the budget is a second approval.
While Interledger does not control the wallet provider website, but it could define a URI scheme as part of the wallet provider specification. Something like
https:// (walletProvider.example/usersWalletAddress) /keys/add?key= (public key contents here)
. Because the key is a public key, it's fine for it to be passed as a URL parameter, where it might be included in server access logs.The text was updated successfully, but these errors were encountered: