If you use "1", then it is invalid choice, because block hashes have 256 bits. Use "0", don't use it at all, or put the block hash you want. But don't use "1".
Well I have been running with assumevalid=1, so this meant basically it has been 0?
Is there a way to know if assumevalid is enabled in the console command? getblockchaininfo doesn't show it.
Of course. But more than that: if you have a full node executable, with the GUI, then you can also get it, just by adding "--help".
Using "--help" on GUI console command returns this: "Method not found (code -32601)"
Because it is manually updated every sometimes. There is no rule, when it should be updated. You can replace it with your own block, mined a day ago, if you want to.
Is there a way to quickly find the blockhash that corresponds to 6 months ago? on mempool.space you can only search by hash or by block height number but not by date I think.
Things are removed automatically, as they are checked and downloaded. But: the size of the chain is not all: there is also the size of the UTXO database, and it can take potentially unlimited space, because the number of UTXOs is not restricted by consensus rules. Usually it won't take more than a few GBs, but still: it could grow in the future.
With prune=1000 testnet3 has taken like 12GB at 50%. Geez. I guess assumevalid is really not enabled. Im 1 year and 9 weeks behind. So if I could find a way to know the blockhash for a reasonable time, like 6 months ago, I could skip 6 months of validations. But I don't want to manually try to find it in mempool.space, there has to be a more efficient way to search by date.
Im not logged right now into my node computer but I think on the bins folder there was a bitcoin-test or something like that executable which I assume launches Knots in testnet mode. My question is, does it use testnet3 or testnet4 by default?
For clarification, that "
test_bitcoin" executable in bin/daemon directory isn't for launching the node in testnet3 nor testnet4.
That's for unit test purposes.
You must run bitcoind or bitcoin-qt with
--testnet (
testnet3) or
--testnet4 arg to launch it in testnet.
If you're also talking about the shortcut in Windows when you used the installer (
set-up) version,
It's in testnet3 since the shortcut has
--testnet arg when you check its parameters.
Yeah, I realized that isn't it. And no im Linux. By shortcut I meant desktop files. I realized it's better than using the .conf file. You do not want to use the .conf file for anything that has to do with blockchain size (prune, assumevalid) because if you accidentally launch mainnet with prune (you may use prune for testnet) then you screwed up your mainnet files. So better leave bitcoin.conf for performance settings that are shared in mainnet and testnet, like dbcache.