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

# High-Level Architecture

Fantasy Slab is built on Solana with a focus on on-chain ownership, transparency, and real-world collectible utility.

## Core Components

* **$SLAB Token** — Primary token with hybrid value accrual (20% gross weekly distribution + optional buybacks/burns)
* **Slab NFTs** — Tokenized graded cards (primarily via Collector Crypt integration)
* **League Participation** — On-chain league entries and draft mechanics
* **Gacha Rewards** — Weekly and seasonal rewards delivered through Collector Crypt gachas

## Revenue Flow (High Level)

1. Users pay league entry fees in USDC
2. **20% of gross revenue** is allocated to $SLAB holders via weekly on-chain distributions
3. Remaining revenue supports slab acquisitions, gacha rewards, operations, and optional buyback/burn activity

## Value Accrual (Hybrid Model)

* **Primary**: Weekly distribution of 20% gross revenue to $SLAB holders (every Sunday)
* **Secondary (Optional)**: Buybacks and burns when the token is significantly overvalued relative to fundamentals

## Key Design Principles

* **On-Chain First** — Revenue tracking, distributions, and ownership are handled on Solana
* **Non-Custodial** — Users retain control of their tokens and NFTs via their own wallets
* **Collector-First** — Real graded slabs and gacha mechanics are central to the reward model
* **Hybrid Economics** — Direct yield to holders with flexible valuation management tools

## Technology Stack

* **Chain**: Solana
* **Token Standard**: SPL Token
* **NFT Standard**: Metaplex Token Metadata
* **Distribution Trigger**: On-chain keepers / automated flows
* **Rewards Delivery**: Collector Crypt gachas

***

[Back to Documentation](/fantasy-slab-docs/readme.md)


---

# 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://fantasy-slab.gitbook.io/fantasy-slab-docs/architecture/high-level.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.