Importing a 256-bit random number as the private key?

[PorkyP]

I would prefer to generate my own random numbers (von Neumann coin flip "algorithm").  Because I have never yet managed to figure out how to convert a 32-byte hexadecimal number to WIF, I'd prefer to just enter them in hex number format.

Is there any way to do this?  I've tried digging through the source code to use the internal functions to generate the WIF, but haven't found the way to do it correctly.  Anyone know which function calls to use with a plain 256-bit random number to get the WIF?

Exporting a wallet in plaintext likewise doesn't really work because the keys are 33 hex bytes long -- there appears to be either a checksum or something else appended or added to them.  When I overwrite one of these hex numbers with my own hex private key, leaving either the front byte in place, and then reload the wallet, I get an error, which is why I think there must be a checksum.  The front byte is always 02 or 03, and I've tried both, and still get errors either way.

I've tried asking this on the Reddit forum and whoever moderates it just deletes my posts, so I figured I'd try here.

[ertil]

The front byte is always 02 or 03, and I've tried both, and still get errors either way.

If you don't know the difference between the private, and the public key, then you probably shouldn't process real coins with your tools. Try test networks like regtest first.

how to convert a 32-byte hexadecimal number to WIF

https://en.bitcoin.it/wiki/Wallet_import_format

I'd prefer to just enter them in hex number format.

Using WIF is optional. If you don't like it, then you don't have to use it. WIF is just some hex chars, after base58 encoding, nothing more. If you prefer base16 over base58, then you can work with base16 WIFs, and get pretty much the same results.

For example:

Code:

base16: ef00000000000000000000000000000000000000000000000000000000000000010184e38d1f
base58: cMahea7zqjxrtgAbB7LSGbcQUr1uX1ojuat9jZodMN87JcbXMTcA

If you don't want to use base58, then just stick with base16, it is just one encoding away from what is used by many other tools.

Some base58 tools: https://learnmeabitcoin.com/technical/keys/base58/

[nc50lc]

Is there any way to do this?  I've tried digging through the source code to use the internal functions to generate the WIF, but haven't found the way to do it correctly.
Anyone know which function calls to use with a plain 256-bit random number to get the WIF?

This "serialize_privkey" internal function should work: github.com/spesmilo/electrum/blob/master/electrum/bitcoin.py#L620

For example, replace "0000000000000000000000000000000000000000000000000000000000000002" with your HEX private key:

Code:

bitcoin.serialize_privkey(bytes.fromhex("0000000000000000000000000000000000000000000000000000000000000002"),"true","banana")

You can replace "true" compressed bool with a blank "" if you want to derive a WIF without the compressed flag byte.
And the last positional arg is just the prefix shown when exporting a private key so it will be displayed in front of the encoded WIF like in the example below,
Use the standard prefixes (e.g.: p2pkh) if you just want to copy-paste it to import.
Result of the example command:

Code:

'banana:cMahea7zqjxrtgAbB7LSGbcQUr1uX1ojuat9jZodMN87K7XCyj5v'

Exporting a wallet in plaintext likewise doesn't really work because the keys are 33 hex bytes long -- there appears to be either a checksum or something else appended or added to them.  When I overwrite one of these hex numbers with my own hex private key, leaving either the front byte in place, and then reload the wallet, I get an error, which is why I think there must be a checksum.  The front byte is always 02 or 03, and I've tried both, and still get errors either way.

Those exported keys are most likely "public keys" based from your description.

[Abdussamad]

true shouldn't be in quotes. It's a boolean argument not a string. It should be just True or False.

[nc50lc]

true shouldn't be in quotes. It's a boolean argument not a string. It should be just True or False.

Oh, right, thanks!
I was also playing with "banana" arg there as it seem to accept any quoted string as True and blank as False.

Anyways, the command works but if @PorkyP wants to properly set the args, use True or False for the compressed flag.