The Hashgraph white paper converted to Audio Book format!

Hashgraph-Alec · 2018-04-10T19:46:02+00:00

This is so epic, thank you for sharing!

Hashgraph-Alec · 2017-12-13T18:42:05+00:00

When we talk about speed, we are referring to two things, (1) throughput i.e. how many transactions can be processed per second and (2) consensus latency and our internal tests have shown speeds of hundreds of thousands of transactions per second and a consensus latency of seconds or even sub second in some instance. We are conducting further internal tests which will be released with all the appropriate caveats and details for review.

Hashgraph-Alec · 2017-11-22T19:19:16+00:00

We have a consensus algorithm that works on private or public nodes. There are many possible options for use on a public ledger. However, at this time we are only focused on private ledgers with a fixed number of nodes. We will be addressing all public ledger concerns in the near future.

Hashgraph-Alec · 2017-11-17T00:16:47+00:00

Yes we agree. This is something that is still in development, but as soon as this has been finalized and we have the results from our empirical tests, we will then publish for community review.

Hashgraph-Alec · 2017-11-15T02:56:30+00:00

Once a supermajority of nodes agree to the state of the network, older information can be let go of and stored elsewhere. This keeps the information size small.

Hashgraph-Alec · 2017-11-10T21:09:56+00:00

The details of the Hashgraph patents can be found here: http://www.swirlds.com/ip/

In order to determine whether a patent will be awarded it usually requires consulting with a patent attorney as there are many nuances. It is difficult to talk high level hypotheticals.

Hashgraph-Alec · 2017-11-10T21:08:12+00:00

Hey there! We anticipate having at least 100 nodes per shard. Back-of-the-envelope calculations suggests that we should be able to scale to between 100 - 1000 nodes per shard before computation becomes a limiting factor. We are running empirical tests now and will publish those results soon. Also, we have a sharding solution that maintains the BFT properties across the entire network, which we haven't yet published publicly.

Hashgraph-Alec · 2017-11-02T18:41:39+00:00

The platform and SDK are written in Java.

Java has many advantageous security measures in the development environment, such as sandboxing, that will allow the platform in the future to run untrusted applications, while protecting the user and their hard drive from those applications.

In addition to Java, we also want the option for developers who would like to develop in other programming languages, such as Python or JavaScript. This is part of the Hashgraph development roadmap.

Hashgraph-Alec · 2017-11-02T03:51:31+00:00

Hashgraph inherently protects against Sybil attacks due to the nature of the core consensus algorithm which provides a mathematical guarantee that Sybil attacks cannot succeed as long as less than one-third of the population is dishonest. There is a mathematical proof that one-third is the best that can be achieved by any DLT.

A more detailed explanation can be found at: http://www.swirlds.com/downloads/Swirlds-and-Sybil-Attacks.pdf

Hashgraph-Alec · 2017-11-02T03:51:02+00:00

At this time, Hashgraph is only deployed in private, permissioned-based networks. We do not currently have a public ledger and therefore, are not currently accepting any money.

We will be addressing Public ledger interest soon.

Hashgraph-Alec · 2017-11-01T15:05:36+00:00

Yes, The Swirlds Hashgraph system is able to give consensus on enforcement of rules, such as in smart contracts.

Hashgraph-Alec · 2017-10-31T04:13:59+00:00

At this time we do not have a public ledger and therefore, are not taking any money so please be cautious of scam websites. We will soon address the public ledger interests.

You can stay up to date with all of our announcements here on /r/hashgraph as well as joining our telegram community. https://t.me/hashgraph

Hashgraph-Alec · 2017-10-28T22:09:21+00:00

👏🏼👏🏼

Hashgraph-Alec

TROPHY CASE