keep-network/keep-ecdsa solidity/v1.2.1

Solidity: 1.2.1 (Mainnet)

on GitHub

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.