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

# RAVEN RUSH DOCS

**Raven Rush** is a next-generation decentralized PvP racing game that fuses high-octane competitive gameplay with Web3 financial mechanics. Built for racers, stakers, and digital pioneers, Raven Rush empowers players to compete in real-time matches across multiple chains — with real value at stake.

<figure><img src="/files/VbizciZOKU6KzrACioMS" alt=""><figcaption></figcaption></figure>

Raven Rush combines the thrill of racing with the power of decentralized tech — a platform where **your skills are your currency**.

Raven Rush is more than a game. It's a movement redefining the intersection of gaming, ownership, and decentralized finance — starting on **BSC**, **Polygon**, **Solana**, and **Arbitrum**, with **Sui** and beyond on the horizon.\
\
Below is a comprehensive overview of everything Raven Rush encompasses: (subsequent updates to be made as we BUIDL)

<table data-header-hidden><thead><tr><th></th><th></th><th data-hidden></th></tr></thead><tbody><tr><td><strong>Section</strong></td><td><strong>Title</strong></td><td><strong>Subsections</strong></td></tr><tr><td>#</td><td><strong>Overview</strong></td><td>—</td></tr><tr><td><strong>1.0</strong></td><td>Introduction &#x26; Background</td><td>1.1 What is Raven Rush? • 1.2 The Problem with Web2 Gaming • 1.3 Core Philosophy • 1.4 Why Racing? • 1.5 Our Mission • 1.6 Snapshot Overview</td></tr><tr><td><strong>2.0</strong></td><td>Game Mechanics &#x26; Design</td><td>2.1 Core Gameplay Loop • 2.2 Game Modes Explained • 2.3 Matchmaking Logic • 2.4 Car Customization &#x26; Upgrades • 2.5 Skill Progression System • 2.6 Race Tracks &#x26; RNG Control</td></tr><tr><td><strong>3.0</strong></td><td>Blockchain Architecture</td><td>3.1 Multi-Chain Deployment • 3.2 Smart Contract Infrastructure • 3.3 On vs Off-Chain Logic • 3.4 Gas Optimization • 3.5 Cross-Chain Asset Management</td></tr><tr><td><strong>4.0</strong></td><td>Token Utility &#x26; Staking Mechanics</td><td>4.1 Token Roles • 4.2 Staking in PvP • 4.3 Tournament Pools • 4.4 Fee Mechanics (2.5%) • 4.5 Staking &#x26; Governance</td></tr><tr><td><strong>5.0</strong></td><td>Player Experience Journey</td><td>5.1 Onboarding • 5.2 Wallet &#x26; Profile Setup • 5.3 XP, Ranks &#x26; Rewards • 5.4 User Interface • 5.5 Leaderboards</td></tr><tr><td><strong>6.0</strong></td><td>Roadmap</td><td>6.1 Rollout Plan • 6.2 Early-Bird &#x26; Waitlist • 6.3 Beta Access • 6.4 Long-Term Vision</td></tr><tr><td><strong>7.0</strong></td><td>Technical Overview</td><td>7.1 Tech Stack • 7.2 Backend &#x26; Game Engine • 7.3 API &#x26; SDK • 7.4 NFT Metadata • 7.5 Infra Resilience</td></tr><tr><td><strong>8.0</strong></td><td>Security &#x26; Fair Play</td><td>8.1 Anti-Cheat • 8.2 Smart Contract Audits • 8.3 Bot Detection • 8.4 RNG Oracle</td></tr><tr><td><strong>9.0</strong></td><td>Governance &#x26; Community</td><td>9.1 DAO Model • 9.2 Voting System • 9.3 Player Councils • 9.4 Moderation Framework</td></tr><tr><td><strong>10.0</strong></td><td>Marketing Strategy &#x26; Ecosystem Growth</td><td>10.1 Pre-Launch Strategy • 10.2 Socials &#x26; Campaigns • 10.3 Referral &#x26; XP Onboarding • 10.4 Esports &#x26; Streamers • 10.5 Creator Support</td></tr><tr><td><strong>11.0</strong></td><td>Legal &#x26; Compliance</td><td>11.1 Regulation Readiness • 11.2 Jurisdictional Controls • 11.3 NFT &#x26; Token Legal Use • 11.4 Terms &#x26; KYC</td></tr><tr><td><strong>12.0</strong></td><td>FAQ</td><td>12.1 Gameplay • 12.2 NFT Ownership • 12.3 Tokens • 12.4 Cross-Chain Play • 12.5 Support</td></tr></tbody></table>


---

# 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:

```
GET https://raven-rush.gitbook.io/docs/raven-rush-docs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.