Post

@BTCBreadMan BTC’ers have 2 choices:
1. Node centralization.
2. Lack of fee paying tx’s that secure the network.
Both are not great for the network.
The solution is to scale the base layer (block speed) and not forcing full nodes to hold the entire tx history.
UTXO sets are all it needs.
English

@KasGobbler Full nodes are not forced to hold the entire tx history.
They are required to initially download it to validate the chain, and then they can optionally prune it down dramatically. To 10gb, 2gb, etc.
At which point they remain a fully validating node.
English

@BTCBreadMan @KasGobbler Pruned nodes are not as useful as full-nodes though.
You need full nodes with the entire transaction history in order for new nodes to download the entire chain.
If everyone ran pruned nodes, the network would die.
English

@BitcoinIsaiah @KasGobbler Correct. But I currently don’t see any reason why everyone, or even most people, would prune their node.
I just wanted to make sure the Kaspa fella knew it was possible.
English

@BTCBreadMan @BitcoinIsaiah @KasGobbler This is a fallacy that you guys need to correct, just to not seem dumb in scientific conversations.
And btw you can ask your AI how it works in simple terms.
x.com/coderofstuff_/…
coderofstuff@coderofstuff_
1/ Overview of Kaspa’s IBD: 1. What nodes do at the very beginning of a sync is to download a pruning proof (to verify the current pruning point [PP] is legitimate and ties all the way back to genesis - this is proven cryptographically and validated by the node. See MLS) …
English

@simogattok @BTCBreadMan @BitcoinIsaiah @KasGobbler btc doesn’t have utxo commitments which is why this same process as done in kas won’t work there.
English