Skip to content

Commit b6ffc5b

Browse files
0xpulkit0xpulkit
authored
Merge pull request #190 from 0xPolygonID/privado-idenity-chain
Documentation for Privado Identity Chain
2 parents cadab76 + 9ddc326 commit b6ffc5b

File tree

6 files changed

+55
-50
lines changed

6 files changed

+55
-50
lines changed

‎docs/issuer/issuer-overview.md‎

Lines changed: 0 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -76,35 +76,4 @@ The [Issuer Node UI](issuer-node-ui.md) provides the full experience of having a
7676
<img src= {useBaseUrl("img/8088.png")} align="center" />
7777
</div>
7878

79-
### Privado Identity Chain
8079

81-
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.
82-
83-
DIDs associated with the Privado Identity Chain will follow a prefix format:
84-
<Tabs>
85-
<TabItem value="Mainnet">
86-
87-
```main
88-
did:iden3:privado:main:
89-
```
90-
</TabItem>
91-
<TabItem value="Testnet">
92-
93-
```test
94-
did:iden3:privado:test:
95-
```
96-
</TabItem>
97-
</Tabs>
98-
For example, a DID would look like this:
99-
100-
did:iden3:privado:main:2Se4SGXrGrsfrCY8KPRT8R4ZbP91f6sAuBTt8xgA1W
101-
102-
:::note
103-
State transitions and MTP issuance are not currently supported.
104-
:::
105-
106-
:::caution
107-
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.
108-
109-
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.
110-
:::

‎docs/privado-identity-chain.md‎

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
id: privado-identity-chain
3+
title: Privado Identity Chain
4+
sidebar_label: Privado Identity Chain
5+
keywords:
6+
- privado id
7+
- chain
8+
- identity
9+
- privado identity chain
10+
- network
11+
---
12+
import Tabs from '@theme/Tabs';
13+
import TabItem from '@theme/TabItem';
14+
15+
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.
16+
17+
### Configuration:
18+
19+
- **RPC**: `https://rpc-mainnet.privado.id`
20+
- **Chain ID**: `21000`
21+
22+
Details regarding the smart contracts and their deployment addresses can be found [here.](./smart-contracts.md)
23+
24+
### DIDs:
25+
DIDs associated with the Privado Identity Chain will follow a prefix format:
26+
27+
```main
28+
did:iden3:privado:main:
29+
```
30+
31+
For example, a DID would look like this:
32+
33+
`did:iden3:privado:main:2Se4SGXrGrsfrCY8KPRT8R4ZbP91f6sAuBTt8xgA1W`
34+
35+
:::note
36+
The Privado Identity Chain is currently accessible in a read-only mode.
37+
<!-- State transitions and MTP issuance are not currently supported. -->
38+
:::
39+
40+
:::caution
41+
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.
42+
43+
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.
44+
:::

‎docs/smart-contracts.md‎

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ keywords:
99
- smart
1010
- contract
1111
---
12-
12+
import useBaseUrl from '@docusaurus/useBaseUrl';
1313

1414
<a href="https://github.com/iden3/contracts" target="_blank">Privado ID Smart Contracts - Github</a>
1515

@@ -20,20 +20,19 @@ As part of our unified address methodology, we deployed contracts via the CREATE
2020
We have deployed contracts across the following mainnets and testnets so far:
2121

2222
**Mainnets**:
23-
23+
- [Privado Identity Chain](/docs/privado-identity-chain)
2424
- [Ethereum](https://etherscan.io/address/0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896)
2525
- [Polygon POS](https://polygonscan.com/address/0x624ce98d2d27b20b8f8d521723df8fc4db71d79d)
2626
- [Polygon zkEVM](https://zkevm.polygonscan.com/address/0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896)
2727
- [Linea](https://lineascan.build/address/0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896)
28-
- Privado Mainnet
2928

3029
**Testnets**:
3130

3231
- [Ethereum Sepolia](https://sepolia.etherscan.io/address/0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896)
3332
- [Polygon Amoy](https://amoy.polygonscan.com/address/0x1a4cc30f2aa0377b0c3bc9848766d90cb4404124)
3433
- [Polygon zkEVM Cardona](https://cardona-zkevm.polygonscan.com/address/0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896)
3534
- [Linea-Sepolia](https://sepolia.lineascan.build/address/0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896)
36-
- Privado Testnet
35+
3736

3837
## Unified contract addresses
3938

@@ -47,8 +46,8 @@ It’s important to note that the State contracts for the following two networks
4746
| Smart Contract Type | Unified Address |
4847
| :----------------------: | :----------------------------------------: |
4948
| **STATE* ** | 0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896 |
50-
| **VALIDATOR_MTP** | 0x27bDFFCeC5478a648f89764E22fE415486A42Ede |
51-
| **VALIDATOR_SIG** | 0x59B347f0D3dd4B98cc2E056Ee6C53ABF14F8581b |
49+
| **VALIDATOR_MTP_V2** | 0x27bDFFCeC5478a648f89764E22fE415486A42Ede |
50+
| **VALIDATOR_SIG_V2** | 0x59B347f0D3dd4B98cc2E056Ee6C53ABF14F8581b |
5251
| **VALIDATOR_V3** | 0xd179f29d00Cd0E8978eb6eB847CaCF9E2A956336 |
5352
| **UNIVERSAL_VERIFIER** | 0xfcc86A79fCb057A8e55C6B853dff9479C3cf607c |
5453
| **IDENTITY_TREE_STORE** | 0x7dF78ED37d0B39Ffb6d4D527Bb1865Bf85B60f81 |

‎docs/verifier/on-chain-verification/overview.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ sidebar_label: On-chain verification
55
description: On-chain verification tutorials.
66
keywords:
77
- docs
8-
- polygon id
8+
- privado id
99
- ID holder
1010
- issuer
1111
- verifier

‎docs/verifier/verification-library/verifier-set-up.md‎

Lines changed: 4 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -269,7 +269,7 @@ The highlighted lines are to be added only if the authentication needs to design
269269
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.
270270
271271
:::info "Testnet / Mainnet"
272-
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.
272+
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.
273273
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:
274274
275275
Mainnet contract address: 0x624ce98D2d27b20b8f8d521723Df8fC4db71D79D
@@ -339,12 +339,8 @@ func Callback(w http.ResponseWriter, r *http.Request) {
339339
},
340340
"privado:main": {
341341
RPCUrl: "https://rpc-mainnet.privado.id",
342-
ContractAddress: common.HexToAddress("0x975556428F077dB5877Ea2474D783D6C69233742"),
343-
},
344-
"privado:test": {
345-
RPCUrl: "https://rpc-testnet.privado.id/",
346-
ContractAddress: common.HexToAddress("0x975556428F077dB5877Ea2474D783D6C69233742"),
347-
},
342+
ContractAddress: common.HexToAddress("0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896"),
343+
}
348344
}
349345

350346
resolvers := map[string]pubsignals.StateResolver{
@@ -406,11 +402,7 @@ async function callback(req, res) {
406402
),
407403
["privado:main"]: new resolver.EthStateResolver(
408404
"https://rpc-mainnet.privado.id",
409-
"0x975556428F077dB5877Ea2474D783D6C69233742"
410-
),
411-
["privado:test"]: new resolver.EthStateResolver(
412-
"https://rpc-testnet.privado.id/",
413-
"0x975556428F077dB5877Ea2474D783D6C69233742"
405+
"0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896"
414406
)
415407

416408
};

‎sidebars.js‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -339,6 +339,7 @@ module.exports = {
339339
"wallet/push-notification"
340340
],
341341
},
342+
"privado-identity-chain",
342343
{
343344
type: "category",
344345
label: "JS-SDK",

0 commit comments

Comments
 (0)