We want to avoid that the activation of the signature of Cardano transactions blocks the network and prevents it to create new certificates. Also we'd like to take advantage of the 2 epochs delay for newcomers in the protocol before they can sign after their first registration.
What
Implement a warm-up in the signer and aggregator that imports Cardano transactions in a different thread wait node startup.
How
[x] Implement the import of the Cardano transactions when the signer/aggregator starts in a thread
[x] In the signer
[x] In the aggregator
[x] Lock signed entity type for signing until all the data are imported
[x] In the signer
[x] In the aggregator
Later
Compute the message to sign on the signer even if the signer is not already eligible to sign it (to extend the warm-up mechanism)
Launch the warm-up import at regular interval (~1 day)?
Why
We want to avoid that the activation of the signature of Cardano transactions blocks the network and prevents it to create new certificates. Also we'd like to take advantage of the
2epochs delay for newcomers in the protocol before they can sign after their first registration.What
Implement a warm-up in the signer and aggregator that imports Cardano transactions in a different thread wait node startup.
How
Later
Launch the warm-up import at regular interval (~1 day)?