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

Key Components

  • omni-authenticator (same term as in tech dive, equivalent to “account abstraction” service in the first image):

    • accepts web2/web3 ways of login

    • generates omni-account based on it

    • issues jwt tokens for further communication with omni-executor

  • omni-executor:

    • accepts user intents, authorized by previous jwt

    • translates user intent into multi-step blockchain path (txs)

    • constructs the tx based on user config

    • executes the tx on the matching chain

    • records the state onto heima chain

  • trade module / heima route:

    • flexible trading on single chain by connecting to different DEX pools

  • Signer service:

    • controls generated EOA accounts used to send tx on chains where user don’t have account, e.g. user logs in with web2 / metamask, but want to send solana tx.

  • heima main-net:

    • record the intent lifecycle and state update

    • on-chain trading history: user should be able to reconstruct the trading history just by indexing the heima blockchain data

PreviousDeveloper OverviewNextIntegration Guide

Last updated 1 month ago

Was this helpful?