What's the difference/benefits from, for example, having a feed to stream pgp signed data where signature is for the current and previous message for example?
You just described a blockchain/DLT...
Daisy: A private blockchain where blocks are SQLite databases, in Go
21–30 of 31 posts
Re: Daisy: A private blockchain where blocks are SQLite databases, in Go
#22What's the point of using a blockchain in this way? Bitcoin's blockchain is necessary because newer blocks need to inherit the proof-of-work done on previous blocks, since the correct chain will be the one with the most cumulative work in it (presuming it's also valid). So it needs to be a sequential list of blocks, where each new block references the previous one. But I can't see why this is useful when a) proof-of-…
You could probably probably get away with putting a single sqlite database on IPFS and using IPNS to point to the latest version and achieve the same thing. IFPS' block level deduplication means you'd only have to download the changes if the database receives a new update. I'd like to see a decentralised database that doesn't require downloading the entire dataset. It should be possible to implement index-only querie…
Something like https://github.com/lmatteis/torrent-net ?
Re: Daisy: A private blockchain where blocks are SQLite databases, in Go
#23I feel like people are actively trying to mash up technologies just because. No real benefit, just toy projects.
Re: Daisy: A private blockchain where blocks are SQLite databases, in Go
#24I feel like people are actively trying to mash up technologies just because. No real benefit, just toy projects.
So? Just for fun is not allowed anymore?
Re: Daisy: A private blockchain where blocks are SQLite databases, in Go
#25Re: Daisy: A private blockchain where blocks are SQLite databases, in Go
#26Earlier quoted context omitted.
So? Just for fun is not allowed anymore?
¯\_(ツ)_/¯ idk I'd rather it be on Show HN than front page.
It was on posted as Show HN six days ago but didn't generate any discussion: https://news.ycombinator.com/item?id=14512531
Re: Daisy: A private blockchain where blocks are SQLite databases, in Go
#27What's the point of using a blockchain in this way? Bitcoin's blockchain is necessary because newer blocks need to inherit the proof-of-work done on previous blocks, since the correct chain will be the one with the most cumulative work in it (presuming it's also valid). So it needs to be a sequential list of blocks, where each new block references the previous one. But I can't see why this is useful when a) proof-of-…
I was thinking the same but you were able to articulate it much better!
This is interesting enough for me to dig into and read the code, but what am I going to use this for? Now if transactions were blocks in a single database I could see more use for this.
Maybe it's too early and too little coffee for me to have a brilliant thought!
Re: Daisy: A private blockchain where blocks are SQLite databases, in Go
#28From what I read, any holder of a private key that is accepted as authoritative can add data to the chain at will and without restriction. The consensus algorithm would then allow that user to rewrite the entirety of the blockchain at will from the point their key was trusted forward by simply creating a longer chain at no cost. What am I missing?
> What am I missing?
You're not missing anything, in my opinion.
Private blockchains make little sense, and the standard rebuttal of this simply lists a large number of "potential applications", without going into detail on any of them and explaining how a private blockchain solves that specific problem.
Re: Daisy: A private blockchain where blocks are SQLite databases, in Go
#29What's the point of using a blockchain in this way? Bitcoin's blockchain is necessary because newer blocks need to inherit the proof-of-work done on previous blocks, since the correct chain will be the one with the most cumulative work in it (presuming it's also valid). So it needs to be a sequential list of blocks, where each new block references the previous one. But I can't see why this is useful when a) proof-of-…
I was thinking the same but you were able to articulate it much better! This is interesting enough for me to dig into and read the code, but what am I going to use this for? Now if transactions were blocks in a single database I could see more use for this. Maybe it's too early and too little coffee for me to have a brilliant thought!
Shameless plug: I've tried to articulate what Bitcoin is, and hence why the blockchain data structure was invented, in this article (hint: it's all related to proof-of-work)[1].
I think a lot of people see that 1) Bitcoin uses a blockchain and 2) Bitcoin creates digital money seemingly out of nowhere, and feel fascinated with the technology without being able to explain exactly why. So we're left with a lot of people using blockchains without really understanding the reasoning behind it.
Re: Daisy: A private blockchain where blocks are SQLite databases, in Go
#30Thinking twice about it, there is something exciting here about the concept. Of all databases, sqlite has this special interest : it's the perfect tool to be embedded as local database in clients. Now, if we consider that blockchain is a new p2p effort to build decentralized softwares, putting sqlite on a blockchain makes a lot of sense : this is a mean to distribute data for decentralized apps. It also makes sense i…
See https://github.com/pixelspark/catena - does exactly this.