-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Unable to make 2 messages transaction with 2 signers #10843
Comments
And there is a related question to my flow described above. Alice made a semi-signed transaction with Bob, and then Alice made another one with Charlie. |
UpdateAbout main comment #10843 (comment)That was surprising for me (my fault) but When I rollback my client In general: my main issue is now resolved and workflow works fine 🎉 But I interested in #10843 (comment) if anyone could answer it will be very helpfully for me :] |
That's correct. The sequence number will increase. Glad you have this figured out 👍 . Okay to close this issue now? |
Yea, thanks, could be closed |
Summary of Bug
I want to implement 2 signers 2 messages transaction from a client via gRPC, but I always receive the same error:
x
— is an account number of transaction composer and he is the first signery
— is a correct chain-id of my nodeVersion
cosmos-sdk v0.44.2
Steps to Reproduce
The flow is pretty simple:
Alice is a first signer and transaction composer
Bob is a second signer, fee payer and user who broadcast complete transaction
Alice prepare the transaction, that looks like
Alice encode that json into an array of bytes as a partial tx request and send it to Bob with 3party transport
Bob receive that bytes array and decode it into Protobuff messages, he read all the things inside that transaction and add his own signature (DIRECT)
and after that Bob broadcast that complete tx request and receive an error described earlier.
There is 2 raw code snippets with Swift language
That keys works fine when I use them with single message (single signer) transactions
I tried to use
.legacyAminoJson
with customStdSignDoc
with sorted keys when encoding that struct to json at Alice stepbut I always get the same error :]
Does anyone know it is valid usage of gRPC cosmos API? And what I'm doing wrong?
For Admin Use
The text was updated successfully, but these errors were encountered: