wrr,no such thing as know timex whyx want usex intersfunxlaux or havx or nerxxxxx, praisx, notanswerablx soundx care decidx tricx etc, learnx, use etc some tech s ok, not nerx
Is it possible to estimate how much disk space should be reserved for a full bitcoin node that is going to be started in pruning mode since his first run? (assume -prune=550)... The final result should be that it needs just 550 mb for blocks content storage... during IBD all blocks are going to be downloaded, and transactions inside each block will be validated... BUT: all blocks are going to be stored together on disk? or each one will be validated and then discarted releasing space for next blokc??... after one single block has been validated, and the UTXOs has been updated for that block transactions, I undertand we can download the next block and remove previous block contet from disk... I've noted that bitcoin node consumes more than 100 gb when started in pruning mode, so I gess that actually it is storing all blocks together, I also assume that after sync process it'll discard blocks up to just prunning target (550 mb in this case).... FINALLY: if pruning mode is supposed to be an alternative to run a full node (minus rescan functionality) in hardware restricted environments, shouldn't the sync process optimese disk usage discarting blocks "on-the-fly"?
58:18 But you have to store all the block data in case of a fork right? I mean all the blocks since the fork started till it resolves so you keep your UTXO set updated and right. Some orphan blocks may be created after fork resolves. Am I right?
Yeah but since he's here lecturing and not living off of his profits, I'm sure he's probably sold quite a bit. Early birds tend to either sell early or never sell at all. No in-between.
