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. Core Concepts

Account Abstraction

Heima's account abstraction introduces a seamless identity layer centered on the omni-account, a unified user ID across all chains.

Instead of managing fragmented wallets and credentials, users interact with blockchain applications through a single, cross-chain identity.

Key features include:

  • Web2 + Web3 login support: Users can onboard via email, phone, passkeys, or social accounts, powered by partner authentication services.

  • Network-aware proxy mapping:

    • EVM chains: via EIP-7702 proxy contracts

    • Substrate chains: native proxy contracts

    • Non-native environments: TEE-backed secure proxy accounts

  • Delegated execution: Projected accounts can act on behalf of an omni-account with programmable, permissioned control.

  • Identity graph: Heima builds an internal graph to link user personas across apps and contexts, enabling personalization without exposing sensitive data.

This model reduces integration complexity for developers, eliminates key fragmentation, and enables secure, user-centric Web3 experiences built on a flexible identity framework.

PreviousHeima Layer 1 NetworkNextChain Abstraction

Last updated 1 month ago

Was this helpful?