You are viewing a single comment's thread from:

RE: The Blockchain Just Became 😨 Obsolete 😨, the Future is Hashgraph... or NOT?! 😎

in #steemit7 years ago (edited)

Hashgraph is simply a more efficient algorithm and data structure than blockchain and therefore it should be pretty obvious that it can't replace all the other code built into Graphene that has way more to do than just the execution and storage of the blockchain. You could however swap out the blockchain if Graphene was developed modularly and use Hashgraph as the algorithm and data structure at the foundation.

DAGs (Directed Acyclic Graphs) are not Hashgraph. Sure, there are a lot of supposed comparisons because these other DAGS (IOTA, ByteBall, RaiBlocks, etc.) don't use a blockchain, but that's pretty much where the comparison's stop. You are mixing apples with oranges here.

IOTA performance is known to be crap. Loads of users have already complained of this. So explaining that IOTA is basically applying Hashgraph with nodes is completely wrong. Comparing any other the DAGs as Hashgraph is wrong too. Hashgraph is not the same and currently is only implemented in Swirlds and nowhere else.

If you really want to understand Hashgraph then you should read my summary and have a listen to Leemon Baird's videos and discussions here. Leemon developed Hashgraph and he makes abundantly clear other DAGs are NOT Hashgraph. You are working off secondhand information and misinformation without understanding the fundamentals of what Hashgraph really is. If you want to understand what it is then you need to first have a serious listen to its creator, who is one of the smartest computer scientists out there.

Sort:  

Hashgraph is not the same and currently is only implemented in Swirlds and nowhere else.

I'd also be interested in your perspectives vis-a-vis what I further commented to @nutela on his comment above as well:

So at this point all that is available for Swirlds is a closed-source library, and I've gotta contact their sales department if I want to deploy my application?! Not to mention, of course, that Swirlds even has multiple patents on the future of the "free and open" blockchain killer, which of course is their private solution, wait for it... Hashgraph!

Swirlds is not Hashgraph. Swirlds is a solution built on top of Hashgraph so no surprise if they don't open source their code. Big deal. I sounds like you are still in the mindset that Hashgraph is a full-fledged solution. Hashgraph is a patented algorithm that can be used as the basis for a lot of different types of solutions - Swirlds is just one of these solutions.

The simple takeaway is that Leemon and company want to make money off of their investment in solving a serious computer science performance challenge. They therefore don't want to give away their exact code to others, but they certainly have in any case revealed how it is working to a large degree already. I don't think this is a crazy thing for them to do. They can then license it to various crypto developers for a portion of their profits. I've seen here for example that Lykke is planning on using Hashgraph

Hashgraph is a patented algorithm that can be used as the basis for a lot of different types of solutions - Swirlds is just one of these solutions.

respectfully, it sounds like you've bought hook, line, and sinker into their "kewl-aid". I understand that hashgraph is just a "consensus algorithm", but the fascinating thing to me, is that everything you say I don't seem to understand, pretty much comes directly from Leemon Baird himself! Furthermore, there isn't even a working model in active production that can verify any of the claims that made. Even if it works, what makes you so confident that this patented algorithm will be any better or faster than any of already proven complete solutions using alternative consensus mechanisms already available today (such as DPOS or even Ripple) for similar usage cases?

And perhaps gun.js is another option as well. GUN is a real-time, distributed, offline-first, graph database engine, doing 20M+ ops/sec in just ~9KB gzipped, and open-source! Of course, it too comes with its own set of constraints and limitations.

From swirlds (his own company which he is also chief marketer and promoter):

A tech report is available, which is a white paper describing the hashgraph, the consensus algorithm, and the mathematical proofs of Byzantine fault tolerance. A second tech report goes through examples illustrating each step of the consensus algorithm.

And as we already know from IPFS, relying on "peers" isn't generally the best way to go for assuring network stability and fast consensus. And gossip circles themselves take time to propagate throughout the whole system too. For example, what if on STEEMIT, it took several minutes before you could confirm a vote or a market bid/offer or trade goes through?

But then again, if I wrote the fastest database system ever, even faster than an in-memory database, it would be unfair to compare it to a complete distributed and persistent solution that didn't involve sending all data to /dev/null...

Consensus time stamping prevents an individual from affecting the consensus order of transactions.

Once an event occurs, everyone knows about it within a couple of minutes. Only the effects of the transaction are necessary in storing, everything else can be discarded. This shrinks the amount of storage currently needed (Bitcoin: 60GB) to a fraction of 1GB, allowing a smart phone to now act as a node.

Link: Blockchain Just Became Obsolete. The Future is Hashgraph

Whooooaa, say what?! Everyone knows about it "within a couple of minutes"?! Well, apparently that's how long it takes for consensus to be assured using Hashgraph. And of course, that's just for ordering, not including all the required validation as well.

And, would you really want to use a smart phone as a node, with the high cost of bandwidth, not to mention high latency and intermittent connectivity?!

Like I said earlier, I just must be missing something here, or perhaps I'm simply jaded by all the bullshit claims I've seen over my 30+ years of programming that never came close to living up to their hype.

I'm not certainly not saying that Leemon Baird and his colleagues have everything solved.. far from it. I think they have a hell of a lot more work to continue with. Additionally, it would not make sense for them to put every transacting entity on Hashgraph as a full node, and so no, I don't anticipate smartphones as full nodes. The connectivity and data storage would certainly be a limitation. The point of even mentioning a smart phone being able to run on it was in comparison to the ridiculous computational power needed to do effective Bitcoin mining.

I have no stake in Hashgraph and really don't care whether it's Hashgraph or another technology that takes us to the next step in fully peer-to-peer transactions. My interest is just to see that the middlemen finally get taken out and if Hashgraph shows real promise of doing this, then let's see what it can do. I'm certainly not religious about it. (By the way, miners are middlemen too, just as we have seen in the ridiculous costs of Bitcoin transactions and their centralization in China and elsewhere.)

If you look historically, it has always been key controlling monopolies / oligopolies that have screwed mankind. These controllers have used their middleman manipulation in trade, money, markets, communications, etc. to basically keep everyone under their thumb. My hope with Hashgraph, or any other technology that works exceedingly well in its stead to keep out the middlemen, is that finally we can have truly free markets, money, trade, and communications. It's also my personal view that blockchain is still in its infancy in its ability to fully enable this needed transformation. This, therefore, is my real interest in Hashgraph, but I don't care if it's Hashgraph or another technology that can achieve it. In other words, I'm not drinking any Hashgraph Kool-Aid, but I do want to see them enable what Baird is envisioning. His vision is to disintermediate everything and this is exactly what I want to see as well.

well, now this response is more difficult for me to take issue with! lol :)

I suppose my biggest issue with all this Baird / Hashgraph stuff is that so far I've seen mostly a bunch of marketing hype from what I would consider another one of those groups that actually seems more interested in helping those middlemen maintain control (ie. private, permissioned ledgers), versus something that works towards openly "setting the world free" (I mean, who else will be a "client")?

I also think EOS is a lot closer to actually solving many of these issues, and Dan's solution is completely open-source. Perhaps its the programmer in me, but I also get what Dan says. It makes sense from a practical perspective. Take, for example, his explanation of how they plan to achieve sub-second stable block times. No hype or B.S., just matter-of-fact "how we plan to achieve this":

In order to minimize the number of missed blocks during producer handoff, it is desirable to minimize the latency between consecutive producers. If a producer in New York is scheduled to follow a producer in China it may take 250ms to receive a block under normal conditions (50% of block interval) and potentially much longer if there is network congestion. A producer in New York and Texas on the other hand would only have 50ms of latency (10% of block interval). This means there is a significantly lower probability of missing blocks during a handoff from New York to Texas than from New York to China.

If we schedule block production such that it rotates from New York, to Texas, to California, to Hawaii, to Japan, China, India, Israel, Italy, England, Iceland, and back to New York then there is never a hand off of more than 50 to 100ms. However if the order is randomized then the average hand off will be significantly higher.

Link: EOS.IO DAWN 2.0 Released & Development Update

That said, I think open-source projects such as Bisq.Network are pretty cool too! :)

I'm looking forward to seeing what Dan develops with EOS, but Dan is working not for himself but for Block One. I am very glad to see it is Open Source, but have to say that I am still very suspicious of Block One, especially considering the BS ICO tactics that BlockOne have used to date. Everything about how this ICO has been done has been a disaster in my view. Let's see what EOS is when it arrives as a usable platform.

I've written another post sometime back about EOS and the naming and branding of EOS by Block One makes me very suspicious as well. (So you still may have something to take issue with. :) I have been studying occult symbolism for a long time because those in power are almost always involved in secret societies that use very specific symbolism to advertise their plans and control. They almost always give us hints to their agendas in symbols rather than words.

