Private key only wallet for Bitcoin Core regtest

Private key only wallet for Bitcoin Core regtest

I'm running a private regtest network on GCP. I generated a list of 2000 vanity testnet addresses ordered sequentially from prefixes mooo1 to n2ooo with their respective pub/priv key pairs, and to prevent complications, I want to only have one private key for each node (change in outgoing transactions are sent to the original address). Because there's no security concern in my setting (it's just a performance test, no money or attacker is involved), I want to make each bitcoind instance only use a single private key for all transactions, and not generate new addresses through an HD wallet. This is because viewing transactions is much more streamlined. I can tell which node is sending bitcoins to which other node, and diagnose issues more easily. Is there an option in bitcoind to only use a single private key?

https://ift.tt/2TGdbHD

Comments

Post a Comment

Popular posts from this blog

bitcoin node: what is the difference between simnet and regtest?

bitcoin node: what is the difference between simnet and regtest? btcd, and presumably other bitcoin node implementations, seem to have 4 network options: mainnet testnet regtest simnet. I get that mainnet and testnet both are "public" in that your node will communicate with other nodes and that both have an existing blockchain and genesis block. However, from what I can tell, both simenet and regtest both create a local only blockchain, and both will create a new genesis block. I this case, what is the difference, and which is better (easier) for developing bitcoin applications? This is what the documentation has to say: --regtest Use the regression test network --simnet Use the simulation test network https://ift.tt/2TAMkwe
Read more

How to check if Electrum is masking my IP with the Tor proxy?

How to check if Electrum is masking my IP with the Tor proxy? When i start Electrum from the command line i see this mensage: (python3:7069): dbind-WARNING **: 14:09:58.452: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken What does it mean? I just installed Electrum following this tutorial: http://docs.electrum.org/en/latest/tor.html I followed the instructions from this topic " Option 2: Multiple servers but Tor Main ". I installed Electrum using the command line on Ubuntu, check the " Installation from Python sources " on this link https://electrum.org/#download if you want to see the codes. And i used this code bellow to download the Signatue keys: $ gpg --keyserver pool.sks-keyservers.net --recv-keys 2BD5824B7F9470E6 I checked the both checkbox: 1)...
Read more

Tor proxy on Electrum, what does Port: 9150 and 9050 mean?

Tor proxy on Electrum, what does Port: 9150 and 9050 mean? The first time that i installed Electrum i navigated to Tools->Network->Proxy i saw there a checkbox "Use Tor proxy on port 9050", i had a problem with my OS so i had to reinstall my OS, Electrum and Tor, and now instead of "port 9050" it's "port 9150". I think that it's because i'm using the Tor Bundle, as said on this electrum docs , downloaded from here: https://www.torproject.org/projects/torbrowser.html.en#linux i want to know what is the difference between the port "9050" and "9150". And if i'm fine using the "9150". https://ift.tt/2T0EvmY
Read more