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

# Force Architecture

Hyperliquid is a performant blockchain offering permissionless access to perpetual trading markets. Trades, execution and settlement occur onchain through Hyperliquid validators.

Hyperliquid Improvement Proposal 3 (HIP-3) lets independent builders deploy and operate their own perpetual markets on Hyperliquid. For more detail, see Hyperliquid's HIP-3 documentation.

**The Force protocol** is a HIP-3 DEX defining market listings, oracle construction, leverage limits and other parameters for Force markets in the rates asset class: interest-rate perpetuals whose underlying is a published rate expressed in percent, not a price.

**Any Force interface** is a front end providing access to Force markets and other Hyperliquid markets. It is not the exclusive access method: Force markets, like all HIP-3 markets, are reachable through the Hyperliquid API and compatible clients. This documentation describes the protocol independent of any interface.

## HIP-3 metadata

|           |        |
| --------- | ------ |
| Name      | `frce` |
| Full name | Force  |

## What is bespoke and what is inherited

Consistent with the HIP-3 model, most venue machinery is inherited from HyperCore, and only the pricing components are built by the deployer.

| Component                                                       | Owner          |
| --------------------------------------------------------------- | -------------- |
| Matching, order types, funding, liquidations, auto-deleveraging | HyperCore      |
| Oracle price, mark price, external price                        | Force protocol |

Force's responsibility is to publish correct rate-index prices. Everything on the matching, margining and liquidation side is Hyperliquid's, parameterised by the market settings the deployer chooses.

## The price pipeline

Each market's oracle is built through a chain of stages.

```
market data  ->  normalisation  ->  storage  ->  index computation  ->  signing  ->  Hyperliquid
 cash feed        one unified       time        session selection      oracle       HIP-3 oracle
 futures feed     price record      series      and correction         signature    price update
 daily mark
 order book
```

Two properties of this design are worth stating.

**Computation and publication are separate.** One service decides the price and writes it to storage; a second reads that series and submits it. Either can be restarted without the other, and only the publishing side holds a signing key. The stored series is the contract between them, and it is also what the API and charts read, so what a trader sees is what was published.

**Publication is refused rather than faked.** If the computed series stops updating, the publisher stops submitting and logs the failure instead of asserting a price it knows is stale. Hyperliquid holds the last value it was given either way, so refusing leaves the market where publishing would, without claiming freshness that does not exist.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.force.xyz/overview/force-architecture.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.