SVX Documentation
HomepageAPISDK
Current
Current
  • Docs
  • Concepts
    • Digital Identity and Why It's Important
    • Digital Wallets
    • Ecosystems
    • Information Security
    • Personal Data & Attributes
    • Privacy- and Security-by-design
    • Secure Data Storage
    • Selective Disclosure / ZKP
    • Tokens and Tokenisation
    • Verifiable Credentials
    • Terminology
  • Platform
    • Secure Value Exchange
    • Authorisation, Tenant & Organisation Manager (ATOM)
    • Credential Service
    • Decentralised Identifiers (DIDs)
    • Keys
    • Tenants, Organisations, and End-Users
    • Vault
      • Enterprise Vault
    • Portal
    • Supported Standards
  • Guides
    • Onboarding to SVX
    • API Guides
      • Credentials
        • Credential Schemas
        • Credential Types
        • Issue Credentials
        • Presentation Definitions
        • Presentations
      • DIDs
        • DID Resolver
        • DID Registrar
        • DID Methods
          • did:key
          • did:web
          • did:ebsi
          • did:indy
        • DID Controller Keypair
      • OpenID Connect
        • For Verifiable Presentation
      • Users
        • Inviting End-Users
        • Authenticating End-Users
      • Vault
        • Items and Slots
        • Connections and Sharing
        • Classification Hierarchies
        • Attachments
        • On-sharing & Client Tasks
        • Account Delegation
      • Machine-2-Machine Communication
    • Portal Tutorials
      • Tenant Administrators
        • Onboard to a Tenancy
        • Dashboard and Navigation
        • Manage Tenancy
        • Manage Tenant Administrators
        • Manage Organisations
        • Manage Organisation Administrators
        • Credential Schemas
        • Applications
        • End Users
      • Organisation Administrators
        • Manage Organisation
        • Onboarding and Organisation Setup
        • Dashboard and Navigation
        • Manage Organisation Administrators
        • Credential Templates
        • View Credentials
        • Verification Templates
        • Verification Requests
        • Connections
        • Applications
    • Wallet Tutorials
      • Wallet Set Up
      • Provider Registration
      • Organisation Configuration
      • Credentials
      • Requests
      • Security
      • Wallet Recovery
  • Tools
    • Meeco SDK & CLI
    • Cryppo SDK & CLI
  • Releases
    • 2.1.1
    • 2.1.0
    • 2.0.0
    • 1.4.3
    • 1.4.2
    • 1.4.1
    • 1.4.0
    • 1.3.8
    • 1.3.7
    • 1.3.6
    • 1.3.5
    • 1.3.4
    • 1.3.3
    • 1.3.2
    • 1.3.0
    • 1.2.5
    • 1.2.4
    • 1.2.3
    • 1.2.2
    • 1.2.1
    • 1.2.0
    • 1.1.0
    • 1.0.0
    • Legacy API-of-Me
  • Policies
    • Privacy
    • Developer Policy
Powered by GitBook
On this page
  • Types of Ecosystems
  • Participants and Components of an Ecosystem
  • Interoperability

Was this helpful?

Edit on GitHub
  1. Concepts

Ecosystems

Last updated 5 months ago

Was this helpful?

Meeco's Secure Value Exchange (SVX) platform supplies the building blocks to implement an interoperable data ecosystem, designed around your enterprise use cases. In Web3, those use cases unlock the power of permissioned personal data and lay the foundation to create Personal Identity Ecosystems (). This new paradigm vastly increases user experience, privacy and security for your organisation and its end-users. Enterprises can explore radically new business opportunities built on digital trust, or, upgrade existing successful Web2 apps to Web3 by embracing trends such as:

  • , and

Types of Ecosystems

Depending on the desired reach of a use case, an enterprise can choose to implement different types of ecosystems:

  • Open Ecosystems (aka Public Ecosystems): for broadly applicable use cases, such as the issuance, verification and management of a driver’s license, university diploma or first aid certificate across various organisations and users.

  • Closed Ecosystems:

    • Private Enterprise Ecosystems: issued by an enterprise to its users. For example: a company issues an access VC to employees, enabling them to gain access to software or buildings via a verification workflow.

    • Personal Identity Ecosystems (PIE’s): are user-centric networks and platforms specifically designed around digital identities and personal reputation management while offering high standards for end-user privacy and data protection.

  • Linked or Interoperable Ecosystems: combine a government credential with a means of payment to allow frictionless onboarding to an eCommerce platform or service.

PIEs enable data oriented relationships between consumers and service providers. Knowing that these ecosystems will thrive on user adoption and data availability, use cases should focus on trust and reliability of its ecosystem. Once an ecosystem has proven its value through various use cases and has yielded a vast user base, further growth will depend on ecosystem as it will attract and share participants of neighbouring ecosystems.

Source: Liminal Research: “The Life of PIEs, The Journey to Personal Identity Ecosystems” (2021)

Participants and Components of an Ecosystem

  • Identity Providers (IDP) together with trust anchors bootstrap the ecosystem by delivering verifiable data and promoting trusted relationships.

  • Digital identity wallets allow users to hold and manage their digital identity, assets, credentials, cryptographic keys and DID’s.

  • Secure data stores enable enterprises to securely store their own and their customer’s data. They also allow wallet Holders to back up data from their identity wallet and securely store or share private data.

  • Verifiable Data Registries (VDR) allow Issuers and Verifiers to publish relevant information for stakeholders to view, including credential revocation transactions, credential schemas, and list other trusted Issuers and Verifiers.

Interoperability

As the number of data ecosystems grow, it will become more beneficial for the participants involved to combine or join ecosystem networks. This will allow them to share services and yield mutual benefits. Whether it is sharing a credential to a trusted Verifier from another ecosystem, or issuing credentials to end-users that have onboarded via an external ecosystem, linked ecosystems will enable wider reach for enterprises and provide end-users with seamless experiences.

delivers modular components to build an enterprise ecosystem. There are different ecosystem participants that act within various roles. Meeco has developed and defined participants and their roles within SVX as follows:

SVX
decentralised identity
verifiable credentials
privacy-by-design
security-by-design
Verifiable Credentials (VCs)
PIE’s
interoperability