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. Developer — Build With Heima

Integration Guide

These components that can be extensible and/or replaceable:

  • extensible: means the basis of component is provided by heima, but can be extended to have customised features. Analog: browser vs browser extensions.

  • replaceable: means the whole component can be fully replaced/customised on client side, as long as it provides given communication API.

extensible components:

  • omni-authenticator: client can add extra user-auth

  • omni-executor: client can define extra:

    • conversion logic from intent → blockchain path

    • cross-chain swap provider

  • heima main-net: client can add extra logic of lifecycle and data management

replaceable components:

  • heima-route: client can provide its own single-chain trading pool

  • signer service: if client wants to hold the private keys of EOA accounts

PreviousKey ComponentsNextEcosystem

Last updated 1 month ago

Was this helpful?