Hacker News new | ask | show | jobs
by rapsey 3090 days ago
> This seems like a glorified eventually consistent database synchronization algorithm.

It is a form of eventually consistent databases. One that also solves the problem of nefarious actors trying to cheat.

1 comments

It's more like a tsunami of Running Balances vying for event horizon. I'm not sure how this is ever supposed to be "consistent" unless you're talking about full historical nodes, in which case yes definitely, but non historical nodes are able to prune transactions after a while. Still a lot to dig out of this gem of a paper, any error in interpretation is my own.
You are using the wrong unit. In a database a unit is a key. In a blockchain a unit is an address. It is entirely consistent from this point of view.