> For the complete documentation index, see [llms.txt](https://spredict.gitbook.io/whitepaper-v1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spredict.gitbook.io/whitepaper-v1/usdspi-token.md).

# $SPI Token

Initially, Spredict was called Defi All Odds, as we wanted to “Defy the odds'' in the manner sports fans or gamblers participated in sports gaming events. The initial smart contract was built on the Ethereum mainnet to be the most inclusive in the crypto sphere, because Ethereum is known by everybody who is in the cryptocurrency market.&#x20;

After a successful launch of our product, the market shifted and transaction fees became unsustainable. Due to the high gas fees, it was economically not possible to provide rewards for all players, which has always been a foundation of the project's mission and vision.&#x20;

After a deep analysis of the situation and according to the long-term development strategy of the Spredict project, the team has decided to launch a new token, $SPI, on Abstract, a consumer-focused EVM L2, to bring more rewards to the players and more incentives to speculators, stakers, and liquidity providers.&#x20;

<figure><img src="/files/yXwuQfLxsryI3dMdOkNP" alt=""><figcaption><p>$SPI logo</p></figcaption></figure>

### $SPI Info <a href="#usdbcb-info" id="usdbcb-info"></a>

**Contract Address** - TBA

**Dextools** - TBA

**CoinMarketCap** - TBA

**CoinGecko** - TBA

{% hint style="info" %}
*Spredict \~ $SPI Team will **NEVER** contact you asking for money, for a seed phrase, your private key, or any sensitive information. Please report any requests for this information.*
{% endhint %}


---

# 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://spredict.gitbook.io/whitepaper-v1/usdspi-token.md?ask=<question>&goal=<endgoal>
```

`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.
