# 4.1 The Concept of Liquidity Vapor

Liquidity Vapor represents a phase shift in how assets are stored on-chain. In the Accessth protocol, user deposits are not held in distinct, segregated vaults. Instead, they are sublimated into a monolithic, omni-asset layer known as the "Fog."

When a user deposits 10 ETH into Accessth, that ETH ceases to be "User A's ETH" in a specific storage slot. It becomes part of the global protocol solvency. User A retains a "Permission Set" valued at 10 ETH. This decoupling allows the underlying asset (the Vapor) to be hyper-efficient.

Unlike an Automated Market Maker (AMM) where assets sit idle until swapped, Liquidity Vapor is a "Superfluid" state. The protocol aggregates all idle capital into a single solvency basin. This basin connects to multiple wholesale liquidity venues (aggregators, bridges, lending desks) simultaneously via the protocol's solver nodes.

Mathematically, this transforms the user's capital from a static integer into a probabilistic access right.

Equation of State:
\
The Total Solvency (S) of the protocol must always equal or exceed the Total Outstanding Permissions (P).
\
S >= P

As long as this inequality holds via Proof-of-Reserve (PoR) oracles, the Fog is solvent. Because users rarely withdraw 100% of capital simultaneously, the Vapor model allows the protocol to utilize the aggregate float for network-level yield generation (see Section 4.3), creating a banking-like efficiency without the fractional reserve risk, as the base layer remains fully collateralized on-chain.


---

# Agent Instructions: 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:

```
GET https://docs.accessth.xyz/part-4/4.1-the-concept-of-liquidity-vapor.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.