> For the complete documentation index, see [llms.txt](https://takes.gitbook.io/takes-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://takes.gitbook.io/takes-docs/technical-design/architecture-overview.md).

# Architecture

Takes separates holder accounting from trading. Contracts record requests, token supply, settlement, and claims. Takes-operated services process individual requests and manage the trading account.

```mermaid
flowchart LR
    U["Your wallet"] --> T["Token A on Arc, Ethereum, Base, Arbitrum, or Monad"]
    T <-->|"Circle CCTP"| H["Token A's HyperEVM hub"]
    H <--> X["Token A's HyperCore account"]
    E["HyperEVM token B"] <-->|"Local calls"| N["Token B's HyperEVM hub"]
    N <--> Y["Token B's HyperCore account"]
    U --> E
    S["Takes services"] --> T
    S --> H
    S --> E
    S --> X
    S --> Y
    X --> D["Positions and account data"]
    Y --> D
    D --> W["Takes app"]
    T --> W
    E --> W
```

## Two contract paths

The diagram shows two different tokens. Each token has its own trading account; the paths do not share backing.

On Arc, Ethereum, Base, Arbitrum, and Monad, the token holds requests and claims while a separate HyperEVM hub controls its trading account. Circle CCTP transfers USDC and authenticated messages between them.

New HyperEVM deployments separate the token and trading hub, connected by local contract calls. No CCTP hop is needed; account deposits and withdrawals still take separate steps. Tokens and hubs use separate beacons, with independent per-pool storage.

[Networks](/takes-docs/reference/supported-networks.md#networks) compares the transfer routes, seed funding, and gas tokens.

## What Takes operates

Takes discovers mined requests and cross-chain messages directly from contracts. Attestation, account setup, execution and trading advance when their prerequisites permit. Services reconcile saved transactions against chain state before another send; an unknown transaction outcome can delay other sends using that chain's signer.

Execution discovery is separate from reporting history. An indexer delay can postpone charts or activity without blocking an otherwise ready request. Each pool permits one capital-changing request in execution at a time; a stalled execution prevents the next request in that pool from starting. Requests are never combined into a shared payout batch.

The app combines contract history with exchange data. It can lag behind the chain. Contracts remain authoritative for claims and token balances.

See [Smart contracts](/takes-docs/technical-design/smart-contracts.md#smart-contracts), [Roles and permissions](/takes-docs/security-and-trust/roles-and-permissions.md#roles-and-permissions), and [Failure and recovery](/takes-docs/security-and-trust/failure-and-recovery.md#failure-and-recovery).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://takes.gitbook.io/takes-docs/technical-design/architecture-overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.