🦧
Profile.io User Docs
  • Introduction
    • What is Profile.io?
    • Profile Product Roadmap
    • Design Direction
    • Motivation & Values
    • SSI Basics & Concepts
    • Profile.io
    • Profile.io Technical Docs
  • System Overview
    • Profile.io Architecture
      • User Profile ID Data
      • Profile Structure
      • Themes
      • Issuer (Organisation) ID
      • Badges (VCs SB NFTs)
      • Data Registries
        • Schema Registry
        • Trusted Registry
        • DID Registry
    • Profile Verification
    • P2P Payments
    • App/Dapp Marketplace
    • Account Abstraction
    • Social / Content Growth Vectors
    • Decentralisation, OpenSource Overview and Compatability
    • Proof of Personhood (POP) Algorithm
  • Profile Implementation
    • Current live platform status
    • User Flows
    • Use Cases
    • About / Contact
    • External Resources
      • Developer Documentation
Powered by GitBook
On this page
  1. System Overview
  2. Profile.io Architecture

User Profile ID Data

PreviousProfile.io ArchitectureNextProfile Structure

Last updated 1 year ago

A Profile ID comprises the following:

  • The address(es) of the generated smart contract accounts (initially Polygon and Solana).

  • An email associated with the Profile ID - this is useful for organisations issuing credentials who maintain a database of the recipients' emails, such as a University.

  • A URL linked to their Profile ID (https://www.profile.io/{Profile ID}).

  • A Decentralised Identifier (DID). This is a key component of SSI and is used to cryptographically pair a Verifiable Credential to an identity.

  • Web3 DNS Address - either subdomain or standard url.

  • Once verified, a verified member badge.

  • Algorithmic proof of personhood score for trust mechisms.

  • A linked EOA address, such as a MetaMask account (subject to certain rules) or;

  • A linked ENS account (such as profile.eth). Only one linked account is permitted per Profile ID.

DIDs are constructed in accordance with . A sample of a DID issued on Ethereum appears as follows:

{
  '@context': [
    'https://www.w3.org/ns/did/v1',
    'https://w3id.org/security/suites/secp256k1recovery-2020/v2'
  ],
  id: 'did:ethr:0xb9c5714089478a327f09197987f16f9e5d936e8a',
  verificationMethod: [
    {
      id: 'did:ethr:0xb9c5714089478a327f09197987f16f9e5d936e8a#controller',
      type: 'EcdsaSecp256k1RecoveryMethod2020',
      controller: 'did:ethr:0xb9c5714089478a327f09197987f16f9e5d936e8a',
      blockchainAccountId: 'eip155:1:0xb9c5714089478a327f09197987f16f9e5d936e8a'
    }
  ],
  assertionMethod: [
    'did:ethr:0xb9c5714089478a327f09197987f16f9e5d936e8a#controller'
  ],
  authentication: [
    'did:ethr:0xb9c5714089478a327f09197987f16f9e5d936e8a#controller'
  ]
}
W3C standards