-
Historically, we use to have Unit Tests for dBFT consensus.
After https://github.com/neo-project/neo/issues/3230 is migrated it would be very important to restore these tests, even minimally, testi…
-
**Summary or problem description**
This issue is focused in discussing desired features for dBFT 3.0, and proposed specification for double-speaker proposals (dBFT3-WS2).
**Do you have any solutio…
-
In the text sections of the page, 'Delegated Byzantine Fault Tolerance' is shortened to 'DBFT', but in the video it is shortened to 'dBFT' (consistent with the way it's written in the blockchain commu…
-
**Summary or problem description**
We're using the notion of "failed" nodes for some dBFT logic (even though technically it'd be better to call them "unknown", we can't really judge if the node faile…
-
### Summary or problem description
This issue is triggered by the dBFT 2.0 liveness lock problem mentioned in https://github.com/neo-project/neo/issues/2029#issuecomment-725612388 and other discuss…
-
https://cointelegraph.com/news/from-pos-to-dbft-a-brief-review-of-consensus-protocols
> Projects using a pure PoS algorithm are Reddcoin, Decred and NavCoin.
-
dBFT inevitably relies on eventual message delivery, so in presence of some communication issues it can be delayed, but not subverted. Yet the degree of this delay can be somewhat impractical (as in #…
-
We need to get back to https://github.com/nspcc-dev/dbft/commit/0cda0851244b58dc46b9885abd00e4cbfac80e9f once, it certainly needs much more testing and it's not critical, but it can obviously improve …
-
1- https://github.com/aleph-zero-foundation/consensus-go
2- https://github.com/nspcc-dev/dbft
3- https://github.com/SmartBFT-Go/consensus
4- https://github.com/dedis/cothority/tree/main/byzcoinx
5…
-
Based on the recent experiments with time-constrained dBFT, the following behaviour pattern was discovered: with low MillisecondsPerBlock setting often CVs happen due to peer disconnections:
```
202…