Pruning is only for *spent* outputs is it not?
Yes, but if u get rid of transactions of these spent outputs, then u can't check proof-of-work coz it contains ALL data.
Topic: Bootstrapping the pruned blockchain - page 2. (Read 1992 times)
Yes, but if u get rid of transactions of these spent outputs, then u can't check proof-of-work coz it contains ALL data.
Pruning is only for *spent* outputs is it not?
Non-full = have no data about spent outputs.
Maybe I'm wrong and lesser nodes r supposed to load ALL transactions history? Otherwise I see no way to validate outputs.
Maybe I'm wrong and lesser nodes r supposed to load ALL transactions history? Otherwise I see no way to validate outputs.
What do you mean by "non full". Pruning or not makes no difference to the fullness of a node. All the rules are still being checked. Pruning just means you throw away old data that other nodes would need to bootstrap themselves from zero.
In theory as long as someone somewhere is serving a non-pruned copy of the chain, there's no difference to the security of the system even if everyone else prunes. Of course that wouldn't be a very stable situation but I'm using the extreme case as an illustration.
In theory as long as someone somewhere is serving a non-pruned copy of the chain, there's no difference to the security of the system even if everyone else prunes. Of course that wouldn't be a very stable situation but I'm using the extreme case as an illustration.
Imagine that the blockchain is pruned. How a lesser (non-full) node can validate unspent outputs in case when other nodes send contradictory data? Will the merkle root of these data be added into blockchain headers?
Jump to: