#
Distributed Compliance Ledger (DCL)
#
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:
Additional information available in the Distributed Compliance Ledger (DCL) Policies, Procedure and Governance.
#
Types of nodes that operate in the DCL
#
Types of account roles that can interact with the DCL
#
Main-Net and Test-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 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 help@csa-iot.org.
Note
The Certification Tool portal will depend on the Membership type.
- Enrollment for Test-Net DCL accounts can be requested by sending an email to dcl-admin@csa-iot.org
Review the following document for instructions: HowTo - Writing to the DCL.pdf
#
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 Observer Node. The CLI software is available at the following link:
https://github.com/zigbee-alliance/distributed-compliance-ledger/releases.
The instructions for the DCL client are available at the following link: https://github.com/zigbee-alliance/distributed-compliance-ledger/blob/master/docs/how-to.md.
#
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
#
Test-Net public ONs
#
FAQs
#
Why is my Vendor information not listed in the DCL?
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
#
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
#
Contact
For any questions related to the DCL, please contact the DCL Admin (dcl-admin@csa-iot.org).