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.