Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ergoauth requires manually entered address #179

Open
esot321c opened this issue Nov 16, 2023 · 0 comments
Open

Ergoauth requires manually entered address #179

esot321c opened this issue Nov 16, 2023 · 0 comments

Comments

@esot321c
Copy link

esot321c commented Nov 16, 2023

Expected behavior:

ergoauth://${strippedUrl}/generateAddressLink/${uuid}/#P2PK_ADDRESS#/ would generate a message signing request which would ask a user to choose their wallet, then sign a message, and return an object as such:

{
  signedMessage: 'abcde'
  proof: 'xyz',
  changeAddress: 'address',
  addresses: ['array', 'of', 'addresses']
 }

Optionally you could leave out the address array for the wallet. Or change it to used and unusued like dappconnectors do. You could leave addesses out of the return object also because it can be picked up by the api via the URL if you only wish to return the chosen address and no others.

Current behavior:

Ergoauth requires the front-end to get the address before making the Ergoauth request. Two ways we have done this:

  1. Request the user adds their address to an input box manually (bad UX, what if the address is on their phone but they are using a desktop device, they have to email it to themselves or something)
  2. Allow the user to scan a QR Code for Ergopay to derive the address (This is bad UX because then we need to tell the user to choose the address, scan another QR code to initiate ergoauth, and choose the same address again. The user could choose the wrong address and we don't get the error state back to our dapp)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant