Client: v2.0.0-m2 (Mainnet)

v2.0.0-m2 is the Chaosnet 1 phase release of the client software. This client version provides integration with the on-chain ECDSA WalletRegistry contract to perform distributed tECDSA key generation. The client generates 51-of-100 tECDSA signing groups used to custody Bitcoin for tBTC v2.

The documentation for the client setup: https://docs.threshold.network/guides/threshold-applications/tbtc-v2-client-setup

In addition, 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 development team, verifiable on Keybase. Our Keybase usernames are all associated with the Keep organization and with our GitHub usernames.

Linux (glibc) client build and checksums are available to download in the Assets section of the release.

---

Docker image is available as docker pull keepnetwork/keep-client:v2.0.0-m2; sha256sum is sha256:193c381e54a76d71f8005c59172854547f0eaee76ace7cc64a454011fcfe7366.

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

• @pdyraga
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk8SRO9e gN94erb57G43YvY asc2ypx7KtJhJpq tOozFkj38or2prU Y1siPVtg5t7FPj4 C5i2mmf44xltRqM ukdiVrwymmvtCp7 CADh7iLBzVN7Wwt Fk0y9hjby0S53Fq bHdmlETPNXaMHN3 ay7qAXKMYU6Qf69 hFU80CdZxIdkEeC R2NkCzLFLCkYH2J SPP55BiGyfB9Mlv FRo0x6O4d9SdWVw 03pwC5FUPW8gu8S V3D6oKLwzucMm6e h78EmwpvdpO. END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegATmS2AN aYlMJfT31ueVNF2 x9Fho3xeSOfm3Qg 9WMT7bXwLU0GnJC Qdmj6SloWuxcNdQ OXpxMoeMcBZBvWA 2QKAJwjrEvmG5iL ZejMy485ngG3KMj KBZICM551QLW462 wGPLos9gz93Y6RV FvGvXBiGyfB9Mlv FRo0x6O4d9SdWVw 03pwC5FUPW8gu8S V3D6oKLwzucMm6e h78EmwpvdpO. END KEYBASE SALTPACK SIGNED MESSAGE.

---

Commit hash for clean builds is 0fde71ce764fc13669d1939dec5b1cd9b6278adf.

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

• @pdyraga
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk8SRO9e gN94erb57G43YvY asc2ypx7KtJhJpq tOozFkj38nTbqH2 4gXhcUQHpwdtGT9 ZOwoovzbugEFjfv gkcGZdKoTmMomwU 8pVfNStc2r9Csm3 M8uYLnjxqV8f8Vw z2GoBs1G5x8PcRD 7PUMAvekfxpdbAP TXEWN92wvDevClR A4dEiBu64UlK2I5 7S4qR0TmLveC1oE MkyU0PyPZI9BygI . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegATbfw86 cGYYtDPI4xTe30y 6CYkN4uaWDB4n1r IRoKZn0N9ac1z4V bfzkWOIdcPOu2if fWp3Ntd0PBVB6hy Khdky18zdg2cvaO TMJJwuVY0fq4K3e eaqKKRURj26Qv3C Dq3RV4h9JeFxL01 RFseJ0TmLveC1oE MkyU0PyPZI9BygI . END KEYBASE SALTPACK SIGNED MESSAGE.

---

Finally, note that the full set of work that went into the 2.0.0-m2 version can be found in the corresponding v2.0.0-m2 milestone.

Client: v2.0.0-m1 (Mainnet)

v2.0.0-m1 is the Chaosnet 0 phase release of the client software. This launch marks the beginning of the first phase of the rollout of tBTC v2. Chaosnet stages are intended to graduate the rollout of tBTC v2 across several stages to ensure client and protocol robustness. This client version generates 51-of-100 tECDSA signing groups, 33-of-64 BLS signing groups as well as tECDSA and BLS signatures with a fixed frequency.

The documentation for the client setup: https://docs.threshold.network/guides/threshold-applications/tbtc-v2-client-setup

In addition, 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 development team, verifiable on Keybase. Our Keybase usernames are all associated with the Keep organization and with our GitHub usernames.

Linux (glibc) client build and checksums are available to download in the Assets section of the release.

---

Docker image is available as docker pull keepnetwork/keep-client:v2.0.0-m1; sha256sum is sha256:2d0fe6f348f1576353b4da94fea3efcd07dd8c33935be0c41b6fa3495a4e65ed.

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

• @pdyraga
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk8SRO9e gN94erb57G43YvY asc2ypx7KtJhJpq tOozFkj38nd4gkY tGo2tI03RrgdcNm ukTf4UMuaSgGd6F 2ltiKCTU3LnvKhe wk5fllj228eWj6h TKQjyFwVhYN9aMn UElaHf6pTmndNgs 1kDQdeq2g2q375C BMHJOTN8ymdR0ya 0W5PMmJ75usg1C9 11sOcC8rV20wTWJ uKixpsbmRHTd29R 8sQ8PkKtelAI0Pz DGd6YeZMZcp1m4C RFGYrMRlweK. END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAUKz83O LViq2Epzezis2CQ NnsUYuYGtw1nS7f p5ldARh8F20O0Vg jEB3Ax0lqkrQbbP HUXqV6pW7CBzp6O YETezAaBgtgYXRt sDhkDIJTG03b7iu mVSkMlejls8K2O8 me3R6DO2L8IR0VE wKjV0C8rV20wTWJ uKixpsbmRHTd29R 8sQ8PkKtelAI0Pz DGd6YeZMZcp1m4C RFGYrMRlweK. END KEYBASE SALTPACK SIGNED MESSAGE.

---

Commit hash for clean builds is 4d745f6d02915f3de263d1e5776ba531c5f1c844.

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

• @pdyraga
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk8SRO9e gN94erb57G43YvY asc2ypx7KtJhJpq tOozFkj38nZz9qU xw0Jwg41b8Kt1ax ctsF36CETEtckeZ VvyVy49DrL96KCI vMpZUxhqeVkhFxg XOGU6B7DThsqfHI 6CaORodbCrXzEnl qIGxfRJ9bLiPXEq YZRcCjj78TiJ3T3 eltyhXHJ1uCYHk9 ieZLl0qVwLez0FJ H2As7DxpkjoEUVg . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAUcG4Am vwlSmVASHOTI9rv LTIydXgSfp94eZ6 kU9vyShGZFN3jE3 4OrLSnVCksrM6bu IrMAmkxRHeoVRbk FN608m0MJNIXa8H JaYzNlXMDCkdhvQ tOiCVF5jk6HULGL bfPQlg7NfNlIMnw S50dd0qVwLez0FJ H2As7DxpkjoEUVg . END KEYBASE SALTPACK SIGNED MESSAGE.

---

Finally, note that the full set of work that went into the 2.0.0-m1 version can be found in the corresponding v2.0.0-m1 milestone.

Solidity: v2.0.0 (Mainnet)

solidity/v2.0.0 is the release of two key contracts that implement the Solidity side of functionalities underpinning Threshold Network tBTC v2 on Ethereum mainnet. These are:

WalletRegistry: The contract is responsible for requesting and managing new ECDSA signing groups, including signing group members selection, verification of a generated key, group lifecycle, and slashing. ECDSA signing groups registered in the contract are backing tBTCv2 wallets. The contract provides an efficient implementation for supporting large wallets on-chain, such as 51-of-100 wallets holding BTC assets for tBTC v2.

• WalletRegistry proxy contract: 0x46d52E41C2F300BC82217Ce22b920c34995204eb
• WalletRegistry implementation contract: 0xfbae130e06bbc8ca198861beecae6e2b830398fb
• WalletRegistryGovernance contract: 0x6aed6cC30D1b2770771052555d257Da86eD47fe8
• ECDSA SortitionPool contract: 0xc2731fb2823af3Efc2694c9bC86F444d5c5bb4Dc

