serai/coordinator
Luke Parker 7d738a3677
Start moving Coordinator to a multi-Tributary model
Prior, we only supported a single Tributary per network, and spawned a task to
handled Processor messages per Tributary. Now, we handle Processor messages per
network, yet we still only supported a single Tributary in that handling
function.

Now, when we handle a message, we load the Tributary which is relevant. Once we
know it, we ensure we have it (preventing race conditions), and then proceed.

We do need work to check if we should have a Tributary, or if we're not
participating. We also need to check if a Tributary has been retired, meaning
we shouldn't handle any transactions related to them, and to clean up retired
Tributaries.
2023-09-27 20:49:02 -04:00
..
src Start moving Coordinator to a multi-Tributary model 2023-09-27 20:49:02 -04:00
tributary Add a next block notification system to Tributary 2023-09-25 23:20:51 -04:00
Cargo.toml Remove lazy_static for proper use of channels 2023-09-25 18:23:52 -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.