There are some Proof-Of-Work chains the place pruning is default on their nodes, i.e. the community doesn’t depend on full unpruned nodes in any respect:
Because of the pruning mechanism, Kaspa nodes solely wants ~3 days of prior historical past to be saved by every decentralized machine.
1. Do Kaspa depend on extra assumptions that Bitcoin don’t depend on to ensure that such prunning to work?
2. How do Kaspa nodes assemble their utxo set in such circumstances?
Who’s to confirm the signature
Lets think about that a while sooner or later because of some purpose (be it excessive price of storage or because of protest towards on-chain inscriptions) all people node on a Bitcoin community is a pruned node. In that circumstances and inside present Bitcoin protocol:
3. Wouldn’t it be doable to begin a brand new node from scratch. Wouldn’t it doable to confirm a the final 550 mb of blocks with out having a reference to even one full, archival node.
4. With a node that was simply began from scratch, wouldn’t it be doable for such a node to assemble the UTXO set during which there can be some utxos that have been created under the blockheight of the chop off level. So far as I do know, the utxo set is constructed by every node based mostly on the information within the blocks (and never synced with different nodes as it’s the case with blocks) – appropriate me if I’m mistaken.
