New answers tagged

4

CAmount is used for multiple purposes in Bitcoin Core, not just in transaction validation logic. It is also used to represent the net effect transactions have on wallet balance, for example, and that net effect is negative as often as it is positive.


3

This is unrelated to taproot. The "addresses" field in Bitcoin Core's RPC output was historical legacy that was at best outdated, and at worst confusing. Since 22.0 the field has been deprecated entirely, for all types of transaction outputs. It can (temporarily) be re-enabled using -deprecatedrpc=addresses, but in 23.0 it will be gone entirely. My ...


1

Of course Taproot isn't activated at all so all nodes would have treated my transaction as an anyone-can-spend and my transaction would easily have made it into a block. No, the new output types for soft forks are constructed in a manner that they are non-standard for old nodes and thus do not get included in the mempool by old nodes, and therefore also not ...


1

I will add an answer to this post chainstate: Container the information about the UTXO and this is by default indexed in a level db. blocks: Contains all the data related to the blockchain, so you can build your own chain state with just scan this file (blkXXXX.dat) one by one


3

This was answered on Twitter by various individuals. You should remove the directory /tmp/test_common_Bitcoin Core regularly. For Martin Leitner-Ankerl this was 6GB of leftover files (leftovers only happen when tests fail or are canceled). theStack also recommends running rm -rf /tmp/bitcoin_func_test_* every now and then. The /tmp directory is usually only ...


Top 50 recent answers are included