Replies: 3 comments
-
The Providers used in the RootLayout of our Next.js app
The
The
This is my config file
We use the
The Let me know if you need any more info |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Beta Was this translation helpful? Give feedback.
0 replies
-
The 4 requests: 308
308
200
401
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi!
I need to make signature for both our SCA and EOA users. I'm using
useSignMessage
hook to sign.The signature message is:
"Sign into voxies"
This is the result of what I logged:
This is the logs of the
account
ofuseAccount
This is the logs of the
user
ofuseUser
The signature's decoded wallet address is not in any of them.
When trying to do the signature, it makes 4 requests;
POST to http://localhost:3001/api/rpc//signer/v1/sign-payload gives 308
POST to http://localhost:3001/api/rpc//signer/v1/sign-payload gives 308
POST to http://localhost:3001/api/rpc/signer/v1/sign-payload gives 200 with the signature in the response
POST to http://localhost:3001/api/rpc/signer/v1/sign-payload gives 401 with {"error":"could not verify api key signature"}
In the onError I receive {"error":"could not verify api key signature"}
This is the logs for an EOA signature:
The EOA signature is not making 4 requests.
Can you help me sorting that out to make valid signatures please?
Beta Was this translation helpful? Give feedback.
All reactions