> For the complete documentation index, see [llms.txt](https://docs.bawsaq.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bawsaq.org/bawsaq-and-the-chain/live-data.md).

# Live data in the world

The city is wired to Robinhood Chain.

* **The tape** at the top of the screen and the ticker round the BAWSAQ tower show every listed company's price in T2 and its change over the longest window the game has seen, up to 24 hours.
* **The dossier cards** show the same price, the change, how much T2 sits in the token's curve, and whether it has graduated to a pool.
* **The Burn Vault** on Exchange Row shows the total BAWSAQ ever sent to the dead address, `0x…dEaD`, and how much of it arrived in the last window.
* **The status line** under the tape shows the current block and the burn total.

The game's server does the reading and passes it on, so your browser never talks to the chain directly and never needs your wallet for any of it. If the line says **live data offline**, the chain is not answering and the game keeps the last prices it saw.


---

# 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.bawsaq.org/bawsaq-and-the-chain/live-data.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.