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

# About

GammaSwap V1 was built to bring convexity onchain through AMMs without liquidations or oracle dependencies. Users could borrow liquidity from AMMs to hedge Impermanent Loss or to speculate on volatility or price direction of any token.&#x20;

The team believes prediction markets enable the same type of risk exposure in a much more capital efficient and easier to understand format. Therefore the team redirected its efforts to improve the experience of trading prediction markets for cryptocurrency assets on-chain.

*Note: the core team is no longer actively developing V1 or incentivizing it. All development and growth is focused on V2.*


---

# 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.gammaswap.com/legacy-v1/about.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.
