Docs introduction framing Heima as a chain-abstraction protocol for cross-chain DeFi with one omni-account, gas abstraction, and intent-based execution.
Best short source for omni-account mechanics, including Web2/Web3 login, EIP-7702 proxy mapping for EVM chains, Substrate-native proxies, TEE-backed secure proxies, delegated execution, and the internal identity graph.
Whitepaper-style long-form architecture writeup. Strongest source for the claim that Heima is a full-stack coordination protocol tying omni-accounts, intent routing, agents, and a Layer 1 registry together via auditable execution.
Public repo showing the project’s Litentry lineage and operational components, including runtime logic, DID pieces, identity-worker, and omni-executor / TEE-worker references.
Key takeaways from primary materials
Heima is best understood as a coordination stack, not just an intent router or just an account-abstraction wallet layer.
The protocol’s distinctive move is to combine four control planes in one system: omni-account identity, cross-chain routing, agent execution, and a dedicated Layer 1 registry/audit layer.
The docs repeatedly place practical authority in the omni-executor, routing engine, registered agent/filler set, and TEE-backed execution/attestation path.
The use of EIP-7702 plus projected accounts means Heima belongs in the account-abstraction conversation, but its real significance is the extra orchestration layer above wallet standards.
The strongest comparison classes in the corpus are Epoch Protocol, Valence Protocol, ERC-4337 / EIP-7702 account-abstraction standards, and verifiable offchain-execution middleware.