Closed schancel closed 3 years ago
Encoding a BigInt in 2s-compliment requires an extra padding byte if the 0x80 bit is set in the first byte position. This commit checks to see if that's the case, and adds the padding to ensure it is parseable.
Hi
Thanks for this, it has triggered a reworking of how BigInt is handled within the api.
It will be pushed shortly.
MW
Encoding a BigInt in 2s-compliment requires an extra padding byte if the 0x80 bit is set in the first byte position. This commit checks to see if that's the case, and adds the padding to ensure it is parseable.