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

# Introduction

## BetBit Sports

### Peer-to-Peer Wager Escrow on Avalanche

BetBit is a decentralized 1v1 wager escrow protocol built on Avalanche. Two participants agree on a wager, both deposit USDC into a smart contract, report outcomes independently, and the winner withdraws their funds. No middleman and no house edge. The smart contract handles custody and settlement.

**Live Demo:** [vip.betbitsports.com](https://vip.betbitsports.com)

**Chain:** Avalanche Fuji Testnet (Chain ID: 43113)

**Currency:** USDC (6 decimals)

***

#### What Makes BetBit Different

**No seed phrases.** Users authenticate with passkeys (biometrics or hardware keys) through ERC-4337 smart accounts. Sign up feels like creating any other web account.

**No gas fees.** Every transaction is gas-sponsored through Pimlico's paymaster. Users never need to hold AVAX or think about blockchain mechanics.

**No trust required.** Funds sit in an immutable smart contract escrow. Neither party, including the BetBit team, can access deposited funds outside the settlement rules coded into the contract.

**Fair settlement.** Both parties submit outcomes independently (blind submission). If they agree, the contract auto-settles. If they disagree, a pre-selected mediator resolves the dispute through an on-chain ruling with an appeal window.

***

#### Quick Links

| Section                                                     | Description                                                    |
| ----------------------------------------------------------- | -------------------------------------------------------------- |
| [Technical Documentation](/technical-documentation.md)      | Tech stack, architecture decisions, implementation approach    |
| [Architecture Overview](/architecture-overview.md)          | Components, workflows, and system design                       |
| [User Journey](/user-journey.md)                            | Full walkthrough from signup to withdrawal                     |
| [Feature Prioritization](/feature-prioritization-moscow.md) | MoSCoW analysis of all features                                |
| [Product Roadmap](/product-roadmap.md)                      | V2 features: operator API, variable odds, team play, AI agents |
| [Smart Contract Reference](/smart-contract-reference.md)    | Contract addresses, ABIs, state machine                        |
| [API Reference](/api-reference.md)                          | Backend endpoints and database schema                          |


---

# 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://docs.betbitsports.com/introduction.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.