serai/processor
Luke Parker bc0cc5a754 Decide flow between scan/eventuality/report
Scan now only handles External outputs, with an associated essay going over
why. Scan directly creates the InInstruction (prior planned to be done in
Report), and Eventuality is declared to end up yielding the outputs.

That will require making the Eventuality flow two-stage. One stage to evaluate
existing Eventualities and yield outputs, and one stage to incorporate new
Eventualities before advancing the scan window.
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 Add Eventuality back to processor primitives 2024-09-19 23:36:32 -07:00
scanner Decide flow between scan/eventuality/report 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

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.