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
I am trying to sign a message sent from my server using the SmartAccountClient but when I verify the message on the server I get the error "invalid raw signature length".
I have had everything working using various other wallets and signers so I don't believe this to be a server issue but I have noticed that the response in "https://api.g.alchemy.com/signer/v1/sign-payload" looks correct but then when I log the signature returned by the function, it is much different.
Am I missing a conversion or something like that to get a valid signature or is a different scheme used?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I am trying to sign a message sent from my server using the SmartAccountClient but when I verify the message on the server I get the error "invalid raw signature length".
I have had everything working using various other wallets and signers so I don't believe this to be a server issue but I have noticed that the response in "https://api.g.alchemy.com/signer/v1/sign-payload" looks correct but then when I log the signature returned by the function, it is much different.
Am I missing a conversion or something like that to get a valid signature or is a different scheme used?
Minimal Example:
Response from "https://api.g.alchemy.com/signer/v1/sign-payload" for the above which looks better to me:
0xa7f3daa904502bee80fb1f1c29d52d65b53ebbe073db9b3b848fb9ec6b50ae9569b5b02772de4729f32b2c05010394f8f9102c1550f6fc4d54fa1fbc68b220831b
Beta Was this translation helpful? Give feedback.
All reactions