Search Results

It's describing how much of the allocated UTXO cache you are using. You can adjust how much maximum memory Bitcoin Core uses for this and others with the dbcache parameter, the higher the limit in meg …

When enabling or disabling txindex the blocks you already have are used, they are not re-downloaded. There is no shortcut, once you start you have to wait for it to finish. The process of re-indexing …

To operate, Bitcoin Core needs to: make DNS queries to a number of public domains in order to find peers to connect to, a full list of these is in chainparams.cpp make arbitrary outgoing connections …

but how? bitcoin is hard to mine, how can this method mine nblocks immediately? generate is only used on the regtest network, where blocks can be mined instantly.

You need to run your node with txindex=1 in the configuration in order to create one, and changing the option on an existing node requires you do do a bitcoind -reindex. …

No. OP_CHECKMULTISIG only supports multiple pubkey not pubkeyhash (addresses).

Large wallets take significantly longer to initialize and eventually bog down the client to the point of making it completely unusable (calls that attempt to sort usable outputs to spend for example g …

1, 2 and 3. Transactions that arrive through inventory announcements on the network are validated completely by checking the form of the transaction for sanity, executing the script, checking signat …

It's at best irrelevant to the search, cranking up the re-key interval too high will end up reducing your performance rather than increasing it. There would really be no problem choosing a single seed …

bitcoin-cli getinfo will show the number of connections. bitcoin-cli getpeerinfo will give information about individual connections.

The wallet contains a lot of metadata, and is actually a database rather than a flat file. At a minimum it contains a record of where you were last synced to in the chain, allowing any node that loads …

As a participant in the peer to peer network, it is impossible for you to know that the state and timing you are seeing are consistent with what other people are seeing. You can't ask other participan …

There’s no way of easily disabling obfuscation, but you could build a version that sets the keys to zero, resulting in no change when the XOR is used. Generally it has no impact on anything, so it’s l …

Many commands block the daemon from responding to requests, and during startup you'll not get responses while the node is initializing.

This is a known crasher in 0.17. You need to either: downgrade to 0.16.3 apply the patch given in the pull request and build Bitcoin Core yourself wait until 0.17.1 is released to fix the issue. …