From d9c69bd319faa24ba79e57ebdfdc33a89bb673f8 Mon Sep 17 00:00:00 2001 From: JC Pacheco Date: Thu, 20 Jun 2024 16:36:32 -0600 Subject: [PATCH 1/9] Create DistributedComplianceLedger.md Created content about DCL Introduction. --- AUTHORS.md | 1 + .../HowItWorks/DistributedComplianceLedger.md | 136 ++++++++++++++++++ 2 files changed, 137 insertions(+) create mode 100644 content/HowItWorks/DistributedComplianceLedger.md diff --git a/AUTHORS.md b/AUTHORS.md index e874b78..5c001fc 100644 --- a/AUTHORS.md +++ b/AUTHORS.md @@ -3,4 +3,5 @@ The following people have contributed to the contents of this site. - Ann Olivo - Jeff Bumgardner - Joni Thrift +- Juan Carlos Pacheco - Sam Machin \ No newline at end of file diff --git a/content/HowItWorks/DistributedComplianceLedger.md b/content/HowItWorks/DistributedComplianceLedger.md new file mode 100644 index 0000000..f359088 --- /dev/null +++ b/content/HowItWorks/DistributedComplianceLedger.md @@ -0,0 +1,136 @@ +# Distributed Compliance Ledger (DCL) + +## Table of Contents +- [DCL Introduction](#dcl-introduction) + - [Types of nodes that operate in the DCL](#types-of-accounts-that-can-interact-with-the-dcl) + - [Types of account roles that can interact with the DCL](#types-of-account-roles-that-can-interact-with-the-dcl) + - [Main-Net and Test-Net?](#main-net-and-test-net) + - [Access and Interaction with the DCL](#access-and-interaction-with-the-dcl) + - [Getting an account for writing to the DCL](#getting-an-account-for-writing-to-the-dcl) + - [Observer Nodes](#observer-nodes) + - [Main-Net public ONs](#main-net-public-ons) + - [Test-Net public ONs](#test-net-public-ons) +- [FAQs](#faqs) + - [Why is my Vendor information not listed in the DCL?](#why-is-my-vendor-information-not-listed-in-the-dcl) + - [How do I interact with the DCL?](#how-do-i-interact-with-the-dcl) + - [Web User Interface](#web-user-interface) + - [Command Line Interface](#command-line-interface) + - [When should I write my product information to the Main-Net DCL?](#when-should-i-write-my-product-information-to-the-main-net-dcl) +- [Contact](#contact) + +## DCL Introduction +The DCL is a blockchain-based system owned and hosted by Alliance members. It is used by the Matter protocol for storing information such as: + +- Vendor information: Information about the manufacturer or vendor of a device. Data is entered by an approved Vendor account. + +- Product information: Information about the device including description, software version, OTA information, etc. Data is entered by an approved Vendor account. + +- Compliance status: Information about the certification status including certification ID, certification date, etc. Data is entered by the Alliance's Certification team. + +- Product Attestation Authorities (PAA) Root CAs: Information about Root CAs used by commissioners during Device Attestation process. + Data is proposed by the Alliance's Trustee and approved by other Trustees. + +Additional information available in the [Distributed Compliance Ledger (DCL) Policies, Procedure and Governance](https://groups.csa-iot.org/wg/members-all/document/26075). + +### Types of nodes that operate in the DCL + +| Type of Node | Description | +| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | +| Validator Node (VN) | It participates in creating a "consensus" process to add information into the ledger. | +| Sentry Node (SN) | It doesn\'t participate in consensus and wraps the VN representing it for the rest of the network as one of the ways for DDoS and access protection. | +| Observer Node (ON) | It doesn\'t participate in consensus and is optimized for public data read and authenticated write interactions with the ledger. | + +### Types of account roles that can interact with the DCL + +| Account Role | Description | +| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | +| Trustee | It is entrusted to approve or deny other DCL roles and PAA Root CAs in the ledger, as well as to disable Validator Nodes. | +| Node Admin | It can instantiate a single Validator Node. | +| Vendor | It can write vendor and product information to the ledger. Alliance members can have one or more vendor accounts. | +| Vendor Admin | It can add and update the Vendor information table of the ledger. | +| Certification Center | It can submit, update, delete or revoke certification status of a product based on the Certification application in the Certification Tool. | + +### Main-Net and Test-Net + +| DCL Type | Description | +| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Main-Net | It is the DCL utilized by the public and is regarded as the production environment. Transactions on the Main-Net involve real products and data. | +| Test-Net | It is used for testing and development purposes. It provides a safe environment for experimentation and troubleshooting before deploying to the Main-Net. | + +### Access and interaction with the DCL + +- **Write** access to the ledger is restricted to approved accounts in the DCL. + +- **Read** access is broadly available through observer nodes. + +### Getting an account for writing to the DCL + +- Enrollment for a Main-Net DCL account is managed through the "DCL Account(s)" section in the Certification Tool system (Knack). You can request access to the Certification Tool + by sending an email to . + +> Note: The Certification Tool portal will depend on the Membership type. + +- Enrollment for a Test-Net DCL account can be requested by sending an email to + +Review the following document for instructions: [HowTo - Writing to the DCL.pdf](https://groups.csa-iot.org/wg/members-all/document/27881) + +### Interacting with the DCL + +There are different options available for users and/or systems to interact with the DCL: + +- Web User Interface, for intuitive navigation. +- API, for seamless integration. +- Command Line Interface (CLI), for efficient management. + +#### Web User Interface +The Web UI allows users to interact with the DCL through a visual interface, making tasks more intuitive and reducing the likelihood of errors. There is no need to install any +application client or configuration setup. + +#### Command Line Interface + +The DCL CLI software (dcld) allows users to interact with the DCL via command line using a connection to a specific available ON. The CLI software is available at the following link: +. + +The instructions for the DCL client are available at the following link: . + +### Observer Nodes + +An Observer Node (ON) offers APIs or Web User Interfaces for users or systems to interact with the DCL. This facilitates both manual and automated authorized writes, as well as +public queries to the DCL. + +It is not a requirement to deploy an Observer Node. The Alliance has ONs available in various regions across the globe, including trusted ONs managed by our members. This ensures +broad accessibility and reliable interaction with the DCL from different locations. + +#### Main-Net public ONs + +| Host Owner | Region | Web User Interface | URL for API | REST | RPC | gRPC | +| ---------------- | ------------ | ---------------------------------- | --------------------------- | ------- | ------- | ------- | +| The Alliance | US, EU | | on.dcl.csa-iot.org | 443 | 26657 | 8443 | +| TrustAsia | CN | | on.main-net.trustasia.com | 443 | 26657 | 8443 | + +#### Test-Net public ONs + +| Host Owner | Region | Web User Interface | URL for API | REST | RPC | gRPC | +| ---------------- | ------------ | ---------------------------------- | --------------------------- | ------- | ------- | ------- | +| The Alliance | US, EU | | on.test-net.dcl.csa-iot.org | 443 | 26657 | 8443 | +| TrustAsia | CN | | on.test-net.trustasia.com | 443 | 26657 | 8443 | + +## FAQs + +### Why is my Vendor information not listed in the DCL? + +Each member add their own Vendor information using an approved Vendor account. + +Review the following document for instructions: [HowTo - Writing to the DCL.pdf](https://groups.csa-iot.org/wg/members-all/document/27881) + +### When should I write my product information to the Main-Net DCL? + +The DCL\'s product information comprises a Model and a Model-Version of the product. Members add this information using an approved Vendor account. This can be done before or after +completing the certification process. The Compliance entry in the DCL is submitted by the Alliance's Certification team after the certification process is finalized. For this to +take place, the Model and Model-Version must already be listed in the DCL, match the data from the Certification Tool, and the member must notify the Certification team that the +DCL information is ready. + +Review the following document for instructions: [HowTo - Writing to the DCL.pdf](https://groups.csa-iot.org/wg/members-all/document/27881) + +## Contact +For any questions related to the DCL, please contact the DCL Admin (). \ No newline at end of file From eae0177e7ac6395fb83ed61fe380b8a4ff61f47b Mon Sep 17 00:00:00 2001 From: JC Pacheco Date: Thu, 20 Jun 2024 17:05:14 -0600 Subject: [PATCH 2/9] Update DistributedComplianceLedger.md --- .../HowItWorks/DistributedComplianceLedger.md | 32 +++++++++---------- 1 file changed, 15 insertions(+), 17 deletions(-) diff --git a/content/HowItWorks/DistributedComplianceLedger.md b/content/HowItWorks/DistributedComplianceLedger.md index f359088..ee456b2 100644 --- a/content/HowItWorks/DistributedComplianceLedger.md +++ b/content/HowItWorks/DistributedComplianceLedger.md @@ -2,33 +2,31 @@ ## Table of Contents - [DCL Introduction](#dcl-introduction) - - [Types of nodes that operate in the DCL](#types-of-accounts-that-can-interact-with-the-dcl) + - [Types of nodes that operate in the DCL](#types-of-nodes-that-operate-in-the-dcl) - [Types of account roles that can interact with the DCL](#types-of-account-roles-that-can-interact-with-the-dcl) - [Main-Net and Test-Net?](#main-net-and-test-net) - [Access and Interaction with the DCL](#access-and-interaction-with-the-dcl) - [Getting an account for writing to the DCL](#getting-an-account-for-writing-to-the-dcl) + - [Interacting with the DCL](#interacting-with-the-dcl) + - [Web User Interface](#web-user-interface) + - [Command Line Interface](#command-line-interface) - [Observer Nodes](#observer-nodes) - [Main-Net public ONs](#main-net-public-ons) - [Test-Net public ONs](#test-net-public-ons) - [FAQs](#faqs) - [Why is my Vendor information not listed in the DCL?](#why-is-my-vendor-information-not-listed-in-the-dcl) - - [How do I interact with the DCL?](#how-do-i-interact-with-the-dcl) - - [Web User Interface](#web-user-interface) - - [Command Line Interface](#command-line-interface) - [When should I write my product information to the Main-Net DCL?](#when-should-i-write-my-product-information-to-the-main-net-dcl) - [Contact](#contact) ## DCL Introduction The DCL is a blockchain-based system owned and hosted by Alliance members. It is used by the Matter protocol for storing information such as: -- Vendor information: Information about the manufacturer or vendor of a device. Data is entered by an approved Vendor account. - -- Product information: Information about the device including description, software version, OTA information, etc. Data is entered by an approved Vendor account. - -- Compliance status: Information about the certification status including certification ID, certification date, etc. Data is entered by the Alliance's Certification team. - -- Product Attestation Authorities (PAA) Root CAs: Information about Root CAs used by commissioners during Device Attestation process. - Data is proposed by the Alliance's Trustee and approved by other Trustees. +| Information | Description | Account Role involved | +| -------------------- | --------------------------------------------------------- | ------------------------------------------------------------------------------------------ | +| Vendor | Information about the manufacturer or vendor of a device. | Data is entered by an approved Vendor account. | +| Product | Information about the product device including description, software version, OTA information, etc. | Data is entered by an approved Vendor account. | +| Compliance status | Information about the certification status including certification ID, certification date, etc. | Data is entered by the Alliance's Certification Center account.| +| PAA Root CAs | Information about Product Attestation Authorities (PAA) Root CAs used by commissioners during Device Attestation process. | Data is proposed by the Alliance's Trustee and approved by other DCL Trustees.| Additional information available in the [Distributed Compliance Ledger (DCL) Policies, Procedure and Governance](https://groups.csa-iot.org/wg/members-all/document/26075). @@ -52,7 +50,7 @@ Additional information available in the [Distributed Compliance Ledger (DCL) Pol ### Main-Net and Test-Net -| DCL Type | Description | +| DCL Deployment | Description | | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | Main-Net | It is the DCL utilized by the public and is regarded as the production environment. Transactions on the Main-Net involve real products and data. | | Test-Net | It is used for testing and development purposes. It provides a safe environment for experimentation and troubleshooting before deploying to the Main-Net. | @@ -65,12 +63,12 @@ Additional information available in the [Distributed Compliance Ledger (DCL) Pol ### Getting an account for writing to the DCL -- Enrollment for a Main-Net DCL account is managed through the "DCL Account(s)" section in the Certification Tool system (Knack). You can request access to the Certification Tool +- Enrollment for Main-Net DCL accounts is managed through the "DCL Account(s)" section in the Certification Tool system (Knack). You can request access to the Certification Tool by sending an email to . > Note: The Certification Tool portal will depend on the Membership type. -- Enrollment for a Test-Net DCL account can be requested by sending an email to +- Enrollment for Test-Net DCL accounts can be requested by sending an email to Review the following document for instructions: [HowTo - Writing to the DCL.pdf](https://groups.csa-iot.org/wg/members-all/document/27881) @@ -119,7 +117,7 @@ broad accessibility and reliable interaction with the DCL from different locatio ### Why is my Vendor information not listed in the DCL? -Each member add their own Vendor information using an approved Vendor account. +Each member must add their own Vendor information using an approved Vendor account. Review the following document for instructions: [HowTo - Writing to the DCL.pdf](https://groups.csa-iot.org/wg/members-all/document/27881) @@ -133,4 +131,4 @@ DCL information is ready. Review the following document for instructions: [HowTo - Writing to the DCL.pdf](https://groups.csa-iot.org/wg/members-all/document/27881) ## Contact -For any questions related to the DCL, please contact the DCL Admin (). \ No newline at end of file +For any questions related to the DCL, please contact the DCL Admin (). From b07063bfc730c299d514a55b4ff23a13cee27216 Mon Sep 17 00:00:00 2001 From: JC Pacheco Date: Tue, 25 Jun 2024 10:54:19 -0400 Subject: [PATCH 3/9] Update DistributedComplianceLedger.md Added Tuya ON info. --- content/HowItWorks/DistributedComplianceLedger.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/HowItWorks/DistributedComplianceLedger.md b/content/HowItWorks/DistributedComplianceLedger.md index ee456b2..9917948 100644 --- a/content/HowItWorks/DistributedComplianceLedger.md +++ b/content/HowItWorks/DistributedComplianceLedger.md @@ -105,6 +105,7 @@ broad accessibility and reliable interaction with the DCL from different locatio | ---------------- | ------------ | ---------------------------------- | --------------------------- | ------- | ------- | ------- | | The Alliance | US, EU | | on.dcl.csa-iot.org | 443 | 26657 | 8443 | | TrustAsia | CN | | on.main-net.trustasia.com | 443 | 26657 | 8443 | +| Tuya | CN | N/A | on-dcl.tuyacn.com | 1317 | 26657 | 9090 | #### Test-Net public ONs @@ -112,6 +113,7 @@ broad accessibility and reliable interaction with the DCL from different locatio | ---------------- | ------------ | ---------------------------------- | --------------------------- | ------- | ------- | ------- | | The Alliance | US, EU | | on.test-net.dcl.csa-iot.org | 443 | 26657 | 8443 | | TrustAsia | CN | | on.test-net.trustasia.com | 443 | 26657 | 8443 | +| Tuya | CN | N/A | on-dcl-testnet.tuyacn.com | 1317 | 26657 | 9090 | ## FAQs From cc421d64eb3d5d68ed7372c2b0e5e61e3df6a3ff Mon Sep 17 00:00:00 2001 From: Sam Machin Date: Wed, 10 Jul 2024 12:03:30 +0100 Subject: [PATCH 4/9] MOve DCL to Guides and add header --- .../DistributedComplianceLedger.md | 6 ++++++ content/Guides/_index.md | 12 ++++++++++++ 2 files changed, 18 insertions(+) rename content/{HowItWorks => Guides}/DistributedComplianceLedger.md (97%) create mode 100644 content/Guides/_index.md diff --git a/content/HowItWorks/DistributedComplianceLedger.md b/content/Guides/DistributedComplianceLedger.md similarity index 97% rename from content/HowItWorks/DistributedComplianceLedger.md rename to content/Guides/DistributedComplianceLedger.md index 9917948..a2611c8 100644 --- a/content/HowItWorks/DistributedComplianceLedger.md +++ b/content/Guides/DistributedComplianceLedger.md @@ -1,3 +1,9 @@ ++++ +title = "Distributed Compliance Ledger" +chapter = false +weight = 10 ++++ + # Distributed Compliance Ledger (DCL) ## Table of Contents diff --git a/content/Guides/_index.md b/content/Guides/_index.md new file mode 100644 index 0000000..24c5a41 --- /dev/null +++ b/content/Guides/_index.md @@ -0,0 +1,12 @@ ++++ +title = "Guides" +chapter = true +weight = 5 +pre = "5. " ++++ + +# Guides + +This section contains detailed explanations of specific areas of Matter, There is not yet comprehensive coverage of all areas but we will endevour to expand the topics over time. + + From d87c8ee72e5f2984eed87e42484eca2f165d094e Mon Sep 17 00:00:00 2001 From: Sam Machin Date: Wed, 10 Jul 2024 14:22:50 +0100 Subject: [PATCH 5/9] Update content/Guides/DistributedComplianceLedger.md --- content/Guides/DistributedComplianceLedger.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/Guides/DistributedComplianceLedger.md b/content/Guides/DistributedComplianceLedger.md index a2611c8..093b37e 100644 --- a/content/Guides/DistributedComplianceLedger.md +++ b/content/Guides/DistributedComplianceLedger.md @@ -1,5 +1,6 @@ +++ -title = "Distributed Compliance Ledger" +title = "Distributed Compliance Ledger (DCL)" + chapter = false weight = 10 +++ From 750209f66eeb347477f525807687d9c6599a32b7 Mon Sep 17 00:00:00 2001 From: Sam Machin Date: Wed, 10 Jul 2024 14:22:54 +0100 Subject: [PATCH 6/9] Update content/Guides/DistributedComplianceLedger.md --- content/Guides/DistributedComplianceLedger.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/Guides/DistributedComplianceLedger.md b/content/Guides/DistributedComplianceLedger.md index 093b37e..fda5d2b 100644 --- a/content/Guides/DistributedComplianceLedger.md +++ b/content/Guides/DistributedComplianceLedger.md @@ -5,7 +5,6 @@ chapter = false weight = 10 +++ -# Distributed Compliance Ledger (DCL) ## Table of Contents - [DCL Introduction](#dcl-introduction) From b0785078296e9a057a1f06fa1f032379ddb2d1bc Mon Sep 17 00:00:00 2001 From: JC Pacheco Date: Mon, 15 Jul 2024 15:29:27 -0600 Subject: [PATCH 7/9] Update content/Guides/_index.md Implemented suggestion. Co-authored-by: Jeff Bumgardner --- content/Guides/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/Guides/_index.md b/content/Guides/_index.md index 24c5a41..478ec3e 100644 --- a/content/Guides/_index.md +++ b/content/Guides/_index.md @@ -7,6 +7,6 @@ pre = "5. " # Guides -This section contains detailed explanations of specific areas of Matter, There is not yet comprehensive coverage of all areas but we will endevour to expand the topics over time. +This section contains detailed explanations of specific areas of Matter. There is not yet comprehensive coverage of all areas but we will endeavor to expand the topics over time. From bc1c98c7a7b89f7acbc76881031d6e8e253f760a Mon Sep 17 00:00:00 2001 From: JC Pacheco Date: Mon, 15 Jul 2024 15:31:36 -0600 Subject: [PATCH 8/9] Update DistributedComplianceLedger.md Implemented feedback --- content/Guides/DistributedComplianceLedger.md | 41 +++++++++---------- 1 file changed, 20 insertions(+), 21 deletions(-) diff --git a/content/Guides/DistributedComplianceLedger.md b/content/Guides/DistributedComplianceLedger.md index fda5d2b..18ba80c 100644 --- a/content/Guides/DistributedComplianceLedger.md +++ b/content/Guides/DistributedComplianceLedger.md @@ -27,12 +27,12 @@ weight = 10 ## DCL Introduction The DCL is a blockchain-based system owned and hosted by Alliance members. It is used by the Matter protocol for storing information such as: -| Information | Description | Account Role involved | -| -------------------- | --------------------------------------------------------- | ------------------------------------------------------------------------------------------ | -| Vendor | Information about the manufacturer or vendor of a device. | Data is entered by an approved Vendor account. | -| Product | Information about the product device including description, software version, OTA information, etc. | Data is entered by an approved Vendor account. | -| Compliance status | Information about the certification status including certification ID, certification date, etc. | Data is entered by the Alliance's Certification Center account.| -| PAA Root CAs | Information about Product Attestation Authorities (PAA) Root CAs used by commissioners during Device Attestation process. | Data is proposed by the Alliance's Trustee and approved by other DCL Trustees.| +| Information | Description | Account Role involved | +| -------------------- | --------------------------------------------------------- | ------------------------------------------------------------------------ | +| Vendor | The manufacturer or vendor of a device. | Data is entered by an approved Vendor account. | +| Product | The product device including description, software version, OTA information, etc. | Data is entered by an approved Vendor account. | +| Compliance status | The certification status including certification ID, certification date, etc. | Data is entered by the Alliance's Certification Center account.| +| PAA Root CAs | Product Attestation Authorities (PAA) Root CAs used by commissioners during Device Attestation process. | Data is proposed by the Alliance's Trustee and approved by other DCL Trustees.| Additional information available in the [Distributed Compliance Ledger (DCL) Policies, Procedure and Governance](https://groups.csa-iot.org/wg/members-all/document/26075). @@ -40,26 +40,26 @@ Additional information available in the [Distributed Compliance Ledger (DCL) Pol | Type of Node | Description | | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | -| Validator Node (VN) | It participates in creating a "consensus" process to add information into the ledger. | -| Sentry Node (SN) | It doesn\'t participate in consensus and wraps the VN representing it for the rest of the network as one of the ways for DDoS and access protection. | -| Observer Node (ON) | It doesn\'t participate in consensus and is optimized for public data read and authenticated write interactions with the ledger. | +| Validator Node (VN) | Participates in creating the consensus process to add information into the ledger. The consensus is the process by which the nodes agree on the state and data of the blockchain; ensuring all nodes have a consistent ledger, while verifying the validity of transactions. | +| Sentry Node (SN) | Doesn\'t participate in consensus and wraps the VN representing it for the rest of the network as one of the ways for DDoS and access protection. | +| Observer Node (ON) | Doesn\'t participate in consensus and is optimized for public data read and authenticated write interactions with the ledger. | ### Types of account roles that can interact with the DCL -| Account Role | Description | -| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | -| Trustee | It is entrusted to approve or deny other DCL roles and PAA Root CAs in the ledger, as well as to disable Validator Nodes. | -| Node Admin | It can instantiate a single Validator Node. | -| Vendor | It can write vendor and product information to the ledger. Alliance members can have one or more vendor accounts. | -| Vendor Admin | It can add and update the Vendor information table of the ledger. | -| Certification Center | It can submit, update, delete or revoke certification status of a product based on the Certification application in the Certification Tool. | +| Account Role | Description | +| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| Trustee | Entrusted to approve or deny other DCL roles and PAA Root CAs in the ledger, as well as to disable Validator Nodes. | +| Node Admin | Can instantiate a single Validator Node. | +| Vendor | Can write vendor and product information to the ledger. Alliance members can have one or more vendor accounts. | +| Vendor Admin | Can add and update the Vendor information table of the ledger. | +| Certification Center | Can submit, update, delete or revoke certification status of a product based on the Certification application in the Certification Tool. | ### Main-Net and Test-Net | DCL Deployment | Description | | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Main-Net | It is the DCL utilized by the public and is regarded as the production environment. Transactions on the Main-Net involve real products and data. | -| Test-Net | It is used for testing and development purposes. It provides a safe environment for experimentation and troubleshooting before deploying to the Main-Net. | +| Main-Net | The production environment that is utilized by the public. Transactions on the Main-Net involve real products and data. | +| Test-Net | Used for testing and development purposes. It provides a safe environment for experimentation and troubleshooting before deploying to the Main-Net. | ### Access and interaction with the DCL @@ -87,12 +87,11 @@ There are different options available for users and/or systems to interact with - Command Line Interface (CLI), for efficient management. #### Web User Interface -The Web UI allows users to interact with the DCL through a visual interface, making tasks more intuitive and reducing the likelihood of errors. There is no need to install any -application client or configuration setup. +The Web UI allows users to interact with the DCL through a visual interface, making tasks more intuitive and reducing the likelihood of errors. There is no need to install any application client or configuration setup. #### Command Line Interface -The DCL CLI software (dcld) allows users to interact with the DCL via command line using a connection to a specific available ON. The CLI software is available at the following link: +The DCL CLI software (`dcld`) allows users to interact with the DCL via command line using a connection to a specific available Observer Node. The CLI software is available at the following link: . The instructions for the DCL client are available at the following link: . From 882ed473269bf80eb2ad9bf8aeba05ddf6376645 Mon Sep 17 00:00:00 2001 From: Sam Machin Date: Wed, 17 Jul 2024 16:09:49 +0100 Subject: [PATCH 9/9] Update content/Guides/DistributedComplianceLedger.md Co-authored-by: Jeff Bumgardner --- content/Guides/DistributedComplianceLedger.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/Guides/DistributedComplianceLedger.md b/content/Guides/DistributedComplianceLedger.md index 18ba80c..d29314e 100644 --- a/content/Guides/DistributedComplianceLedger.md +++ b/content/Guides/DistributedComplianceLedger.md @@ -40,7 +40,8 @@ Additional information available in the [Distributed Compliance Ledger (DCL) Pol | Type of Node | Description | | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | -| Validator Node (VN) | Participates in creating the consensus process to add information into the ledger. The consensus is the process by which the nodes agree on the state and data of the blockchain; ensuring all nodes have a consistent ledger, while verifying the validity of transactions. | +| Validator Node (VN) | Participates in creating the consensus process to add information into the ledger. The consensus is the process by which the nodes agree on the state and data of the blockchain, ensuring all nodes have a consistent ledger while verifying the validity of transactions. | + | Sentry Node (SN) | Doesn\'t participate in consensus and wraps the VN representing it for the rest of the network as one of the ways for DDoS and access protection. | | Observer Node (ON) | Doesn\'t participate in consensus and is optimized for public data read and authenticated write interactions with the ledger. |