# 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 --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.heima.network/developer-build-with-heima/key-components.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.