KeepRandomBeacon: The Threshold Network and tBTC v2 specifically require a trusted source of randomness for the process of a trustless group election. While the network requires that randomness to function correctly, the source of randomness is itself broadly applicable. This trusted source of randomness takes the form of a BLS Threshold Relay. The threshold relay generates verifiable randomness that is resistant to bad actors both in the relay network and on the anchoring Ethereum blockchain. RandomBeacon contract is in charge of requesting relay entries, verifying submitted entries, and all other activities such as relay group lifecycle or slashing.

• RandomBeacon contract: 0x5499f54b4A1CB4816eefCf78962040461be3D80b
• RandomBeaconGovernance contract: 0xd0A3088eD9fff4357b79cd3896bd38876fcB1c63
• Random Beacon SortitionPool contract: 0x4e4cBA3779d56386ED43631b4dCD6d8EacEcBCF6
• ReimbursementPool contract: 0x8adF3f35dBE4026112bCFc078872bcb967732Ea8

The release commit hash is signed by the development team, verifiable on Keybase. Our Keybase usernames are all associated with the Keep organization and with our GitHub usernames.

---

Commit hash for clean builds is be7d537ccc8909b20837c375501aca3cd583cf41.

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

• @pdyraga:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk8SRO9e gN94erb57G43YvY asc2ypx7KtJhJpq tOozFkj38nze8ES VZG79swpYGVfjHW 3NvIZUaMO1seQn1 7WpblHz56y4sbyA fPb2CBL93huEcO5 SqQvPqYheBkRC6X CSdC8sSIZDRtZHL Cr52ck79n1L6f7z 0beqCmvvcPuju3Z WRVyI8MwxnUqRDY kLbal0Se55JHnH0 sgrsuUePZlEJND7 . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAT4a6Aw MazGRUp4ZC9m5H9 zax4TmrhUwiIZSa bRXFJaaNgV9ycfu oceOTTnRRKmS0In VcXS2HfnHtrEEuU QzqqlzIuAARVC5K gd9L8DNhjj6JKM4 E3mpbrtsIoaej44 OTFMWt4RIESpISc dbNsx0Se55JHnH0 sgrsuUePZlEJND7 . END KEYBASE SALTPACK SIGNED MESSAGE.

---

Finally, note that the full set of work that went into the solidity/v2.0.0 version can be found in the corresponding solidity/v2.0.0 milestone.

Token Dashboard: 1.19.1 (Mainnet)

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

• Fixed a bug where the button to undelegate the stake that was moved to T, and then unstaked on T dapp was blocked, even though user should be able to undelegate the stake in such case.
• Fixed a bug where stakes that were canceled during the initialization period were still displayed in the authorization table (Applications -> Threshold page).
• Disabled the "Authorize and Stake" button in the authorization table (Applications -> Threshold page) for stakes that are in the initialization period (and added a tooltip informing about why it is disabled).

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 development 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 4c3d5ad77dcc22cc0824e4a4c6ed186d254f42c2.

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

• @michalsmiarowski:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk7SMgAL 5NY1277Utw5mA8i 1L9QkD7NpCS6kJU UaLrqKt0dB6AInl QMswUcKgaySRRzk T8AiCOAkDsm2DGa SK7WvPGcnDqhWLf 5t7MYEltVmHvDGT UNqZtJp6of4ORJX kBa2cIQPfFOG3US hXxkVU4LZeGPGWK Baby186cKt55Uw7 ByH2IsppWugBf55 FCH9I0oR9Wxfeuk i4N2OrpXviDIeji . END KEYBASE SALTPACK SIGNED MESSAGE.

• @r-czajkowski:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKYlB2X GFJeY9xtCM7xvtw JiHcqkwrXPjpQeO OPKKjvWVoSnwpSS LL1dp0NpcFzK4xb XYAWiKsvYv8mQIS L50PKaWii9wARKt fpDKyeYznkjYcHG h1bzHznRACvrO3W BZm9lZEXQELzNKM PkRzW6UfvCRNkIi 2gAroFbGmsbeB95 QSBGeGZnntDykhp O4suC0oR9Wxfeuk i4N2OrpXviDIeji . END KEYBASE SALTPACK SIGNED MESSAGE.

