> 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/events/architecture.md).

# Events Architecture

Architecture, responsibilities, and venue metadata for Events by trade\[XYZ].

Hyperliquid Improvement Proposal 4, or [HIP-4](https://hyperliquid.gitbook.io/hyperliquid-docs/hyperliquid-improvement-proposals-hips/hip-4-outcome-markets), adds fully collateralized outcome contracts to HyperCore. Trade\[XYZ] deploys Events markets under the name `txyz`.

Every HIP-4 market is instantiated from a template approved by Hyperliquid validators. A template constrains the market’s display text, side names, typed keywords, and permitted semantics. For each `txyz` market, the outcome deployer selects an approved template, supplies the values that template permits, sets the applicable deployer fee scale, and publishes the resolution methodology. HyperCore processes orders and maintains the canonical onchain balances and positions.

After the offchain resolution methodology determines a result from the declared source, the outcome deployer or an authorized settlement sub-deployer submits the settlement action. HyperCore validates and applies that action onchain; the authorized onchain action causes the outcome balances to settle.

trade\[XYZ] provides a non-custodial interface to these markets. It is not the exclusive means of accessing `txyz` markets.

<table><thead><tr><th>HIP-4 metadata</th><th width="386.78125">Draft status</th></tr></thead><tbody><tr><td>Venue name</td><td><code>txyz</code></td></tr><tr><td>Outcome deployer address</td><td><code>0x88806a71D74ad0a510b350545C9aE490912F0888</code></td></tr><tr><td>Authorized settlement sub-deployers</td><td><code>0x8EF95FA212D22448c9c7eAFa277b4c8bbf3f9D57</code></td></tr><tr><td>Deployer fee scale</td><td>Currently the <code>deployerFeeScale = 0</code></td></tr><tr><td>Resolution methodology</td><td><a href="/events/resolution.md">Resolution</a> and the terms of the applicable market</td></tr></tbody></table>


---

# 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://docs.trade.xyz/events/architecture.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.