Hacker News Reader

Comment by cocktailpeanuts | Hacker News Reader

it's kind of annoying how people abuse the term "blockchain" nowadays whenever there's something remotely close to distributed systems.

"Distributed Ledger without the Blockchain" is just a distributed database, which has been possible forever. Check out couchdb/pouchdb, etc.

The innovation of Bitcoin's blockchain was that it introduced distributed ledger that didn't require centralized trust. If you take that way, you're just a database no matter how you try to spin it.

This is like saying "We've built orange juice without the orange!" Yeah, you've built bottled water.

View on HN

FaunaDB’s consistency model is very different than CouchDB. (Disclosure, I’m one of the early contributors to CouchDB and work at Fauna.)

More about the FaunaDB consistency model here. https://fauna.com/blog/consistent-transactions-in-a-globally...

Does it matter in the context of this comment thread? I'm sure you guys have built a damn good bottled water, but it ain't orange juice.

Yes. The point of the post is that with global ACID, distributed ledgers among trusted parties are just regular applications. You can’t do this with eventually consistent databases. What I’m describing is a genuine solution our customers are choosing FaunaDB for. For their distributed ledger requirements, a blockchain is overkill.

And the point of the GP was that that does not address the OP point that it is "just a distributed database"

A distributed database with global consistency, which is a new category. FaunaDB (and similar databases) allows a distributed ledger among trusted parties to be “just a database application.”

Great. Just take the word blockchain out of the article, it adds nothing but confusion.

I disagree, with the number of people pushing blockchain when they just want a distributed ledger, an article like this is quite helpful.

So you're telling me... it's a distributed database? Global consistency is nothing new.

How does FaunaDB guarantee that all partitions of a transaction commit or abort? The Calvin paper just says "see here for our distributed pessimistic locks that make this not a problem" but if FaunaDB uses oplocks then that doesn't apply.

In FaunaDB all transaction resolution is deterministic. Once global log order is determined, partitions will wait for the transaction inputs at the correct version and will each independently come up with an identical result.

So the input log isn't partitioned? I'm going off of https://fauna.com/blog/consistent-transactions-in-a-globally... which states

> Each database has a single partitioned RAFT-replicated log that is used to derive a total order of all transaction effects, and that handles all cross-region network communication.

But if each partition knows about all the reads in a transaction and verifies all the timestamps, that sounds workable. Not that I'm in any way qualified to pass judgment on something like this, but I feel like I have a little bit of understanding. Overall it sounds really cool and the idea of agreeing on inputs instead of outputs is tremendously clever.

Admittedly, the specific mechanics of how the log interacts with data partitions was glossed over a bit in that post.

However, to answer your question, the input log is partitioned: Transactions for each epoch are striped across the log partitions. A data partition will need to read a batch from each log partition in order to be able to process the transactions for any given epoch.

And to that sentiment, blockchains are neither new nor interesting. Most developers have been using them daily for close to 7-10 years.

It is unfortunate that this tech is so hyped.

I think this is because people mean different things when they talk about "blockchains".

it is not interesting if we just see it as some glorified chunked linked list using cryptography.

However it IS a novel new piece of technology if we don't define it as that but instead see it for what it actually is. Blockchain is interesting because it uses that chunked linked list data structure to create distributed consensus. So it's unfair to just isolate the data structure on its own and say it's not interesting or novel.

It's only because it used that sort of data structure and applied it to consensus mechanism that it became interesting, and that's what blockchain is. Which is why I think this headline is ridiculous.

> it is not interesting if we just see it as some glorified chunked linked list using cryptography.

See I think the problem here is that people don't realize how many things they use are already blockchains and have been blockchains for years. Git is a blockchain, darcs was a blockchain.

Hell, lots of Wiki implementations are actually secretly blockchains.

What was novel about Satoshi's vision was POW races over the commit rights with enough smarts around how folks would accept blocks. But even then that's a game theoretical way to build the consensus.

The chain itself simply records it.

> What was novel about Satoshi's vision was POW races over the commit rights with enough smarts around how folks would accept blocks. But even then that's a game theoretical way to build the consensus.

Like i said, people think of different things when they say blockchain so I don't blame you or anyone. I'm just pointing out the phenomenon. Even the most passionate cryptocurrency evangelists seem to have different ideas on what they think "blockchain" is when you watch their speeches.

As you pointed out, the PoW approach to commit rights to a canonical ledger that's distributed is what's novel about this. Some people think this "canonical ledger" concept is not part of what blockchain is, some people do. No one is right or wrong because it's just semantics.

When you compare Git to blockchain you are comparing just the data structure aspect, and I'm trying to point out that some people define blockchain as the distributed ledger network itself, which is where the confusion comes from.

> When you compare Git to blockchain you are comparing just the data structure aspect

Not really, though. While the git client chooses not to verify it continuously, github does. This is a very powerful feature of git, the history of code is difficult to alter once held (especially if you use modern variants of git that use a secure hash).

