-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
signature verification failed; please verify account number and chain-id: unauthorized #14789
Comments
Here's the JSON of the Proto before serialisation:
|
have you resolved it? I have the same question |
hey how are you broadcasting the transaction. I use cli predominantly and it asks me for chain-id when i forget. |
I use c++ to send rpc request,it sometimes can be success,sometime the above problems occur |
I'm getting this error in trying to upload a contract in Secret Network, according to their guide: https://docs.scrt.network/secret-network-documentation/development/development-concepts/create-your-own-snip-20-token-on-secret-network I'm guessing it's not a Secret issue but a Cosmos problem. this was closed but no resolution was posted. is there one? |
I'm trying to broadcast a transaction via the api
/cosmos/tx/v1beta1/txs.
I'm serialising the entire transaction as a protobuf, and the simulation api works fine.
If I broadcast a transaction via /cosmos/tx/v1beta1/txs/simulate, I get the following response:
However if I try to upload the transaction via "/cosmos/tx/v1beta1/txs." I get the following response.
"signature verification failed; please verify account number and chain-id: unauthorized"
Here's a Json of the model that I pass the Cosmos Rest Backend.
Then I upload the entire transaction as the following JSON object:
Version
v0.45.1
Steps to Reproduce
Simply protobuf serialise the transaction Tx Object, and pass it into the Json (final entry) above, and run a post on the api:
/cosmos/tx/v1beta1/txs.
Then you will get the message:
"signature verification failed; please verify account number and chain-id: unauthorized"
So I'm not sure what I'm doing wrong here.
I'm using ECDSA Signing to generate the signature with the private key, and running verification is successful.
The public/private keys look correct, and everything matches the data that cosmos looks like it requires for a successful broadcast.
So I'm not sure what's going on?
The text was updated successfully, but these errors were encountered: