Skip to content

1.4.4-2-dev

Pre-release
Pre-release
Compare
Choose a tag to compare
@Artemkaaas Artemkaaas released this 07 Nov 10:12
· 15 commits to pki-compatibility since this release

What's Changed (comparing to 1.2.2)

Updates in Data Models and API (new optional fields)

  • All Data Models:
    • optional field schemaVersion field (default - 0)
  • Account:
  • Model:
    • optional fields enhancedSetupFlowOptions, enhancedSetupFlowTCUrl, enhancedSetupFlowTCRevision, enhancedSetupFlowTCDigest, enhancedSetupFlowTCFileSize, maintenanceUrl, discoveryCapabilitiesBitmask, commissioningFallbackUrl (see ADD_MODEL and model.proto)

Updates in Data Models

  • PKI
    • enum field certificateType (see certificate.proto) pointing to the type of added certificate and having the following definition:
    enum CertificateType {
       DeviceAttestationPKI = 0;
       OperationalPKI = 1;
       VIDSignerPKI = 2;
    }
    

New API

Updates in Logic and API

Other

  • Transaction broadcasting block mode has been removed from the updated cosmos-sdk. Starting from this version, dcl has only two modes: sync and async, with the default being sync. In this mode, to obtain the actual result of a transaction (txn), an additional query call with the txHash must be executed. For example: dcld query tx txHash - where txHash represents the hash of the previously executed transaction.
  • Due to upgrading cosmovisor to v1.3.0 in Docker and shell files, the node starting command has changed from cosmovisor start to cosmovisor run start

Documentation Updates

Full List of Issues

https://github.com/zigbee-alliance/distributed-compliance-ledger/milestone/6

Full Changelog

Upgrade procedure

  • The release must be applied via cosmovisor and Upgrade Proposal transactions, see pool-upgrade-how-to.md.
  • The upgrade name must be equal to v1.4.4.
  • The release must be applied to all nodes (Validators, Observers, Sentries, etc.)
  • All upgraded nodes must be at v1.4.4 with cosmovisor enabled.
  • It's recommended to enable the auto-download for cosmovisor on all nodes, see pool-upgrade-how-to.md.
  • Adding new nodes to the running pool (Test Net in particular) must be done via one of the ways described in running-node-in-existing-network.md.