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.