News for hackers. Stuff that matters.
Re:Why we rolled our own consensus algorithm by lifty on Thursday November 15, 2018 @03:16PM (#18462874)
There is a new consensus algorithm called Avalanche, which apparently starts a new, 3rd category. You can read the white paper here: https://ipfs.io/ipfs/QmUy4jh5mGNZvLkjies1RWM4YuvJh5o2FYopNPV...
Re:Why we rolled our own consensus algorithm by nybble41 on Friday November 16, 2018 @03:24PM (#18471688)
Avalanche looks interesting, but there doesn't seem to be anything in the white paper to suggest how they plan to deal with Sybil attacks. Their safety guarantees are dependent on the number of Byzantine nodes in the network, but what prevents a single attacker from simulating a large number of independent nodes (e.g. with VMs, or a botnet) and exceeding that limit? Can a minority of correct nodes continue to function safely despite a hostile Byzantine majority?
Re:Why we rolled our own consensus algorithm by Geee on Thursday November 15, 2018 @05:51PM (#18464229)
From a quick glance, isn't this somewhat similar to what Nano is doing? Nano does balance-weighed voting on conflicting blocks via gossip until the network arrives at consensus. https://nano.org/en/whitepaper
Re:Why we rolled our own consensus algorithm by tobowers on Thursday November 15, 2018 @03:42PM (#18463087)
Absolutely. That’s the “perhaps 3” part of the above. Avalanche is really interesting. Can’t wait to see Ava.