Hacker News new | past | comments | ask | show | jobs | submit login

Ensuring the integrity of your distributed application by running the same code on every node in the network is a fundamentally bad idea. It only makes sense in zero trust, monetary applications like Bitcoin and Ethereum itself - or speculative tokens built on top of them.



> It only makes sense in zero trust, monetary applications like Bitcoin and Ethereum itself - or speculative tokens built on top of them.

Which only make sense in a very narrow "technically correct" kind of way. From a larger perspective they still don't make sense. Pissing away small countries worth of electricity to validate an incredibly small number of transactions is a horrible idea.

...And that is just one of the deep, fundamental flaws in blockchain-based currency.


The duplicated code can be as simple as a few cryptographic operations for each broadcasted transaction. This can easily scale to tens of thousands of nodes and transactions per hour without requiring significant computing resources over the baseline of running a high bandwidth internet node.

When the consistency algorithm is proof of work chains, or when the proof of work is used to control the scarcity and disbursement of the valuable token, only then you have the whole "world turning into fucking Mordor" problem.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: