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

# Perpetuals Architecture

Architecture and metadata for the xyz HIP-3 deployment.

Hyperliquid Improvement Proposal 3, or [HIP-3](https://hyperliquid.gitbook.io/hyperliquid-docs/hyperliquid-improvement-proposals-hips/hip-3-builder-deployed-perpetuals), lets builders deploy perpetual markets on HyperCore.

The `xyz` deployment defines its market listings, oracle sources, leverage limits, margin modes, funding parameters, trading sessions, and other eligible parameters. HyperCore processes orders, matching, margin, liquidations, funding transfers, and settlement onchain.

A distributed set of relayer instances maintained by the trade\[XYZ] team computes and publishes to Hypercore the oracle, mark, and external price described in [Mechanics](/perpetuals/mechanics.md). Relayer updates are transmitted approximately every three seconds.

| HIP-3 metadata  | Value                                        |
| --------------- | -------------------------------------------- |
| Deployment name | `xyz`                                        |
| Full name       | `XYZ`                                        |
| Deployer        | `0x88806a71D74ad0a510b350545C9aE490912F0888` |
| Oracle Updater  | `0x1234567890545d1Df9EE64B35Fdd16966e08aCEC` |


---

# 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.trade.xyz/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.