serai/coordinator/tributary
Luke Parker cc491ee1e1
Don't return from sync_block until the Tendermint machine returns if it's valid or not
We had a race condition where'd we be informed of blocks 1 .. 3, and
immediately add 1 .. 3. Because we immediately tried to add 2 after 1, it'd
fail since the tip was still the genesis, yet 2 needs the tip to be 1.

Adding a channel, while ugly, was the simplest way to accomplish this.

Also has any added block be broadcasted. Else there's a race condition where a
node which syncs up to the most recent block does so, yet fails to add the next
block when it's committed to.
2023-04-24 02:46:13 -04:00
..
src Don't return from sync_block until the Tendermint machine returns if it's valid or not 2023-04-24 02:46:13 -04:00
tendermint Don't return from sync_block until the Tendermint machine returns if it's valid or not 2023-04-24 02:46:13 -04:00
Cargo.toml Break coordinator main into multiple functions 2023-04-23 23:15:15 -04:00
LICENSE Create a folder for tributary, the micro-blockchain 2023-04-11 10:18:31 -04:00
README.md Clarify Arc RwLocks and sleeps in coordinator 2023-04-23 18:29:50 -04:00

Tributary

A verifiable, ordered broadcast layer implemented as a BFT micro-blockchain.