When I run the simulation Api, the transaction works perfectly. However when I run a transaction just via the standard api, it fails with a "signature verification failed" error. This issue is related to the signature being passed to Cosmos not containing the correct Chain-Id or Sequence Number. However I've confirmed that the base64 has it. And all the payloads being sent are correct (Protobuf & Rest JSON), according to the Cosmos SDK support team.
I've also confirmed that the signature contains the correct Chain-Id & Sequence number.
This issue is related to the C# SDK that I'm currently building. It allows users to broadcast Tx data to Terra (Cosmos). Here's the link, if you want to generate a PR:
You don't want to know how many hours I've spent trying to figure this one out.
[b]I'm trying to send a broadcast to the Cosmos Blockchain, via the Terra Pisco/Rebel1 Api.[/b]
LUNA2: https://pisco-lcd.terra.dev/swagger/#/
LUNC: https://rebel1.grouptwo.org/swagger/#/
When I run the simulation Api, the transaction works perfectly. However when I run a transaction just via the standard api, it fails with a "signature verification failed" error. This issue is related to the signature being passed to Cosmos not containing the correct Chain-Id or Sequence Number. However I've confirmed that the base64 has it. And all the payloads being sent are correct (Protobuf & Rest JSON), according to the Cosmos SDK support team.
[b]I have generated an issue in the cosmos-sdk repo below (it contains all the details, models, dtos, protos, I pass cosmos):[/b] https://github.com/cosmos/cosmos-sdk/issues/14789 [list] [*] I've verified the Protobuf data according to terra-money's terra.js library https://github.com/terra-money/terra.js. And the data looks correct. [*] I've also confirmed that the signature contains the correct Chain-Id & Sequence number. [/list] [b]This issue is related to the C# SDK that I'm currently building. It allows users to broadcast Tx data to Terra (Cosmos). Here's the link, if you want to generate a PR:[/b]