serai/processor/scanner
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
..
src Decide flow between scan/eventuality/report 2024-09-19 23:36:32 -07:00
Cargo.toml Handle dust 2024-09-19 23:36:32 -07:00
LICENSE Move scanner.rs to scanner/lib.rs 2024-09-19 23:36:32 -07:00
README.md Move scanner.rs to scanner/lib.rs 2024-09-19 23:36:32 -07:00

Scanner

A scanner of arbitrary blockchains for Serai.

This scanner has two distinct roles:

  1. Scanning blocks for received outputs contained within them
  2. Scanning blocks for the completion of eventualities

While these can be optimized into a single structure, they are written as two distinct structures (with the associated overhead) for clarity and simplicity reasons.