Note: Henceforth release notes and version tags for Solidity contracts and client will be managed separately. Solidity contract releases will have a tag prefix of solidity/ and client releases will have no tag prefix.
v1.2.0 is the latest release the Keep ECDSA client, which primarily drives ECDSA keeps. The most important client changes since v1.1.0 are:
- A new metrics module that allows monitoring the number of connected peers, bootstrap peers, and the health of the Ethereum client connection over HTTP at endpoint
/metrics. More details on enabling this are available in the sample configuration file. - A new diagnostics module that exposes diagnostic information (including a full list of connected peers and information about a client's network id and operator address) over HTTP at endpoint
/diagnostics. More details on enabling this are available in the sample configuration file. - A major upgrade to the libp2p library. Note that v1.2.0 is not mutually compatible with the previous client version.
- General improvements to reduce the number of calls to the Ethereum client.
- Implementation of an Ethereum client call rate limiter, to help reduce instances where remote clients are forced to rate limit the Keep client.
- Improvements around the retry handling for sortition pool registrations.
- Configurability around the look-back period and keygen and signing timeouts at client startup. More details on these items are available in the sample configuration file.
- Finally, thanks to @alphastorm, a move to Alpine as the Docker container runtime that reduces our Docker image size by ~90%, an order of magnitude improvement 🎉
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.2.0; sha256sum is sha256:d5f3bc8c43bfc3350797739b77afeec4de90eb7763b83bcd7e8ed03cfd503251.
Signatures of sha256sum from the deployment team (verify these in the Keybase app):
-
@Shadowfiend:
BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkAA9fdX h3PR4kiSBsxaoE3 9WyxA9pNLCah0b4 uFaShwCkPRi4afT 6XYiaHeODosGwxe Qgg5D4IYk2uj5Kv HFeZQ9V72xzebYw jxtgdNqVXDQiWqR 0AY7OeaAqrOHRWV 7XC2msOqmD6CQxu lRT0QcfbyhrktQN eBdK7Z5fsV82T2M 1ORxZ1Xencmz63l MDmuBDbey3MdGO6 arH6InRxGlJUY7c p9DQGHmTQ9tXi8l rns1DDX8dxlDZtG Ft. END KEYBASE SALTPACK SIGNED MESSAGE. -
@pdyraga:
BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7jMQZMB fkvcJWFbqVdfYjP Q7UBhP9C8j4kOcB YY7mp6UN4MdWCe3 MBX2OYCkD7Lrbmq y4FTNsVQnxPN5NU kOSMqQ9rixFkMKb KrwYBoz6wTsjMIJ 9pa7yxmtBcCAr4f yCSpeylUAzIGHQt kUjIJDbey3MdGO6 arH6InRxGlJUY7c p9DQGHmTQ9tXi8l rns1DDX8dxlDZtG Ft. END KEYBASE SALTPACK SIGNED MESSAGE. -
@nkuba:
BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAU2FeCE LdQu8USpgGC40EK DY83QwUcMmuuHG2 WBh9BXTlnymdI4Y Q63OKpiLl3bNsLH oWwBxd49pbROvn1 gbhvfljS8Yp9k1l dMYlL7eRJeiXavM bplbqt1d2MUzyJC QPHnrk8yzq1xUbC QpMP5CbyoM2ErWT 2tt145NUqohxs9a pQSOQbR0536SSu0 a3PCap2PD9cr5x0 7ck943gCSI5. END KEYBASE SALTPACK SIGNED MESSAGE.
Commit hash for clean builds is fb48534c25f93c41c14f9c5602390dd066705393.
Signatures of commit hash from the deployment team (verify these in the Keybase app):
-
@pdyraga:
BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7jN7h3A CFKJhXz24UweM5b 9gPbTUBRWWnc6Xq Ze8lLyTwDmiyiX5 rDPFZoj1qikzMJh mUDZHwlWZlN29w4 K8V1JjsRGYBhWyw D4hJ4RVHoWdnxZi O7TN6qeiFS5fOtC l3kLlStdX5F4CCd cA4TT0RbrXczj0v s4DDcMxh2Na9O31 . END KEYBASE SALTPACK SIGNED MESSAGE. -
@Shadowfiend:
BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkAA9fdX h3PR4kiSBsxaoE3 9WyxA9pNLCah0b4 uFaShwCkPRJD2hG uRNJqK5FQwvRgiy MJj2cUjcGUy5LrB ZmjSTUEnKOnfs2T 05aIYPHYnNtEX7G qmGOwV8Xdzbqjjr PI7zj1Nc0y2OoPS bA1vPV5cyYecl0z Ha6rCTNObnajU2r OwnJseL940qK1hc zja7v0RbrXczj0v s4DDcMxh2Na9O31 . END KEYBASE SALTPACK SIGNED MESSAGE. -
@nkuba:
BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegATS094H UXC6cMCy92Ufd29 490EHVUJkYsdkNr RtcbMT0txO56BsB TbrwZ8i0mDjq19z n4kCBVZ9rlT8xcp JIrlBBzKsnfCmOu BKA8Vp6i6A0h4Bt 1Wj6s3UzYtxRaeu XajKTxnkph4RfGe pvWCJ0RbrXczj0v s4DDcMxh2Na9O31 . END KEYBASE SALTPACK SIGNED MESSAGE.
Finally, note that the full set of work that went into the 1.2.0 milestone across contracts and client can be found in the corresponding 1.2.0 milestone.