Separated Supporting zero-knowledge proofs out into a page of its own

Author: TinaKT

source/mainnet/docs/integration/wallet integration/integrating-identity-layer.rst

@@ -44,27 +44,5 @@ Choosing between these two options is a key architectural decision. The choice i
 
 To help you make an informed choice, we recommend reviewing our :ref:`detailed guide on Concordium's identity layer<reference-identity>`. For a practical example, you can explore the source code of `Concordium Wallet <https://github.com/Concordium/cryptox-android>`_, an open-source reference wallet, which provides a complete implementation of :ref:`option 1<option-1-direct-idp>`.
 
-Zero-knowledge proofs
-=====================
 
-Concordium's identity layer uses :term:`zero-knowledge proofs (ZKPs)<zero-knowledge proof>` to ensure user privacy. These cryptographic proofs are a core component of the :term:`identity object`. They enable a user to confirm their verified status on-chain without disclosing personal data. This system also allows for selective disclosure; for instance, a user could generate a proof to confirm a specific attribute (e.g., "is over 18"). A third party can then verify the proof against the user's public commitment on the blockchain, confirming the attribute without revealing other personal data.
-
-Your wallet's responsibility for handling these proofs depends directly on the integration path you chose in the previous section.
-
-If you selected :ref:`option 1 (direct IDP integration) <option-1-direct-idp>`, your wallet is responsible for generating the cryptographic requests that produce the final ZKP within the identity object. The Concordium SDK is designed to handle this complex process.
-
-If you selected :ref:`option 2 (ID App integration) <option-2-id-app>`, this responsibility is offloaded entirely to the Concordium ID App.
-
-
-**Advantages:**
-
-* **User privacy** - Users' identity is verified on-chain without exposing personal data.
-* **Regulatory compliance** - Enables access to regulated digital assets and enterprise dApps that require verified identity.
-* **Reduced security liability** - The protocol handles identity proofs, eliminating the need to store sensitive user PII.
-
-**Developer tools:**
-
-* The `Concordium Proof Explorer <https://web3id-proof-explorer.testnet.concordium.com/>`_ is an interactive tool for creating and testing proofs with account credentials and verifiable credentials
-* View the `source code on GitHub <https://github.com/Concordium/concordium-web3id/tree/main/test-tools/proof-explorer>`_
-* For detailed guidance on writing statements that interact with Concordium wallets and creating proofs for dApps and services, refer to :ref:`the Create proofs documentation<create-proofs>`
 

source/mainnet/docs/integration/wallet integration/supporting-zero-knowledge-proofs.rst

@@ -0,0 +1,28 @@
+.. include:: ../../../variables.rst
+.. _supporting-zero-knowledge-proofs:
+
+================================
+Supporting zero-knowledge proofs
+================================
+
+Concordium's identity layer uses :term:`zero-knowledge proofs (ZKPs)<zero-knowledge proof>` to ensure user privacy. These cryptographic proofs are a core component of the :term:`identity object`. They enable a user to confirm their verified status on-chain without disclosing personal data. This system also allows for selective disclosure; for instance, a user could generate a proof to confirm a specific attribute (e.g., "is over 18"). A third party can then verify the proof against the user's public commitment on the blockchain, confirming the attribute without revealing other personal data.
+
+Your wallet's responsibility for handling these proofs depends on your chosen integration path:
+
+If you selected :ref:`option 1 (direct IDP integration) <option-1-direct-idp>`, your wallet is responsible for generating the cryptographic requests that produce the final ZKP within the identity object. The Concordium SDK is designed to handle this complex process.
+
+If you selected :ref:`option 2 (ID App integration) <option-2-id-app>`, this responsibility is offloaded entirely to the Concordium ID App.
+
+
+**Advantages:**
+
+* **User privacy** - Users' identity is verified on-chain without exposing personal data.
+* **Regulatory compliance** - Enables access to regulated digital assets and enterprise dApps that require verified identity.
+* **Reduced security liability** - The protocol handles identity proofs, eliminating the need to store sensitive user PII.
+
+**Developer tools:**
+
+* The `Concordium Proof Explorer <https://web3id-proof-explorer.testnet.concordium.com/>`_ is an interactive tool for creating and testing proofs with account credentials and verifiable credentials
+* View the `source code on GitHub <https://github.com/Concordium/concordium-web3id/tree/main/test-tools/proof-explorer>`_
+* For detailed guidance on writing statements that interact with Concordium wallets and creating proofs for dApps and services, refer to :ref:`the Create proofs documentation<create-proofs>`
+

source/mainnet/docs/integration/wallet integration/wallet-integration.rst

@@ -12,9 +12,10 @@ Integration overview
 
 Concordium is a Layer-1 :term:`proof-of-stake` blockchain with a built-in :ref:`identity layer<reference-identity>` at protocol level balancing user privacy with regulatory compliance. The platform supports multiple transaction types, offers native staking and :term:`delegation` functionality, and uses an efficient gRPC-based node communication protocol.
 
-Integrating Concordium requires implementing support for several protocol-specific features:
+Integrating Concordium involves implementing support for several protocol-specific features:
 
-* **Identity layer management:** handling verified on-chain identities and zero-knowledge proofs
+* **Identity layer management:** handling verified on-chain identities
+* **Zero-knowledge proofs (ZKPs):** managing cryptographic proofs for privacy-preserving identity verification
 * **Transaction types:** supporting CCD transfers, smart contracts, staking, and protocol-level tokens
 * **Staking functionality:** enabling users to delegate CCD and earn rewards
 
@@ -26,6 +27,7 @@ Guide structure
 The following pages provide detailed guidance for each integration area, including technical specifications and links to relevant SDKs and APIs.
 
 * :ref:`Integrating Concordium's ID layer<integrating-identity-layer>`
+* :ref:`Supporting zero-knowledge proofs (ZKPs)<supporting-zero-knowledge-proofs>`
 * :ref:`Supporting transactions<supporting-transactions>`
 * :ref:`Supporting staking<supporting-staking>`
 * :ref:`Connecting your wallet to the network<connecting-wallet-to-network>`
@@ -36,6 +38,7 @@ The following pages provide detailed guidance for each integration area, includi
    :maxdepth: 1
 
    integrating-identity-layer
+   supporting-zero-knowledge-proofs
    supporting-transactions
    supporting-staking
    connecting-wallet-to-network