4 ms·

The PBFT algorithm, or any Byzantine fault tolerant algorithms are deliberate on what's the message-passing scheme and election protocol would look like. Howev

by liuliu 8y ago

The PBFT algorithm, or any Byzantine fault tolerant algorithms are deliberate on what's the message-passing scheme and election protocol would look like. However, in recent ICO craze, a lot of algorithms (with the exception of Bitcoin, and maybe others I didn't read) don't go very long way other than "we will broadcast to everyone". These under-specified message passing scheme can be troublesome, especially for these algorithms without Proof-of-work.

woah 8y ago
Which protocols have you read?
- liuliu 8y ago
  Will try not to reply here since it can be inflammatory (any cryptocurrency topic here HN). That's been said, can you find any mention of "messages" in this article: https://steemit.com/dpos/@dantheman/dpos-consensus-algorithm-this-missing-white-paper https://steemit.com/dpos/@dantheman/dpos-consensus-algorithm... which directly referenced as their DPoS algorithm here: https://github.com/EOSIO/Documentation/blob/master/TechnicalWhitePaper.md#consensus-algorithm-bft-dpos https://github.com/EOSIO/Documentation/blob/master/Technical... (I am not saying these are wrong, just under-specified scheme will essentially become implementation-specified and doesn't help anyone here).
atomical 8y ago
Check out Hashgraph. It is asynchronous Byzantine.
- kerng 8y ago
  Hashgraphs currently require a permissioned environment (eg. a node needs to know how many others there are and trust them to reach consensus) - so why not just use SQL Databases? They are even faster.
  - atomical 8y ago
    SQL database, operated by different vendors, would allow double spending.
  - st1ck 8y ago
    Pretty much all of BFT consensus protocols (like Paxos or Honey Badger) are like this, except SCP (Stellar). They are used e.g. in aviation, so they are very practical.
legionof7 8y ago
I think that 95% of the ICO craze people meet at least one of these: 1.Don't have an algorithm concept in the paper 2.Don't know what an algorithm is 3.Have a concept, don't know what it means' 4.Don't know what the Byzantine Generals Problem is 5.Don't know what blockchain is

by liuliu 8y ago

woah 8y ago

Which protocols have you read?

liuliu 8y ago
Will try not to reply here since it can be inflammatory (any cryptocurrency topic here HN). That's been said, can you find any mention of "messages" in this article: https://steemit.com/dpos/@dantheman/dpos-consensus-algorithm-this-missing-white-paper https://steemit.com/dpos/@dantheman/dpos-consensus-algorithm... which directly referenced as their DPoS algorithm here: https://github.com/EOSIO/Documentation/blob/master/TechnicalWhitePaper.md#consensus-algorithm-bft-dpos https://github.com/EOSIO/Documentation/blob/master/Technical... (I am not saying these are wrong, just under-specified scheme will essentially become implementation-specified and doesn't help anyone here).

atomical 8y ago

Check out Hashgraph. It is asynchronous Byzantine.

kerng 8y ago
Hashgraphs currently require a permissioned environment (eg. a node needs to know how many others there are and trust them to reach consensus) - so why not just use SQL Databases? They are even faster.
- atomical 8y ago
  SQL database, operated by different vendors, would allow double spending.
- st1ck 8y ago
  Pretty much all of BFT consensus protocols (like Paxos or Honey Badger) are like this, except SCP (Stellar). They are used e.g. in aviation, so they are very practical.

legionof7 8y ago

I think that 95% of the ICO craze people meet at least one of these: 1.Don't have an algorithm concept in the paper 2.Don't know what an algorithm is 3.Have a concept, don't know what it means' 4.Don't know what the Byzantine Generals Problem is 5.Don't know what blockchain is