In a very real sense, git is a blockchain and it's strictly incorrect to suggest that you need an unproven POW game theoretic system designed by an anonymous dude with a fake japanese name.

> No one is right or wrong because it's just semantics.

Why is it that people cheerfully offer this when called out on blockchains but think I'm being improper for calling Etherium an obvious ponzi scheme designed to enable a bunch of quasi-legal and obviously scammy ICOs and then not have to issue refunds even as the ICO folks get fined and outlawed?

> some people define blockchain as the distributed ledger network itself

Some people are just using words in a very wrong way. This is technology, not postmodernist social theory. Even if it was postmodernist, the people using these words in this way are just wrong and not speaking to the academic or even industry consensus. "Blockchain" is "web 2.0". It actually meant something specific for a short period and then marketers got ahold of it and it was basically a non-word.

Even as you pointed out, "git" is a decentralized version tracking system, and "github" is a centralized website that hosts it. In this case it's pretty clear where git starts and ends.

however bitcoin blockchain is a data structure AND a network. And the innovative part is that it manages to stay decentralized (unlike github) while keeping a single canonical ledger. This has nothing to do with postmodernist societal theory, it's a fact.

Also I'm not sure if you actually took a look at the code and ran a node and hacked around with a bitcoin wallet, but from my experience there's a lot more to Bitcoin blockchain than your simplified version of what it is.

> In a very real sense, git is a blockchain

Let me bite and go into technical details and argue with you. Even if we're talking on a purely data structure level, git is NOT a "block" chain. There's a clear reason why blockchain had to use the "block" structure to group transactions together instead of chaining them individually.

Thinking git is a blockchain is as ridiculous as saying anything that uses this type of linked list structure is a blockchain.

Finally, let's not bring in these ludicrous ICO stuff into this argument. I am as much of a skeptic as you about these scams, but just because there are many scams out there, doesn't mean that the original technology is not a work of genius.

If you really think it is not, then I recommend you actually reading the white paper, running a node, and looking into the code. I bet you will realize what you've been skeptical about is nothing more than what the ignorant media have been hyping up, but not the actual technology.

p.s.

Note that i'm the GP of this entire thread which you commented to, so I am as cynical as--probably more than yourself--about people using the term for marketing purposes.

> however bitcoin blockchain is a data structure AND a network. And the innovative part is that it manages to stay decentralized (unlike github) while keeping a single canonical ledger. This has nothing to do with postmodernist societal theory, it's a fact.

But it's not true. Neither the blockchain nor the POW hashes assert consensus. What asserts consensus is technically fear of losing money and the desire to make more money. PoW blockchains only work so long as a majority of computing power in the system is not hostile.

Let me reiterate: THE BLOCKCHAIN DOES NOT ASSERT DISTRIBUTED CONSENSUS AND THE POW HASH JUST DEFINES WHO CAN "PLAY" THE MINER GAME AS A SMALLER SUBSET OF INVESTED PEOPLE.

That is fact. This is why distributed system engineers are very eye-rolley about the ide seea that the blockchain has a Byzantine problem solution. It really doesn't, it just bribes them. As long as those bribes work for a majority of the generals, the system moves one step forward.

This is fundamentally different from other algorithms in the space, and does fundamentally different things.

> git is NOT a "block" chain. There's a clear reason why blockchain had to use the "block" structure to group transactions together instead of chaining them individually.

Squashed commits exist, dude. And quite often Bitcoin's chain has short lived forks. Heck, it's even got a long-lived fork.

The folks with merge rights are your miners in this system. You could also make an analgoue to POS chain systems where the stake is not a majority share of currency but some sort of community mandate or grant.

What's funny to me: cryptocurrency is moving away from Bitcoin's model and towards the POS world rapidly. What's more, people are redefining "stake" in exotic and exciting ways besides Victorian-era money worship models.

> Thinking git is a blockchain is as ridiculous as saying anything that uses this type of linked list structure is a blockchain.

A blockchain is just a Merkle Tree. The "genius" you're so lovingly referring to with Bitcoin is the game theoretic part of Bitcoin. The technical parts are ancient.

It's worth noting that there are lots of attacks that would count as Byzantine faults that neither POW nor POS shared consensus models can handle.

> I recommend you actually reading the white paper, running a node, and looking into the code. I bet you will realize what you've been skeptical about is nothing more than what the ignorant media have been hyping up, but not the actual technology.

I've written them. They're the kind of thing I write over a few glasses of whiskey when the family is away. It was boring. They're not hard unless you're writing them in some crazy makework language like C or Go.

The most exciting parts of cryptocurrency are how we start redefining shared value in a way that offers some of the adaptive benefits of capitalist markets while still offering societally confirmed limits.

