v1.1.1-rc (Ropsten)

Bump keep-core dependency to latest Ropsten rc

v1.1.0 (Mainnet)

CLIENT ONLY

Keep ECDSA client release improving Ethereum chain integration mechanism and updating network handshake protocol. This version of the client improves nonce management to avoid duplicate nonce problems in production environments with load-balanced Ethereum clients. Additionally, it implements monitoring of transactions submitted to the mempool, automatically increasing gas price in case transactions are not mined in the expected time frame. This version has an improved network handshake protocol ensuring the ECDSA client connects only with other ECDSA clients by checking the protocol identifier both parties are running. Last but not least, it implements an additional safeguard for key generation making sure that even if all clients in the signing group get restarted after submitting the key to the mempool but before the transactions are mined, key generation is not going to be retried and key material stored on disk is safe.

IMPORTANT: this version of the client refuses connections from clients in previous versions. It is recommended to upgrade to the new version as soon as possible.

We are 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.1.0; sha256sum is sha256:55a89b5d39f3a8825bc06187dc2c5669577fe4dbb7f8e76f795314d43e23c0f8.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7icJaAD 2VCJqrMpObtdtXU ZYogRssqLMcVYmG w4qHD28IWyO0YwW Ag1HOwlYdnuyQB6 7kdIBUvvGmcpUSA aMBYm58tVUx0xvY qgMxyaqEVKiP8qU 8ydDFZ16UDpEBor xPR5JmyY9fLmRcz pN8PoBuAcejZHYA QAV1YCEDOpKLhND 0b5EDMsoV6NTgQL w7aCqOqMaNjNC1Y T801Kb8tFcW. END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegATRA6z3 KWHhKTVXFuymqlO MiYh27ev2dr1PLZ 8LNzja28WRyjxJz ySxziTLVEairpf4 yc9wT3sAkAzuya2 RT9OYliXzbaJQf2 Ao5EM0wuWSyqcUD u7ZMXtN1jj0J9SM kcVgVm3NiHlA89g 2HxyiBuAcejZHYA QAV1YCEDOpKLhND 0b5EDMsoV6NTgQL w7aCqOqMaNjNC1Y T801Kb8tFcW. END KEYBASE SALTPACK SIGNED MESSAGE.

• @lukasz-zimnoch:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk90sDpX wIX07Cfy2Yz31Xq 8mliRvTpoVIDeBV VZiP1JZd9aS60ma LTlfOkrcPcnSdjs Er092Mw7S3ATTkE IgezaxqPAfeTgTs bwijW3rI9wUmb9A yOMMB5chiChfVQt IaKzlTsT0XjVGnx lenkVQx2qKNPr6i 4SYFQT881ofmy2e g3diM4tk5Li87PY Qmz6mBuAcejZHYA QAV1YCEDOpKLhND 0b5EDMsoV6NTgQL w7aCqOqMaNjNC1Y T801Kb8tFcW. END KEYBASE SALTPACK SIGNED MESSAGE.

• @sthompson22:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk90o9Mi AQ4Q0masVnp14vX ToxAMpoeQ1wBD8c XBrn3XH3hcrZizl 75OBaG0TCNUVMCu y4ffWHX22e9dcQP KMOd9MBAYBnnqGb vzzSr92MqWkwGcA Zwnplnc2Jke7nRZ rD7vR1ol5HyAWh1 DdLnkML3B6agmX2 Jb9vLmSnloELU7I otJ72S9fcalwGrH 4kc6yBuAcejZHYA QAV1YCEDOpKLhND 0b5EDMsoV6NTgQL w7aCqOqMaNjNC1Y T801Kb8tFcW. END KEYBASE SALTPACK SIGNED MESSAGE.

---

