New answers tagged


OK so this is difficult. First you have to set up your Electrum "config" file (it doesn't have an extension) to make sure you can connect. You cannot use mine because it won't work but this is an example of mine. You have to add in "rpcport": XXXXX, with whatever port you want, make sure not to mess up the "," after each comment or Electrum will overwrite ...


As you were told on bitcoin talk forum you can't import arbitrary private or public keys and create a multisig setup with them using electrum. It only supports using extended private and public keys or seed words for this functionality. If you just want to create a watch only wallet with the address itself then you can do that. Go to file > new/restore, ...


This link was provided concerning this issue on github:


Bitcoin Core does not install libsecp256k1. It is packaged into the binary itself so it is not installed into the system. If libsecp256k1 is not available in your system's package managers (which it probably shouldn't because it isn't officially distributed AFAIK), you can install it from source. The instructions for that are directly in the README.


The locktime value is deliberately set to discourage a subtle attack known as "Fee sniping" and randomly set to an earlier block height to improve privacy (eg for CoinJoin users that need more setup time). This is also done in Bitcoin Core with the nLockTime.


How can i convert this (preferably using bash/Perl/python) into a WIF that can be imported into (preferably) Electrum? OpenSSL .pem files contain base-64 encoding of the values encoded using DER. In case of private keys they use PKCS#8 explained in RFC5208. To extract the key itself, you first have to decode the base-64 string and get the key out by reading ...

Top 50 recent answers are included