Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I did not say public. Private blockchains are a thing. And it's not just an internal database. They are forkable and potentially run by the customer themselves or in their own AWS private cloud or wherever. But by following the protocol, they could easily switch providers, or integrate several clients that provide different features around the same data. The customer can truly own their data and the side chain can interact with the main chain where it makes sense.

Lots of technical problems there, that's why I say it's a ways off. But it's all doable.



Why would a customer fork their own blockchain?

If it’s not public what’s the point of using a blockchain? How is it not just a secured database?

Databases can be moved between providers. You can choose where/how to interact with them.


> But by following the protocol, they could easily switch providers, or integrate several clients that provide different features around the same data.

What you're suggesting is solvable by an open data standard and export/import features on software. A blockchain provides none of those by virtue of being a blockchain.




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

Search: