Ecosystem/serai
Ecosystem/serai
1
0
Fork 0
mirror of https://github.com/serai-dex/serai.git synced 2024-12-23 12:09:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
serai/processor
History
Luke Parker 13b74195f7 Don't have acknowledge_batch immediately run 
`acknowledge_batch` can only be run if we know what the Batch should be. If we
don't know what the Batch should be, we have to block until we do.
Specifically, we need the block number associated with the Batch.

Instead of blocking over the Scanner API, the Scanner API now solely queues
actions. A new task intakes those actions once we can. This ensures we can
intake the entire Substrate chain, even if our daemon for the external network
is stalled at its genesis block.

All of this for the block number alone seems ridiculous. To go from the block
hash in the Batch to the block number without this task, we'd at least need the
index task to be up to date (still requiring blocking or an API returning
ephemeral errors).
2024-09-19 23:36:32 -07:00
..
frost-attempt-manager Definition and delineation of tasks within the scanner 2024-09-19 23:36:32 -07:00
key-gen Cleanup DB handling a bit in key-gen/attempt-manager 2024-09-19 23:36:32 -07:00
messages Smash out the signer 2024-09-19 23:36:32 -07:00
primitives Have acknowledge_block take in the results of the InInstructions executed 2024-09-19 23:36:32 -07:00
scanner Don't have acknowledge_batch immediately run 2024-09-19 23:36:32 -07:00
src Definition and delineation of tasks within the scanner 2024-09-19 23:36:32 -07:00
Cargo.toml Smash key-gen out of processor 2024-09-19 23:36:32 -07:00
LICENSE Smash out the signer 2024-09-19 23:36:32 -07:00
README.md Add support for multiple multisigs to the processor (#377) 2023-09-25 09:48:15 -04:00

README.md

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.