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

# why robinhood chain

Robinhood Chain is a permissionless, EVM-compatible Layer 2 built using Arbitrum infrastructure. It supports standard Ethereum development tools, uses ETH for gas, and is designed for on-chain financial applications.

For PEEPS, the chain offers:

* **EVM compatibility** — familiar wallets, Solidity contracts, and Ethereum tooling;
* **fast execution** — suitable for active token launches and trading interfaces;
* **lower-cost transactions** than Ethereum mainnet in typical conditions;
* **open deployment** — developers can deploy smart contracts without permission; and
* **an emerging ecosystem** where meme culture can develop alongside broader on-chain finance.

PEEPS is an independent application deployed on Robinhood Chain. Use of the chain does not imply that Robinhood sponsors, operates, or endorses PEEPS.


---

# 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://peeps-2.gitbook.io/peeps-docs/peeps-whitepaper/vision/why-robinhood-chain.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.