Rename cl group of contracts to anoncreds

Signed-off-by: artem.ivanov <[email protected]>

docs/README.md

@@ -17,7 +17,7 @@
 - Identity:
   - [DID Methods](design/did-methods.md) - Supported DID method
     - [IndyBesu DID Registry](design/indybesu-did-registry.md) - `indybesu` DID Registry
-  - [CL Registry](design/cl-registry.md)
+  - [Anoncreds Registry](design/cl-registry.md)
 - [Client](design/vdr.md) - design of VDR library
 
 ### Migration documents
@@ -27,7 +27,7 @@
 ### Development designs
 
 - [Roadmap](./roadmap.md)
-- [DID and CL registers approach](./design/registry.md)
+- [DID and Anoncreds registers approach](./design/registry.md)
 - [Transaction Endorsement](./design/endorsement.md)
 - [Contract upgradability](./design/upgradability.md)
 - [Legacy identifiers support](./design/legacy-identifiers-support.md)

docs/design/auth.md

@@ -232,7 +232,7 @@ Contract name: **transactionAllowed**
 | EthereumExtDidRegistry | changed               | any           | Get block number of latest DID change |
 | EthereumExtDidRegistry | nonce                 | any           | Get nonce to signe for endorsing      |
 
-### CL Registry management
+### Anoncreds Registry management
 
 | Contract                     | Method                           | Required Role               | Action Description                              |
 |------------------------------|----------------------------------|-----------------------------|-------------------------------------------------|

docs/design/contracts.puml

@@ -62,20 +62,20 @@ package "Smart Contracts" {
             component [Universal Did Resolver]
             note bottom of [Universal Did Resolver]
               Resolve Issuer DID from various DID registries
-              - used by CL contracts to verify did existence and owner
+              - used by AnonCreds contracts to verify did existence and owner
             end note
         }
 
-        package "CL" {
+        package "Anoncreds" {
 
             component [Schema Registry]
             note bottom of [Schema Registry]
-              Store CL schemas
+              Store AnonCreds schemas
             end note
 
             component [Credential Definition Registry]
             note top of [Credential Definition Registry]
-              Store CL Credential Definitions
+              Store AnonCreds Credential Definitions
             end note
         }
 

docs/design/did-methods.md

@@ -2,7 +2,7 @@
 
 Out of box Ledger provides an ability to use one of two supported DID methods: `did:ethr` or `did:indybesu`.
 
-Contracts implementing both methods are deployed on the network and integrated with `CL Registry`.
+Contracts implementing both methods are deployed on the network and integrated with `Anoncreds Registry`.
 
 Ledger `permission` related modules are implemented in a way to use **account address** but not a DID.
 

docs/design/endorsement.md

@@ -93,7 +93,7 @@ function changeOwnerSigned(address identity, uint8 sigV, bytes32 sigR, bytes32 s
 
 TO BE defined later.
 
-### CL Registry (Schema / Credential Definition)
+### Anoncreds Registry (Schema / Credential Definition)
 
 #### Flow
 

docs/design/registry.md

@@ -1,4 +1,4 @@
-## DID/CL Registries approach 
+## DID/Anoncreds Registries approach 
 
 General design for smart contracts oriented for storing objects like DID Document, Schema, Credential Definition.
 The main question is whether we need to validate storing object or not? 

docs/roadmap.md

@@ -14,7 +14,7 @@ Note: Right now we have finished PoC implementation. Roadmap tasks and their pri
 * Network identity implementation:
     * Indy2 DID method
       * Basic DID Document validation
-    * CL Registry:
+    * Anoncreds Registry:
       * Schema and Credential Definition registries with basic validation
 * Migration:
     * Design of migration from legacy (Indy) network
@@ -23,7 +23,7 @@ Note: Right now we have finished PoC implementation. Roadmap tasks and their pri
 * VDR:
     * Client library preparing and executing Ledger transactions (native part)
     * Support Indy2 DID Method
-    * CL Anoncreds entities (schema, credential definition)
+    * Anoncreds Anoncreds entities (schema, credential definition)
 * CI/CD
     * Basic pipelines
 * Docs
@@ -33,8 +33,8 @@ Note: Right now we have finished PoC implementation. Roadmap tasks and their pri
 
 * Network identity implementation:
     * Deprecate Indy2 method in favor of using `did:ethr` contract and specification
-    * CL Registry: implement event approach matching to `did:ethr` design
-    * Endorsement support for DID Documents and CL entities
+    * Anoncreds Registry: implement event approach matching to `did:ethr` design
+    * Endorsement support for DID Documents and Anoncreds entities
 * Network Permission implementation:
     * Restrict execution of transactions exclusively to users with specific roles
 * Network configuration
@@ -80,7 +80,7 @@ Note: Right now we have finished PoC implementation. Roadmap tasks and their pri
   * Support Indy 2.0 in ACA-Py
 * Migration:
     * Process finalization
-* CL Registry:
+* Anoncreds Registry:
     * Revocation entities support
 * Command Line Interface
 * CI/CD

network/config.json

@@ -27,11 +27,11 @@
             "address": "0x0000000000000000000000000000000000003333"
         },
         "schemaRegistry": {
-            "specPath": "smart_contracts/artifacts/contracts/cl/SchemaRegistry.sol/SchemaRegistry.json",
+            "specPath": "smart_contracts/artifacts/contracts/anoncreds/SchemaRegistry.sol/SchemaRegistry.json",
             "address": "0x0000000000000000000000000000000000005555"
         },
         "credDefRegistry": {
-            "specPath": "smart_contracts/artifacts/contracts/cl/CredentialDefinitionRegistry.sol/CredentialDefinitionRegistry.json",
+            "specPath": "smart_contracts/artifacts/contracts/anoncreds/CredentialDefinitionRegistry.sol/CredentialDefinitionRegistry.json",
             "address": "0x0000000000000000000000000000000000004444"
         },
         "legacyMappingRegistry": {