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

# Market Types

Aftermath supports two types of perpetual markets: linear and inverse.

{% columns %}
{% column %}

#### Linear Markets

In a linear market, the collateral asset is a stablecoin (USDC). All PnL is calculated and settled in USD terms. This is the simpler model, your margin and profits are denominated in the same unit as the contract's quote currency.

Linear markets are ideal when you want straightforward USD exposure without additional price risk from your collateral.

Examples:

* BTC/USD collateralized by USDC
* SUI/USD collateralized by USDC
* EUR/USD collateralized by USDC
  {% endcolumn %}

{% column %}

#### Inverse Markets

In an inverse market, the collateral asset is the base asset itself (or a wrapped version). The contract is still denominated in USD, but settlement occurs in the collateral asset. This means your margin value fluctuates with the underlying price.

Inverse markets let you maintain long exposure to an asset while using it as collateral. If you're bullish on BTC and want to trade BTC/USD perpetuals, collateralizing with BTC means your margin grows when BTC appreciates.

Examples:

* BTC/USD collateralized by BTC
* SUI/USD collateralized by BTC
* SUI/USD collateralized by ETH
  {% endcolumn %}
  {% endcolumns %}

## Adding New Markets

Both the base asset (index price) and collateral asset require oracle price feeds. Any onchain asset with a reliable oracle can serve as collateral, enabling rapid deployment of new markets without protocol upgrades.


---

# 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.aftermath.finance/perpetuals/architecture/market-types.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.