The thing that really strikes me about your (and so many other people's) misunderstanding of cryptocurrency is that you have conflated the notion of machine consensus with human consensus. At the speed of the current Bitcoin network, machine consensus is an old and solved problem. A boring problem. What the Bitcoin paper is about is a system that builds human consensus. That's a trickier problem.

> But it's not true. Neither the blockchain nor the POW hashes assert consensus. What asserts consensus is technically fear of losing money and the desire to make more money. PoW blockchains only work so long as a majority of computing power in the system is not hostile.

What exactly is 'not true'? Go back and re-read the sentence you said 'that's not true' to. i was talking about the distinction between a data structure and a network. if you think THAT's not true, then explain why blockchain is not a data structure and a network simultaneously, instead of your irrelevant rant about how Bitcoin is not perfect, because I never said bitcoin was perfect either.

> Let me reiterate: THE BLOCKCHAIN DOES NOT ASSERT DISTRIBUTED CONSENSUS AND THE POW HASH JUST DEFINES WHO CAN "PLAY" THE MINER GAME AS A SMALLER SUBSET OF INVESTED PEOPLE.

You can reiterate as much as you want, and no one is stopping you from believing in your definition of blockchain, but remember that you're just rambling on and on about a topic I never was discussing about.

> Squashed commits exist, dude

Do you really think just because you CAN achieve something in a piece of technology, that makes it same as another piece of technology that is specifically designed to work in that manner? By that standard, iPad, iPhone, laptop, smart watch, they're all same thing. They're made up of Cpu and memory and fundamentally same tech if you open them up.

> A blockchain is just a Merkle Tree. The "genius" you're so lovingly referring to with Bitcoin is the game theoretic part of Bitcoin. The technical parts are ancient.

The game-theoretic part is what people are most excited about, and the only proven way so far to make this type of model work is through this specific data structure AND a network called blockchain. PoS, PoW, doesn't matter, the only proven network is Bitcoin so far. There are other newer approaches like 'tangle' from iota, but you'll probably say that's just nothing more than a graph database haha.

To you blockchain may just be that data structure but to me and many other people, it is also the entire network. my only argument was that people can't agree because people have different views on the terminology.

if you want to talk about whether bitcoin's model scales or not, go to twitter, take sides, and find your friends and fight there, there are plenty of trolls there who will be happy to play with you.

> I've written them. They're the kind of thing I write over a few glasses of whiskey when the family is away. It was boring

no you haven't. just listen to yourself, you sound like a guy just out of coding bootcamp who says 'i can easily build a facebook over a weekend'. Anyone can theorize about a concept and anyone can even write a 'facebook' over a weekend. But that's a child's play, what matters is whether you actually create something in the real world that works on a scale. if you just read just another medium blog post about 'how i built a blockchain in 200 lines of code' and did the same thing and think "there! i've built a blockchain, that was nothing!", then i really can't help you there buddy.

> The thing that really strikes me about your (and so many other people's) misunderstanding of cryptocurrency is that you have conflated the notion of machine consensus with human consensus

All i talked about in this thread is that blockchain is a network AND a data structure. Some people like you think it's just the pure data structure part, some people think it's both. no one is right or wrong about that because there's no fixed definition that says which is which, unlike the internet where they have specific terms like 'tcp', 'ip', 'the internet', etc. You can discuss whether that argument is correct or not, but that's not what you've been doing. you're just ranting about Bitcoin itself and i don't really care about that.

Man this must be what talking to a wall must feel like.

> All i talked about in this thread is that blockchain is a network AND a data structure.

Unless you mean by network the game theoretic part of the algorithm, there is no "network".

You keep inventing majesty, magic and mysticism for old tech. I'm done. We won't talk here again.

Feel free to not talk, i don't mind.

> there is no "network".

Yes there is, Bitcoin is a p2p network that maintains the blockchain. without the network you don't have bitcoin.

The only difference is you think the blockchain is separate from the network, whereas my point was there are people who also see them as inseparable. my point was there are two different ways of seeing things, including your view. I didn't even say you were wrong, and i didn't even say the other pov was wright. i was just providing another perspective.

Suit yourself, but it's impossible to have civil conversation when all you get in response is condescension.

But what if bottled water is what people actually want even though they're asking for Brawndo?

Most people in IT already know what distributed databases are. They don't want a distributed database. They want blockchain and nothing else. The only reason they want it is because it's something they don't understand, and they naively hope that it will help them somehow.

But they already understand what a distributed db is and know they don't need it.

Which means people will not suddenly start using FaunaDB just because they try to spin it as an alternative to blockchain. people may not yet have full understanding of the implications of the blockchain but they're not idiots.

You still need to trust the software developers and the miners.

That's not what 'trust' means in the context of cryptocurrencies.

Actually, you don't have to trust all of them. Some miners can go rogue and it won't matter; everything will still work. The software of blockchains is almost always open source, so you don't have to blindly trust it either; reading the source code and checking it for problems it is always an option.

Reply on news.ycombinator.com