Heima Docs
  • Overview — What is Heima?
    • Introduction
      • Heima
      • HEI Token
  • Background and Problem Statement
    • Problem
    • Our Solution
    • Current Chain Abstraction Systems and How Heima Solves Their Limitations
  • Core Concepts
    • Heima Layer 1 Network
    • Account Abstraction
    • Chain Abstraction
    • Agent Hub
  • Case Study（PumpX）
  • Developer — Build With Heima
    • Developer Overview
    • Key Components
    • Integration Guide
  • Ecosystem — Connect with Heima
    • Ecosystem
      • Parachain
      • Litentry Foundation
      • PumpX
  • Featured DApps
    • Web App
    • IdHub
      • User Guides
        • Getting Started with the IDHub
          • Setting up a Shielding Key
          • Linking a Web3 Account
          • Linking a Web2 Account - Twitter
          • Linking a Web2 Account - Discord
          • BRC 20 Sign-in
        • Generating Credentials
        • How to Stake, Bridge, and Unstake on IdentityHub (deprecated)
      • Direct Invocation
      • EVM Sign-In
      • Verifiable Credentials (VCs)
      • Identity Score
      • IdentityHub Client
      • Securing Privacy
      • IDHub FAQs
      • Rules of IDHub v0.8
      • Glossary of Terms
  • Resources — More about Heima
    • References
    • FAQ
    • Support
    • Brand Kit
  • Heima Whitepaper
    • Read Online
  • PDF Download
Powered by GitBook
On this page

Was this helpful?

  1. Featured DApps
  2. IdHub

IdentityHub Client

PreviousIdentity ScoreNextSecuring Privacy

Was this helpful?

The IDHub client helps users to generate, manage, and interact with their aggregated identities. The client also syncs with the parachain to submit the latest state of the user's ID graph and issue verifiable credentials.

When a 3rd party dApp wants to access the user's identity data, it must make a request to the IDHub client and get the user's authorization before it gets the data. The Heima Network will only allow returning identity data to the identity owner, it is up to the user to decide whether to give the data to a 3rd party.

The IDHub client allows the user to interact with the IDHub dashboard, IDgraph, VCs, and the Identity score.

The client interacts with the parachain & sidechain - where calls made to the parachain are encrypted and opaque to invoke confidentiality. The content of the operation is only visible to the Client and the sidechain TEE (SGX, SGX workers/nodes, and SGX runtime).

Different types of calls can be executed by the client based on the operation destination. They include:

  • Untrusted Call: The client interacts with the parachain node via untrusted calls, sending transactions or queries.

  • Trusted call: The client interacts with the TEE enclave directly.

  • Direct Invocation: Client calls extrinsic in SGX runtime (same as a trusted call).

  • Indirect invocation: Client encrypts SGX runtime call, sends to Teerex Pallet in parachain. The worker node syncs blocks, identifies call_work extrinsic, parses call from parachain, and dispatches them to SGX runtime.