News for hackers. Stuff that matters.
Re:The Limits to Blockchain Scalability by noobly on Sunday May 23, 2021 @10:40PM (#27260627)
>I dont care how my coins was moved 10 years ago. The only storage that is relevant for me, now, for value transfer is the current undisputed state

I don't have anything to add, but this has always struck me as inelegant, especially for Ethereum, which is more of a dApp platform. Can someone point me towards something that can run dApps and maintain current state with distributed consensus _without_ a blockchain (or explain why this is an ignorant question)? Also, what's wrong with truncating the chain after X blocks?

Re:The Limits to Blockchain Scalability by dlubarov on Monday May 24, 2021 @01:00AM (#27261199)
> Also, what's wrong with truncating the chain after X blocks?

I would say nothing. Truncating history isn't explicitly built into the protocol, but that's what most users do in practice. I believe Geth and Parity both prune old state by default. There are "achive" nodes that store all history, but they're in the minority.

Bitcoin Core also has options for pruning old state, and for disabling some validation of old history. Though, unfortunately, it will still download blocks from the genesis even if both options are enabled.

Re:The Limits to Blockchain Scalability by dannyw on Monday May 24, 2021 @03:17AM (#27261769)
That's more of a philosophical decision. Even if you don't want old blocks, someone else might want.

As part of your expected obligations of the network, you're asked to seed those blocks.

Re:The Limits to Blockchain Scalability by antender on Monday May 24, 2021 @12:36PM (#27266450)
You mean something like Hyperdrive (formerly Dat) + Beaker browser?