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.