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

# Introduction

A Fully Decentralised Price Prediction Market on Solana

> ## **Predict Whether The Price of Solana Will Go Up Or Down**

**UpOrDown** is an intuitive prediction app built around Solana’s Oracle Price Feed. The core idea is simple: players predict whether the price of **SOL** will go **up** or **down** within a set time frame.

Each round, users can place their SOL tokens into one of two pools:

* **Pool Up** – for those who believe the price will rise.
* **Pool Down** – for those who believe the price will fall.

At the end of the round, the Oracle determines the actual price movement. The winning side takes the entire prize pool—both their own stake and the losing side’s stake—distributed proportionally among the winners.

**Example:**

* Total staked in Pool Up: **5 SOL**
* Total staked in Pool Down: **5 SOL**
* Final price: higher than the starting price

Since the price went up, Pool Up is the winner. The 5 SOL from Pool Down gets added to Pool Up, making a total of **10 SOL**. That 10 SOL is shared proportionally among everyone who bet “Up.”

{% content-ref url="/pages/WvAmTNGYVzuitOuDSsV7" %}
[How To Play](/how-to-play.md)
{% endcontent-ref %}


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.upordown.wtf/introduction.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 `build a script that syncs our docs to a CMS` 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.