Solidity: 1.6.0 (Mainnet)

solidity/v1.6.0 is the mainnet release of Solidity contracts adding a new BatchPhasedEscrow contract used to allocate weekly liquidity rewards for staking pools.

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 team.

---

Commit hash for clean builds is 45179938bddad7fc0011cb1be81ce911313c1bcd.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7j13t2j 6dqdWQHYOMNUVLR 4UmlsophLcsRoEj 1N4gYExMN4vqIIX F6G5elpq0syamfz dK1Pfh4sFaknr9H ZmkfHpRmeCkYUev U6WBUNDIIij1j5n Gy79WVRsdVK6vfi xD1zHeqNft8drgc DhzZy0PcjbtKevS FQb3cudJbtpAwVw . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAT3tnGq NgE0UC8pb9BnnaY RiJcg3dfvhs6WOq v2WH0L6JFtob5FI Seh9PTCsk2MIUXh bcIguYHIarPGgEi gyoBkLDvn2raGuk YVodHwtsbIGFcpN RuK1X5Kv76coDcw xJfgehi1ky30pYd ICVrm0PcjbtKevS FQb3cudJbtpAwVw . 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.

Token Dashboard: 1.5.0 (Mainnet)

token-dashboard/v1.5.0 is the latest release of the KEEP token dashboard. The token dashboard changes since 1.4.1 are:

• Support for claiming tBTC rewards from the new Merkle distributor contract which will have allocations of all tBTC rewards starting from 2020-11-13 onwards.
• Banner style updates to align it with Keep design system.

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

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

The release commit hash is signed by the deployment team, verifiable on Keybase. Our Keybase usernames are all associated with the Keep organization and with our GitHub usernames. The Docker image hash for the token dashboard is not additionally signed; if you are concerned about its provenance, the release commit hash can be used to produce a local docker or standalone build of the dApp.

---

Commit hash for clean builds is 071681446360452db7233ed0e4fb55ad3ecc4a03.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7iUFfji V9bltsF24qJHY3i g5sAJ3p3UShUz94 PIQJEa0mH87GwGu ttyeAX1gvuZRyzz Iae6d1jDYpjH1La cNzA47cyprOjPG3 x9uAXcfbcPG8urT YGy1xWwVDqjVfD7 79J35NLuN09WuMU 8P3WX0pzACS1arI zWuQ0tHALsVk70N . END KEYBASE SALTPACK SIGNED MESSAGE.

• @Shadowfiend:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkAA9fdX h3PR4kiSBsxaoE3 9WyxA9pNLCah0b4 uFaShwCkPQsEcMI 17UgoCqDXnj537H BwWQQxIBv06S1rn d7HQySknUarrg5o K3VGzav9C7apInc 5zQCuqOoqkNJpFb fAL5cix7jWjDF4r 2DHLJfY9am3oWbA Hm273yxlwY4xkGg 7dA6nJz9b3llUJz 3xMhh0pzACS1arI zWuQ0tHALsVk70N . END KEYBASE SALTPACK SIGNED MESSAGE.

---

Docker image is available as docker pull keepnetwork/token-dashboard:v1.5.0; sha256sum is sha256:f2e2ec8305f4edfaf4a40d5576176eaa4e2faaae3e2d6a0c27bfee194ef71bbd.

---

Finally, note that the full set of work that went into the 1.5.0 milestone can be found in the corresponding token-dashboard/1.5.0 milestone.

Solidity: 1.5.0 (Mainnet)

solidity/v1.5.0 is the mainnet release of Solidity contracts with a small change to PhasedEscrow allowing it to receive tokens via approveAndCall.

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

---

Commit hash for clean builds is 2fb40a350363725e6aa265dde61189faa7795be8.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7igitPO Cc108T2az4eiCWy 5kbO7svUFQPqdNJ az4YtpyNstyHfDc kbjgrROuZIkx1JW u6hgS8txJVv97lG pOV7vH41chL5o3R 1pPV9gb7aYW5uzf Gsm2srcwnUQhwXi 2B3cHEwX6ZltbQy 4PTS10q5hLqhUzl AXclGvlZDgidVFI . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegATMHCZy WkbdW38fCxv68mP N13wsy1LUvDirNq Mvm2XwR7kvD8SEd tMxD5V2lE5Zn1x9 cMvzKCeuuCOPmFG DiaUj6PEeKLCQKG y7W3uGyk3NFPAjP Op2Zw0Q9VCMQmC0 rpzFiPMH3HRihXn Gp78X0q5hLqhUzl AXclGvlZDgidVFI . 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 1.5.0 milestone.

Token Dashboard: 1.4.1 (Mainnet)

token-dashboard/v1.4.1 is the latest release of the KEEP token dashboard. It is a bugfix release. The most important token dashboard changes since 1.4.0 are:

• Prompts to connect a wallet on all pages that require it.
• A fix for operator address lookup on the tBTC earnings page.
• A fix to have the dApp correctly refresh when the account selected in Metamask changes, rather than show outdated info.
• A fix for stake balance status not updating correctly when a top-up is committed.
• Correctly disable the Withdraw Tokens button on rewards pages when there are no tokens to withdraw.
• Adds proper loading feedback to a couple of pages that were missing it.
• Adjust the display of available ETH bond to avoid excessive numeric overflow.

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

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

The release commit hash is signed by the deployment team, verifiable on Keybase. Our Keybase usernames are all associated with the Keep organization and with our GitHub usernames. The Docker image hash for the token dashboard is not additionally signed; if you are concerned about its provenance, the release commit hash can be used to produce a local docker or standalone build of the dApp.

---

Commit hash for clean builds is a15cedc246906d797786b5cd5f21f7f72d3b4c6e.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7j2gfVH 4Hlk2If9jhv238c hN3EenwIXjfAIjV XqoNr7zEUgnWC4m tUIQ9L2xIvwk2uo 4jGKRex5NILcagg TSMr4YBEHVg8dIk OzO50rQnWhk09V2 1XjvFjLFJkqfvd4 aJtuvDMF5QXCXB4 YVVS90pZVIxriJE k9KaSRAqHI8rumD . END KEYBASE SALTPACK SIGNED MESSAGE.

• @Shadowfiend:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkAA9fdX h3PR4kiSBsxaoE3 9WyxA9pNLCah0b4 uFaShwCkPRa9Yxr N8Nw8JyUBybSFYj xDli9aHqs8oZpKj PhGa8VUnOJfwz1Q 7Fh7nGpo4thTTuO hScQKVonExsAnaC nI6HNa5T30zWKZl RoBxdLGhPKRsCYL jDTLJvLodxVPy9c FNJnS8KvFMqDiju WG8M10pZVIxriJE k9KaSRAqHI8rumD . END KEYBASE SALTPACK SIGNED MESSAGE.

---

Docker image is available as docker pull keepnetwork/token-dashboard:v1.4.1; sha256sum is sha256:c87bfe0a31ae9de505c55c1e7f1c373a0e4c220e8083187db9a631c7a1c9f4dc.

---

Finally, note that the full set of work that went into the 1.4.1 milestone can be found in the corresponding token-dashboard/1.4.1 milestone.

Token Dashboard: 1.4.0 (Mainnet)

token-dashboard/v1.4.0 is the latest release of the KEEP token dashboard. The most important token dashboard changes since 1.3.2 are:

• A redesigned experience to give you an easier overview of your token balances and delegations across grants and liquid tokens, and to quickly start delegating. As liquid tokens become more common, the dashboard also makes it quicker to work with liquid tokens than before.
• Initial steps towards a redesigned wallet experience, bringing wallet connection options closer to the point where they are needed and highlighting the current network and KEEP balance on all pages.
• Redesigned navigation with clearer organization.
• Renaming of what has been referred to as “rewards” to “earnings”---these are the ETH and TBTC earned through doing work for the network.
• Addition of the Rewards section, which is centered on KEEP rewards from the stakedrop. Both random beacon and tBTC rewards are listed, with tBTC rewards allowing withdrawal for rewards that are available but not yet withdrawn.
• An updated Resources page to take the place of the Glossary, with new links to documentation.
• Redesigned tooltips that are easier to read.

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

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

The release commit hash is signed by the deployment team, verifiable on Keybase. Our Keybase usernames are all associated with the Keep organization and with our GitHub usernames. The Docker image hash for the token dashboard is not additionally signed; if you are concerned about its provenance, the release commit hash can be used to produce a local docker or standalone build of the dApp.

---

Commit hash for clean builds is 763ed4d18c1848942ae50053aa1cf78af62ee976.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7jZmRDt K7rVXYkNrSCVk5V 1jFzd217qQc3BR9 18UAnmHLfF22kw6 Gcw9BzoNkN128Ri j9t4OzWa8WNaQeX AcHDMubsrI9FJOA bpBZcjyfCeuGH0d s2ca6rK5tVzdyv3 1eIWpdUFunTculi qrNnU0RbVfEzGsW WcmHi8mqDgtlxQ6 . END KEYBASE SALTPACK SIGNED MESSAGE.

• @Shadowfiend:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkAA9fdX h3PR4kiSBsxaoE3 9WyxA9pNLCah0b4 uFaShwCkPR2xfuU 2KVs8BosfD5YxrA hYXejwBqIbJYcmU OQ32N4UkM5gvSAt M5GzXxvPpvoVNVM A9JjbpDMVLP7e7g 8F2XuzGEXgwxxAI UwnF9stG2Dpwho4 r5LOWTvCZkCrymr tLbklmduGJ3lPjh 8KHi40RbVfEzGsW WcmHi8mqDgtlxQ6 . END KEYBASE SALTPACK SIGNED MESSAGE.

---

Docker image is available as docker pull keepnetwork/token-dashboard:v1.4.0; sha256sum is sha256:6db67c0bfc4ca5c420848c3832a5bd0d42df2b9ffe7999cdfc7802aab859434b.

---

Finally, note that the full set of work that went into the 1.4.0 milestone can be found in the corresponding token-dashboard/1.4.0 milestone.

Solidity: 1.4.1 (Mainnet)

solidity/v1.4.1 is the mainnet release of Solidity contracts for Beacon KEEP Staker Rewards

Groups can receive rewards once the interval they were created in is over, and the group has been marked as stale.
There is no time limit to receiving rewards, nor is there a need to wait for all groups from the interval to be marked as stale.
If a group is terminated (abnormally), that fact can be reported to the reward contract. Reporting a terminated group returns its allocated reward to the pool of unallocated rewards.

• BeaconRewards: KEEP Staker Rewards for September release.
• BeaconBackportRewards: KEEP Staker Rewards for May release.

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

---

Commit hash for clean builds is ca16e33dd121ba21be73ba2c400412d188b9e98b.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7iqT5NQ h6Dav1Wb34OaXd6 Rvu4BjO3BsCmp8y DNsqCXBZFhh9rtx 1GfLpewaB1el8zU JLXgWijecj0kGyV 0HN9SWUWFdWFbnZ psYTFaaPwzg6iJ1 o7aM0rOdW6atoeW vmb8sejzvCcJuvp TFS2z0Q90V6E99V jr1lLAANIrNjggc . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAUMoHak Jerwgh9yQwZDirW ByYB1Rq5I1GIsvE HrYpx6JngaAQ075 vyzi18satVgaVmT rlHZHRy5IJ84in1 Mj56D3ejRLuNDd5 1kewWbYLIP0GQVc XzAM7gEMlLpxS0V xSLnXgXj7K7kMY3 ZkydV0Q90V6E99V jr1lLAANIrNjggc . 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 1.4.1 milestone.

Client: 1.3.1 (Mainnet)

v1.3.1 is the latest release of the Keep core client, which primarily drives the Keep random beacon.

v1.3.1 fixes problem with failing ticket submission for operators having addresses starting with multiple zeros. It also improves error handling by revisiting log levels of some messages and not raising an error in certain situations, in case the problem was resolved.

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-client:v1.3.1; sha256sum is sha256:1d8508f8e274f34ef5f78677b7c42cb05d3c80da84a8837cf6363b42b0856c6a.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7jXTzAK M3bD8DnnkhPYlao jR0MNRmuOFMZogZ 8He3WV7z4J9i6ln SL9MG9SElVh3lWg ggGsxTiTORQJJdQ DLb23I7QHseLM89 gQ22JYlIUt4KfUE 8FXEMmHJgNaNo99 Qtk0pNcLndJT9f6 sunSAD5nOZqkDc5 DTMbFXDCbOG52p1 rYivqXWWoJd6F6J U4A1EOuNRXcdxxJ 4b. END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAT6TVcL QNeHWM7sd8AYqpl WkXgRMroSfEfZT6 j1byNWdfX7HdhGb vazy5BfehgJOb7h 1dAnltpkBrSFIyM ZKErK6M3vljNZSu OYN7EBHD1VZi0wb nhUSEOGRM9711mA YRTsu70RtBsWf5N ZqFIkD5nOZqkDc5 DTMbFXDCbOG52p1 rYivqXWWoJd6F6J U4A1EOuNRXcdxxJ 4b. END KEYBASE SALTPACK SIGNED MESSAGE.

• @dimpar:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkEUJD61 aS5dXdI0P9hkT7A V1KLgryVhYq77Eh HjVwI1gm0pC9ecG oVNIoBjsOhYgXfW 5pPpa955PxONuqt wzQfrAahiYVUx8G CanQMyAKBnSHdEy g8CnfOZEjHzxeXv aYKzJ0AzulGcqmC QJnmXG5rAKFqLu1 HwwXy4QlBH9zBBR NTaOKqfc8f5cIiG gstl8D5nOZqkDc5 DTMbFXDCbOG52p1 rYivqXWWoJd6F6J U4A1EOuNRXcdxxJ 4b. END KEYBASE SALTPACK SIGNED MESSAGE.

---

Commit hash for clean builds is 86922936b61d12b5c848b897369d8cdf30f8ae6b.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7jqRlK4 6Wi3PtB9QFaapUF qAQE0xqM2crbcuJ 57KQpT0kFaZdxWI SiVnvDvkhv6tVH0 2Ulb0o5KkrgqnU0 TmZvxEFsNFki9nn Ip5qHSfsz1seKK7 sHrDvyfrJhdGhVN YZ2T2VSoU5XJ5Ly KX8RM0Tgfn2Pb73 r0nr5n0ztuXzJVi . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegATAXW8y JXjxrOfOVvoSV51 HyEXmUlYAPQuVeu oBPCk8LEwARWntV OwpkkClcz6tKOY3 xRMWt8s5n1h1XKN SJu2nhmEr0sBsoz v6gXL90YMVrHQow 05sMMhKDxV07lZR iPPZRxaRYv7DuVL NriRM0Tgfn2Pb73 r0nr5n0ztuXzJVi . END KEYBASE SALTPACK SIGNED MESSAGE.

• @dimpar:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkEUJD61 aS5dXdI0P9hkT7A V1KLgryVhYq77Eh HjVwI1gm0paFUVe i1z3gL4N4KO1s66 L9hDoB37OqiRS1k 1e8DXNw49o7F863 EwqU12FgMVvzAww 9ixlL471YQc19Oy AKvi5aA4ySgSwTS MN9Bw9XB4Q3T1GS l5EvJwmj6Nr1Zkt v5r39CLR6VKPZAO q9buS0Tgfn2Pb73 r0nr5n0ztuXzJVi . 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.3.1 milestone.

Token Dashboard: 1.3.3 (Mainnet)

This is a bugfix release of the token dashboard. Changes:

• #2058: fix an issue with releasing tokens from a grant when the grant in question is a ManagedGrant.

Token Dashboard: 1.3.2 (Mainnet)

Note: Henceforth release notes and version tags for Solidity contracts, token dashboard, and client will be managed separately. Solidity contract releases will have a tag prefix of solidity/, KEEP token dashboard releases will have a tag prefix of token-dashboard/, and client releases will have no tag prefix.

