keep-network/keep-ecdsa v1.5.0

Client: 1.5.0 (Mainnet)

on GitHub

Overview

This release brings two important improvements to client functionality.

First, the ECDSA client now has the ability to monitor the operator ETH account balance and start emitting ERROR logs if the balance drops below a designated threshold. The client will NOT terminate, it will just log to trigger any monitoring. See the relevant section of the sample config file for how to enable this functionality. It is strongly recommended that you enable this behavior, as not maintaining an operator account balance properly can result in liquidations.

Second, tBTC-specific behaviors are here! With some light configuration updates, the ECDSA client now takes care of making sure most behaviors needed to avoid tBTC timeouts are handled automatically. This includes:

• Ensuring that a published public key is properly picked up by the corresponding tBTC deposit.
• Ensuring that redemption signatures are properly picked up by the corresponding tBTC deposit.
• Ensuring that if a redemption Bitcoin transaction proof has not been provided, the Bitcoin fee is automatically bumped on the contract side.

See the relevant section of the sample config file for how to enable this functionality. It is strongly recommended that you enable this behavior, as not doing so can result in liquidations.

There are also several smaller bug fixes and improvements, detailed below. Note that the client version can be updated without any config changes, and config changes can be made separately.

Details

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

• Support for tBTC application-specific actions: retrieve public key, provide redemption signature, increase redemption fee. More details on enabling this extension are available in the sample configuration file.
• Ethereum account balance monitoring. More details on enabling this are available in the sample configuration file.
• Optimization of the signature submission process making signing group members submit a signature in order and allowing them to reduce ether costs.
• Block confirmations monitoring for public key and signature submission allowing the client to better deal with chain reorganizations.
• CLI command allowing to sign a message with the operator's Ethereum private key, useful for the coordination of BTC recovery between signers from liquidated and funding-timed-out deposits.
• General nonce handling improvements allowing to better deal with Ethereum client mempool synchronization delays.

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.5.0; sha256sum is sha256:62da914f9c35ced9023a5146e71023365062c826a93ef8182e289714226d5805.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7isVaFP Tbglvk1vQfNHXXg BoBIQpbvwh3hcP6 rPd1DHBW2Nec5Pt HWr3RMXSmWJV1s0 29lhwKW5ITwYHpl aM9lfurXpZ5cz9O 7FbSpEPSNt8f3Jg rmZti6eH1ZFM3fw 9KzXMfyBXKOyvJK vxMQLCNdHft9m6t 2Y7cnkZNtcbVNTG cN956tclL0Xj3Ss fTT1A1IXZis4OiA vV. END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegATNtClc GarycwByPD6fIiJ 6SflTdX3tIYMY67 Ocvkev5E228ksKj FyV6KjzRTFJrjRb cAopBasQ6R2zbk6 3ujP4AWSDdPndXO nchWuFJCGMwhUuy j5gMpe9Ylu5udRq Wp9BLMZkPywbX3q AVZY1CNdHft9m6t 2Y7cnkZNtcbVNTG cN956tclL0Xj3Ss fTT1A1IXZis4OiA vV. END KEYBASE SALTPACK SIGNED MESSAGE.

Commit hash for clean builds is dd08d6075a66153517cc200e5eb19bea8ca1ba25.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7jBGxFg MImXI4qbNjaGcPi ofZC6CwxWYMQclf PgIWZwTiqItzoTa 7Gxb82hknumxqpy sdCRZaeCuw44iGo r3Z4DtfOdZ4gV0B 7w923te4LxAU6ee UQcmFGnMAc2hDwR h4NnuU2pfDcbNue Bu0360P6uwBJnvV VCAOCBwJLzYctcL . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAU3PhZt V8UalKvof6o2Mz0 6Lc2nE7eWSmEO06 CIenZbvUQrWRxeG RBjeoyTOCmDyIRd mWE4ru0G35K89Uu QezZ6Z18KTeG8gr YPrkvUrhzHMvdp1 CoHi5WaqRPSn5Fo 4blTzu4YeMuazTN mmcXw0P6uwBJnvV VCAOCBwJLzYctcL . 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.5.0 milestone.