From 07c2daaeeca8fdf6012ede98abfb81a570a060b2 Mon Sep 17 00:00:00 2001 From: Pulkit Mittal Date: Tue, 22 Oct 2024 10:10:46 +0530 Subject: [PATCH 1/3] chore: rm privado test network --- docs/smart-contracts.md | 9 ++++----- .../verifier/verification-library/verifier-set-up.md | 12 ++---------- 2 files changed, 6 insertions(+), 15 deletions(-) diff --git a/docs/smart-contracts.md b/docs/smart-contracts.md index 6906e84..3c67342 100644 --- a/docs/smart-contracts.md +++ b/docs/smart-contracts.md @@ -20,12 +20,11 @@ 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 Idenity 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**: @@ -33,7 +32,7 @@ We have deployed contracts across the following mainnets and testnets so far: - [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/verification-library/verifier-set-up.md b/docs/verifier/verification-library/verifier-set-up.md index 38c41aa..127ae03 100644 --- 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 Privado Idenity 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. You can find the addresses for the validator smart contracts here. Below is an example for adding a resolver for polygon mainnet: Mainnet contract address: 0x624ce98D2d27b20b8f8d521723Df8fC4db71D79D @@ -340,11 +340,7 @@ 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"), - }, + } } resolvers := map[string]pubsignals.StateResolver{ @@ -407,10 +403,6 @@ 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" ) }; From 4c8c63320a281d72b31c9705b605d1152105fb54 Mon Sep 17 00:00:00 2001 From: Pulkit Mittal Date: Tue, 22 Oct 2024 11:07:23 +0530 Subject: [PATCH 2/3] feat: privado idenity chain documentation --- docs/issuer/issuer-overview.md | 31 ------------- docs/privado-idenity-chain.md | 44 +++++++++++++++++++ docs/smart-contracts.md | 4 +- .../on-chain-verification/overview.md | 2 +- .../verification-library/verifier-set-up.md | 6 +-- sidebars.js | 1 + 6 files changed, 51 insertions(+), 37 deletions(-) create mode 100644 docs/privado-idenity-chain.md diff --git a/docs/issuer/issuer-overview.md b/docs/issuer/issuer-overview.md index 91281d6..6581c07 100644 --- 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 -### 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: - - - -```main -did:iden3:privado:main: -``` - - - -```test -did:iden3:privado:test: -``` - - -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-idenity-chain.md b/docs/privado-idenity-chain.md new file mode 100644 index 0000000..a611c9a --- /dev/null +++ b/docs/privado-idenity-chain.md @@ -0,0 +1,44 @@ +--- +id: privado-idenity-chain +title: Privado Identity Chain +sidebar_label: Privado Identity Chain +keywords: + - privado id + - chain + - idenity + - 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. + +::: + +:::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. +::: \ No newline at end of file diff --git a/docs/smart-contracts.md b/docs/smart-contracts.md index 3c67342..c1bb6ca 100644 --- a/docs/smart-contracts.md +++ b/docs/smart-contracts.md @@ -9,7 +9,7 @@ keywords: - smart - contract --- - +import useBaseUrl from '@docusaurus/useBaseUrl'; Privado ID Smart Contracts - Github @@ -20,7 +20,7 @@ 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 Idenity Chain +- [Privado Idenity Chain](/docs/privado-idenity-chain) - [Ethereum](https://etherscan.io/address/0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896) - [Polygon POS](https://polygonscan.com/address/0x624ce98d2d27b20b8f8d521723df8fc4db71d79d) - [Polygon zkEVM](https://zkevm.polygonscan.com/address/0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896) diff --git a/docs/verifier/on-chain-verification/overview.md b/docs/verifier/on-chain-verification/overview.md index ad23035..6fd52fc 100644 --- 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 index 127ae03..b065b19 100644 --- 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 Idenity 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 Privado Idenity 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. You can find the addresses for the validator smart contracts here. Below is an example for adding a resolver for polygon mainnet: Mainnet contract address: 0x624ce98D2d27b20b8f8d521723Df8fC4db71D79D @@ -339,7 +339,7 @@ func Callback(w http.ResponseWriter, r *http.Request) { }, "privado:main": { RPCUrl: "https://rpc-mainnet.privado.id", - ContractAddress: common.HexToAddress("0x975556428F077dB5877Ea2474D783D6C69233742"), + ContractAddress: common.HexToAddress("0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896"), } } @@ -402,7 +402,7 @@ async function callback(req, res) { ), ["privado:main"]: new resolver.EthStateResolver( "https://rpc-mainnet.privado.id", - "0x975556428F077dB5877Ea2474D783D6C69233742" + "0x3C9acB2205Aa72A05F6D77d708b5Cf85FCa3a896" ) }; diff --git a/sidebars.js b/sidebars.js index 997faa8..e058704 100644 --- a/sidebars.js +++ b/sidebars.js @@ -339,6 +339,7 @@ module.exports = { "wallet/push-notification" ], }, + "privado-idenity-chain", { type: "category", label: "JS-SDK", From 9ddc326764b4fe8df82796533b01247ce1a6783e Mon Sep 17 00:00:00 2001 From: Pulkit Mittal Date: Tue, 22 Oct 2024 15:55:50 +0530 Subject: [PATCH 3/3] fixed typo --- docs/{privado-idenity-chain.md => privado-identity-chain.md} | 4 ++-- docs/smart-contracts.md | 2 +- docs/verifier/verification-library/verifier-set-up.md | 2 +- sidebars.js | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) rename docs/{privado-idenity-chain.md => privado-identity-chain.md} (97%) diff --git a/docs/privado-idenity-chain.md b/docs/privado-identity-chain.md similarity index 97% rename from docs/privado-idenity-chain.md rename to docs/privado-identity-chain.md index a611c9a..8559ad1 100644 --- a/docs/privado-idenity-chain.md +++ b/docs/privado-identity-chain.md @@ -1,11 +1,11 @@ --- -id: privado-idenity-chain +id: privado-identity-chain title: Privado Identity Chain sidebar_label: Privado Identity Chain keywords: - privado id - chain - - idenity + - identity - privado identity chain - network --- diff --git a/docs/smart-contracts.md b/docs/smart-contracts.md index c1bb6ca..b6e5e81 100644 --- a/docs/smart-contracts.md +++ b/docs/smart-contracts.md @@ -20,7 +20,7 @@ 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 Idenity Chain](/docs/privado-idenity-chain) +- [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) diff --git a/docs/verifier/verification-library/verifier-set-up.md b/docs/verifier/verification-library/verifier-set-up.md index b065b19..4f6f466 100644 --- 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 Idenity 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 Privado Identity 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. You can find the addresses for the validator smart contracts here. Below is an example for adding a resolver for polygon mainnet: Mainnet contract address: 0x624ce98D2d27b20b8f8d521723Df8fC4db71D79D diff --git a/sidebars.js b/sidebars.js index e058704..fec776a 100644 --- a/sidebars.js +++ b/sidebars.js @@ -339,7 +339,7 @@ module.exports = { "wallet/push-notification" ], }, - "privado-idenity-chain", + "privado-identity-chain", { type: "category", label: "JS-SDK",