Client: 1.8.2 (Mainnet)

Overview

This release incorporates the recent fixes from binance-chain/tss-lib keeping compatibility with the protobuf message scheme used by mainnet Keep ECDSA clients.

The client version can be updated without any config changes.

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.8.2; sha256sum is sha256:fe960628e3868daf82812931f719e71311680f7212ded351711dc46b92f0862c.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk8SRO9e gN94erb57G43YvY asc2ypx7KtJhJpq tOozFkj38oNDZ7H 42RTevG6TwAKXAd 2nMp9Ox5SINJpSk hZSEwuMEfVfcFi3 NJb3ee5HzKDvbnS WcyMKX5Wc1x8u7W Y2H3S40BeWEa0oz f6HeXFcBkxTvmww mLu8gbsF0gz8vPB q00i7eb5NS0JJ7s 5r2oLOEqEgIqK5p HjnFyBd8MtES9JR BLx1ndEjOKViK7H YaD6BSKo9ZBmU7v 9jkbnQqd6BP. END KEYBASE SALTPACK SIGNED MESSAGE.

• @lukasz-zimnoch:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk90sDpX wIX07Cfy2Yz31Xq 8mliRvTpoVIDeBV VZiP1JZd9abl3Yb Ko7nGagbTD3JSdO eEZuoAvqfnKaAdW R3edNjP3qsFqgJA C0sbPT1YY1ZSovI SmID6NmctuMNu8e kxk7G7CbWVr3yOu 6nyO1RmA1SZvFrq Pnn6iM8sEAwq00Y 1KMWlBnO8QuW5QK 46v3pOEqEgIqK5p HjnFyBd8MtES9JR BLx1ndEjOKViK7H YaD6BSKo9ZBmU7v 9jkbnQqd6BP. END KEYBASE SALTPACK SIGNED MESSAGE.

---

Commit hash for clean builds is ba59bc0e1eff6025b09812a2b82b1541f2a8983a.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk8SRO9e gN94erb57G43YvY asc2ypx7KtJhJpq tOozFkj38ooKx95 JrfS0VQ6CfwDZKE cMsNEzbWmvmXaq2 2QQJ1GN2JxBzsNQ Ot8qDmkYOB51Xwj JYDGAujZeaGelbd w449Kt801dQvD2T 9nr3DCSKwkK0c5A 7cWgQDSt4de6Nim iZ6OidNbB4LYCOg f6pHe0oQtuxQjHf 4D3OA3MqLbUxSkb . END KEYBASE SALTPACK SIGNED MESSAGE.

• @lukasz-zimnoch:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk90sDpX wIX07Cfy2Yz31Xq 8mliRvTpoVIDeBV VZiP1JZd9bG02ZF wF7mjrFb4CXWTt8 K3lUkhBFz7xRq1o O52kkMuq9ixAKNZ anFQqcsUcFmOD3c alwWfwYB2mlFJWs W4iIZBjNjFaZcVG SA1INwNdTrRW7DW 0NY4ITDliGQGBy0 Cf4x27AYZfTpvgi AMjw20oQtuxQjHf 4D3OA3MqLbUxSkb . END KEYBASE SALTPACK SIGNED MESSAGE.

Solidity: 1.8.0 (Mainnet)

solidity/v1.8.0 is the mainnet release of Solidity contracts including KEEP liquidity rewards contract for the second version of saddle.finance TBTCv2 pool: LPRewardsTBTCv2SaddleV2.

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

---

Commit hash for clean builds is c437dae28ca3c994df38c05177c4aaece3d7e1e7.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7injUSX rCneq3sv5uRYU0g mYJvEThshfwgEMk 5NWHsggMKO8q84i eMhZmTsZ4RGlqFQ 3E5NcyMk8JZGJ59 KFvo9bwMJz07p7W RsrpJ7yyg6jYIjW xVVkAAv3zMjp9sS dPmm33zDqCbc4uL L86yW0RbEnY8J35 kHW4bVIe0PxeXxP . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegATeAym2 MVZyyxw3xQM494K T58ejOGALJRkD3p VDx1lZrrtjbzt96 4JuWIv5N6oVrKsR xFHc6CBH8Fl3jsA iHov6Hjz5qswH3w 1mR0F6UCdjKnN2B CWKGYjF4Y7e3su9 aofAcWA7fbCZZI2 9wBV20RbEnY8J35 kHW4bVIe0PxeXxP . 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/v1.8.0 milestone.

Client: 1.8.1 (Mainnet)

Overview

This release incorporates the recent fixes from binance-chain/tss-lib keeping compatibility with the protobuf message scheme used by mainnet Keep ECDSA clients.

It also adds support for EIP-1559 dynamic fees in the strategy monitoring transaction status and updating its parameters to have the transaction mined faster.

The client version can be updated without any config changes.

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.8.1; sha256sum is sha256:42a2d8d9e86ef225b4fb0d00f9ec1793ec666f5237531dd19984fe278823b2ef.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7iYa2tJ d2SJ48Sz4IDLz5L YxXBf8IkKnbLQJr HggYxfzmFne3nku 61bVnwUdOafOKoL sMFaCDXeBAe0L7C WQ4wX1nGHUCmP6A q4vlqqFPb3Fhtpq LG4TOigbe3ovOYk PPoxtGtsLlwhKvu HfvtcBQToL6U52J rrURmtjtbZpqWSU 9Cu1F3DLM1wN8eo ew91BV7YH1indCw T8. END KEYBASE SALTPACK SIGNED MESSAGE.

• @lukasz-zimnoch:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk90sDpX wIX07Cfy2Yz31Xq 8mliRvTpoVIDeBV VZiP1JZd9aggNU0 JQfJEpZGj1TTQe4 oLrvMNFSOwkKO4p eRE83LAmnpo4JD8 2iGi4nfJUgobD5l bfpUw6DHLBY5E3j nQz5cEdNmuoveeW tkwoqEEGAHrqeAh iZYSr4LT3ITYyAs gec8XmeEeMCWewQ LHNnYBQToL6U52J rrURmtjtbZpqWSU 9Cu1F3DLM1wN8eo ew91BV7YH1indCw T8. END KEYBASE SALTPACK SIGNED MESSAGE.

---

Commit hash for clean builds is 5031a0a8c52c2495644a2d94efe9a3efd38f2c80.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7jMzKsj Ktt90ZCzSKjGSUc f3KzY4Hy6XZs79n iiPvhpQWoP8EWvb 2X153EhgcI3ylrb 3FiFZ2D0qWIXnmS V7mt6Ocief6cJZI VSuCcX6arzRhjUQ gJK9DWbGYlajgFb JGeX9DqR7KuB1O5 iB9nQ0TgJwXw3Zg qrFY6rlkeCtG6JE . END KEYBASE SALTPACK SIGNED MESSAGE.

• @lukasz-zimnoch:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk90sDpX wIX07Cfy2Yz31Xq 8mliRvTpoVIDeBV VZiP1JZd9aUN0au 2JuG8H5z23KXAOo jnRoV6oGjWRVlEj IbHXr8BfplYWVqS mBgYs8JHOcf89B0 a5Q5TPrEXqeEX9v kUicdzAeznZRvj1 4BBxdqYCibuu31f H3wZ6xTKJuVSWYY a9mf7a6dzp8IgaJ vrz7s0TgJwXw3Zg qrFY6rlkeCtG6JE . 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.8.1 milestone.

Client: 1.8.0 (Mainnet)

Overview

The most significant updates released in this client version are:

• implementation of tBTC Deposits Liquidation Recovery described in RFC-2,
• refactoring to enable multi-chain support,
• support of Celo blockchain #686,
• building Docker image with a non-root user #771.

This client version is backward compatible. The client version can be updated without any changes to the configuration file, but we advise aligning the configuration with the current requirements. Please see the Details section for more information.

Details

tBTC Deposit liquidation may result in an ECDSA keep securing collateral being seized and the keep termination. In such a scenario, the ECDSA keep signers are in control of BTC that can be split among their owners. For details of the required client configuration for this functionality, please see the tBTC Liquidation Recovery documentation.

Please note that defining Extensions.TBTC.Bitcoin properties in the configuration file is optional. If the configuration is not provided the client will still be functional, but In case a tBTC Deposit liquidation occurs the client will not perform the recovery process.

The structure of the configuration file has been modified. The address of TBTCSystem contract of tBTC v1 is expected to be provided under ethereum.ContractAddresses.TBTCSystem. It is no longer expected to provide the SanctionedApplications property. Another property that was removed is Extensions.TBTC.TBTCSystem. Please see the configuration sample and parameters documentation.

The client was refactored to enable integration with the multiple chains. Additionally to Ethereum, it implements support of Celo blockchain.

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.8.0; sha256sum is sha256:91870c3eee1c1ff1c047b6766cc2a8d5728da32bb11d4f96252cd51d8e8d79c8.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7iWf2mS THB4EqFQLzj89cj m81UvPhmIljRV24 Qj9pDYysAGgfSll VwJct8RRCParsGR ZYeW27dqmSUeurp IlLk6urZPaBdV2Y WZbM4hk3hK5oZDf 9oF4NjSbMgYgBIC MiRm29pPulrhwry 8gOSUD5jE1LWvPB CxuwrV8N92yCQ4g Cno5e0QQonhQZEE s5N1AIK3JEpVneF Ls. END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegATcOzdd doelxKshbpkrkhI Qz724JwkIViEzGv 1CIf9pNhcE6VX4R nLkr9VZZlHKZhde 0A0kEsMq9fdKoq3 jZFNeCsJdULlsZg O4cnFMBSmMMJZKL 4KqGWlwYacI4r9K FJ5kWgSj5GvHyjl I6XMED5jE1LWvPB CxuwrV8N92yCQ4g Cno5e0QQonhQZEE s5N1AIK3JEpVneF Ls. END KEYBASE SALTPACK SIGNED MESSAGE.

---

Commit hash for clean builds is e486292673f9681a4b19ac14e62f5d23645c1335.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7k395mr r6yQnO0fyrOWQOx 9CkHZnIlX8ZNW51 aKcPM3QvdpxR5YP OkmmD4EA460OQHB 4vCFsi3rrb5z2O1 RbD8AOSW3oVDI2o gP8aA5j0mkh9d5v Ji5hrEu6lFZUguI 1bx73XtK193zD11 i6s5b0PWxCsmGIn LApKso78rAzUIKr . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAUMohfH Kqs7eQL6368idcx Os8KEpYX1En44Xx ZojDCK9V59JMxBP juk0xAyJxXpMaaX tN6RGFt1V7cMK3O fAWEWa6AndjY8X4 7bTV0zPcOavj3lt 368ZnEFfOM1sgj5 Jf3rvZSZ7cpQ2Cz UEcb50PWxCsmGIn LApKso78rAzUIKr . 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.8.0 milestone.

Solidity: 1.7.0 (Mainnet)

solidity/v1.7.0 is the mainnet release of Solidity contracts including KEEP liquidity rewards contract for saddle.finance TBTCv2 pool: LPRewardsTBTCv2Saddle.

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

---

Commit hash for clean builds is 47a35f187a528fd9883a07a886f59f1b36479bd9.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7jENjwL tTy9BylqqWMZB6S 1U3TTj72Mzcqy6Y Kk0mCJ3nZVOsOzI vuI3sjZnEAH25BG X8gjldF5K8ARI9X BqnkuasVW2ohDAI EVYlWFAgz0vLxba fio4xcka9pqcYMw eLPNlgHADGyDuUH MtDvj0oRdO593rP d2lT8KviEa3Z2Gv . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAT3qb2a lGLeXFO5l4FZ4k2 RagBbTJF15m7ud6 SFQSrlmWXgDw0eO ntxXzAcEusV4HH8 dYiQ8rcbc0u68fA Z68t94yOxEGcziX 1pCMXoeK0n4c5U9 RgX4I87wSYxGAcb JXgRWVJlweXFXIx Ya9Qd0oRdO593rP d2lT8KviEa3Z2Gv . 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/v1.7.0 milestone.

Client: 1.7.2 (Mainnet)

Overview

This release is a hotfix improving on-chain information caching in the ECDSA client network firewall.

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

Details

v1.7.2 is the latest release of Keep ECDSA client, which primarily drives ECDSA keeps. This client release improves on-chain information caching in ECDSA client network firewall by storing GetKeepAtIndex and IsActive on-chain call results in a memory cache. Additionally, it introduces a synchronization mechanism ensuring on-chain calls executed when loading information to the cache are not duplicated. The changes let to optimize the execution time of firewall rules and are especially important for bootstrap nodes receiving a significant portion of connection requests at the same time.

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.2; sha256sum is sha256:0ce7cecbd951cf6b6748a39a814cdb078c85f95dcbd38247983e41a2742ddfaf.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7jTIlse w97T06222xWSZQO aYwlbUa5fBpNjMN keTO8MgjLCRcSZm k6wylwmIwnGFMK9 tTTpNWwiEGbxnkl ZF4zPTaqNouWFYf IdoSiQXI8C8M05x taMDZB8Ub4exYtn U7jgX7UebQ0cl9Z M8I5rDbbQ8Kqje2 oPs2RgTgMz1WP08 WAE8dwl6efBtWTG b8T2IGdnCGPKVtZ KA. END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegATWCCyx 0gFtM7ECNMhn74Z DY5MPRsFjXbHPOV 1qxKrSsL0R5of5R aneAQurs6hhn8d9 ab3tBmhgurCno5b cmYnuOl3aeAXnrG 2pMEz7hcjwBCxaI e6klAukXdivrXKi Dvfeo9BgWrDPfsh zsjytDbbQ8Kqje2 oPs2RgTgMz1WP08 WAE8dwl6efBtWTG b8T2IGdnCGPKVtZ KA. END KEYBASE SALTPACK SIGNED MESSAGE.

---

Commit hash for clean builds is 057c0e7104778b6d544ec29f73e35b06a01584a0.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7iYph1B vQg8yWOkE8V4jdM R3UzKkFEY9pZzgm e06OkpwZ9oavv5l fyWgrntCKCfogjV hKFUDDascZRiCEQ wxiM7tRn8rEBFww Km8DvQ8MdRF87HC 0es0tj0w5j9EBi8 nEYTJ70VkEapJz6 yyllq0Tma6clb0w kQ5tqolKl4sxd3I . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAT2tvd9 gfChdpOWJk9DjPK 5ISQL55MIjc6acm 4n50INmMPvEJr5g RtVyuvBfORuIpaS phg5xYJKA00manJ yXIzhrYsyRU77jp Hz862rF1GsjaMfc Ppc8AYaUTQSSAOw dyDvgRmvvtCnwAa so9Pm0Tma6clb0w kQ5tqolKl4sxd3I . 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.2 milestone.

Client: 1.7.1 (Mainnet)

Overview

This release is a hotfix for EIP155 support in the client. It also updates the default max gas price and improves parameters of public key and signature submission monitoring loops to optimize gas expenditure in certain cases.

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

Details

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

• Transactions are signed according to EIP155. go-ethereum v1.10.0 has switched to denying non-EIP155 signatures by default. Operators running Keep ECDSA v1.7.0 client version and lower had to provide --rpc.allow-unprotected-txs when starting go-ethereum to allow the client submit transactions to the chain if running go-ethereum version >= v1.10.0. This hotfix release of ECDSA client brings support for EIP155 signatures and the client can now work with go-ethereum >= v1.10.0 without unprotected TX allowance.
• Increased default max gas price to 1000 Gwei. We have recently observed an average gas price on Ethereum mainnet to peak even to 625 Gwei. Some operators had to update their configurations because 500 Gwei default max gas price was not enough. Note that increasing the default max gas price to 1000 Gwei does not mean that every transaction will be submitted with this gas price. This is the maximum gas price the client is allowed to use after several transaction gas bump replacement operations if the transaction could not mined in an expected time frame.
• Public key and signature submission retries are now less aggressive. The previous parameters could lead to increased gas expenditure, especially in cases when the max gas price was too low and original transactions were not getting mined for a long time.

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.1; sha256sum is sha256:72374970f7fdb8443d2bd2e6eced979720f274b17253ea8a4154fbc3a25fce5e.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7idvas3 afe2bSFVaF68oaY o3m68KotNltjn53 fbaJmsF8fA5EGOO xtqnVfJTgbMrJ6D xdbhDkEQIgrjYJD ewAyiAPOdVQIuuQ k6XZFlUSzbLUURm sTn6UgRdjF5rSC4 Cf9WLa5wuinrRC8 vyDmkO02INIHKRS x5F7Ekjadq4bIBc nnTT4JTUxPWdDku J3S2LCYUaCQMxZh QL. END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegATb0JaK 5t0XlgsOJEDgtfz pNoRyxdxPUZSmmc 6AX8OByrYQPRYPi 8mEi3oj0UmT9Qfo gct9RJctP0VCIFP rQj6YLagtuLQTC7 DV0GCDKCRj0gXG4 uqf2BXUHYkPGfAN RZF8b91Ulr8laOd FqYoUO02INIHKRS x5F7Ekjadq4bIBc nnTT4JTUxPWdDku J3S2LCYUaCQMxZh QL. END KEYBASE SALTPACK SIGNED MESSAGE.

---

Commit hash for clean builds is 0ce2baa5a5aca5647ca3b99c336feff7f77a8867.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7jCVB5P XOCPylYnBVkZ2PS RXiIJa3eg6URmDu qBN7YdP9sQbG9XF wryX2PuFObwzWBM 74fpNr6fDz1j5EY kMdWlncqVJtZjwD UFZoWvxX8CxRxPt pEqhP125IHY7iMY 9sTBrAqilMa7Pho dctwH0TmCbsbg3O EbSvbK7iTe1xYc3 . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAUfXGul TJxt8Qcl4K1Xztc lDzwSEnEsLgSw2Y 0WaMo5dkVohGRy8 jtnnEjYeKv3IpGp qPZX9s2TnZUrlkz ylFQzCtrIOdMxGt WmySqXorYa15xsB drAkX6aBXlJyPzK OKvmjvOz8whFggs oDMQT0TmCbsbg3O EbSvbK7iTe1xYc3 . 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.1 milestone.

Client: 1.7.0 (Mainnet)

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.

Solidity: 1.6.0 (Mainnet)

solidity/v1.6.0 is the mainnet release of Solidity contracts including KEEP liquidity rewards contract for saddle.finance TBTC + Saddle pool: LPRewardsTBTCSaddle.

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

---

Commit hash for clean builds is 1cac69b5f19b76cd953f93f2d788d0b6fa8811f3.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7jBHlEX PhQw0ilKsU1tdlw ancYlhWQnLzH9Ex Vo4AAyxlnrSAGYa WDiYOhaS0ZSPBlM DnknnDPmaCdY1XR oaD4FCX7VbnhyyK 5ve1eKqEfePjxZl OXE2D4XVcej0ydq OstHC7m9FfBe2Uc fxnWt0r1kw2fvJL PZEETfccA7qfMod . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAUVu9AT xfvinjTftpW3oTv ZKxgEUaEgrujoQn ztzQURA6aAt2O5R dSoV0uXxrj06qbV Vj3p1lmf1aFXe6S aTgLu5VnUYl3XHs 9G8wLcggg0Wzm8R 3wDoTCSd9aDcaDh 2lhqv8t6tccHp7f yr1rX0r1kw2fvJL PZEETfccA7qfMod . 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.6.0 milestone.