Eos is the Greek goddess of the Dawn and the mother of Lucifer, the morning star (a.k.a. Eos-phoros). This is a veiled reference to Lucifer worship that was used most prominently in late 1800s and early 1900s. (Have a look at another previous post here for more on this.) Just as an example of this, if you go to Newport, RI and see the handful of Vanderbilt and other Gilded Age mansions there that are open to the public, three of them have massive centerpiece murals of Eos on the ceiling. Why? Because just like the Obama logo and tagline, they saw themselves as bringing in "the dawn of a new day." The Soviets used this symbolism very prominently as well since Lenin and Trotsky were Freemasons in Brooklyn before they headed over to start the "people's revolution" funded by the most powerful bankers in the world at that time. I'm not saying that EOS is therefore absolutely not to be trusted, but I watch all the actions of the people that are involved in major initiatives and I can tell you that I don't like a number of things with Block One to date. This symbolism definitely concerns me as part of the story because it is by no means a mistake on their part. They know exactly what this symbolism means even if the vast majority of the uninitiated populace have no idea what it really means.

Soviets 2.jpg

Eosphoros.jpg

Hopefully this doesn't weird you out too much, but I reference it simply because just as you are wondering about motivations with Hashgraph, I am also wondering about motivations with Block One and EOS.

BTW, thanks for the tip on Bisq. I'll happily have a closer look.

you might find some of our hangouts and "after-party" discussions quite interesting... stop by next time if you have a chance! :) lol

Link: BitShares Hangout #52 | 2017-12-30 | Sat @200PM UTC | OpenSource Agenda [Beyondbit Payouts Powered by SP!]

(and that's all I'll say about that, for now! lol)

Thanks very much for the invite.. I'll be sure to stop by.

EOS ico will produce the most decentralized blockchain in terms of users and accounts. It has worked so bloody well - DPOS hinges on a wide and varied voting base so individual actors can not get control of the network. Block one has the most shares, owning 10% of the network. The next biggest whale owns less than 1% of the network. More than 80% of the network is owned by ethereum accounts that hold 10,000 or less EOS.

This ICO is a slam dunk. Look at steem or bitshares of Bitcoin for that matter where 98% of accounts own like 2% of the Bitcoin or something stupid.

Woa, real good arguments with the minutes... But wait validating is done by virtual voting! Which means you already have that for free, it's Gossip about Gossip!

they're validating "the order", not the actual payload

Lol, looks like time has proven this entire rant incorrect.

I read your post, and I've re-watched some of the videos you posted (most of which I had already seen before). Oddly, the validation is always conveniently overlooked. Yet, Baird does an excellent job at repeating "Fast, Secure, and Fair" to make sure the terms are well-ingrained into the viewer's subliminal and subconscious mind. He even starts out by saying it's currently meant for permissioned blockchains, yet he repeatedly compares it directly to other blockchains, again repeating the mantra, in comparison, that Hashgraph is "Fast, Secure, and Fair".

I'm not saying that Hashgraph doesn't have its particular niche, but the performance claims, by Baird included, are frankly only achievable in very particularly tight usage cases. If I'm still missing something here, perhaps @dan could fill in any gaps in my understanding here, as I'm quite sure he understands this far better than most, myself included.

And once more, for good measure, to really ingrain it into your minds...

You say that DAGs aren't Hashgraph. However, do you really believe that if graphene swapped out its currently foundation in lieu of Hashgraph that it would really be orders of magnitude faster? That seems quite unlikely to me. But perhaps I will be proven wrong in the near future.

As such, I do look forward to seeing some of these performance claims validated in a real-world application such as STEEMIT in the near future (quoting from your post):

Hashgraph is both an algorithm and data structure that doesn't use blocks or wait for blocks to be confirmed. There are no blocks of transactions, but instead streams of events that can be segregated into clear transactions. Since there is no waiting for blocks, Hashgraph can do hundreds of thousands of transactions per second. In comparison, Bitcoin can do 7 transactions per second and Ethereum 15 transactions per second, but even these rates are at their best performance and not their worst.

Coin Marketplace

STEEM 0.23
TRX 0.26
JST 0.040
BTC 98098.76
ETH 3483.62
USDT 1.00
SBD 3.27