@holger80 update on the matter, after installing the secp256k1 bindings, it also triggers an error, meaning the recorvery parameter parsing is being incorrect there, I guess is related to the bit split, I'll return when I get more details.
Thanks!
You are viewing a single comment's thread from:
So, steem-js does loop through all possibilities instead of trying to guess the recovery param, (it actually try all values AFAIK)
I added the new error message, when secp256k1 is installed.
The recorvery parameter parsing could be the cause, good thinking.
Yes. the discoveral of the recovery param is leading to a negative number when using your provided transaction id. I'll keep debbuging here.