> 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/product/buy-and-stake-stocks.md).

# Buy and stake stocks

The Stocks page lists every share the issuer tokenizes. You can buy one outright, hold it in your wallet, sell it back, or stake it into the pool of its market.

## The catalogue

Each row is a dShare: the ticker, the company, the price of its perp market when one is listed, and whether it can be ordered on this chain. A stock is orderable when the issuer has deployed its token on the chain the terminal runs on. Stocks that are in the catalogue but not issued here yet are listed and marked as such.

The catalogue is refreshed from the issuer once a day.

## Buying

1. Pick the stock and the amount of USDC to spend.
2. The ticket shows the estimated shares, the fees and when the order will fill.
3. Confirm. Two things happen:
   * you pay first: USDC goes to the platform's adapter wallet, or, on a live issuer account, you sign a permit that lets the issuer pull it;
   * the order is placed at the issuer on your own issuer account.
4. The shares land in your wallet on the fill.

Orders fill during the NYSE session. An order placed in the evening waits for the next open. The Stocks page shows every order with its status and, once filled, the fill price and the transaction.

Selling is the mirror: you send the shares, USDC lands in your wallet on the fill.

## Fees on a purchase

|              |                                                                 |
| ------------ | --------------------------------------------------------------- |
| Issuer fee   | about 10 bps of the notional, charged by the issuer on the fill |
| Platform fee | 10 bps of the notional                                          |

There is no fee to hold, and none to stake.

## Staking

Staking a dShare means depositing it into the pool of its market. In exchange you receive the pool's LP token at the pool's NAV.

While staked:

* the pool uses your shares as inventory that backs traders' longs;
* the pool earns the taker fees, the borrow and the traders' losses, and pays their gains;
* every cash dividend the issuer pays on the pool's shares is booked to the pool's NAV, so your LP token is worth more after the ex-date. The platform takes none of it.

Redeem any time to get shares or USDC back, at NAV, minus the pool's mint/burn fee. See [Provide liquidity](/product/provide-liquidity.md) for how the pool works and what the fee steers.

A staked share is a pooled claim. You also carry the pool's result against traders, which is positive over time when the pool is used and negative in a period when traders win. Holding the share in your wallet instead has no such exposure and no yield.

## Identity

dShares are securities. Buying, selling or staking needs a verified wallet. See [Identity and access](/legal/eligibility-and-identity.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 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.jaawle.xyz/product/buy-and-stake-stocks.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.