token-dashboard/v1.3.2 is the latest release of the KEEP token dashboard. Note that release notes for 1.3.0 and 1.3.1 are rolled into these release notes for simplicity. The most important token dashboard changes since 1.2.2 are:

• Significantly improved performance across the dashboard experience, along with clearer loading feedback when data is being pulled from on-chain.
• Integration with the new staking contract and support for stake copying for existing delegations on the old contract, as well as top ups.
• A new token overview page with summary information for all your grants and liquid tokens.
• A new token grants list page that lets you view individual information for each grant.
• A clearer rewards page for the random beacon.
• A page to view tBTC-related rewards.
• Improved Ledger support, including a fix for Ledger Live address generation.
• Fix for a bug where Ethercan URLs were pointing to Ropsten instead of mainnet.

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

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

The release commit hash is signed by the deployment team, verifiable on Keybase. Our Keybase usernames are all associated with the Keep organization and with our GitHub usernames. The Docker image hash for the token dashboard is not additionally signed; if you are concerned about its provenance, the release commit hash can be used to produce a local docker or standalone build of the dApp.

---

Commit hash for clean builds is aca4a7ba93c1b0570d4cfe476bb75b1e54389b06.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7ippmuW vckbvwlXPdgRj3b Vdjfq7MrenGbIgL BB4nR8fN6IToFWr q6lwvr8mrZpQ2ee nlSAcegqvI8ef4Z WCZ9kMzy6iU490Q GahCnOlIHNaEwKD 16BgjwGV9pSNQyI XthEuwRmfRh8WP1 n9Rjh0R5ovhrYSa FYvr2DXEnWX0hXy . END KEYBASE SALTPACK SIGNED MESSAGE.

• @Shadowfiend:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkAA9fdX h3PR4kiSBsxaoE3 9WyxA9pNLCah0b4 uFaShwCkPRkXDLM 1seLE7cUJmiUihh AeoWGJxR67w95u7 4ulb05V49vvqxds q4wWKZsT5yJcM8T 1mmQy4MgwkGfpAg 9zFwG4Q1rZPkPRn 8enCkV7OqE1ghRc Y9d7Ksp9x3y6VYf eN0UT1lGpEq03eJ qQHpt0R5ovhrYSa FYvr2DXEnWX0hXy . END KEYBASE SALTPACK SIGNED MESSAGE.

---

Docker image is available as docker pull keepnetwork/token-dashboard:v1.3.2; sha256sum is sha256:fde3d5fd8b09ee830dc2b5ec4195487f74cba050f297bedaff0a9a1eeedf516e.

---

Finally, note that the full set of work that went into the 1.3.0 milestone across contracts, token dashboard, and client, can be found in the corresponding 1.3.0 milestone.

Client: 1.3.0 (Mainnet)

Note: Henceforth release notes and version tags for Solidity contracts, token dashboard, and client will be managed separately. Solidity contract releases will have a tag prefix of solidity/, KEEP token dashboard releases will have a tag prefix of token-dashboard/, and client releases will have no tag prefix.

v1.3.0 is the latest release of the Keep core client, which primarily drives the Keep random beacon. The most important client changes since 1.2.0 are:

