> 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.md).

# Events

Outcome contracts deployed by trade\[XYZ] through Hyperliquid HIP-4.

Events by trade\[XYZ] are fully collateralized outcome contracts deployed on HyperCore through [HIP-4](https://hyperliquid.gitbook.io/hyperliquid-docs/hyperliquid-improvement-proposals-hips/hip-4-outcome-markets). They provide exposure to a defined event or price outcome within a fixed settlement range. Unlike perpetuals, Events expire and do not use leverage, funding, liquidations, or auto-deleveraging.

trade\[XYZ] deploys Events under the deployment name `txyz`. Each market has published terms that identify its outcomes, trading deadline, resolution methodology, and settlement treatment. HyperCore processes trading and applies the onchain settlement submitted by the outcome deployer or an authorized settlement sub-deployer.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>🏗️</td><td><strong>Events Architecture</strong></td><td>Roles, onchain components, and deployment metadata.</td><td><a href="/events/architecture.md">Events Architecture</a></td></tr><tr><td>↔️</td><td><strong>Contract Mechanics</strong></td><td>Outcome tokens, merged books, questions, prices, and settlement.</td><td><a href="/events/event-contract-mechanics.md">Contract Mechanics</a></td></tr><tr><td>✅</td><td><strong>Resolution</strong></td><td>How market data and declared sources determine a result before onchain settlement.</td><td><a href="/events/resolution.md">Resolution</a></td></tr><tr><td>🧾</td><td><strong>Fees</strong></td><td>Hyperliquid outcome-trading fees.</td><td><a href="/events/fees.md">Fees</a></td></tr><tr><td>💻</td><td><strong>Developer Resources</strong></td><td>Read-only tools and feeds for Events market data.</td><td><a href="/events/developer-resources.md">Consolidated Resources</a></td></tr></tbody></table>

Before trading, review the applicable market terms and [Events Risks and Disclaimers](/legal-and-disclaimers/events-risks-and-disclaimers.md).


---

# 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.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.