Skip to content

v3.0.5

Latest
Latest
Compare
Choose a tag to compare
@ayushmishra2005 ayushmishra2005 released this 28 Jun 09:09
· 5 commits to master since this release
v3.0.5
9eceb50
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

docs: update docs with questions #205
fix: remove bootnode since not static and fix incorrect key of validator 10 #203
feat: Add Harbour nodes 5-10 #199

[Edit 29 June 2021 @ CET 1337]

Upgrade Priority:

Westlake: High
Harbour: High

Summary

  • Fixed Harbour as it was not generating blocks.
  • Added Multisig functionality to distribute funds to third parties. DataHighway needs to send DHX tokens to Supernode accounts via a Proxy account from the Treasury account for them to recognise the transactions. The Proxy account will be controlled via a multisig. The multisig signatories will check that all third parties (e.g. supernodes and exchanges) are able to return Harbour HBR tokens (testnet) sent from the multisig Proxy account to provide assurance that they are able to parse multisig transactions prior to sending them any Westlake DHX tokens (mainnet). See DataHighway Whitepaper Financial Model
  • Added validators 5-10 to chain specification. After this on-chain upgrade the additional nodes could connect to Harbour.

Impacted Parties

This release should affect Westlake nodes now that an on-chain upgrade to spec_version 8 has occurred.

[Edit 29 June 2021 @ CET 1638] After the forkless on-chain upgrade the built binary (built locally or on the server) should be copied and distributed to all validators and bootnodes so they have the latest non-runtime changes. Copy attached as datahighway_runtime.compactv3.0.5.wasm

Harbour has been restored and nodes may be added again.

Release Tests

Multsig

This release was used to upgrade Harbour to spec_version 8 via an on-chain upgrade where the new Multisig pallet functionality is going to be tested by the multisig signatories to confirm that transaction with HBR tokens are able to be sent from a Multisig proxy account to all external parties and that those HBR tokens are returned back to the Multisig proxy account by those same external parties to provide assurance that their systems are able to parse multisig transactions correctly.

Additional Validators

Harbour

Additional validators and full nodes may be added. See DataHighway Developer Hub

Westlake

Further investigation is required prior to adding additional validators and full nodes to Westlake.

Changes

Runtime

Local

  • Added replacement Bootnode Node ID for running Local chain (#198)
  • Updated FAQ to mention replacement Bootnode Node ID and use --chain local instead of chain definition file for running Local chain (#205)

Harbour

  • Added Harbour nodes 5-10 to chain specification and endow each account (#199)
  • Fixed incorrect grandpa key of validator 10 so it authors blocks (#203)
  • Removed bootnode for Harbour from chain specification since it is not static (#203)
  • Generated and used new Bootnode Node ID for Harbour so we have its Node Key to be published at DataHighway Developer Hub
  • Incremented runtime spec_version to 8 via on-chain upgrade (#204)

Westlake

  • Incremented runtime spec_version to 8 via on-chain upgrade (#204). This was only going to be performed after receiving assurance that external parties had returned HBR tokens sent to them as assurance that their systems are able to parse multisig transactions correctly, however the exchange that previously would not support parsing transactions received from the Sudo account has also indicated that they do not want to work using our Harbour testnet, so we have no choice but to instead use Westlake mainnet to test that they are able to parse transactions received from a multisig account correctly (using a small amount of DHX).
Assets 3