From what I understand, and the reason I mentioned it here, is that tendermint confirmations times are limited only by the bandwidth of the network, for example, with about 10,000 validators = about 1min confirmations times and also unlike dpos doesn't rely on having trust in the 101 delegates.
"On the other hand existing proof-of-stake protocols do
not have a well defined intrinsic penalty for instigators of a double-spend attack.
This is commonly called, ironically, the “nothing at stake” problem. Newer protocols
like the BitShares delegated-proof-of-stake protocol attempt to address this problem
by placing the role of ranked-delegate at stake [3], but security is dependant on
the extrinsic ability of stakeholders to accurately predict the future performance of
delegates."
Reference on confirmation time about 19:00 mark
http://letstalkbitcoin.com/blog/post/beyond-bitcoin-21-consensus-without-mining
"On the other hand existing proof-of-stake protocols do
not have a well defined intrinsic penalty for instigators of a double-spend attack.
This is commonly called, ironically, the “nothing at stake” problem. Newer protocols
like the BitShares delegated-proof-of-stake protocol attempt to address this problem
by placing the role of ranked-delegate at stake [3], but security is dependant on
the extrinsic ability of stakeholders to accurately predict the future performance of
delegates."
Reference on confirmation time about 19:00 mark
http://letstalkbitcoin.com/blog/post/beyond-bitcoin-21-consensus-without-mining
Directly from the developer:
Hi Keith, the conf time depends on the available bandwidth of each node and the number of validators. With say a 10Mbit connection for everyone and 5000 validators it should get sub minute confirmations.
