> For the complete documentation index, see [llms.txt](https://docs.0y.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.0y.world/product-live-duels/how-trench-duel-works.md). # How Trench Duel Works Two Solana tokens. 45-second trading window. 30-second PvP race. Pick your winner. Trench Duel is 0Y Markets' fast-paced token racing market, where two Solana tokens compete to see which performs better over a 30-second race window. Unlike a Higher or Lower market, you are not predicting whether a token's price will rise or fall. You're choosing which of the two tokens will perform better relative to the other. That means a token can even fall in price and still win, as long as it falls less than its opponent. #### How Trench Duel Works Each Trench Duel follows a simple cycle: 1\. Two tokens are matched 0Y selects actively traded Solana tokens using on-chain market data. Eligible tokens are ranked based on recent activity and price movement, then matched against suitable rivals. 2\. Pick your token Each duel opens with a 45-second trading window. Choose the token you think will perform better during the upcoming race. The market starts at 50/50, with odds changing as traders take positions. You can buy either side or sell your position before trading locks. 3\. Trading locks After 45 seconds, trading closes and the starting prices for both tokens are determined. Once the race begins, no new trades can be placed. 4\. Watch them race The two tokens race for 30 seconds. Follow their performance live on the race chart as their percentage moves update throughout the duel. 5\. Winner is confirmed At the end of the race, the token with the larger percentage change from its starting price wins. The result shown at the bell is provisional while 0Y confirms the underlying price data. Once confirmed, the duel settles automatically and winning positions are paid out. A new duel opens every minute when an eligible matchup is available, so the next duel is already taking trades while the current one races. #### Duel Timeline A new duel starts every minute, and each one follows this timeline: | Time | What happens | | ------------ | ---------------------------------------------------------------------------------- | | 30s before | The next pair is picked, checked that both tokens are still trading, and published | | 0:00 | The duel opens; trading starts at 50/50 | | 0:00 to 0:45 | Trading window, 45 seconds. Traders can buy either side or sell back | | 0:45 | Lock: trading closes, both tokens are re-checked, starting prices are taken | | 0:45 to 1:15 | The race, 30 seconds | | 1:00 | The next duel opens | | 1:15 | The bell. The leader shown is provisional until prices are confirmed | | Bell + \~10s | Settled: winner confirmed, payouts or refunds | If no eligible pair is ready for a slot, that slot is skipped rather than opening late. #### Winning Isn't Just About Going Up Trench Duel measures relative performance, not simply whether a token goes up or down. For example: | Token | 30-sec performance | Result | | ------- | ------------------ | --------- | | Token A | +4% | 🏆 Winner | | Token B | +2% | Loser | Token A wins because it gained more. But this can also happen: | Token | 30-sec performance | Result | | ------- | ------------------ | --------- | | Token A | -2% | 🏆 Winner | | Token B | -5% | Loser | Even though both tokens fell, Token A still wins because it performed better over the race. #### How Tokens Are Selected and Matched **Where do Trench Duel tokens come from?** Trench Duel currently features Solana tokens from Jupiter's trending lists (last hour and last 5 minutes), checked with Helius on-chain data. Before a token can enter a duel, it must meet minimum liquidity and trading-activity requirements (for most tokens: at least $50,000 of liquidity, plus $5,000 of volume, 50 trades and 20 traders in the last hour). 0Y also checks that each token is actively trading before the matchup is published and again before the race begins. \ **How are tokens ranked?** Eligible tokens are ranked by heat, calculated from the average percentile of their recent 15-minute volume, number of trades, number of traders and absolute price movement. **How are two tokens matched?** Each token is matched with a nearby-ranked rival. Matchups must: * be on the same chain * involve different tokens and tickers * fall within the required liquidity, activity and volatility ratios * stay within the permitted ranking gap **Can the same tokens keep appearing?** Trench Duel uses a variety of rules to avoid repetitive matchups. The same matchup is not repeated within the recent cooldown period, and a token normally races no more than two rounds in a row. When fewer eligible tokens are available, some variety rules may be relaxed to keep races moving. The core pairing checks are never relaxed. **How does Up Next work?** The next three matchups are planned ahead and displayed under Up Next. Before each duel opens, both tokens go through a fresh trading check. If either token is no longer actively trading or fails the eligibility requirements, that matchup is removed and the next pair moves up. New matchups are added to the end of the schedule. #### How the Winner Is Calculated To reduce the impact of individual price spikes or isolated trades, Trench Duel uses volume-weighted average prices (VWAP) rather than a single price tick. The starting price is calculated using trades during the 15 seconds before the trading lock. The final price is calculated using trades during the 15 seconds before the race ends. The token with the larger percentage change between those prices wins. #### Ties, Voids and Refunds If the two tokens finish within 0.1 percentage points of each other, the duel is treated as a near tie and all trades are refunded. A duel may also be voided and refunded if reliable starting or final price data is unavailable, a token stops trading before the race begins, or the result cannot be confirmed within the settlement window. #### Trading Limits and Fees Trench Duel uses 0Y’s binary LMSR market model. * Minimum trade: $0.10 * Maximum trade: $10 per account per duel * Payment: Cash Balance or Trading Credits * Trading fee: 2% on every buy and sell * Spread: 3% on the buy price and on sell proceeds * Sell before lock: Available * Fee on winnings: 10% of profit * Maximum profit: 10× stake Trading is only available before the duel locks. You cannot enter or exit a position during the race. #### The Trench Hub The Trench Hub brings the entire experience together. You'll be able to see: * the current live duel and countdown * each token's live percentage movement * upcoming matchups in Up Next * watched tokens and potential matchups * recent duel results Each individual duel also includes a live race chart, odds, trading panel, transactions and final result. After settlement, the experience automatically moves to the next duel. #### Ready to Enter the Trenches? Pick your token before the lock. Then sit back and watch the next 30 seconds unfold. Enter Trench Duel → --- # 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.0y.world/product-live-duels/how-trench-duel-works.md?ask=&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.