Ecosystem/serai
Ecosystem/serai
1
0
Fork 0
mirror of https://github.com/serai-dex/serai.git synced 2025-01-12 05:44:53 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
serai/processor
History
Luke Parker 554c5778e4 Don't track deployment block in the Router 
This technically has a TOCTOU where we sync an Epoch's metadata (signifying we
did sync to that point), then check if the Router was deployed, yet at that
very moment the node resets to genesis. By ensuring the Router is deployed, we
avoid this (and don't need to track the deployment block in-contract).

Also uses a JoinSet to sync the 32 blocks in parallel.
2024-09-19 23:36:32 -07:00
..
bin Remove accidentally included bitcoin feature from processor-bin 2024-09-19 23:36:32 -07:00
bitcoin Update to the latest bitcoin-serai 2024-09-19 23:36:32 -07:00
ethereum Don't track deployment block in the Router 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 Merge BlockWithAcknowledgedBatch and BatchWithoutAcknowledgeBatch 2024-09-19 23:36:32 -07:00
monero Add hooks to the main loop 2024-09-19 23:36:32 -07:00
primitives Pass the latest active key to the Block's scan function 2024-09-19 23:36:32 -07:00
scanner Report a Change Output with every Eventuality to ensure we don't fall out of synchrony 2024-09-19 23:36:32 -07:00
scheduler Remove OutInstruction's data field 2024-09-19 23:36:32 -07:00
signers cargo fmt signers/scanner 2024-09-19 23:36:32 -07:00
src Remove OutInstruction's data field 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

README.md

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.