Hot answers tagged

6

The transaction index exists because it is leftover from how Bitcoin Core used to work for validating new blocks and transactions. Prior to 0.8.0, Bitcoin Core maintained the transaction index, and when validating transactions, would look up outputs by going into the transaction index, finding the transaction being spent, then finding its output. The ...


3

Changing the txindex setting no longer requires a reindex since version 0.17.0 (see https://bitcoincore.org/en/releases/0.17.0/, under "Transaction index changes). It'll update just the txindex itself whenever it's out of sync automatically. So: It doesn't inject a reindex (which would cause throwing away the entire chainstate database, and rebuilding ...


3

The block filter index is build asynchronously from block downloading and validation. It is possible that the thread handing block storage and pruning could be enough ahead of the thread building the block filter index that it starts to delete blocks before the index thread processes them. This would be bad. So for the initial block filter index ...


3

27GB as of 2020-06-14 You yourself can check this via going to .bitcoin/blocks/index folder. Where .bitcoin folder is usually hidden folder on home when using linux. It depends if you have pruned than the index folder might appear less in size. As of today my index folder is 105.4 MB since I've prune=1000 and it would remain the same in future as well. ...


3

There’s functionally no distinction between an output which doesn’t exist, and one which hasn’t existed from the perspective of validation. The node never needs to consider this so by default it stores no information about it.


3

If you have turned off -txindex (which should have happened when you enabled pruning), then you can just delete the the indexes/txindex folder as it isn't being used.


2

You can enable the txindex by either adding it to your bitcoin.conf file: txindex=1 or You can run bitcoind with the -txindex flag: $ bitcoind -txindex See: $ bitcoind --help -txindex Maintain a full transaction index, used by the getrawtransaction rpc call (default: 0)


1

Where are watch-only addresses stored and how does my node keep index of their balances / utxos? Usually the software creates a wallet file just like any other and stores information in that, except the wallet file will be missing private key information. If I want to backup and boot a new instance of my node will it retain the indexes associated with my ...


1

You're trying to use an optional feature of Bitcoin Core: the ability to query for old transactions. This functionality needs: (a) the full blockchain (where else would it get the transaction from) (b) an index by txid so it doesn't need to read through 270 GB to find what you're looking for. The error message you get is telling you that this (b) index is ...


1

The commands you have used are not for syncing to the bitcoin blockchain but to install a bitcoin, now with this client you can sync if you want, you will need days or weeks depending on your computer bandwidth and performance and 250+ giga of hard drive, you can start syncing by locating your bitcoin directoryand simply running: ./bitcoind You can find ...


1

use txindex = 1 in you bitcoin.conf file and restart daemon with -reindex flag if you are building it for the first time, it might take a while but after txindex is defined you can get data for any transaction in blockchain no matter if its related to your wallet or not. Alternetivly you can start your daemon with bitcoind -daemon -txindex=1 -...


1

You can check the debug logs (might require -debug flag) and see if it is indexing transactions: $ tail -f ~/.bitcoin/debug.log You can also try to get a transaction by txid, and if it returns transaction data, then the blockchain has been indexed for transactions (might have to wait for sync to complete): $ bitcoin-cli getrawtransaction {txid}


Only top voted, non community-wiki answers of a minimum length are eligible