10

Until BFT messages are deployed and working, the DPOS side of BFT-DPOS will reach finality for a transaction 180 seconds after it is included in a block. This is assuming a nominal network conditions with 21 producers. The math to arrive at this number is that, each block must be "pre-committed" to by 2/3 + 1 producers in order to be eligible for "...


4

From the code: /** * @class fork_database * @brief manages light-weight state for all potential unconfirmed forks * * As new blocks are received, they are pushed into the fork database. The fork * database tracks the longest chain and the last irreversible block number. All * blocks older than the last irreversible block are freed ...


2

You must wait for a block height to be lower than the current Last Irreversible Block (also known as LIB) to be considered irreversible. With the quick speed of the network, it is common to see microforks that occur - often when ProducerB starts producing its schedule off of Block 11 of ProducerA's round. This can happen due to latency conditions because of ...


2

According to the whitepaper: Transaction Confirmation Typical DPOS blockchains have 100% block producer participation. A transaction can be considered confirmed with 99.9% certainty after an average of 0.25 seconds from time of broadcast. In addition to DPOS, EOS.IO adds asynchronous Byzantine Fault Tolerance (aBFT) for faster achievement ...


2

Fork database is all the valid reversible blocks your node received, once the longest branch has the irreversible block, the branches from the irreversible block will be removed.


2

Every block produced by a block producer includes a header field that indicates the highest numbered block that they confirmed. Using this information, each of the block producers are able to determine the highest number block that has received (2/3)+1 confirmations, making it the last irreversible block. You can see here for more information from Dan ...


1

When you do a transaction you get the expiration time of the transaction along with the tx hash other than few other parameters. The expiration time is the time till which the tx is valid.If the tx gets included in the blockchain in block x after it is broadcasted ( this can be checked by using the command cleos get transaction txid ) , then . within the ...


Only top voted, non community-wiki answers of a minimum length are eligible