> For the complete documentation index, see [llms.txt](https://seer-2.gitbook.io/seer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://seer-2.gitbook.io/seer/seer-solution/exchange-integration.md). # Exchange Integration Classic prediction market positions can only be traded on a dedicated exchange (with the disadvantage for liquidity providers to only be able to use one specific type of liquidity position). Smart contract technology allows dapps to be composable with each other’s (Money Legos). We can take advantage of this by separating the position minting/redemption from the position trading by making position ERC20 tokens tradable on all supported exchanges. Note that Gnosis already made some work in this direction allowing the wrapping of positions into ERC20 tokens\[14]. For Seer, the tokens will be natively ERC20. This allows taking advantage of existing exchanges (such as Uniswap V3 allowing concentrated bonded curves and de facto limit order, or Gnosis auction for auctions). In order to solve the issue of split liquidity, aggregators (such as 1inch\[15], Paraswap\[16] or Cowswap\[17]) allowing users to get the best price when buying/selling a position could be used by end user frontends. Those aggregators could also use the minting/redemption mechanisms as if it were an exchange itself. For example if you want take a YES position, you have two ways to do that: * Buy YES tokens on the open market. * Mint YES and NO tokens using the underlying asset and sell the NO tokens on the open market. Current prediction markets require users to make those actions themselves, not necessarily taking the action which would result in the best price. The front-end could automatically split any order in those two types of actions in order to always give the users the best price. Exchange integration can also be a way to have more liquidity incentives. Exchanges are competing for liquidity and also provide incentives to liquidity providers using their platforms. The Seer DAO will seek partnership with different exchanges in order to make the outcome tokens as liquid as possible. --- # 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://seer-2.gitbook.io/seer/seer-solution/exchange-integration.md?ask=&goal= ``` `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.