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

# Player Shares

**Player Shares** are the core asset of Basketball.fun — they represent tokenized performance of individual NBA players within the on-chain player marketplace.

Every NBA player has **1,000,000 total Player Shares**, which function like meme tokens tied to the player’s popularity, performance, and narrative momentum. These Player Shares can be acquired, traded, and valued in real-time on a decentralized AMM (Automated Market Maker).

Player Shares behave like a **market-priced fandom asset** — a way to express conviction in a player beyond just sports betting odds and fantasy league prospectives.

We allow players to speculate on hype cycles, and build a portfolio of your favorite NBA stars.

<figure><img src="https://images.unsplash.com/photo-1608245449230-4ac19066d2d0?crop=entropy&#x26;cs=srgb&#x26;fm=jpg&#x26;ixid=M3wxOTcwMjR8MHwxfHNlYXJjaHwyfHxiYXNrZXRiYWxsfGVufDB8fHx8MTc2NDQ5ODYyNHww&#x26;ixlib=rb-4.1.0&#x26;q=85" alt=""><figcaption></figcaption></figure>

Per Player

* Total Supply: 1,000,000 tokens
* Packs: 500,000 (50%)
* AMM (LP): 500,000 (50%)&#x20;

You open&#x20;

League-Wide (100 players)

* Tokens to packs: 50,000,000
* Target pack revenue: $1,000,000
* Tokens per $: 50 (keeps pack EV equal across tiers at launch)

Circulation at T0

* In wallets: 50% (pack side)
* In AMMs: 50% (LP side)


---

# 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://basketball-fun.gitbook.io/basketball.fun-docs/player-shares-and-packs/player-shares.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.