Daisy: A private blockchain where blocks are SQLite databases, in Go

Re:Daisy: A private blockchain where blocks are SQLite datab... by oelmekki on Wednesday June 14, 2017 @02:51AM (#14551067)

There is something I don't get about the databases distributed : they are read/write, and their data is not part of what is distributed in p2p, is that right? It seems to be what means "Block payloads are SQLite database files. Except for special metadata tables, their content is not enforced".

If that's so, what is the purpose of distributing blank sqlite databases (with exception of blockchain keys metadata)? Also, how is it p2p distributed if several users may have the sqlite databases in different state (and thus, different sqlite files)?

[ Parent | on HN ]

Re:Daisy: A private blockchain where blocks are SQLite datab... by rnabel on Wednesday June 14, 2017 @06:41AM (#14551813)

The way that I understand it, the SQL databases are not empty and the mining process, if similar to standard blockchains, will mean that the block's hash has to be of a specific format. Thus data can be distributed, e.g. academic articles, which are safe from changes, as the hash is fixed.

I'm guessing that SQL databases were chosen to enable easy queries of structured data...

[ Parent | on HN ]

Re:Daisy: A private blockchain where blocks are SQLite datab... by gricardo99 on Wednesday June 14, 2017 @02:59AM (#14551105)

My understanding is the data is distributed, the metadata tables are enforced by the blockchain protocol, but the contents are free to be whatever the writer wants to put in the database. Once it's written, the metadata/protocol enforces the integrity of the data on the blockchain.

[ Parent | on HN ]

Re:Daisy: A private blockchain where blocks are SQLite datab... by oelmekki on Wednesday June 14, 2017 @03:02AM (#14551118)

Indeed, it would make sense. "Content is not enforced" would mean "content data structure is up to block creator". Thanks!

[ Parent | on HN ]