Solidity: 1.5.0 (Mainnet)

solidity/v1.5.0 is the mainnet release of Solidity contracts with liquidity rewards for Uniswap pools and improvements to staker rewards allocation scripts.

Three liquidity reward contracts have been deployed to mainnet:

• Liquidity rewards contract for Uniswap TBTC-ETH pool,
• Liquidity rewards contract for Uniswap KEEP-ETH pool,
• Liquidity rewards contract for Uniswap KEEP-TBTC pool.

Improvements to staker rewards distribution script include auxiliary functionality allowing to evaluate block number based on a timestamp as well as modifications to allocation scripts to accept start and end block height as input parameters to improve the precision of interval boundaries.

In addition to the primary contracts, we're providing the release commit hash (which corresponds to the solidity/v1.5.0 tag) and associated signatures from the deployment team.

---

Commit hash for clean builds is dafa5ed4a19cc6333dcf76e1fa8892ff777f1247.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7jQN13u 5nOwMeIKE468HIN pisbpTcpjVESycq oHiWR7pcWrMit6D kwRMlXx5F9Gll1L nD0imq94352VLBQ Ib27It4mNes206M tFwheC3mwdpVWpA bfZ9Xh9hOszbnRh xOBrTIZDmBvvsXi xk5sE0qVScOg1SX EKvDOWNCX2BZBMV . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAUPyYoY XBwxJs1KxFzVFsq 0KNfu7UrkhUdWWM VwJPMxowJHsXHQz tPx33ulK1fehu0Q 9xJiNmDmzyIJAwK ULKeSh9x5F4d4a2 uLdZfeAGAvUhYaf PF3dY87hkIlNhy1 43fifWUbV1ANdkj d4EcQ0qVScOg1SX EKvDOWNCX2BZBMV . END KEYBASE SALTPACK SIGNED MESSAGE.

---

Finally, note that the full set of work that went into this release across contracts can be found in the corresponding solidity/1.5.0 milestone.

Solidity: 1.4.0 (Mainnet)

solidity/v1.4.0 is the mainnet release of Solidity contract for ECDSA KEEP staker rewards distribution based on Merkle tree as well as a release of the off-chain mechanism allowing to calculate rewards distribution and generate proofs for claiming rewards.

• ECDSARewardsDistributor: KEEP Staker Rewards Merkle distributor.

The rewards calculations will be performed weekly off-chain and committed for distribution using ECDSARewardsDistributor contract. The code for generating the distribution is located in /staker-rewards directory and the algorithm is thoroughly explained in the README.

In addition to the primary contracts, we're providing the release commit hash (which corresponds to the solidity/v1.4.0 tag) and associated signatures from the deployment team.

---

Commit hash for clean builds is 848b7c29a6f2e129a198607c044c754164c568b7.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7iyk7pE hZGVRDAhiF55Mtk yVz8sBcOIxdcw4H GlvL7Gn6UKAKvA4 dMLVAgfR9s8nbFe 85KHiUusKxy7DMa vKMdZbrfkPl5bBf H7Oygogv9oPgbqN Qarr0C3Zpj1q3aS DwzdArTqnamxaRk K60bg0SjrKtngN4 UVfoN80DBZvdQpz . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAUOMcfU 6QVUldtSxTxdcUW JNBGuYZrly19O64 99dPhOSb7PPpJZj 2EfwzZVla9EBqDF hmiuO5ZXBUVNlkm W6QG4RqEU44XRsA KiiDCud02EU6jXb KW6N0IVth7R62XY CGLRQmXEWI1u1Gd GyhJg0SjrKtngN4 UVfoN80DBZvdQpz . END KEYBASE SALTPACK SIGNED MESSAGE.

---

Finally, note that the full set of work that went into this release across contracts can be found in the corresponding 1.4.0 milestone.

Client: 1.5.0 (Mainnet)

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.

Client: 1.4.1 (Mainnet)

v1.4.1 is the latest release of Keep ECDSA client, which primarily drives ECDSA keeps.

v1.4.1 provides a fix to a bug not allowing to start the client for an operator not having a minimum stake. Operators whose stake dropped below the minimum as a result of slashing but that are still in active keeps should be able to run and operate their nodes normally.

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.4.1; sha256sum is sha256:573d7f898121651e145fea50264847e05b939f87da14c04284296661907ef1f7.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7jD5PTz gdNuNHscXk0fNkS bYuo0pd04hkzJ0U jVLcKc9aOfWy0vp qlARfqyGF4jST75 iXh3I4TC9jBDcAY 80lnoYrQCWWi6I9 S4WU92uW0kRLJF1 mqYxfDSufLtUzSQ Kuz78QDhIFSORH5 4rBpZCbyk24tLnD xWZFC7l2u863oHW IGheGMW6Mjm792F XIE1HJzzhQpZg2j N1. END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegATVQ7kx BxtSWd2NV4I8Oon lmrrfbdGubk2WQ6 R0GPdYS8zxwHFpo ikOVBL2DCxcyoPH LvA9RSydYDtMk3o QpYtSuc60nmPBnp 4lq7sCd42q4nvDd 8biIz922XZbMVKN CIevOF11qT4JJEr B7whtCbyk24tLnD xWZFC7l2u863oHW IGheGMW6Mjm792F XIE1HJzzhQpZg2j N1. END KEYBASE SALTPACK SIGNED MESSAGE.

---

Commit hash for clean builds is a9bac25904ce71809548974663a5663b4419f273.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7iujEBs Dlgklr9tujK41ch Hfn9AsT2b3RXBMN Ls9HkWUbcAwdQ9x XQxAGlUtZZIKCuq 5a3yoRtGzmFPIRy 8npMoP8IhjCYR89 X0udBppEo7LTTAi TdxJP51kyPtUNvv VXjg0kTxr5Rr7Ip 7p1a30R5h8ILWm2 GYIHwIFuvdjL4uB . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegATw7vxX lgIdUE5PzucmDDU bsaS7kCHPZjQCsa MhUxaR0NnTW6ur6 gc8I8fxuP3B5okk 4hHlsKX2vDNVHCJ P9ifIWVYj89ouah kO2p09nfm4jTDKn XVPB3Z7CvlcNClE lqPnDcMgLrA91dQ VNNAt0R5h8ILWm2 GYIHwIFuvdjL4uB . 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.4.1 milestone.

Solidity: 1.3.1 (Mainnet)

solidity/v1.3.1 is the mainnet release of Solidity contracts for ECDSA KEEP Staker Rewards

When an interval is over, it will be allocated a percentage of the remaining unallocated rewards based on its weight, and adjusted by the number of keeps created in the interval if the quota is not met. The adjustment for not meeting the keep quota is a percentage that equals the percentage of the quota that was met; if the number of keeps created is 80% of the quota then 80% of the base reward will be allocated for the interval. Any unallocated rewards will stay in the unallocated rewards pool, to be allocated for future intervals.

Keeps can receive rewards once the interval they were created in is over, and the keep has been marked as closed.
There is no time limit to receiving rewards, nor is there a need to wait for all keeps from the interval to be marked as closed.

If a keep is terminated (abnormally), that fact can be reported to the reward contract. Reporting a terminated keep returns its allocated reward to the pool of unallocated rewards.

• ECDSARewards: KEEP Staker Rewards for September release.
• ECDSABackportRewards: KEEP Staker Rewards for May release.

In addition to the primary contracts, we're providing the release commit hash (which corresponds to the solidity/v1.3.1 tag) and associated signatures from the deployment team.

---

