-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[bug] Invalid signature when using smart accounts with SIWE #3260
Comments
got the same. drove me nuts. wait for appkit // siwe v1.5.0 release bump soon, fixes been FINALLY merged. 🚀 |
@magiziz ETA public release ? |
@elix1er thanks glad i'm not the only one. for some reason, one click sign w/ solana stopped working as well. the modal just stopped showing anymore |
pull the latest now. or @canary. |
can you please confirm that this problem persist or not on latest v1.5.3 ? |
checking now - |
Can anyone find a solution? I cannot verify the signature format returned from Appkit with the same libraries that I used to verify personal_sign. I am trying to verify the signature on the server side. |
please check our new siwe examples and also the docs so you can fix it |
same problem here, the signed message is too long:
|
Hi @itxtoledo @kenjicncr Smart Accounts may emit two different type of signatures depending on if they are deployed or not. It seems our siwe package verification logic is missing the non deployed case which we will address Some references: for now: @elix1er SIW Solana should not have issues in the latest version, could you verify? 🙏 |
Link to minimal reproducible example
https://github.com/reown-com/web-examples/tree/main/dapps/appkit-siwe
Summary
Description
When attempting to sign in with a smart account using Sign-In with Ethereum (SIWE), the signature verification is failing despite the signature being correctly formatted and coming from a valid smart account.
Since email sign-ups default to smart accounts, this make them unuseable for verifcation
Current Behavior
Expected Behavior
Reproduction Steps
Example Signature
0x0000000000000000000000004e1dcf7ad4e460cfd30791ccc4f9c8a4f820ec67000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000003c000000000000000000000000000000000000000000000000000000000000003241688f0b900000000000000000000000041675c099f32341bf84bfc5382af534df5c7461a0000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000007a6733696a79300000000000000000000000000000000000000000000000000000000000000000000284b63e800d...
Environment
Additional Context
The signature format indicates this is coming from a smart account rather than an EOA wallet. The verification process needs to handle smart account signatures differently from regular EOA signatures.
List of related npm package versions
@reown/appkit-siwe: latest
next-auth: latest
The text was updated successfully, but these errors were encountered: