keep-network/keep-ecdsa v1.7.0

Client: 1.7.0 (Mainnet)

on GitHub

Overview

This release brings important improvements to client functionality in the area of Ethereum event subscriptions.

The ECDSA client applies exponential backoff to Ethereum event resubscription attempts. Also, it monitors the stability of event subscriptions and emits errors to logs in case they do not meet the required stability parameters.

The ECDSA client, for every Ethereum event subscription, runs an additional event monitoring loop in the background polling past events in intervals to make sure no events were omitted by the client even if they were dropped as a result of having an unstable connection to Ethereum.

Note that the client version can be updated without any config changes.

Details

v1.7.0 is the latest release of Keep ECDSA client, which primarily drives ECDSA keeps. The most important client changes since v1.6.0 are:

• Added exponential backoff to Ethereum event resubscription attempts to minimize the risk of rejecting resubscription attempts by Ethereum client in case of a massive WebSocket connection drop.
• Improved logging around Ethereum event resubscription attempts to log on error level every immediate resubscription failure.
• Added detection of unstable Ethereum event subscriptions. In case the Ethereum event subscription had to be retried sooner than 15 minutes after it has been established, an error is logged to logs informing about unstable subscription and alerting the operator to inspect their connectivity to Ethereum.
• Refactored event subscription API to allow for a pipe-to-channel pattern. This change is not affecting client operators but is an improvement allowing for the implementation of a cleaner event handler code.
• Added background monitoring loop for every Ethereum event subscription polling past events in intervals next to a regular watchLogs subscription. Some third-party Ethereum providers used by some of Keep Network operators are not particularly reliable in delivering events. This monitoring loop ensures that even if the event was dropped by watchLogs subscription, it is going to be picked later by the monitoring loop and processed by the client.
• Improved event deduplication mechanism for key generation and signature request events to cover the case if original events were emitted a long time before a duplicate. Covered keep close and keep terminate events with a similar deduplication mechanism.

In addition to the information above, we're providing two pieces of information for operators and other interested parties:

• The Docker Hub image hash.
• The release commit hash.

Docker image is available as docker pull keepnetwork/keep-ecdsa-client:v1.7.0; sha256sum is sha256:fb74c44bc8562ba76ce32a28fd97e80b7748ad7c67edcf00548502d3f18eb274.

Signatures of sha256sum from the team (verify these in the Keybase app):

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7k0EPCe MIkyY34Uohzeme3 kPVhEXkmNHK48lm zCzcmunOkMtfC71 h5H4OoZygTlB2Q0 5AHko0jmnhleYLz moWNUXq3cfx1aWr HGgpun8pl9Oatkz 8cBxxj4vPKsoTfb Qxnw5rVJiovvIqc hSidlBuLMOQVD67 w1zpm69kdlNhGZn 9YfRLyXbCe47iIb vCk2MfJTldl8fu2 XU. END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegATHnpxG hVK0sLAm8ZwOm96 XaktsFxmzwvRKQC zLFN5BNV4mIzWdG NxHrIaiL77sEglA ZkoVeOMHYxOS5TY Ng24yLEqXdrdvtw 7Q59SBvQ8vZ3obd ZOggS7SRtBNkLMX X6N7qsvqiR6Cqxr RcwBlBuLMOQVD67 w1zpm69kdlNhGZn 9YfRLyXbCe47iIb vCk2MfJTldl8fu2 XU. END KEYBASE SALTPACK SIGNED MESSAGE.

Commit hash for clean builds is f240e81002a7b26eb6326be068dbf80b53bc0a18.

Signatures of commit hash from the team (verify these in the Keybase app):

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7k0kuML JfMc9Ks01UHo4bJ wNMRSlN6DAkl6RU 77takJGlN22EVHZ fSmScEwXnLvoLJ3 NtSFKn6MNFzRdqL uMpFSFFSNqceaKF k7OwAmNgJokO7V3 LqMW38c6uvLE5M9 FGaa03JyQqpeu0B FrheU0qVJMSLpnK qKvIcr8UoMQD5LM . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegATGBmDh gBAN61nfBdTdhTk HxJne3ZRVeDU30F UoJcDNYSCdmI4ZK XqifaiWD973AcGp RZsIzX68ADT17XT rfqEMLctgYMqpIj VKbcXEUknKcg9LG EnEJHJlgInPb6GQ pvFU5o0hzh8dOJ8 zgDWk0qVJMSLpnK qKvIcr8UoMQD5LM . END KEYBASE SALTPACK SIGNED MESSAGE.

Finally, note that the full set of work that went into the client can be found in the corresponding 1.7.0 milestone.