Commit hash for clean builds is e565fb3cb26f3f50e2e8034102569c5c7051a719.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7jPsdm2 S6Tk8YIxrWlkcT1 4OWuC3aQyJnXgUw XR9OFWhHGtNNlfx R5YVwPaF7Fzz446 fsd6QRh0Sqcdqwh 0osDJUCFZvKVMAo cF8uNF3kqFwTAJo 8J0r3DZN3XBWfLm WIR5SpkKc9fpgAB IpSPD0R53zdg6nv au5tb3VA7VDJYVN . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAU3Fjnw hCuDpzqcTPwhs3N M9YNtkdICeGUORJ KF52MbkAixGmM1y pqkoRDVEoIZ36SX LAIAOBrWwFPL5qg bTyGbD1BPY8YdCT SNA7jkmn8puPKF5 BCpMs7Loj9WguAh DNMTgFrBRC79D09 UsxZz0R53zdg6nv au5tb3VA7VDJYVN . END KEYBASE SALTPACK SIGNED MESSAGE.

---

Finally, note that the full set of work that went into this release across contracts can be found in the corresponding 1.3.1 milestone.

Client: 1.4.0 (Mainnet)

v1.4.0 is the latest release of Keep ECDSA client, which primarily drives ECDSA keeps.

v1.4.0 adds additional snapshotting of key material so that even if there is any possibility of overwriting key material on disk or losing key material from memory after it is submitted to the chain but before it is written on-disk, all key shares of all key generations are captured in a separate directory without the possibility of overwriting.

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.4.0; sha256sum is sha256:a83a6ecc801ffe199aacdf8609a6044cc290b6e9bce1a049aac65de8b9cb04bd.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7iW47aX ui4YTnmW9Gl2NeL dv5JSENFyhrsau1 CwWl3RASH7U9Dxz neHFdZ3PVjjVMtP tVNBQmXeXZQbDpT lSniyqt0OKxSh2a qVJNpvRTi2zaS8D UvT4vmTF2gJwPzR o83hO8yP5QkgkNd 0b7dWDKQfc9ML5r 6qFQl1cbxYzGTDd ZUQoKWAjXFF4ogU dFs2O9pae58gtjN 7E. END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegATpeR9d peLpQyenGSaIDHy lNUNH3nteOz2Wo7 JZ2oi1WFQJMO4yf QNCtGgZMpmsBpDh uale362D7FiEkBQ Ry8Ff9I3ZjyBuZv 6AKT8IVnxm5MG3Q 9BXQHAiQpDR5Q6j EA8aIfyV4Rkq5Ct 6LjYUDKQfc9ML5r 6qFQl1cbxYzGTDd ZUQoKWAjXFF4ogU dFs2O9pae58gtjN 7E. END KEYBASE SALTPACK SIGNED MESSAGE.

---

Commit hash for clean builds is e9f166bbc5655fdc0037f49ca90d19a3d7e74976.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7jYx7Mj pL4DCIkh9GBSaJr xb11nq4nNMG9BeO BvJQdSfHaG2gghl 6CVrhE220G02Amn VDS6uE465qb1qiQ UEK2johtQfTjbrc BGvisBCIJ0QbgCI PzHaQJdnBmDipTi kTzfs6Td04M52xU Pn9bI0TmE0iz8KH nDIu7kQVEnEYwyM . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAUZQJ7V YwO7Q3e6rCQDpu3 g6yv9DZZMtM18Q3 01w65Nx2cFr0RKy vVRjy4KCy1fQ1mR nw1EFTg0Q7z41LT x7WORAoVSj8rqjE weEmXst1OY0ya2R AhGExkhBuDPWuVC sScO3gjxn7N9sEU ulkZw0TmE0iz8KH nDIu7kQVEnEYwyM . 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.4.0 milestone.

Client: 1.3.0 (Mainnet)

v1.3.0 is the latest release of Keep ECDSA client, which primarily drives ECDSA keeps.

v1.3.0 adds a possibility to sign a digest out-of-band using a command-line tool so that, for example, a recovery of BTC is possible in case a tBTC deposit was liquidated.

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.3.0; sha256sum is sha256:f22474ad0c161401f46e321124646c3abbd5cc09560c7598fabb14ec2c218626.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7jz3Flj ib7SOW6rcJeXQnB wXoYjeEnYfOMROJ l16upr7JXnqPvPb BhpwDqHXusgak1Q 9UM3vWdeqYDiHHj PyaI89MVRaPP9Js DLxyuneE1NYaVnW JITahUWYOl0VT3p pP2htBL9ZIsRFmU 1fas6BfEB9NndmX ZfV6QwQnfZX8Yz1 w3tndcOAjizQOPE tLY2OP0ZKzgObxj Ow. END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAU3temS hl6ohqGFZxVuYhp CitMA4B2PcoAYzP WjG5GYhhQF0et9S BJHUx5U9TbuU2yt SZAbYjmLBs8S3LF TwViEhRZRHIGg5N REcGGdsVcpBwo01 h5WJ09cbhgMOORM uTf1iP8QSq8gRM0 DZtRKBfEB9NndmX ZfV6QwQnfZX8Yz1 w3tndcOAjizQOPE tLY2OP0ZKzgObxj Ow. END KEYBASE SALTPACK SIGNED MESSAGE.

---

Commit hash for clean builds is db9fea58af6da6f0bdb6ae99b834eb5860920133.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7jR6LC0 MHWTvuNKAclENN7 uLPXgBDwWwHnLXo pOZgq09L46SPx6s AbNLjsQjmVz7gJs bK3idj1wKx9wsK5 XwoE5oG42nVO7JV hBz3DO2AsXA2ZTi fg2z9ZlAR2nGz7W hW8BqfPZEZd3GR9 DTMMn0Tgwns1eLM 9U4YKXq5D08Sjbf . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegATUsLyw ksNxw8VsEqT781c mn4glNQcUr1nd3k EbF0niWVlHC6vJC SB25cpNcuXqutvS x7Z9VhxAFtZLEKM ergxHT7NcMcy0rm sadoIFhTZETUmyI JBA9srQ2DAJniSy shWmikx9IKUFwOu 6IbjR0Tgwns1eLM 9U4YKXq5D08Sjbf . 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.3.0 milestone.

Client: 1.2.1 (Mainnet)

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

• Improvements around handling duplicates of Ethereum events triggering new keep creation. Ethereum nodes can send duplicates of these events in certain cases, including reorgs. Certain specific event triggers could lead to multiple DKG and key submission processes competing for on-chain submission, resulting in potentially conflicting key shares during keep creation. In rare cases, this could lead to loss of funds. This issue is now fixed through better deduplication of events.
• Revisited log levels of client-side sortition pool registration issues and around key generation and signing event duplicates filtering.
• Longer delay for sortition pool eligibility check retries.

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.1; sha256sum is sha256:50386fbfffde9e5d9250db9ee07ac94065707a3874a4957b709696e4b9e8093e.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7inQIYe N4QRt667IxEkemY PZ03icu8YscPprB UqIwkIvX66AdDQx UDa8GmV5MiglkkB oiL2o7RUaAdKKrE iP29p7zscui8E0T BVf2CLU9iLqnDaO BQR6H4QNrwIalD0 W4PwgXOvG8cArDk D9jH8DbqHytvjBI Px9q3ErPSq3z0dv DkJbnVEma6YkSJr hX42O8PfuxO9vkk Td. END KEYBASE SALTPACK SIGNED MESSAGE.

• @Shadowfiend:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkAA9fdX h3PR4kiSBsxaoE3 9WyxA9pNLCah0b4 uFaShwCkPRGoQI7 qQyilDgM9V6BSj6 ELbsXuB6ohm0e0Z k57z4fSLveqIjtT 1slxYtE5dUW5J0r VleuzXFNpWx3Enh gFSVmTWgTCJNRmR RCvTxEg1uLXctfx FMxmbyBIyZfMGrG H4Ck6LmxWaTpe4o N6giIDbqHytvjBI Px9q3ErPSq3z0dv DkJbnVEma6YkSJr hX49rek15BDl0T1 uLC. END KEYBASE SALTPACK SIGNED MESSAGE.

