> For the complete documentation index, see [llms.txt](https://learn.trovemarkets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.trovemarkets.com/misc/legal/terms-of-service.md).

# Terms of service

## Trove Terms of Service

By connecting your wallet to Trove's perp dex or interacting with any Trove smart contract (on testnet or mainnet), you agree to the following terms.

### 1. You Are Using Experimental Software

Trove is currently in public testnet phase on Hyperliquid L1. Mainnet is not live yet. Everything you do right now uses fake testnet USDC with zero real-world value.

When mainnet launches, real value will be at risk. You acknowledge that:

* You are an early tester, not a "customer"

We will audit before mainnet, but until then you are choosing to use experimental, high-risk software.

### 2. No KYC, No Custody, No Reversal

Trove is 100% non-custodial and permissionless.

* We never have access to your funds or private keys
* All transactions are final and irreversible
* There is no support team that can refund you, reverse trades, or recover lost funds
* Liquidations are automatic and permanent

You are solely responsible for your wallet and seed phrase security.

### 3. Eligibility

You represent and warrant that:

* You are not using a VPN to bypass geographic restrictions
* Your use of Trove is legal in your jurisdiction

If you are in a restricted jurisdiction, you are prohibited from using the protocol.

### 4. Prohibited Conduct

You agree not to:

* Attempt to manipulate oracles, indexes, or markets
* Use bots or scripts to front-run or exploit the protocol
* Engage in wash trading or other forms of market manipulation
* Use Trove for illegal activities (money laundering, terrorism financing, etc.)

We reserve the right to flag and publicly report obviously manipulative wallets on-chain.

### 5. Risks (Read This Twice)

Trading perpetual futures with leverage is extremely risky. You can get liquidated. Specific risks include, but are not limited to:

* Liquidation due to price volatility in collectibles markets
* Oracle delays or temporary inaccuracies
* Smart contract exploits (especially pre-audit)
* Funding rate attacks
* Index composition changes
* Hyperliquid L1 chain halts or upgrades
* Total loss of all collateral

You acknowledge that collectibles are among the most volatile and illiquid assets on earth.

### 6. No Warranties

Trove is provided "AS IS" with zero warranties of any kind .We do not guarantee:

* Uptime or availability
* Accuracy of indexes or oracles
* That your positions will not be liquidated

### 7. Limitation of Liability

To the maximum extent permitted by law:

* Trove developers, contributors, and affiliated entities are not liable for any losses
* Total liability is capped at $0
* No consequential, indirect, or punitive damages — ever

### 8. Changes to Terms

We can update these terms at any time. Continued use after changes = acceptance

#### 9. Contact Us

Email: <legal@trovemarkets.com>

X/Twitter: @troveMarkets\
Telegram: @troveMarkets

***Welcome to the first real collectibles perp dex***


---

# 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://learn.trovemarkets.com/misc/legal/terms-of-service.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.
