Merge branch '#560-Enable-removing-ICA-certs' into #524-Enable-removing-NOC-root-certs

Author: Abdulbois

.github/.wordlist.txt

@@ -86,4 +86,6 @@ ul
 WebSocket
 cometbft
 CometBFT
-CometBFT's
+CometBFT's
+distributedcoplianceledger
+zigbeealliance

README-DEV.md

@@ -157,8 +157,12 @@ Please take into account the following when sending a PR:
   Consider using a docker container built from the provided [Dockerfile](scripts/Dockerfile) to have a predictable version of ignite. See [README.md](scripts/README.md).
 - Have a look at the scripts and commands used for generation of existing modules, messages and CRUD operations and do it in a similar way
   (for example [PKI module commands](scripts/starport/upgrade-0.44/07.pki_types.sh)).
-  Note: On previous scaffolding of modules `starport` cli used instead of `ignite`. 
-         While generating new module, command structure will the same except it must start with `ignite`.
+  - 
+    **Note**:
+    1. On previous scaffolding of modules `starport` cli used instead of `ignite`. 
+               While generating new module, command structure will the same except it must start with `ignite`.
+    2. After execution of command `ignite scaffold ...` generated `.proto` files will be added into `proto/distributedcoplianceledger/{module}/{proto}`
+    . So make sure to put contents of generated proto files into related folders inside `proto/zigbeealliance/..` folder.
 - If a new transaction with a new data in state (key-value) and new queries needs to be created, then both message and CRUD commands need to be executed.
 - If just a message to update existing state values need to be created, then a message command is enough.  
 - Adjust the generated code

docs/CHANGELOG.md

@@ -0,0 +1,15 @@
+## [v1.4.0-dev3](https://github.com/zigbee-alliance/distributed-compliance-ledger/releases/tag/v1.4.0-dev3) - 2024-04-24
+
+### Dependency Changes
+* Upgrade cosmos-sdk to v0.47.8
+  * Migrate to CometBFT. Follow the migration instructions in the [upgrade guide](https://github.com/cosmos/cosmos-sdk/blob/main/UPGRADING.md#migration-to-cometbft-part-1).
+  * Upgrade all related dependencies too 
+* Upgrade Golang version to 1.20
+
+### Breaking Changes
+* 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."
+* `starport` cli tool is no longer supported. Please use `v0.27.2` version of [ignite](https://github.com/ignite/cli).
+* 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`

docs/how-to.md

@@ -48,7 +48,7 @@ Here is the list of supported settings:
 - `output <type>` - Output format (text/json)
 - `node <node-ip>` - Address `<host>:<port>` of the node to connect.
 - `broadcast-mode <mode>` - Write transaction broadcast mode to use (one of: `sync`, `async`. `sync` is default). 
-  - Note: In `sync` broadcast mode, to get the actual result of transaction(`dcld tx ..`) one more query call with `txHash` must be executed(`dcld query tx=txHash`)
+  - Note: To get the actual result of transaction(`dcld tx ..`) one more query call with the `txHash` must be executed(`dcld query tx txHash`)
 
 In order to connect the CLI to a DC Ledger Network (Chain), the following parameters should be used:
 

docs/running-light-client-proxy.md

@@ -9,7 +9,7 @@ A Full Node (Validator or Observer) should be used for multi-value query request
 
 See the following links for details about a Light Client:
 
-- <https://docs.cometbft.com/main/explanation/core/light-client>
+- <https://docs.cometbft.com/v0.37/core/light-client>
 
 ## Running Light Client Proxy - Short
 
@@ -21,7 +21,7 @@ dcld config node tcp://<light-client-proxy-host>:8888
 
 ## Running Light Client Proxy - Detailed
 
-See <https://docs.cometbft.com/main/explanation/core/light-client> for details
+See <https://docs.cometbft.com/v0.37/core/light-client> for details
 
 ### 1. Choose Semi-trusted or Non-trusted Nodes for Connection
 

genlocalnetconfig.sh

@@ -175,8 +175,6 @@ for node_name in node0 node1 node2 node3 observer0; do
         sed -i $SED_EXT 's/laddr = "tcp:\/\/127.0.0.1:26657"/laddr = "tcp:\/\/0.0.0.0:26657"/g' "$LOCALNET_DIR/${node_name}/config/config.toml"
         # Make REST endpoints available externally
         sed -i $SED_EXT 's/address = "tcp:\/\/localhost:1317"/address = "tcp:\/\/0.0.0.0:1317"/g' "$LOCALNET_DIR/${node_name}/config/app.toml"
-        # Make gRPC endpoints available externally
-        sed -i $SED_EXT 's/address = "localhost:9090"/address = "0.0.0.0:9090"/g' "$LOCALNET_DIR/${node_name}/config/app.toml"
 
         # Make REST endpoints available externally
         sed -i $SED_EXT 's/address = "tcp:\/\/localhost:1317"/address = "tcp:\/\/0.0.0.0:1317"/g' "$LOCALNET_DIR/${node_name}/config/app.toml"

scripts/README.md

@@ -29,6 +29,11 @@ Build proto (for example `buf generate --template buf.gen.gogo.yaml`).
 ```bash
 ./scripts/protocgen.sh
 ```
+or 
+
+```bash
+ignite chain build
+```
 
 Generate Cosmos base openapi