serai/processor
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
..
messages Add support for multiple multisigs to the processor (#377) 2023-09-25 09:48:15 -04:00
src Start moving Coordinator to a multi-Tributary model 2023-09-27 20:49:02 -04:00
Cargo.toml Minimize features pulled in to try and reduce build times 2023-07-25 22:29:39 -04:00
LICENSE Update licenses 2023-01-11 23:05:31 -05:00
README.md Add support for multiple multisigs to the processor (#377) 2023-09-25 09:48:15 -04:00

Processor

The Serai processor scans a specified external network, communicating with the coordinator. For details on its exact messaging flow, and overall policies, please view docs/processor.