---

Docker image is available as docker pull keepnetwork/token-dashboard:v1.19.1; sha256sum is sha256:0afa7efb37ad4ba6cd23075aea135b1f2e20cd46fe8c03af4ab1cf5d7f05591a.

---

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

Token Dashboard: 1.19.0 (Mainnet)

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

• Removed the ability to Undelegate stake that is already moved to T.
• Added functinality that checks PRE status for a moved legacy KEEP stake - now if the PRE is properly set up the Rewards button will be displayed instead of Set up PRE and it will redirect to the Threshold dashboard.
• Added proper links in tooltips for the buttons mentioned earlier so it will be easier to understand what should be done next after moving the legacy stake to T.
• Replaced banner in the Overview page with the new one that informs about Threshold staking.
• Unpinned the footer of the sidebar on the left.
• Updated PRE setup link.
• Fixed some of the buttons which were redirecting to a new page without keeping the wallet address in the URL.

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 development 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 7f4af838725d80c84bd85f38cfc74abed8940f67.

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

• @michalsmiarowski:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk7SMgAL 5NY1277Utw5mA8i 1L9QkD7NpCS6kJU UaLrqKt0dC3MSWb u9BZ9KS7CQ1bzpa nJe9SVTfhCyqTsH HgbB2ZDL2tCCATc cT3U8GFcgZhDquE WWDQueU8pZUHBJa rYEfN40PctF1wcE swqc2akEGBaIJZI jx314wvuKFwl5YJ BZvPxHDnKeIREm5 fIMmE0QZnV3F2cl 7RukAYF4vUZdaXn . END KEYBASE SALTPACK SIGNED MESSAGE.

• @r-czajkowski:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKYlB2X GFJeY9xtCM7xvtw JiHcqkwrXPjpQeO OPKKjvWVoU9Fcfz Rm2LxGBwBmbxc33 xJZILLCdpuefK03 jFelUWyZp04idZG 12Hmi0IrnERJacL elKag1FyIg3yZC4 ccIvQu75AJIFUF6 giz5gC3sXQyW5iS XSk0J7WbHC403gn hZeIEEkVOzsbunF Cobsk0QZnV3F2cl 7RukAYF4vUZdaXn . END KEYBASE SALTPACK SIGNED MESSAGE.

---

Docker image is available as docker pull keepnetwork/token-dashboard:v1.19.0; sha256sum is sha256: 7e578920ae5c370a45be973637e1fb69ed99d8dd24423b2e7b9804be614894b9 .

---

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

Token Dashboard: 1.18.0 (Mainnet)

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

