Pre-Release 1.2.2

v1.2.2-pre

Merge branch 'master' into update-docs-catchup

Release 0.12.1

Note

This release must be used instead of 0.12.0 when adding a new node to the Main Net form block 0 (see https://github.com/zigbee-alliance/distributed-compliance-ledger/blob/master/docs/advanced/running-node-in-existing-network.md#3-catchup-from-genesis)

What's Changed

• Validations fix for certification dates by @DenisRybas in #505 (see #503)

Pre-Release 1.2.1

Changes and Fixes (comparing to 0.12.0)

1. Update DCL Code for Approval count to ceiling instead of round #409
2. Feature: re-vote for pending #412
3. Feature: remove a proposal by the owner #287
4. Do not allow proposing Root certificate by non-Trustee #427
5. Deletion of Model Versions #421
6. Document subscribing to events via Tendermint WebSockets #414
7. Adding a Model requires "partNumber" and "productLabel" but those attributes should be optional #429
8. NFR: New Role with permission to add/update Vendor Info #430
9. Edit of DCL Compliance entry #464
10. Deletion of DCL Compliance entry #465
11. Set OTA for existing Model #466
12. DA PKI Revocation of PAI and VID-scoped PAA by Vendor #459
13. DA PKI Revocation of non-VID scoped PAAs by Vendor #479
14. Add a VID field for non-VID scoped PAAs (Root certificates) #477
15. A transaction for assigning a VID to non-VID scoped PAAs (root certificates) #478

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.2.0.
• The release must be applied to all nodes (Validators, Observers, Sentries, etc.)
• All upgraded nodes must be at 0.12.0 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. Starting a new node from the genesis state will not work. There are instructions on how to add a new node to the

Pre-Release 1.2.0

Changes and Fixes (comparing to 0.12.0)

1. Update DCL Code for Approval count to ceiling instead of round #409
2. Feature: re-vote for pending #412
3. Feature: remove a proposal by the owner #287
4. Do not allow proposing Root certificate by non-Trustee #427
5. Deletion of Model Versions #421
6. Document subscribing to events via Tendermint WebSockets #414
7. Adding a Model requires "partNumber" and "productLabel" but those attributes should be optional #429
8. NFR: New Role with permission to add/update Vendor Info #430
9. Edit of DCL Compliance entry #464
10. Deletion of DCL Compliance entry #465
11. Set OTA for existing Model #466
12. DA PKI Revocation of PAI and VID-scoped PAA by Vendor #459
13. DA PKI Revocation of non-VID scoped PAAs by Vendor #479
14. Add a VID field for non-VID scoped PAAs (Root certificates) #477
15. A transaction for assigning a VID to non-VID scoped PAAs (root certificates) #478

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.2.0.
• The release must be applied to all nodes (Validators, Observers, Sentries, etc.)
• All upgraded nodes must be at 0.12.0 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. Starting a new node from the genesis state will not work. There are instructions on how to add a new node to the

Pre-Release 1.1.1

Changes and Fixes

1. Update DCL Code for Approval count to ceiling instead of round #409
2. Feature: re-vote for pending #412
3. Feature: remove a proposal by the owner #287
4. Do not allow proposing Root certificate by non-Trustee #427
5. Deletion of Model Versions #421
6. Document subscribing to events via Tendermint WebSockets #414
7. Adding a Model requires "partNumber" and "productLabel" but those attributes should be optional #429
8. NFR: New Role with permission to add/update Vendor Info #430
9. Edit of DCL Compliance entry #464
10. Deletion of DCL Compliance entry #465
11. Set OTA for existing Model #466

Upgrade procedure

• The release is not intended to be applied to the production networks. It's for local testing only.

Release 0.12.0

Release 0.12.0

• 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 v0.12.0.
  • The release must be applied to all nodes (Validators, Observers, Sentries, etc.)
  • All upgraded nodes must be at 0.11.0 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. Starting a new node from the genesis state will not work. There are instructions on how to add a new node to the Test Net:
  • Running Node Index with examples for the Test Net
  • Adding new Observer nodes to Test Net
  • Adding new Validator nodes to Test Net

Major Changes (comparing to 0.11.0)

• Features:
  • New fields in Compliance Info schema
  • Be able to query device Compliance Info by CDCertificateID

Release 0.11.0

• 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 v0.11.0.
  • The release must be applied to all nodes (Validators, Observers, Sentries, etc.)
  • All upgraded nodes must be at 0.10.0 with cosmovisor enabled.
• The release contains a number of breaking changes which leads to the consequences mentioned below.
• 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. Starting a new node from the genesis state as described in running-node.md will not work. There are instructions on how to add a new node to the Test Net:
  • Adding new Observer nodes to Test Net
  • Adding new Validator nodes to Test Net
• Querying Certificates:
  • Certificates created before 0.10.0 must be queried as follows:
    • subject is a human readable string with unparsed VID/PID OIDS (before More human friendly way to display Matter OIDs in the certificates is fixed);
    • subject_key_id is a hex string without leading zeros.
  • Certificates created after 0.11.0 must be queried as follows:
    • subject is a certificates's Subject's DER sequence bytes encoded in base64 format;
    • subject_key_id is a hex string with leading zeros.
    • See transactions.md.
  • See Certificate SKID and subject should be unambiguous format for X509 transactions for details.
  • The reason for that difference is that data migration hasn't been done for the Test Net, so certificates created before 0.10.0 should be queried in the "old" way.

Major Changes (comparing to 0.10.0)

• Features:
  • Be able to reject a proposal
    • REJECT_ADD_X509_ROOT_CERT
    • REJECT_ADD_ACCOUNT
    • REJECT_DISABLE_VALIDATOR_NODE
    • REJECT_UPGRADE
  • Change Vendor Account Apporval to >=1/3 Trustee approval
• Defects Fixed:
  • Certificate subject must be a base64 encoded Subject DER sequence bytes, not base64 encoded Subject string
  • Be able to re-propose Upgrade with the same name if we don't get a quorum of Trustee approvals by the specified block height (time)
  • New accounts cannot be added even if there is a quorum of trustee approvals
  • Rename "FirmwareDigests" to "FirmwareInformation"

Release 0.10.0

• 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 v0.10.0.
  • The release must be applied to all nodes (Validators, Observers, Sentries, etc.)
  • All upgraded nodes must be at 0.9.0 with cosmovisor enabled.
• The release contains a number of breaking changes which leads to the consequences mentioned below.
• 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. Starting a new node from the genesis state as described in running-node.md will not work. There are instructions on how to add a new node to the Test Net:
  • Adding new Observer nodes to Test Net
  • Adding new Validator nodes to Test Net
• Querying Certificates:
  • Certificates created before 0.10.0 must be queried as follows:
    • subject is a human readable string with unparsed VID/PID OIDS (before More human friendly way to display Matter OIDs in the certificates is fixed);
    • subject_key_id is a hex string without leading zeros.
  • Certificates created after 0.10.0 must be queried as follows:
    • subject is a certificates's Subject in base64 format;
    • subject_key_id is a hex string with leading zeros.
    • See transactions.md.
  • See Certificate SKID and subject should be unambiguous format for X509 transactions for details.
  • The reason for that difference is that data migration hasn't been done for the Test Net, so certificates created before 0.10.0 should be queried in the "old" way.

Major Changes (comparing to 0.9.0)

• Features:
  • As a user, I need to be able to get the information about the created account even if the account is revoked
  • Validators: Revocation
• Defects Fixed:
  • Certificate SKID and subject should be unambiguous format for X509 transactions
  • More human friendly way to display Matter OIDs in the certificates
  • Defect: Certificate approval should need 2/3 Trustee Votes
  • VIDs should be hexadecimal values
  • typo "companyPrefferedName" in /dcl/vendorinfo/vendors
  • Defect: Account Approvals were getting overwritten in store

Release 0.9.0

• The release doesn't contain any breaking changes from the data/consensus point of view comparing to 0.7.0.
• The release can be safely applied by every Node Admin asynchronously (no need to coordinate and upgrade at the same time).
• The recommended way to apply the release to the Test Net is to use switch_to_cosmovisor script as described in switch to cosmovisor how to.
• The release contains a breaking change for the REST API (openapi): camel case instead of snake case is now used in JSON requests and replies for model, pki and compliance queries.

Major Changes (comparing to 0.7.0)

• Software upgrade and cosmovisor support
  • upgrade doc
  • upgrade how to
  • switch to cosmovisor how to
• REST API fix (breaking change): openapi uses camel case instead of snake case.

Release 0.8.0

Please don't upgrade to this release now!

• Software upgrade and cosmovisor support
  • upgrade doc
  • upgrade how to
  • switch to cosmovisor how to
• Bug fixes
  • Certificate approval should need 2/3 Trustee Votes
  • Defect Fix : Approvals were getting overwritten in store