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

# README

Payy is the first EVM compatible stablecoin chain with privacy at every layer.

### Privacy-first

Payy was purpose built for privacy. Privacy is not a feature that can be added as an afterthought. True usable privacy requires a holistic, thoughtful and complete approach.

### Stablecoin native

Stablecoins need dedicated features. Payy makes working with stables and payments seamless, unlocking wide adoption by consumers and business.

### EVM compatible

Every EVM opcode is supported. Ramps, wallets and application developers can build on Payy using their existing tooling. Privacy is transparently layered in without any breaking changes to the EVM protocol.

### Key features

Payy is purpose built to enable privacy for stablecoin payments and finance.

| Feature                 | Payy                      | Ethereum    |
| ----------------------- | ------------------------- | ----------- |
| EVM compatible          | ✅                         | ✅           |
| Finality                | 300ms (deterministic)     | 15 minutes  |
| Throughput (tps)        | Initially 10k, up to 100k | 12          |
| Avg ERC-20 transfer fee | $0                        | $0.50       |
| Avg txn gas             | $0.01                     | $0.50       |
| Txn gas / fee           | PUSD, PAYY                | ETH         |
| Privacy cryptography    | Native ZK precompile      | Unoptimised |

### Jump right in

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-hashtag-lock">:hashtag-lock:</i></td><td><strong>Privacy</strong></td><td>Payy enables 3 native privacy flows.</td><td></td><td></td><td><a href="/pages/xxRhHjFUJlurO0waNJ36">/pages/xxRhHjFUJlurO0waNJ36</a></td></tr><tr><td><i class="fa-dash">:dash:</i></td><td><strong>Stablecoins</strong></td><td>Features to enable stablecoin use cases.</td><td></td><td></td><td><a href="/pages/1odsmnSlqGGJ8IhPc4tv">/pages/1odsmnSlqGGJ8IhPc4tv</a></td></tr><tr><td><i class="fa-trowel">:trowel:</i></td><td><strong>Architecture</strong></td><td>ZK L2 rollup architecture.</td><td></td><td></td><td><a href="/pages/xVn8igInT3ZRRxFW4ySj">/pages/xVn8igInT3ZRRxFW4ySj</a></td></tr></tbody></table>


---

# 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.payy.network/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.