Commit hash for clean builds is 59dd98c31bb51faacbcbe6b0cc62d36ceb4fb220.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7iwGmjT GN5GWMHqkrGwefB WfWBbwhj8YZwcZo lJm9lffr6y1JsZg QUijWNi4PQdFt8v 9HyVAtoav0f8TD2 KfA6f42KS33bywz C09MLPyusisxATk EYmzkKn09tdSHko tJpkvuKc8UTHU8L 7B3mI0owoxh9NcR z7sbXEjOf7gIxv6 . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegATBkrOU hVKCvyZ9QCkVzgo Bwn5UtlTtdJgnT8 jVRfcbWKwXZIgZJ l4DJ3MrYnkFY1es IdjCfYn7SRtz3dK imLczMXHePQvHXF PKQsdXNIK4IYaiH V0GeSsxnhLmo9ah WK9dVNgts27SPfa BUgty0owoxh9NcR z7sbXEjOf7gIxv6 . END KEYBASE SALTPACK SIGNED MESSAGE.

• @lukasz-zimnoch:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk90sDpX wIX07Cfy2Yz31Xq 8mliRvTpoVIDeBV VZiP1JZd9b3FbiF xqWWOS02HwtpRI3 PbGb0XiLVWOuZRY oW8BYiqmWEDWuPF qQKO0p9JjNtRUeQ 0v6bDW2EO7HyZc9 XRK0KtmFVZDZpzO 7CsJyMRPfsqgQaa 9LnhhE1DUUaziv1 frSwGtqYOKMm8Xs DkHji0owoxh9NcR z7sbXEjOf7gIxv6 . END KEYBASE SALTPACK SIGNED MESSAGE.

• @sthompson22:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk90o9Mi AQ4Q0masVnp14vX ToxAMpoeQ1wBD8c XBrn3XH3hdOMY3P IbhYk9AfyykMMkh ZVDccY9nZ22MsOQ Vqz7KAN6lC2lfaU SV0jVowAs4GXko7 Hab7xODEEKqPe1C 6nkRmOS3ASF4H8z XtUoyhW0DdkTpQO sZL9GiQcJt4mI1s ynPW8uSGo5d4Fvo ekIcg0owoxh9NcR z7sbXEjOf7gIxv6 . END KEYBASE SALTPACK SIGNED MESSAGE.

v1.1.0-rc (Ropsten)

CLIENT ONLY

Notable changes in the release:

