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

eip-0028 ErgoAuth #96

Open
esot321c opened this issue Oct 2, 2023 · 0 comments
Open

eip-0028 ErgoAuth #96

esot321c opened this issue Oct 2, 2023 · 0 comments

Comments

@esot321c
Copy link

esot321c commented Oct 2, 2023

I've encountered a couple roadblocks while developing for eip-28

Mobile issues

  • Ergoauth doesn't return to the authenticating website once the message is signed. (It does return on an Ergopay request)
  • No way to generate the required SigmaBoolean without running appkit. Shouldn't it just accept a normal address string? Why does it need to be converted to a SigmaBoolen first? I can't find a way to do this in ergo-lib-wasm-nodejs or fleetsdk, though I'd be happily proven wrong. I couldn't figure it out by going through the sigmastate source files which have the functions that appkit uses, but if someone would show me the correct function, I'll build a typescript version.

Inconsistencies

There should be a consistent signature string returned. It doesn't matter which is chosen, but a standard would be helpful so we don't need to filter for wallet type first.

For reference: mobile returns 20 random characters, then the provided message, then the address WITH https:// followed by 20 more random characters. Nautilus returns the provided message, a semi-colon, the source address WITHOUT https://, another semi-colon, followed by two strings of random characters separated by a semi-colon.

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