You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to add a signature to Preconfirmations to prove that they were sent by the block producer.
The KMS signatures take longer than 50ms, which isn't acceptable for preconfirmations. We are targetting 30ms from tx submission.
Instead, every ~10 mins the consensus service can generate a new private/public keypair that can be used preconfirmations. The public key will need to be signed by the KMS still, and then gossiped to the network.
This needs to be added.
The text was updated successfully, but these errors were encountered:
## Linked Issues/PRs
<!-- List of related issues/PRs -->
In preparation for #2739
## Description
<!-- List of detailed changes -->
There were a lot of confusing paths in the `run` method, including
redundant `Trigger` checks and other redundancies. This refactor helps
read the code, as we are going to be adding more functionalities to the
task.
### Before requesting review
- [ ] I have reviewed the code myself
---------
Co-authored-by: Green Baneling <[email protected]>
We need to add a signature to Preconfirmations to prove that they were sent by the block producer.
The KMS signatures take longer than 50ms, which isn't acceptable for preconfirmations. We are targetting 30ms from tx submission.
Instead, every ~10 mins the consensus service can generate a new private/public keypair that can be used preconfirmations. The public key will need to be signed by the KMS still, and then gossiped to the network.
This needs to be added.
The text was updated successfully, but these errors were encountered: