Merge pull request #190 from 0xPolygonID/privado-idenity-chain

Documentation for Privado Identity Chain
0xPolygonID · Oct 22, 2024 · b6ffc5b · b6ffc5b
2 parents cadab76 + 9ddc326
commit b6ffc5b
Show file tree

Hide file tree

Showing 6 changed files with 55 additions and 50 deletions.
diff --git a/docs/issuer/issuer-overview.md b/docs/issuer/issuer-overview.md
@@ -76,35 +76,4 @@ The [Issuer Node UI](issuer-node-ui.md) provides the full experience of having a
 <img src= {useBaseUrl("img/8088.png")} align="center" />
 </div>
 
-### Privado Identity Chain
 
-The Privado Identity Chain, currently in beta with limited functionality, is a blockchain network designed to serve as the primary chain for user identities. It will act as the authoritative source of truth, enabling other chains to synchronize their state with it. This chain is essential for preventing the fragmentation of identities and credentials across the various chains we will be working with, ensuring that identities and credentials remain consistent and reusable across all chains.
-
-DIDs associated with the Privado Identity Chain will follow a prefix format:
-<Tabs>
-<TabItem value="Mainnet">
-
-```main
-did:iden3:privado:main:
-```
-</TabItem>
-<TabItem value="Testnet">
-
-```test
-did:iden3:privado:test:
-```
-</TabItem>
-</Tabs>
-For example, a DID would look like this:
-
-did:iden3:privado:main:2Se4SGXrGrsfrCY8KPRT8R4ZbP91f6sAuBTt8xgA1W
-
-:::note
-State transitions and MTP issuance are not currently supported.
-:::
-
-:::caution
-Currently, a few issuers, such as Synaps, are deployed on the Privado Identity Chain. During the beta phase, where the chain has limited functionality, issuers can continue to use other supported chains, such as Polygon POS.
-
-Once the full version of the Privado Identity Chain is released, issuers on both the Privado chain and other supported chains will remain supported, ensuring seamless operation and interoperability across multiple chains.
-:::
diff --git a/docs/privado-identity-chain.md b/docs/privado-identity-chain.md
@@ -0,0 +1,44 @@
+---
+id: privado-identity-chain
+title: Privado Identity Chain
+sidebar_label: Privado Identity Chain
+keywords:
+  - privado id
+  - chain
+  - identity
+  - privado identity chain
+  - network
+---
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+The Privado Identity Chain, currently in beta with limited functionality, is a blockchain network designed to serve as the primary chain for user identities. It will act as the authoritative source of truth, enabling other chains to synchronize their state with it. This chain is essential for preventing the fragmentation of identities and credentials across the various chains we will be working with, ensuring that identities and credentials remain consistent and reusable across all chains.
+
+### Configuration:
+
+- **RPC**: `https://rpc-mainnet.privado.id`
+- **Chain ID**: `21000` 
+
+Details regarding the smart contracts and their deployment addresses can be found [here.](./smart-contracts.md)
+
+### DIDs:
+DIDs associated with the Privado Identity Chain will follow a prefix format:
+
+```main
+did:iden3:privado:main:
+```
+
+For example, a DID would look like this:
+
+`did:iden3:privado:main:2Se4SGXrGrsfrCY8KPRT8R4ZbP91f6sAuBTt8xgA1W`
+
+:::note
+The Privado Identity Chain is currently accessible in a read-only mode.
+<!-- State transitions and MTP issuance are not currently supported. -->
+:::
+
+:::caution
+Currently, a few issuers, such as Synaps, are deployed on the Privado Identity Chain. During the beta phase, where the chain has limited functionality, issuers can continue to use other supported chains, such as Polygon POS.
+
+Once the full version of the Privado Identity Chain is released, issuers on both the Privado Identity Chain and other supported chains will remain supported, ensuring seamless operation and interoperability across multiple chains.
+:::
diff --git a/docs/smart-contracts.md b/docs/smart-contracts.md
@@ -9,7 +9,7 @@ keywords:
   - smart
   - contract
 ---
-
+import useBaseUrl from '@docusaurus/useBaseUrl';
 
 <a href="https://github.com/iden3/contracts" target="_blank">Privado ID Smart Contracts - Github</a>
 
@@ -20,20 +20,19 @@ As part of our unified address methodology, we deployed contracts via the CREATE
 We have deployed contracts across the following mainnets and testnets so far:
 
 **Mainnets**:
-
+- [Privado Identity Chain](/docs/privado-identity-chain)
 - [Ethereum](https://etherscan.io/address/0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896)
 - [Polygon POS](https://polygonscan.com/address/0x624ce98d2d27b20b8f8d521723df8fc4db71d79d)
 - [Polygon zkEVM](https://zkevm.polygonscan.com/address/0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896)
 - [Linea](https://lineascan.build/address/0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896)
-- Privado Mainnet
 
 **Testnets**:
 
 - [Ethereum Sepolia](https://sepolia.etherscan.io/address/0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896)
 - [Polygon Amoy](https://amoy.polygonscan.com/address/0x1a4cc30f2aa0377b0c3bc9848766d90cb4404124)
 - [Polygon zkEVM Cardona](https://cardona-zkevm.polygonscan.com/address/0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896)
 - [Linea-Sepolia](https://sepolia.lineascan.build/address/0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896)
-- Privado Testnet
+
 
 ## Unified contract addresses
 
@@ -47,8 +46,8 @@ It’s important to note that the State contracts for the following two networks
 |   Smart Contract Type        |                 Unified Address                   |
 | :----------------------: | :----------------------------------------: |
 |   **STATE* **    |  0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896 |
-|   **VALIDATOR_MTP**    | 0x27bDFFCeC5478a648f89764E22fE415486A42Ede |
-| **VALIDATOR_SIG** | 0x59B347f0D3dd4B98cc2E056Ee6C53ABF14F8581b |
+|   **VALIDATOR_MTP_V2**    | 0x27bDFFCeC5478a648f89764E22fE415486A42Ede |
+| **VALIDATOR_SIG_V2** | 0x59B347f0D3dd4B98cc2E056Ee6C53ABF14F8581b |
 | **VALIDATOR_V3** | 0xd179f29d00Cd0E8978eb6eB847CaCF9E2A956336 |
 | **UNIVERSAL_VERIFIER** | 0xfcc86A79fCb057A8e55C6B853dff9479C3cf607c |
 | **IDENTITY_TREE_STORE** | 0x7dF78ED37d0B39Ffb6d4D527Bb1865Bf85B60f81 |

diff --git a/docs/verifier/on-chain-verification/overview.md b/docs/verifier/on-chain-verification/overview.md
@@ -5,7 +5,7 @@ sidebar_label: On-chain verification
 description: On-chain verification tutorials.
 keywords:
   - docs
-  - polygon id
+  - privado id
   - ID holder
   - issuer
   - verifier

diff --git a/docs/verifier/verification-library/verifier-set-up.md b/docs/verifier/verification-library/verifier-set-up.md
@@ -269,7 +269,7 @@ The highlighted lines are to be added only if the authentication needs to design
 The request generated in the previous endpoint already contains the `CallBackURL` so that the response generated by the wallet will be automatically forwarded to the server callback function. The callback post endpoint receives the proof generated by the identity wallet. The role of the callback endpoint is to execute the [Verification](verification-api-guide.md) on the proof.
 
 :::info "Testnet / Mainnet"
-The code samples on this page utilize Polygon's Amoy testnet, which is associated with the verifier, and the Privado chain, which is associated with the users' identities. This includes the smart contract addresses and RPC endpoints specified in the `resolvers` object. If you wish to use a different network, you will need to add a resolver for it.
+The code samples on this page utilize Polygon's Amoy testnet, which is associated with the verifier, and the <ins><a href="../../privado-identity-chain" target="">Privado Identity Chain</a></ins>, which is associated with the users' identities. This includes the smart contract addresses and RPC endpoints specified in the `resolvers` object. If you wish to use a different network, you will need to add a resolver for it.
 You can find the addresses for the validator smart contracts <ins><a href="../../smart-contracts/#validator-addresses" target="">here</a></ins>. Below is an example for adding a resolver for polygon mainnet:
 
 Mainnet contract address: 0x624ce98D2d27b20b8f8d521723Df8fC4db71D79D
@@ -339,12 +339,8 @@ func Callback(w http.ResponseWriter, r *http.Request) {
 		},
 		"privado:main": {
 			RPCUrl: "https://rpc-mainnet.privado.id",
-			ContractAddress: common.HexToAddress("0x975556428F077dB5877Ea2474D783D6C69233742"),
-		},
-		"privado:test": {
-			RPCUrl: "https://rpc-testnet.privado.id/",
-			ContractAddress: common.HexToAddress("0x975556428F077dB5877Ea2474D783D6C69233742"),
-		},
+			ContractAddress: common.HexToAddress("0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896"),
+		}
 	}
 
 	resolvers := map[string]pubsignals.StateResolver{
@@ -406,11 +402,7 @@ async function callback(req, res) {
     ),
     ["privado:main"]: new resolver.EthStateResolver(
       "https://rpc-mainnet.privado.id",
-      "0x975556428F077dB5877Ea2474D783D6C69233742"
-    ),
-    ["privado:test"]: new resolver.EthStateResolver(
-      "https://rpc-testnet.privado.id/",
-      "0x975556428F077dB5877Ea2474D783D6C69233742"
+      "0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896"
     )
 
 };

diff --git a/sidebars.js b/sidebars.js
@@ -339,6 +339,7 @@ module.exports = {
         "wallet/push-notification"
       ],
     },
+    "privado-identity-chain",
     {
       type: "category",
       label: "JS-SDK",