Why does DPOS provide greater tps (faster) than Bitcoin-NG?

Why does DPOS provide greater tps (faster) than Bitcoin-NG?

In Bitcoin-NG example Waves, a leader is elected who can then validate micro transactions, with speed limited by network propogation times.

DPOS example EOS for example has 21 delegates ("block producers"). They validate transactions, and thereafter speed is limited by network propogation times.

Typically DPOS is quoted as having something like 10x greater tps capacity than Waves (Bitcoin-NG) e.g. https://scryptoworld.com/waves-set-become-fastest-decentralized-blockchain-platform-globally/ (these figures seems a bit off but just an example)

What is it that makes DPOS faster?

Is hardware limitation a factor? e.g. together 21 block producers can sign more transactions when network is under stress (although network propogation is more of a barrier than signing speed? - and 21 bps (or majority) would all have to check the transactions anyway?)

If a transaction is validated by 21 blocks producers then it is sent out to network as being valid as the 21 say so (as I understand) - but isn't this the same as Bitcoin-NG, or with Bitcoin-NG is it not true that it is valid once the leader says so, it has to be included in subsequent blocks to be confirmed (in which case is tps a measure of 0-conf tps i.e. when is a transaction a transaction)?

http://bit.ly/2CWec6v

Comments

Post a Comment

Popular posts from this blog

sendrawtransaction and txn-mempool-conflict

sendrawtransaction and txn-mempool-conflict When i sendrawtransaction to bitcoind, i get error (exceptions) 18: txn-mempool-conflict (use Bitcoin JSON-RPC denpamusic/php-bitcoinrpc ) But the transaction is sent to the network and is subsequently confirmed. Example one decoded transaction : https://jsfiddle.net/rn58a4j6/ then i send this transaction: 94ec12fc463230b4285a29b047608627c05572a4c6eabe6688a201ce49ae72f7 https://ift.tt/2MY2KP0
Read more

couldn't connect to server: EOF reached (code 1)

couldn't connect to server: EOF reached (code 1) I'm running a full node on my raspberry pi3. I try to do a simple command such as bitcoin-cli getblockchaininfo but I always get this error: error: couldn't connect to server: EOF reached (code 1) (make sure server is running and you are connecting to the correct RPC port) My bitcoin.conf file looks like this: Bitcoind options server=1 daemon=1 reindex-chainstate=1 reindex=1 txindex=1 disablewallet=1 listenonion=0 Connection settings rpcuser= * rpcpassword=* rpcport=8332 rpcallowip=127.0.0.1 rpcthreads=10 I also tried to get a command with "bitcoin-cli -rpcuser: * - rpcpassword=* -rpcportt8332 getblockchaininfo". But this also didn't work. Does someone has some advice or experience with this error? https://ift.tt/2D82TLW
Read more