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

# Introduction

Welcome to FlipFlopBet — the next-generation decentralized casino built on Base Chain. FlipFlopBet redefines on-chain gaming by offering a completely gas-free, trustless, and transparent betting experience powered by Coinbase’s x402 Protocol.

#### What is FlipFlopBet?

FlipFlopBet is not just another crypto casino — it’s a fully decentralized, self-custodial platform where players can place bets directly from their wallets without intermediaries. Every game outcome, bet, and payout is executed on-chain, ensuring fairness, transparency, and immutability.

#### Powered by x402 Protocol

At the heart of FlipFlopBet lies Coinbase’s x402 Protocol, a breakthrough payment settlement layer that allows instant and gasless transactions. This means users can enjoy smooth, real-time gameplay without worrying about gas fees or complex wallet interactions.

#### Platform Fee

To sustain operations and continue building the ecosystem, FlipFlopBet charges a 3% fee on every bet made. The remaining amount is distributed automatically to the winning side, ensuring fair and transparent profit sharing.


---

# 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.flipflopbet.com/flipflopbet/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 `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.