• Do not retry key generation if key material is available in the registry (#457)
• Automatic pending transaction resubmissions with a higher gas price (#456)
• Pass protocol identifier during the handshake (#456)
• Ethereum subcommands added to the client (#451)

v1.0.0

Keep ECDSA contract release and client release.

v1.0.0 contains the final release of 4 key contracts that implement the Solidity side of the ECDSA keep system on Ethereum mainnet. These are:

• BondedECDSAFactory, the ECDSA operator contract that is the primary interaction point for ECDSA keep applications like tBTC. This is the contract that authorizers need to authorize to allow their operators to operate ECDSA keeps, and is the second contract (after the random beacon operator contract) that (with authorizer opt-in) can slash KEEP token stakes. Read more about operator and service contracts in the Keep spec's section on upgrade management. Making bond available for applications is a separate authorization step, mentioned below.
• KeepBonding, the bonding contract that is the primary interaction point for managing bonds for bonded ECDSA keeps, like those that back tBTC. This contract allows anyone to provide ETH bonds to an operator address, and allows an operator or their corresponding stake owner to withdraw unused bonds to the beneficiary account at any time. It also allows any authorized applications (like tBTC) to take available bond and use it for the application's purposes. Applications must be individually authorized by the authorizer to access an operator's available bond balance via the KeepBonding contract.

In addition to the primary contracts for ECDSA keeps, we're providing two pieces of information for operators and other interested parties:

• The Docker Hub image hash.
• The release commit hash.

Both hashes are signed by the deployment team, verifiable on Keybase. Our Keybase usernames are all associated with the Keep organization and with our GitHub usernames.

Once tBTC has been released, the token dashboard will see a new release that will be posted on https://github.com/keep-network/keep-core/releases and that will support authorization and bonding for tBTC.

---

Docker image is available as docker pull keepnetwork/keep-ecdsa-client:v1.0.0; sha256sum is sha256:c3a10757e70bde00781c73894f8852c1df0fd36fdfd373d0a568f9ca07aef12e.

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

• @pdyraga
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7jQdKCK IPcmke83vBDqI0Z VjjZL71tlroBXE8 l8cuxXRmE9nF8PB 6Kfz9j52aNPEg8X z8yfyUzyzJ9tiMm J5B8GlyzgDn8GTp HWD6KIddDNZfuVl Cpz4ZPbBGTW3z8B WNPYoY6VfvqKAE2 IDUqeBQs5yRYXsO KLrQJlBEa8fZZbU OlrN5MbetqtOk4B LpE64wYHpUebqS7 FgkFu08X8Dd. END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAUKiwEh a17phFpKCVqqUoI NFGSimfRjymtp2u ajrPdabTtOvUQ8c maLuDlC7xwakPS2 1xAzqrdBIm0bcrh 4Am56L9QfykM9O2 viqhNef373ElxcX jgh0qI5YWld5K1q dOyL2R5d9gUMlHB nHrhABQs5yRYXsO KLrQJlBEa8fZZbU OlrN5MbetqtOk4B LpE64wYHpUebqS7 FgkFu08X8Dd. END KEYBASE SALTPACK SIGNED MESSAGE.

• @shadowfiend
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkJKtqy5 A9BS2uGfFg43p4I EOsZfCflZKxtcT1 MPL5J5Ywa0YU6Xv o7CgMBfFLNCE5ne 0GzmdYNQKwLOxL0 jFvabfoSQavalvF GOyPqqIPE3Qf7N3 xVsrL8UpDxrqPhL oYmHWORdLdBLMFD OIx8MUWI4rinTw3 aRIgdANd7Avqhsd uUfzcn4ZMqXTKYi TK1rcBQs5yRYXsO KLrQJlBEa8fZZbU OlrN5MbetqtOk4B LpE64wYHpUebqS7 FgkFu08X8Dd. END KEYBASE SALTPACK SIGNED MESSAGE.

• @sthompson22
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk90o9Mi AQ4Q0masVnp14vX ToxAMpoeQ1wBD8c XBrn3XH3hchPQEM 7OPUwajshIpOmxh oWa0Pf8MWcVr1fj mJLUVPbalZjAUKk eki5HbCGUwVGqKN xj5yUncccBx4pZz 7WVb3RXjEa6gIUE bNtiFg2s1hWl99m rWcB7CAHf1JlNwj VkpIOdQ180zitwc N1RjsBQs5yRYXsO KLrQJlBEa8fZZbU OlrN5MbetqtOk4B LpE64wYHpUebqS7 FgkFu08X8Dd. END KEYBASE SALTPACK SIGNED MESSAGE.

---

Commit hash for clean builds is f76cfd269c71a3f97d3d00a7f64937e148f132b0.

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

• @pdyraga
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7jVyeEy sUitsszmOY2RIeX EdFi1D988QDBhkZ k9i62hLSII3nKfK CYUmyOG26i7Jwnk 7ozf10jfxlS3ZWL kGtyNtSW2Dpjl0t RMQK8dHcffZSbWe yTwm9hnth1yoHq4 LetmtZuoKnAuEEw GWs0O0oRWzofQp3 29CQ61aDcszbaue . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAUCihoo lGQWT7MdDx3pX1P ORvcDLfD2pASVPE 11uTEg0oJ60D1HV BB75XZCFMgLEG1l 0MfJOns55pNzOIl 1uSUbNhBxmEu1Hq zGKzNVDCTuDL13R 9mdy4WwNdTB12d2 2IcKAHhUAsBTMfZ uld6u0oRWzofQp3 29CQ61aDcszbaue . END KEYBASE SALTPACK SIGNED MESSAGE.

• @shadowfiend
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkJKtqy5 A9BS2uGfFg43p4I EOsZfCflZKxtcT1 MPL5J5Ywa1EUOOF MzD6jZwRUJ9Q0cr 08GgtY10E9JXLn6 hbYBYzCxX81TUaD 4wTkCeDax22QAcU 2f3mPh4ufaphVpu kZtqHC3AEWBq33O GpVPG8TqsWfxJer 38kSx3hAAG9q8Bx NzU3szNFFZRz4zk STxWi0oRWzofQp3 29CQ61aDcszbaue . END KEYBASE SALTPACK SIGNED MESSAGE.

• @sthompson22
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk90o9Mi AQ4Q0masVnp14vX ToxAMpoeQ1wBD8c XBrn3XH3hbrN28A zdK9Tlwb7DHsxGv g63BAhKqktyeJme mRwGU9S3y66C2qO VoeHlaPOM9AUaTg 7ZtO2I8BptWuHUJ Ik80F8s4BuMTy8Y QvuMaMxp7GTGZDj a2TtH1j7RBaKoFj 4LiwZ4SGQ7ycJGF aRSiG0oRWzofQp3 29CQ61aDcszbaue . END KEYBASE SALTPACK SIGNED MESSAGE.

v0.16.0 (Ropsten)

v0.16.0-rc

Result of npm upgrade @keep-network/keep-core

v0.15.0 (Ropsten)

• Fixed from address for contract call options (#432)
• Renamed magpie to beneficiary and Registry to KeepRegistry (#431)
• Updated keep-core dependency (#434, #433)

v0.14.0 (Ropsten)

• Minimum stake or active keep membership policy (#406)
• Signature fraud should be reportable if KEEP slashing fails (#356)
• Retries loop missing time delay (#395)
• Improved validation of group size and threshold input parameters (#392)
• Check for signing request confirmations from the block it was requested (#403)
• Abort signing when signing timeout has passed (#404)
• Log messages improvements (#407)
• BondedECDSAKeepFactory implements IRandomBeaconConsumer (#399)

v0.13.0 (Ropsten)

• Bugfix: Client breaks on status monitoring after being removed from sortition pool (#317)
• Bugfix: Duplicated events delivery handled as separate events (#355)
• Bugfix: Signer generation chokes when there are not enough pre-params in the pool (#349)
• Throw critical error and exit the client when can't get to storage dir (#336)
• Updated sortition-pool dependency to v0.3.0 (#383)
• KeepBonding monitoring events (#380)
• Improvements to operator status monitoring (#381)
• Minimum stake schedule (#302)
• Check for in-progress key generation on client start (#337)
• Wait for enough confirmations on client start before archiving and signing (#371)
• Wait for enough confirmations before signing after receiving an event (#364)
• Pin solidity version to final version for mainnet (#359)
• Lock operator's stake until keep is active (#360)
• Delegate slashing authorization to keeps (#361)

v0.12.0 (Ropsten)

• Concurrent handling of BondedECDSAKeepCreated event (#346)
• Configurable tss-lib pre-parameters generation timeout (#345)
• Updated tss-lib dependency to version 1.3.1 (#347)
• __beaconCallback(uint256) updating group selection seed (#339)

Infrastructure:

• StackDriver logging improvements and TBTCSystem contract update (#350)

v0.11.0

• Repository renamed: keep-tecdsa -> keep-ecdsa (#319, #329)
• Updated tss-lib dependency to version 1.3.0 (#332)
• Workaround for tss-lib PreParams generation on machines with < 3 CPU (#331)
• Add a concept of terminated keep, track keep creation timestamps in the factory (#333)
• Two-step proxy initialization call moved to the second step of upgrade (#323)
• Fixed possible context leak for monitoring key publication context (#338)
• Fixed context deadline exceeded in TestGenerateKeyAndSign (#289)
• Solidity and JavaScript linters (#328)

Infrastructure:

• More keep-ecdsa deployments (#330)
• Tenderly integration (#315)