> For the complete documentation index, see [llms.txt](https://docs.heima.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heima.network/developer-build-with-heima/key-components.md).

# 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