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

# Welcome to Dust

Dust invests your spare change, onchain. You opt in once, and every swap you make gets rounded up to the next dollar. The difference goes into a basket of blue-chip Stock Tokens that you choose, and it grows quietly in the background while you trade.

You bought a meme coin. We bought you a piece of Nvidia with the change.

That is the whole product. There is no portfolio to manage, no deposit schedule to keep, no willpower involved. You trade the way you already trade, and three months later you open your vault and find you accidentally own $80 of the market.

Dust lives on Robinhood Chain, the Layer 2 where Stock Tokens trade around the clock against USDG, the dollar stablecoin. It is also available on Solana. [Why Robinhood Chain](/dustprotocol-docs/the-details/robinhood-chain.md) explains the home, and [Also on Solana](/dustprotocol-docs/the-details/solana.md) covers the second deployment.

## What you'll find in these docs

If you are new here, start with [The problem](/dustprotocol-docs/the-problem.md) and [How Dust works](/dustprotocol-docs/how-dust-works.md). Together they take about five minutes and cover everything most people want to know.

If you are ready to use Dust, go straight to [Getting started](/dustprotocol-docs/getting-started.md).

If you are the kind of person who reads the fine print (we like you), the pages on [custody](/dustprotocol-docs/the-details/wallets-and-custody.md), [fees](/dustprotocol-docs/the-details/fees.md), [security](/dustprotocol-docs/the-details/security.md), and [risks](/dustprotocol-docs/reference/risks-and-disclosures.md) say exactly how your money moves, what we charge, what we can and cannot touch, and what could go wrong.

## Where things stand

Dust runs on Robinhood Chain, its home, and is also available on Solana. On Robinhood Chain the contracts are deployed on mainnet, the keeper runs on production infrastructure, and the full loop has been verified against live mainnet state: a round-up, a sweep into Stock Tokens at the quoted price, and a withdrawal back out. On Solana the program is deployed to mainnet and the same loop has been run with real money, through Jupiter into xStocks and back. What stands between that and opening the doors, on either chain, is an external audit and a capped, invite-only beta. These docs describe the protocol as built, and flag what is proven versus what is still gated. We would rather tell you plainly what is not ready than let you assume everything is. The [roadmap](/dustprotocol-docs/reference/roadmap.md) has the current status.

## The one-paragraph version for busy people

Dust is non-custodial: your assets sit in a wallet only you control, and you grant Dust one narrow, revocable permission that lets it move only your round-up change, only into your own vault position, under a weekly cap you set. We never hold your keys, never pool your funds, and never decide what to buy on your behalf beyond the rule you set yourself.


---

# 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://dustprotocol.gitbook.io/dustprotocol-docs/readme.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.