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

# Introduction

**Soccit** is a gamified football prediction market built on **Solana**, powered end‑to‑end by the **TxODDS TxLINE** live data feed. Fans predict *what happens inside a match* — substitutions, final scores, and (soon) goalscorers — lock those predictions into an on‑chain match vault, and are scored and paid out automatically from the same feed that referees the real game.

This GitBook is the **Brief Technical Documentation** for our submission. It covers three things:

1. **Core idea** — what Soccit is and the prediction → settlement loop it closes.
2. **Business & technical highlights** — why it matters and how it is built.
3. **The specific TxLINE endpoints we used** — the exact TxODDS surface our pipeline consumes, both HTTP and on‑chain.

## At a glance

|                      |                                                                                                                   |
| -------------------- | ----------------------------------------------------------------------------------------------------------------- |
| **Category**         | Prediction Markets & Settlement (World Cup Track)                                                                 |
| **Data provider**    | TxODDS — TxLINE Soccer feed, **Service Level 12** (free real‑time World Cup & International Friendlies)           |
| **Chain**            | Solana (program live on **devnet**; TxLINE subscription paid once on **mainnet**)                                 |
| **On‑chain program** | `TbxGzvqiuNfeV8GAoP2unFwjTu1Ry7hjnaesCorJm9v`                                                                     |
| **Frontend**         | Next.js 16 · React 19 · Tailwind 4 · Solana wallet‑adapter                                                        |
| **Backend**          | Node/TypeScript services — Hono + tRPC API, TxLINE worker, scoring projector, settlement keeper (MongoDB + Redis) |

## Repository layout

Everything lives in one repository (`ameliazsabrina/soccit`, `main`), split into two workspaces:

* **`backend/`** — the Anchor program (`backend/programs/soccit`) plus the TypeScript services (`backend/services/*`): the TxLINE ingest worker, the scoring engine, the settlement keeper, and the read/stream API.
* **`frontend/`** — the Next.js app (`frontend/app`): match arena, live scoreboards, leaderboards, vault/settlement views, and wallet‑signed predictions.
* **`documentation/`** — this GitBook.

## How to read this

* Start with [**Core Idea**](/soccit/core-idea.md) for the product and the prediction loop.
* [**Technical Highlights**](/soccit/technical-highlights.md) and [**Business Highlights**](/soccit/business-highlights.md) cover the *how* and the *why*.
* [**TxLINE Endpoints Used**](/soccit/txline-endpoints.md) is the checklist reviewers are looking for — every TxODDS endpoint, with method, purpose, and where it lives in the code.
* [**Architecture Reference**](/soccit/architecture.md) has the end‑to‑end data flow and the Soccit read/stream API surface.


---

# 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://amelias-organization-20.gitbook.io/soccit/readme.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.