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

# Welcome

Jaawle is one terminal for stocks, ETFs and crypto, on-chain.

Three things happen here, on the same assets and with the same wallet:

* **Trade perpetuals.** Long or short Apple, the S\&P 500 or Bitcoin up to 10× with USDC as collateral. Every stock market is backed by a pool that holds the real tokenized shares.
* **Buy the stock.** Any listed stock in the issuer's catalogue, as a tokenized share, bought on your own issuer account and delivered to your wallet.
* **Stake and earn.** Deposit shares or USDC into a market's pool. The pool earns the traders' fees and borrow, and every cash dividend stays in it, so it stays yours.

Everything settles in USDC on Base. Collateral sits in audited contracts or in your wallet, never with the platform. Prices come from Pyth, shares from the issuer (today Dinari).

## How this book is organised

| Section                                                                 | Read it if you want to                                                                     |
| ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| [Product](/product/markets.md)                                          | use the terminal: markets, trading, buying stocks, pools, triggers, sessions, fees         |
| [Assets and prices](/assets-and-prices/tokenized-shares-and-custody.md) | know what backs a market, who holds the shares, and where prices come from                 |
| [Risk](/risk/liquidation-and-insurance.md)                              | understand liquidation, insurance, and what can cost traders and liquidity providers money |
| [Protocol](/protocol/overview.md)                                       | understand the contracts: pools and NAV, the trading engine, dividends, governance         |
| [Security](/security/design.md)                                         | review what can go wrong and what stops it                                                 |
| [Legal](/legal/eligibility-and-identity.md)                             | check who may use the platform and how identity is verified                                |
| [FAQ](/legal/faq.md)                                                    | get a short answer                                                                         |

## Status

The platform is in closed beta on Base Sepolia. Market orders commit on-chain and settle at the next published price; take-profit, stop-loss and limit orders run on-chain and are executed by the keeper. Until the issuer partnership is live, share purchases and pool rebalances run against a simulation that fills at the oracle price during the NYSE session; nothing is bought for real yet. Mainnet follows an audit of the contracts.


---

# 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.jaawle.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.
