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

If it's private, it isn't auditable. You can keep a journal of all transactions, and when you decide that history needs to be changed, you make the change in your journal and roll it forward from there. If the auditors have half a clue, you can't do this for events that happened before the most recent previous audit, but if they have a whole clue, they won't accept the current state of your system as anything more accurate than your attestation.

The counterargument to "words mean what people agree they mean" is that "to computers, instructions mean what they have already been defined to mean". If you change Python's meanings, you need to tell everybody that you're using Python 3.5-Joe, not Python 3.5.

>If it's private, it isn't auditable

Clearly true, but in this field "private" is really being used to denote "not a Public Blockchain like Bitcoin and Ethereum".

It doesn't mean "actually private". It means "we built our own rather than pay to use Ethereum".

No, because that would be another public blockchain.

Private really means what you think it is "a blockchain that only a small selected group can access". A lot of "Private blockchains" are just Ethereum-nodes running behind a firewall and with a secret genesis-block.

It does not, however, mean that it cannot be peer-reviewed. Allthough that still leaves the problem of not knowing if what you've reviewed is what is running.

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