---

Commit hash for clean builds is d394fd3b882b0b1df42190c5fdcb3ae217fce130.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7k36cA7 zJUaSYMwHfWTmJA 1krRuMFr9JXujUz MKvMgyem7Ifsrhe cyAktEqdefyyPuL rheVvRCw1MdzGEz mLE1OaILFdzxt1R fMuZ2le7vj4GHKZ 7eu2y34t5QR5ulz UdwnHNHFjeEv0nO iVc6S0pTcbLz7mR 3jtGKXvo4NRakFc . END KEYBASE SALTPACK SIGNED MESSAGE.

• @Shadowfiend:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkAA9fdX h3PR4kiSBsxaoE3 9WyxA9pNLCah0b4 uFaShwCkPROc3LD 3HaKqYMMGFyqTv4 1GXxJJcAEuuJT8E OMWQBpeht4FNzu2 lEs3krJ6HNdfExp ZvNVKvpYg6LTiq7 8X3j6Km6OlzWqL8 0XQUFa4HqFQch0s ChFWegbDxdOUKWe bfz8TWphnYcHChE TFk0W0pTcbLz7mR 3jtGKXvo4NRakFc . END KEYBASE SALTPACK SIGNED MESSAGE.

---

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

Solidity: 1.2.1 (Mainnet)

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.

solidity/v1.2.1 is the mainnet release of several Solidity contracts that have received changes since v1.1.0. These are:

• BondedECDSAKeepFactory: A new version of the BondedECDSAKeepFactory contract that allows allows applications (like tBTC) to specify a sortition pool's minimum bondable value (this is currently set to 20 ETH for this release) and prepares the contract for upcoming ETH-only operator support.
• KeepBonding: A new version of the KeepBonding contract that allows deauthorizing sortition pools, enables the withdrawal of unbonded value by the grantee of a token grant (note that unbonded value is still sent to the beneficiary), and finally prepares the contract for upcoming ETH-only operator support.

In addition to the primary contracts for ECDSA keeps, we're providing the release commit hash (which corresponds to the solidity/v1.2.1 tag) and associated signatures from the deployment team.

---

Commit hash for clean builds is 5418b2bfb2260e72bfd1750b9c060fbe4a2b7ec4.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7jSFpCo Bu1Jf6EKwAtb49m Kena536GlMSvbUy 2cAtsmkC9ffNgDx Cj7L8cBeXVX7ukw j3CwRLYqKsdgahl Nx14jiNFiixceKp O82eKSfJkQDHhXC MyNVQCZ9KmZQfPR MTwmid1fzQ8H2V9 xDDTJ0P6XgWB3ko lEMxlLZIm0fSGLk . END KEYBASE SALTPACK SIGNED MESSAGE.

• @Shadowfiend:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkAA9fdX h3PR4kiSBsxaoE3 9WyxA9pNLCah0b4 uFaShwCkPRqnE7g u82yS2lNKfYUyx7 1jwPGviAUuy4kmH 2cwR8RSrK6rMFwb vOCdg8aaxicRDgx 99MmrGfFkdRK4Nr cevC7YIxnm2FiYd OOTStrdOVSvULbO 63CmwDmEoTNCIzi IlGFjG54jQgkEt8 CALuX0P6XgWB3ko lEMxlLZIm0fSGLk . END KEYBASE SALTPACK SIGNED MESSAGE.

---

Finally, note that the full set of work that went into the 1.2.1 milestone across contracts and client can be found in the corresponding 1.2.0 milestone.

Client: 1.2.0 (Mainnet)

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.