> For the complete documentation index, see [llms.txt](https://academy.horizonprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.horizonprotocol.com/english-v2/horizon-protocol/community-driven/hips/hip-17-add-dot-avax-and-matic-to-horizon-futures.md).

# HIP-17: Add DOT, AVAX, and MATIC to Horizon Futures

**Type:** Horizon Improvement Proposal&#x20;

**Date:** July 16th, 2024&#x20;

**Status:** Completed

<figure><img src="/files/O1NYDRNYtkp433Hnhe6D" alt=""><figcaption></figcaption></figure>

#### Summary

This HIP proposes to add Polkadot (DOT), Avalanche (AVAX), and Polygon (MATIC) to the Horizon Futures platform to increase the options available to traders and boost trading volume. By introducing these assets to the Futures market, we aim to enhance the platform's appeal and provide traders with more opportunities to diversify their trading strategies.

#### Specification

Add Polkadot (DOT), Avalanche (AVAX), and Polygon (MATIC) markets on Horizon Futures and set the system parameters as below:

<figure><img src="https://lh7-us.googleusercontent.com/docsz/AD_4nXdnWdXMVVj7QH7PwVvswgCH8E9aWgAPpk_7BPtP6gA4Yx-T9BnVJYPmEDVUZoYJ-AqDLaW63iw2KWDKfjbQ4h-3NCY9EnKDPtIqZLIgKal3GMtoaEDEd3-KjWhiJkrU0MxlqFxn2oW8HOPJybw7tLTsGe4n?key=1JkFRa0VWvo5ZB_plVQHaQ" alt=""><figcaption></figcaption></figure>

#### Motivation

Following the successful listing of seven markets on Horizon Futures, this proposal aims at further expanding the range of assets available on Horizon Futures. By offering a diverse set of markets, we aim to attract more traders to the platform, increase trading activity, and enhance overall market liquidity.

In this batch of listings, more L1 coins will be added to the current available options. Given that Polkadot (DOT), Avalanche (AVAX), and Polygon (MATIC) are large market cap assets in the ecosystem with a solid track record, they are the optimal choice for addition as the next Futures assets based on trader interest.

#### Considerations

* Global Debt Pool Impact: Adding new assets to Horizon Futures will introduce increased volatility and potentially impact the global debt pool. Therefore, assets should be added gradually to ensure the platform's stability and manage risk effectively.

#### Post-Implementation Evaluation

Upon the addition of new assets to Horizon Futures, an evaluation will be conducted to assess the market's performance and impact. Key metrics such as trading volume, user activity, and market stability will be analyzed to inform future decisions and strategy adjustments. The aim is to continue to add more markets to Horizon Futures while maintaining an active risk management strategy.

#### Feedback & Questions

If you have any suggestions, concerns, or inquiries regarding this proposal, please don't hesitate [to reach out](https://linktr.ee/horizon_protocol). Your feedback is valuable in ensuring the success and continuous improvement of Horizon Futures.

<br>


---

# 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://academy.horizonprotocol.com/english-v2/horizon-protocol/community-driven/hips/hip-17-add-dot-avax-and-matic-to-horizon-futures.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.
