> For the complete documentation index, see [llms.txt](https://rooter-3.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rooter-3.gitbook.io/whitepaper/matchups.md). # Matchups Who are you rooting for? A matchup makes it a real question with a scoreboard. ## The rules * Two coins. Seven days. * A sponsor puts up a prize in ETH or $ROOTR. Anyone can sponsor. Rooter sponsors one featured matchup each week from its own share of fees. * Rooted volume on each coin during the window is counted from the fee hook's own events. * At the close, the prize is paid into the winning coin's Rooter Pool and distributed to its holders like any other fee. ## What a matchup changes Only the prize. The fee, the split, the escrow and the pools are untouched. A matchup is a bonus on top of rooting, not a different way to root. Losing costs a rooter nothing beyond the trading they chose to do. ## What a matchup cannot do It cannot be settled by hand. Volume is read from the chain, the winner is whichever number is larger, and the prize goes only to the winner's Rooter Pool. It cannot be cancelled once funded. A tie splits the prize. Matchups are a later phase of the protocol; see [What comes next](/whitepaper/what-comes-next.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 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://rooter-3.gitbook.io/whitepaper/matchups.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.