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

# Liquid banking

<figure><img src="https://721067793-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fsp6RnXDjniKct5WCnbtk%2Fuploads%2FMFT1vyqtuiVlc2G0axoZ%2Fimage.png?alt=media&amp;token=fa501699-7fe4-4448-8b41-57be1d230db7" alt=""><figcaption></figcaption></figure>

**Hyperliquid** pioneered a performant, fully on-chain central limit order book (CLOB) for **spot and perpetuals trading**, closing the gap with CEXs on depth, latency, and user adoption. What it didn’t natively offer was a way to **spend trading proceeds**, **hold yield-bearing balances**, or **off-ramp** directly from the trading environment.

Liquid Banking is custom built to solve exactly that, exclusively on Hyperliquid.

A **modular, permissionless, fully on-chain financial stack** powered by performant smart-contract modules that compose like building blocks to enable finance on-chain. Retain ownership, flexibility and speed as you experience **accounts, payments, credit, savings, trading, and on/off ramps** without middlemen.

Ownership, modularity and performance that makes “banking on-chain” possible, we call it **Liquid Banking.**


---

# 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.hyperbeat.org/liquid-banking.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.