into a whole binary number that will be converted into its hexadecimal value, and apply bx base58check-encode to this value to get back your WIF key.
library mentioned is little-endian (hardcoded). so he needs not a number .
Can't still find the cause of my
What are you talking about precisely? Could you use a translator please, it's not the first time you talk to me about this function and last time you were already
wrong despite your rude words
.
This is the result I get on my computer, is it wrong? It's the same one as JohanM
above for the
base58check to hexadecimal conversion and the same I get with this
online tool.
And ofc the
base58check-encode command give back the right WIF key from this value, as expected.
>bx base58check-decode 5JphUWRuWJwZktUdGBUmtsazoc1GGuRXFBxoTkJWZGpXjUzXXa7
wrapper
{
checksum 1484882920
payload 84a1a9c49c1257de2d4ff2eec4f6cf109e6be3df6e075efb9ad895efeab20201
version 128
}
>bx base58check-encode -v128 84a1a9c49c1257de2d4ff2eec4f6cf109e6be3df6e075efb9ad895efeab20201
5JphUWRuWJwZktUdGBUmtsazoc1GGuRXFBxoTkJWZGpXjUzXXa7