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

CIP30DataSigner.signData Produces a Different Signature and Key Compared to Eternl #480

Open
fabianbormann opened this issue Dec 31, 2024 · 1 comment

Comments

@fabianbormann
Copy link
Contributor

I am using the CIP30DataSigner like this:

CIP30DataSigner.INSTANCE.signData(userAccount.baseAddress().getBytes(), message.getBytes(), userAccount);

However, when I use the same user account with Eternl to sign the exact same message using the same requested address (showing up in the popup window), it produces a different signature and key compared to the one I got from the CIP30DataSigner.

I’m happy to provide more information if needed, but I currently suspect that my usage or understanding might simply be incorrect.

@satran004
Copy link
Member

@fabianbormann Let me check this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants