3 ms·
That's an excellent flowchart. BTW, there is a real example of meaningful blockchain use for auditing single source data (the "caveat" in the flowchart). It's t
by dandanua 4y ago
That's an excellent flowchart. BTW, there is a real example of meaningful blockchain use for auditing single source data (the "caveat" in the flowchart). It's the hypercore protocol https://hypercore-protocol.org/ https://hypercore-protocol.org/
- BenoitP 4y agoThat's very interesting. Would you mind coming up with a concrete and detailed business case? In this example you will provide, who are the entities with write access? How do they have a hard time deciding who should be control of the data store?
- dandanua 4y agoIn the hypercore protocol participants control only their own data. So, no write conflicts. But they need to verify parts of data of other participants. The blockchain (specifically, the Merkle tree) helps with that. An alternative solution would be to just sign the pairs `(recordCounter, recordData)` instead of putting records in a tree and signing the root node. But the hash tree also helps to verify integrity, in addition to authenticity.
- BenoitP 4y agoYou didn't answer my question. Let's stay strictly on topic here if you would mind. We don't want to waste resources exploring a dead-end. So, what's the business case? Would you mind coming up with a concrete and detailed business case? In this example you will provide, who are the business entities with write access? What's their context? What are their interests? How do they have a hard time deciding who should be control of the data store?