3 ms·
Yes, so what this does is timestamp transactions (in this case SQL DML) in a decentralized way between nodes that do not or cannot trust each other. All this wh
by misterdata 9y ago
Yes, so what this does is timestamp transactions (in this case SQL DML) in a decentralized way between nodes that do not or cannot trust each other. All this while enforcing write permissions ('grants') that were agreed upon earlier.
The idea that some of these transactions store data is not any different from the idea that some transactions in Bitcoin add new coins to the system, or that some transactions in Ethereum create and store contracts (which are code and data).
Now of course you could, instead of storing the actual data and/or SQL, put data in a DHT and reference and timestamp that.
- dozzie 9y ago> Yes, so what this does is timestamp transactions (in this case SQL DML) in a decentralized way between nodes that do not or cannot trust each other. All this while enforcing write permissions ('grants') that were agreed upon earlier. And this should be the very first thing to put in README. This is the single most important thing about any program that uses a blockchain protocol: what exactly is the decentralized, adversity-proof timestamping used for. Right after that should be placed rationale, i.e. how does the hostility resistance help compared to cooperation-based protocols.
- GhostVII 9y agoWhy would that need to be in the README? Isn't it the whole point of blockchain?
- dozzie 9y ago> Isn't it the whole point of blockchain? What "it"? Your question does not match anything I said.
- misterdata 9y agoI think it is actually a good idea to describe the whole point of using a blockchain as suggested. A lot of organisations I encounter don't really have a clue and do not realize that even a traditional database could fill their need perfectly in many cases.