Daisy: A private blockchain where blocks are SQLite databases, in Go
1–10 of 31 posts
Re: Daisy: A private blockchain where blocks are SQLite databases, in Go
#2This looks interesting, but I feel like it's conflating two equally interesting ideas, "what if only certain nodes could make new blocks" and "what if the blocks had some kind of structured data".
I think moving those into two separate but compatible projects might help both of them take off.
Re: Daisy: A private blockchain where blocks are SQLite databases, in Go
#3This looks interesting, but I feel like it's conflating two equally interesting ideas, "what if only certain nodes could make new blocks" and "what if the blocks had some kind of structured data". I think moving those into two separate but compatible projects might help both of them take off.
Private versions of Ethereum do both things; JP Morgan is leading the charge on this with their Quorum software. But it's object-structured data instead of SQL.
Re: Daisy: A private blockchain where blocks are SQLite databases, in Go
#4Everything abut this feels like the most terrible idea ever, but in such a fascinating way. It's beautiful.
Re: Daisy: A private blockchain where blocks are SQLite databases, in Go
#5If a blockchain is a public ledger, what is a private blockchain?
Re: Daisy: A private blockchain where blocks are SQLite databases, in Go
#6Why store a database file in each block when you could also store transactions? This is what Catena does: https://news.ycombinator.com/item?id=14548174. Also allows for some interesting things you can do with privileges, for instance.
Re: Daisy: A private blockchain where blocks are SQLite databases, in Go
#7There 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)?
Re: Daisy: A private blockchain where blocks are SQLite databases, in Go
#8If a blockchain is a public ledger, what is a private blockchain?
A blockchain is a distributed ledger, not necessarily public, although bitcoin, being the most famous, is public.
In this implementation it seems anyone can read the blockchain, but writing to it is permissioned/controlled.
Re: Daisy: A private blockchain where blocks are SQLite databases, in Go
#9There 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,…
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.
Re: Daisy: A private blockchain where blocks are SQLite databases, in Go
#10There 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,…
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.
Indeed, it would make sense. "Content is not enforced" would mean "content data structure is up to block creator". Thanks!