• Changed tBTCv2 + SaddleV2 pool to an external one and moved its incentives to T (more info: https://forum.keep.network/t/repurpose-saddle-tbtc-pool-liquidity-incentives-and-move-incentives-to-t/404
• Updated Ledger packages to use the webusb instead of u2f. Currently, it's supported only on Chrome. More info: https://github.com/LedgerHQ/ledgerjs/blob/master/docs/migrate_webusb.md

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 development 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 396e1ba7197774884e05093bd2eced960eaeaa90.

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

• @michalsmiarowski:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk7SMgAL 5NY1277Utw5mA8i 1L9QkD7NpCS6kJU UaLrqKt0dBmkJli aBwygHAphsZOkJ4 MzIw7DDUL685PqM hzDapPzyiCsiW7a nG5saNnUH9JfSkj iKWPl0i8F4aTZZk iJ2LpY1w3Ujukde CZp9QGcxBZpIg6F 11WX1L2pW8gHuss YkPAHFYVMJx9ZAq sXQjJ0Qf4lHyQ2x QTs5nvxErxP6xX6 . END KEYBASE SALTPACK SIGNED MESSAGE.

• @r-czajkowski:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKYlB2X GFJeY9xtCM7xvtw JiHcqkwrXPjpQeO OPKKjvWVoSy7EUs XdbsOuejiJoSyUK 27xUiv2VTapmlUG jA0vIbIqR1cWaZf 9tMMRETgT1FrqTK vMvAu5K9AAA4CVa utCMx70UNLNjWZT xv3PMBWN8vwTQJL l4UnKF2eScING9S iXlMmGPlmLg847n aUrEH0Qf4lHyQ2x QTs5nvxErxP6xX6 . END KEYBASE SALTPACK SIGNED MESSAGE.

---

Docker image is available as docker pull keepnetwork/token-dashboard:v1.18.0; sha256sum is sha256:294cac04e99bd98706d537fd5c1392ec25401b2b10125db4e8083c58f8a48dd9.

---

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

Token Dashboard: 1.17.1 (Mainnet)

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

• Fixed a bug that cause undelegated and recovered stakes to be displayed in Application -> Threshold page.
• Restyle warnings informing grantees about the necessity to contact their grant manager first if they want to move the newly created stake to T (and provide grant manager email address).
• Fixed a bug that caused a need to refresh the Application -> Threshold page to see actual data, afer delegating or undelegating toknes.

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 development 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 6db8fcdd359259b5415b22a86a3f675bc5e4a6b4.

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

• @michalsmiarowski:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk7SMgAL 5NY1277Utw5mA8i 1L9QkD7NpCS6kJU UaLrqKt0dBqCisa fUTLjQ2k4IJf9kP gkgWSqwcR5TBAwd ftDBvpFhJJY7L8Y HQErk89MFl0aa8Y YAdkiy8z89xN9cr O2WnqRPRIQ8uBy1 qe6ZuE0yOPxkhZF hUHLENJuT5Pm0Kn llN6qld56LoAwnl 247uc0oRdKcikqg NniJW1x007NjSAm . END KEYBASE SALTPACK SIGNED MESSAGE.

• @r-czajkowski:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKYlB2X GFJeY9xtCM7xvtw JiHcqkwrXPjpQeO OPKKjvWVoT7ItTl JwLiZEmzmWtCQEk zPhl8lWNtIK7XlU 6xwj0jCLIflnsnP 1nfQC1VRdNaG7G4 Ctgr9K8RQuLmcIn g5iGHrjv3chuRpE 7uYRBccO3mFoAzf BIOe7QQz4ndkWqh qfVPspR9DlIk9aE cdOj40oRdKcikqg NniJW1x007NjSAm . END KEYBASE SALTPACK SIGNED MESSAGE.

---

Docker image is available as docker pull keepnetwork/token-dashboard:v1.17.1; sha256sum is sha256:794cf6c8386b03af5d80e217557048393028fac398be1789ba7203b62ad56d05.

---

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

Token Dashboard: 1.17.0 (Mainnet)

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

• Added a new Applications page that provides a possibility to migrate existing KEEP stake to Threshold network.
• Added a new Threshold page where token holders can see how many of their KEEP tokens are staked, how many tokens are withdrawable from grant, and how many of them can be upgraded to T.
• Added a warning in confirmation modal for delegating a stake from a grant informing grantees about the necessity to contact their grant manager first if they want to move the newly created stake to T.
• Added Grant Tokens and Wallet Tokens labels when displaying stakes in the table.
• A bunch of UI bug fixes that should improve user experience.

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 development 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 5a683d64dfec8f7c130c515d6b2b611d7ca77a72.

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

• @michalsmiarowski:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk7SMgAL 5NY1277Utw5mA8i 1L9QkD7NpCS6kJU UaLrqKt0dBSgJZb FdGSFP685Y9qokY pjT2iJGoRVsGalH JxWAvJd8VCpUcyQ tz9vna1T9InFoP9 pfzmFo7uLd0Miz5 CcKR3lAXvFzVQrV Gsr00o6hAw16Rl8 ZuBxVBgX2ET20VP K0aeEmoatzT4JLQ aGPMv0Rhe8IWedV 2yYHQfD4Hon8beU . END KEYBASE SALTPACK SIGNED MESSAGE.

• @nkuba:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkUgHswq LONGnytauGuQ68W zKcm0YTewHXEGd3 2M8FiSegAUHaofr qh73IGvxoN1l6vY 89QTjjRZ3zAJOnd zBGH7CkIVF6s89f rbRdX8WyrwuxyYC txJclZV41l7sbpf KsMlCvchi9joFbZ NyokDu9LA0LKcUX bgBtobgMiee6gYL jR0bqi1Y0i6tWIe dpO1x0Rhe8IWedV 2yYHQfD4Hon8beU . END KEYBASE SALTPACK SIGNED MESSAGE.

---

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

---

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

Token Dashboard: 1.16.2 (Mainnet)

token-dashboard/v1.16.2 is the latest release of the KEEP token dashboard. This patch release disables the KEEP/ETH pool because the incentives for this pool have been removed.

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 development 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 9266486032e71dca602767a3ad632d7cfc1c5773.

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

• @michalsmiarowski:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk7SMgAL 5NY1277Utw5mA8i 1L9QkD7NpCS6kJU UaLrqKt0dAtW2Jg uF1LIBRy8NM87cw 7xZbcJ60J3xlkcm TWYLDe7CfBias3J gr3fHL8vEbExraZ tDbzW3ip4A6RX0W HnMcGsxMGSqqTO8 BtiPdJsJhZRW95q OM6Q4f29UGpwzjl twAwC2toZecNFUw O1MF50oR1gSaXbF 5mZJXL7gEspIXx5 . END KEYBASE SALTPACK SIGNED MESSAGE.

• @r-czajkowski:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKYlB2X GFJeY9xtCM7xvtw JiHcqkwrXPjpQeO OPKKjvWVoTKHRPX UvIBPjzKA5BI9Vq siYhOaMzzl5fejs XZs4e7Ibj0RqZgZ zkYQNiYMTMFIjHp tnfVl2vwoQ4MpB0 F9YPrpTzWgg81yR pBBZY31TmAt7n85 buQYgkSaCYxGJUZ yI3Ke7SC3v3fgSH Cfw870oR1gSaXbF 5mZJXL7gEspIXx5 . END KEYBASE SALTPACK SIGNED MESSAGE.

---

Docker image is available as docker pull keepnetwork/token-dashboard:v1.16.2; sha256sum is sha256: 6774bd1675f319311e2cd338ef2ca900f74495b17d098c26b90088da22724532 .

---

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

Token Dashboard: 1.16.1 (Mainnet)

token-dashboard/v1.16.1 is the latest release of the KEEP token dashboard. This patch release fixes link to the mBTC/tBTCv2 pool.

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 development 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 c6f164b28046bfccc70759bec90ba3d0e9d54274.

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

• @michalsmiarowski:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zk7SMgAL 5NY1277Utw5mA8i 1L9QkD7NpCS6kJU UaLrqKt0dBss39X OCqutIN95apmrgD uutqU2C2CArAfKT GBN7vqxPkF61dLt KLX5IvIaF7Qmsiq tk1zYCqm8xS60ZD 9wG314YMczWPnzX VczcnR0I99Ru7Iv 7wIATH5r3cMZ5Nz 0woAvTPQVuhcIRl eq2xd0p3Ttpq2lw d7Piadje05JHOJo . END KEYBASE SALTPACK SIGNED MESSAGE.

• @r-czajkowski:
  BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkKYlB2X GFJeY9xtCM7xvtw JiHcqkwrXPjpQeO OPKKjvWVoTvf7g4 6Xm5Nf824PkNpem dwCMMtyEa34XHAB clixG2nEV7cAEEB N1Xxy7Ne9Fl2HK3 HA47vMaZTNgSXJT fjJB1MgAM8UQJ23 vMpfOY1AeXJqUp8 DWj0MqigRRCTR7d boztfaEDvcS9s0l t2DIf0p3Ttpq2lw d7Piadje05JHOJo . END KEYBASE SALTPACK SIGNED MESSAGE.

---

Docker image is available as docker pull keepnetwork/token-dashboard:v1.16.1; sha256sum is sha256:90e015b706273647761aa5c5b9a3a834438645c3db7aaf52524980bb014ee638 .

---

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