demo
Well-known member
Forget about blockchain.
What about this?
http://www.swirlds.com/downloads/SWIRLDS-TR-2016-02.pdf
Can this scale?
And what about this?
https://www.enigma.co/enigma_full.pdf
Forget about blockchain.
What about this?
http://www.swirlds.com/downloads/SWIRLDS-TR-2016-02.pdf
Can this scale?
I don't think that speed will be an issue for Dash for a few years at least, also to implement such a big change would take a very long time and would require extensive rework and testing, but I agree that we should consider all of the alternatives for the future.
I would like to hear from the core team if there is someone that is looking into this and similar ideas?
I did some research on that Hashgraph technology and I must say I find it impressive. But I see a few issues with integrating it in Dash.
First, it's not open source (at least currently) and Dash is committed to being open source.
Second, it's not yet tested in really big networks, so I'm not certain if all potential vectors of attack are yet known.
Third, I don't see how it can be integrated into Dash structure, as it would require no miners and no masternodes.
Dash is not committed of being open source, because Evolution is (until now) closed source.First, it's not open source (at least currently) and Dash is committed to being open source
Dash Evolution is not open source, because the definition of opensource requires this to be open from the very early stages.Dash Evolution will be open source once it's finished and operational and will not require licensing.
I guess that then you don't consider Linux open source also because Linus Torvalds developed the first kernel himself?
Forget about blockchain.
What about this?
http://www.swirlds.com/downloads/SWIRLDS-TR-2016-02.pdf
Can this scale?
The primary function of mining is NOT to slow down the blockchain but to ensure SCARCITY and decentralized coin distribution. Speed is worthless if we get the economics wrong.
From what I have been able to determine, Hashgraph is not resistant to adversarial nodes, or to Sybil attacks. There's a reason it's only been implemented in closed applications so far, and there is no discussion of having an open or public version of it yet (or at all.)
If you are curious if masternodes can scale to data-center proportions, while still being supported by income from transactions, the answer is yes, even assuming we are stuck at today's hardware and we never get price or performance improvements while needing to cover the whole world's transnational capacity.
This was proven (with supporting evidence) by one of the folks in the BCH community.
http://blog.vermorel.com/journal/2017/12/17/terabyte-blocks-for-bitcoin-cash.html
As for masternode hardware scaling...yeesh...even if it's plausible that's still such an absurd and unnecessary expenditure of energy and wasted computational power. Why not just implement a better algorithm and avoid all of that entirely? It makes no sense to continue that way other than "people are already invested in it."
I don't actually have a problem with changing the algorithm; but I won't hold my breath for Hashgraph specifically until I see them with a public release.
There are always trade-offs, and I don't see how you can make the barrier to entry for changing a ledger so much lower (i.e. more efficient) without simultaneously lowering it's resistance to having the ledger changed by an attacking party.
If it can be done, and it truly is a revolutionary new way of getting around the byzantine general's problem, then by all means research it; but like I said, I won't hold my breath.
Masternode Hosting benefits from economies of scale. That's why services such as Splawik's host two thirds of the MNs already. This is a dangerous situation perilously close to being a single point of failure. With drastically greater hardware requirements, this problem will only get worse as the network grows.