serai/processor
Luke Parker 7eb388e546
PR to track down CI failures (#501)
* Use an extended timeout for DKGs specifically

* Add a log statement when message-queue connection fails

* Add a 60 second keep-alive to connections

* Use zalloc for processor/message-queue/coordinator

An additional layer which protects us against edge cases with Zeroizing
(objects which don't support it or don't miss it).

* Add further logs to message-queue

* Further increase re-attempt timeouts in CI

* Remove misplaced continue inmessage-queue client

Fixes observed CI failures.

* Revert "Further increase re-attempt timeouts in CI"

This reverts commit 3723530cf6.
2024-01-04 01:08:13 -05:00
..
messages Correct a couple years of accumulated typos 2023-12-17 02:06:51 -05:00
src PR to track down CI failures (#501) 2024-01-04 01:08:13 -05:00
Cargo.toml PR to track down CI failures (#501) 2024-01-04 01:08:13 -05:00
LICENSE Update licenses 2023-01-11 23:05:31 -05: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.