mirror of
https://github.com/serai-dex/serai.git
synced 2025-12-08 12:19:24 +00:00
7d738a3677
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.
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.