Proto signing fails when accountNumber = 0
See original GitHub issueAll the tests for proto signing use 1
as the accountNumber
:
We had a situation where we tried to send tokens from accountNumber: 0
, which gets converted to a Long
of {low: 0, high: null, unsigned: null}
here:
omitDefaults
then recursively converts this to a plain JS object of {low: null, high: null, unsigned: null}
here:
This leads to an invalid signature (ref: https://github.com/tendermint/vue/issues/39)
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Generating, Signing and Broadcasting Transactions
This document describes how to generate an (unsigned) transaction, signing it (with one or multiple keys), and broadcasting it to the network.
Read more >Protocol Documentation - Hashgraph Developers
Each signature pair corresponds to a unique Key required to sign the transaction. SignaturePair. The client may use any number of bytes from...
Read more >gRPC Client | IRISnet Documents
An overview of all available gRPC endpoints shipped with the IRIShub is Protobuf documention. # Generating, Signing and Broadcasting Transactions. It is ...
Read more >Docs · cosmos/cosmos-sdk - Buf.build
cosmos/tx/v1beta1/service.proto ... AuthInfo describes the fee and signer modes that are used to sign a ... not support fee grants, this will fail....
Read more >Data Types — Daml SDK 2.5.0 documentation
Int Stores signed 64-bit integers. ... For example, you can no longer access the account number of a Location directly, because if it...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
0.24.0-alpha.26 is released, which should fix this again since we regenerated internal types with a version of ts-proto that does not serialize default values like accountNumber = 0.
Right. With the ts-proto migration PR the adr27 module containing the fix got unused, which is a bug. It was fixed with a ts-proto update, which omits all default values.
I’ll publish an update by the end of the day.