Client: 1.6.0 (Mainnet)

Overview

This release brings two important improvements to client functionality.

First, the ECDSA client now prints Ethereum addresses of operator nodes who announced their presence and signaled readiness during key generation and signing. This change helps to diagnose and react to potential problems before hitting a timeout.

Second, the ECDSA client now has the ability to monitor pre-params pool size for a key generation as one of the metrics exposed. This feature helps to profile the performance of the machine the client is running on and to diagnose potential performance problems.

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.6.0 is the latest release of Keep ECDSA client, which primarily drives ECDSA keeps. The most important client changes since v1.5.0 are:

• Improved logging during presence announcement and readiness signaling phases of key generation and signing. Ethereum addresses of operators who properly announced their presence and signaled readiness are logged on INFO level. Ethereum addresses of operators who failed to announce their presence or signal readiness are logged on ERROR level.
• Config file values for BalanceAlertThreshold and MaxGasPrice can now be provided in wei, Gwei or ether units. More details on units are available in the sample configuration file.
• Key generation pre-params target pool size can now be configured based on the server's performance and key-generation request peaks it is expected to handle. More details on configuring pre-params target pool size are available in the sample configuration file.
• Key-generation pre-params target pool size is now available as one of the client's metrics.
• Fixed bug about not exiting public key submission monitoring loop when the maximum number of retries has been reached.
• Reduced a signature publication delay to 90 seconds to adjust expected transaction confirmation times to reality and improve the clarity of logs.

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.6.0; sha256sum is sha256:0290c708bb643e7e8c0f52bd64eb4f995e3253389ab8f33e902ffef575bd9a0a.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7iivNUV Sb9Es1T1Wg9x6EP NTEZt4ObuP8aiXW utA8rsXurhHm2Dr kB5py1SaEV1nutO 8WsNuaocNQDeO8S jaZlXBTxXaU4cPV XtZjr2LvOzzPlmH DAxe7vsVrlx6WY5 9QI1la1KMsj4OU0 hbFvWNKYpytGXZt ziQE10qbg3rpNln XrOinSHvXIMOmZK NQj2PbSWDbekpj0 3V. END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegATcCqxU GHHTM2CGCjDCeaV b9OpEI3qaHBmgaJ nfuQVVlFgIRfPxH MVA4HgSaKQLSHU5 YUtbLDxQSSrGEyK QR50PKeOJ5DQ57n a0LQnYv2I4VqeAi SbJ0MAbRnaC6fpJ y3CatuL9isMfo51 Udp2YNKYpytGXZt ziQE10qbg3rpNln XrOinSHvXIMOmZK NQj2PbSWDbekpj0 3V. END KEYBASE SALTPACK SIGNED MESSAGE.

---

Commit hash for clean builds is a93de9a4d09c3c78a6db10db2e7c244392f05b46.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7irRjQI 4pf0WvlCHdcq0sF GwnDKUIJzG6TWx8 jmHDYISz20ijwaS GRqcAPurdeN86Jz 7TXOcj9hnDzCx0z vHhHMEWN97lBt7P 6tywWPiUaUMiqcM qGazvA2r91DhPgY fSFWFfoI1k98Rf4 979hA0q5QDpVijd aZsNFPCrJVE8xLq . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAU5wtAl xcBYQNONafl3bRm gmkNXNZs2kcpixq MV7HAW0elgKggYF gEFmIo7FJFztxmH 6NUnxO78Ir8y3Bj t7OhQTkBwT7o1ZJ 6pLuo6Ct5X06nKm sTl62SQgt4JgqRh qOCpkzwMoVF7pmt S8PFA0q5QDpVijd aZsNFPCrJVE8xLq . 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.6.0 milestone.