serai/processor
Luke Parker e1ad897f7e Allow scheduler's creation of transactions to be async and error
I don't love this, but it's the only way to select decoys without using a local
database. While the prior commit added such a databse, the performance of it
presumably wasn't viable, and while TODOs marked the needed improvements, it
was still messy with an immense scope re: any auditing.

The relevant scheduler functions now take `&self` (intentional, as all
mutations should be via the `&mut impl DbTxn` passed). The calls to `&self` are
expected to be completely deterministic (as usual).
2024-09-19 23:36:32 -07:00
..
bin Allow scheduler's creation of transactions to be async and error 2024-09-19 23:36:32 -07:00
bitcoin Allow scheduler's creation of transactions to be async and error 2024-09-19 23:36:32 -07:00
ethereum Remove async-trait from processor/ 2024-09-19 23:36:32 -07:00
frost-attempt-manager Route the coordinator, fix race conditions in the signers library 2024-09-19 23:36:32 -07:00
key-gen Misc continuances on the Monero processor 2024-09-19 23:36:32 -07:00
messages Note better message structure in messages 2024-09-19 23:36:32 -07:00
monero Allow scheduler's creation of transactions to be async and error 2024-09-19 23:36:32 -07:00
primitives Remove async-trait from processor/ 2024-09-19 23:36:32 -07:00
scanner Allow scheduler's creation of transactions to be async and error 2024-09-19 23:36:32 -07:00
scheduler Allow scheduler's creation of transactions to be async and error 2024-09-19 23:36:32 -07:00
signers cargo fmt signers/scanner 2024-09-19 23:36:32 -07:00
src Remove async-trait from processor/ 2024-09-19 23:36:32 -07:00
view-keys Move additional_key.rs to serai-processor-view-keys 2024-09-19 23:36:32 -07:00
README.md Split processor into bitcoin-processor, ethereum-processor, monero-processor 2024-09-19 23:36:32 -07:00

Processor

The Serai processors, built from the libraries here, scan an external network and report the indexed data to the coordinator. For details on its exact messaging flow, and overall policies, please view docs/processor.