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

# Welcome to Tally

Developer documentation for Tally, the share-true layer for tokenized US stocks on BNB Chain.

Tally shows what a tokenized stock really is: how many **shares** you get, not how many tokens. It compares the same US stock across the three issuers on BNB Chain (Ondo, bStock and xStocks), buys from the cheapest tradable one, and refuses to complete a trade if you would receive fewer shares than the minimum you saw.

{% hint style="info" %}
These pages are for developers and the curious: how Tally was built, why it works the way it does, and the contracts behind it. If you only want to use the app, read [How it works](https://app.tallyprotocol.xyz/how-it-works) instead.
{% endhint %}

## Why it exists

One token of a tokenized stock is not one share. Ondo's NFLX token is ten shares, bStock's NFLX token is one, and issuers change the number of shares per token over time. A tool that compares raw token prices sees fake price gaps of hundreds of percent. Tally converts everything into shares first, then checks the numbers against the chain.

## Where to start

{% content-ref url="/pages/QZFd5pwo4DyTqBV3WOP7" %}
[What Tally is](/getting-started/what-is-tally.md)
{% endcontent-ref %}

{% content-ref url="/pages/jF9eX7TCTVWACTik9ljs" %}
[The unit trap](/concepts/the-unit-trap.md)
{% endcontent-ref %}

{% content-ref url="/pages/ZHPQfl8L8wqjgqkb7glL" %}
[ShareGuard overview](/smart-contracts/shareguard-overview.md)
{% endcontent-ref %}

{% content-ref url="/pages/vsSTD6hR8jguLw4QhLDH" %}
[The story](/building-tally/the-story.md)
{% endcontent-ref %}

## Links

|             |                                                                      |
| ----------- | -------------------------------------------------------------------- |
| App         | [app.tallyprotocol.xyz](https://app.tallyprotocol.xyz)               |
| Source code | [github.com/deyoungjohn/tally](https://github.com/deyoungjohn/tally) |
| Built for   | BNB Hack: Tokenized Stocks Edition                                   |

{% hint style="warning" %}
Tokenized stocks track a US stock's price. They are not the underlying shares and carry no shareholder rights. ShareGuard has not been independently audited. Read the [security model](/architecture/security-model.md) before trusting it with more than test amounts.
{% endhint %}


---

# 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.tallyprotocol.xyz/readme.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.