Identity ‐ Documentation

Prometheus-X Work Packages 1.4 & 1.5 Documentation

Context

This documentation summarizes the locations and operating modes of the deliverables of the Identity module, whose specifications are here.

List of delivered Open Source components

Reminder of the expected Open Source components:

• Catalog_directory contract

  • EVM-compatible smart contract & ABI
  • Documentation (including call methods)
  • Client code for Web integration of the catalog directory

• Catalog_administration contract

  • EVM-compatible Smart contract & ABI
  • Documentation (including call methods)
  • Client code for Web integration of the credentials & descriptions directory

• Authentication Component via did:ethr: Allows authentication via DID and verification of credentials. Integrated with catalog_app, it enables the appropriate rights for catalog users.

• Signature Component via did:ethr: Incorporated into the catalog_app code, it particularly allows the signing of self-descriptions.

• Component for Publishing Descriptions on IPFS

Deliverables

Catalog_directory Contract

• Summary: The Catalog_directory Contract is an EVM-compatible smart contract designed to manage a directory of catalogs accredited by the Prometheus-X association, allowing their official recognition within the ecosystem.

• Location of deliverables:

  • EVM-compatible Smart contract & ABI
  • Documentation (including call methods)
  • Client code for Web integration of the catalog directory

Catalog_administration contract

• Summary: The Catalog_administration contract is an EVM-compatible smart contract designed to model, issue, and distribute credentials (identity, authorization credentials: for example, "ecosystem_owner" or "ecosystem_data_user"., etc) in the form of SBT (SoulBound Token, non-transferable NFTs).

• Location of deliverables:

  • EVM-compatible smart contract & ABI
  • Documentation (including call methods)
  • Client code for Web integration of the credentials & descriptions directory

Authentication Component via did:ethr

• Summary: Allows authentication via DID and verification of credentials. Incorporated into the catalog_app code, it enables users to sign-in.
• Deliverable location and documentation

Signature Component via did:ethr

• Summary: Incorporated into the catalog_app code, it particularly allows the signing of self-descriptions.
• Deliverable location and documentation

Component for Publishing Descriptions on IPFS

• Summary: Incorporated into the catalog_app code, it particularly allows the recording of self-descriptions in a decentralized storage environment (IPFS).
• Deliverable location and documentation

Appendix: Production deployment steps

Production Deployment Steps

1. Deployment of the 3videnz-RevealableConsensualSBT Catalog on Mainnet (Visions)
2. Deployment of the PrometheusXCatalogsDirectory Contract on Mainnet (Prometheus)
   • (Optional) If the deployment address is not the contract owner, transfer ownership of the contract.
   • (Optional) Add administrators to the PrometheusXCatalogsDirectory contract to manage the added catalogs.
   • Add the Visions catalog 3videnz-RevealableConsensualSBT to the PrometheusXCatalogsDirectory.
3. Configuration of 3videnz-siwed-react in siwed.config.js of the Client Application (Visions)
   • Define the mainnet being used.
   • (Optional) Configure mywallet in production.
   • Configure the PrometheusXCatalogsDirectory.

Example 3videnz-siwed-react Configuration

export default defineConfig({
    // ...
    chains: [{
        chainId: 43114,
        name: 'Avalanche C-Chain',
        currency: 'AVAX',
        explorerUrl: 'https://snowtrace.io/',
        rpcUrl: 'https://avalanche-c-chain-rpc.publicnode.com'
    }],
    customWallets: [{
        id: 'mywallet.cloud',
        name: 'mywallet.cloud',
        webapp_link: 'https://app.mywallet.cloud/',
        image_url: '/mywallet-icon-512.png'
    }],
    identityRegistries: [{
        type: 'PrometheusXCatalogsDirectory',
        chainId: '0xa86a', // Hexadecimal format of Avalanche C-Chain 43114
        address: '0x...' // Address of the PrometheusXCatalogsDirectory (see Production Deployment Steps 1.)
    }]
    // ...
});