• A new metrics module that allows monitoring the number of connected peers, bootstrap peers, and the health of the Ethereum client connection over HTTP at endpoint /metrics. More details on enabling this are available in the sample configuration file.
• A new diagnostics module that exposes diagnostic information (including a full list of connected peers and information about a client's network id and operator address) over HTTP at endpoint /diagnostics. More details on enabling this are available in the sample configuration file.
• A major upgrade to the libp2p library. Note that v1.3.0 is not mutually compatible with the previous client version.
• A bug fix to the DKG reconstruction phase that could allow invalid group keys to be produced in certain cases.
• General improvements to reduce the number of calls to the Ethereum client.
• Implementation of an Ethereum client call rate limiter, to help reduce instances where remote clients are forced to rate limit the Keep client.
• Finally, thanks to @alphastorm, a move to Alpine as the Docker container runtime that reduces our Docker image size by ~90%, an order of magnitude improvement 🎉

Don't forget to update your configurations to point to the latest TokenStaking and KeepRandomBeacon contracts and bootstraps! See the mainnet run docs for details.

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.

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.

---

Docker image is available as docker pull keepnetwork/keep-client:v1.3.0; sha256sum is sha256:8e4f82dddb3e47a225825e6ed99339a0b484cbb89dde69e0d59f7c43eef10aba.

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

• @Shadowfiend:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkAA9fdX h3PR4kiSBsxaoE3 9WyxA9pNLCah0b4 uFaShwCkPQbKs2p TuyMW5tXDxUTIrk MqSJzoS1VykS5KL luZRYAGJpQWrIqX dNiN72zkuVjQL60 dL3xQ93BvW9eOig oVH5xBQ9etB3kSU DD1BGUlb3SG7rrl PNej9ltRU0r0Zco aXWaqJd4JaPrQZZ 1EXOHCtjgQChsST ikXvJNpHsZD5D5b 2cGlimqNb8LxFqH kR91EPGdCSIfmMr SL. END KEYBASE SALTPACK SIGNED MESSAGE.

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7in2XKT qNBEYwZhAVsIRRb ASG3B26Wrjc9piF Fss4ebXKeagWzPA qIjX8sEVeboBns2 4kvqxPBXnpypvuM 3MR4HMMm0SBdq56 bp5wP4BOIwhXwxX xJwygc5rgWrr3vd fNKEUTt7JS2UCCA e3xx7CtjgQChsST ikXvJNpHsZD5D5b 2cGlimqNb8LxFqH kR91EPGdCSIfmMr SL. END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegATmHTSK nRupUUBqxAwGPjq t4y4YnjRly7GejR QCWgU8Myzum4ouP 9qIqzUjR6icmTDT SbMOeZboaak3Ar5 XQfESsyEogWhZ8e H4aBP9Fkm6ZVDz4 MIKg1DKVZYowJJ1 AksnmqSA2qslBkE VdO8PBtzJQBgEcs 6ddDANTj6yhBhzk P6GKMNeDPzvpt1Z GJp652DGkp4wCbj 2huPd0nJJ9l. END KEYBASE SALTPACK SIGNED MESSAGE.

---

Commit hash for clean builds is b2eb62592058518bcd15a3e3510487a5118c5a61.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKUP1mo cBOwsMO2Zoy9oS4 RuaO1bwgSUG4cNZ RnlK7jKb7j1rewf 1u1642ekMW8UvhZ zdY2sfeWRQSSUBt qMHE4FaneqG15qt 2HEf22oWk0RzmPk rCGQ8uPWQI2XGwQ tZhISwpttYhgHp6 pLqKYbnFawLnLDM SM2QjnaX5K7h7VG 4iQfGqR7FXkBSp6 FPowt0qVghiAq1L PipGLgBk1aKDfSj . END KEYBASE SALTPACK SIGNED MESSAGE.

• @Shadowfiend:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkAA9fdX h3PR4kiSBsxaoE3 9WyxA9pNLCah0b4 uFaShwCkPR4Q2u2 8kNG2ryexPRuVwV o0UlGqKJGQiBV8L RqsWOWnzwv2VPLB J0YAnIMGP3At174 wGEmZd8lByHldSj 2CXrxiDGNtq3tzS Q3anBGmbJ3VIz5K WppIFm4HLAwi526 SaK8KmDOV9xmGGF TzLil0qVghiAq1L PipGLgBk1aKDfSj . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegATJIUuA LGx7sICQVY1wVek 98hogs9oU5poYGj pMEfXXmILM1C3Jj xgLgufbGjrLl9U6 VG0SIr7lBRslLJD PGxrbNOIiN2SQvF pvWdMF5Zb1CcBnR a1YdlEdqpQK5o0E CC0Ec3hr6WK1y6D Wv3fX0qVghiAq1L PipGLgBk1aKDfSj . END KEYBASE SALTPACK SIGNED MESSAGE.

---

Finally, note that the full set of work that went into the 1.3.0 milestone across contracts, token dashboard, and client, can be found in the corresponding 1.3.0 milestone.