serai/coordinator
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 Implement Tributary syncing 2023-04-24 00:53:18 -04:00
tributary 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 Start handling P2P messages 2023-04-23 17:01:30 -04:00
LICENSE Add empty coordinator 2023-04-11 09:21:35 -04:00
README.md Add empty coordinator 2023-04-11 09:21:35 -04:00

Coordinator

The Serai coordinator communicates with other coordinators to prepare batches for Serai and sign transactions.

In order to achieve consensus over gossip, and order certain events, a micro-blockchain is instantiated.