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
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
Smart account signature verification fails with "Invalid signature" error
The signature is properly formatted and starts with 0x
Using @reown/appkit-siwe for verification
Expected Behavior
Smart account signatures should be properly verified
Authentication should succeed with valid smart account signatures
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:
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: