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

# Status and limits

What is live, and the limits that apply today. Values were read from the networks on **2026-10-16**. Addresses are in [Network reference](/defi/reference/network-reference.md).

## Status

| Network          | State                                        |
| ---------------- | -------------------------------------------- |
| Ethereum mainnet | Live and unpaused                            |
| HyperEVM mainnet | Live and unpaused, with Private Sub-accounts |
| Sepolia          | Test network                                 |
| HyperEVM testnet | Test only. Proofs are forgeable.             |

Palliora DeFi is live on both mainnets. Nothing is in beta. Deployment dates are in [Network reference](/defi/reference/network-reference.md) and [Changelog](/defi/reference/changelog.md).

## Launch limits

Launch limits are in force while the protocol is young. They are on purpose, and they will be increased in steps and announced here.

| Limit                          | Ethereum mainnet | HyperEVM mainnet | Sepolia  |
| ------------------------------ | ---------------- | ---------------- | -------- |
| Minimum deposit                | $10              | $2               | $2       |
| Maximum deposit                | $250             | $250             | $200     |
| Total value cap                | $5,000           | $5,000           | $5,000   |
| Withdrawal fee set by the pool | 0 bps            | 0 bps            | 0 bps    |
| Price feed staleness limit     | 30 hours         | 30 hours         | 30 hours |

The limits count the dollar value of a deposit, using each asset's price feed. A deposit outside the range is refused. A deposit that would take the pool over the total value cap is refused too. Withdrawals and transfers are not limited.

Total value locked, read on 2026-10-16: about $169.76 on Ethereum and about $44.04 on HyperEVM. These move with every transaction. Read `getTvlUsd()` on the pool for the current figure.

If a price feed is older than the staleness limit, or returns an invalid price, deposits of that asset are refused until the feed recovers. The pool does not read price feeds for withdrawals or transfers.

On Ethereum, the Paymaster also reads a price feed to convert the relay fee. It has its own staleness limit, which is 24 hours. A relayed transaction can be refused while that feed is stale, even if the pool's own feeds are fresh.

## What differs between networks

|                                   | Ethereum mainnet                                                     | HyperEVM mainnet                             |
| --------------------------------- | -------------------------------------------------------------------- | -------------------------------------------- |
| Who submits a relayed transaction | An ERC-4337 bundler, through the Gateway and the Paymaster           | A relayer, which calls `pool.transact`       |
| Fee for relaying                  | Paid in a token that has a price feed, from your notes               | A flat fee in USDC, from your notes          |
| Sanctions screening               | On at deposit and registration                                       | No screener is set                           |
| Adaptors                          | Uniswap, Aave, Lido and Morpho                                       | The funding adaptor for Private Sub-accounts |
| Tokens                            | WETH, USDC, static aWETH, static aUSDC, wstETH, and two vault shares | WHYPE and USDC                               |
| Contract revision                 | 2                                                                    | 1                                            |

The contract revision counts upgrades of that pool. Ethereum was upgraded to the current code, so it reports 2. HyperEVM was deployed from that code, so it reports 1.

## Private Sub-accounts

These limits apply when you fund a Private Sub-account and when you bring the money back.

| Item                                        | Value                                                                                          |
| ------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| Token                                       | USDC only                                                                                      |
| Minimum funding                             | 1 USDC. It is fixed in the funding adaptor.                                                    |
| Return                                      | A pool deposit, so the pool's deposit limits apply. The minimum is $2 and the maximum is $250. |
| First transfer from Hyperliquid to HyperEVM | About 1 USDC, taken by HyperCore once per Sub-account                                          |
| Return gas                                  | A flat fee in USDC from the GasStation. See [Fees](/defi/reference/fees.md).                   |
| Positions                                   | One position for each Sub-account. A spent Sub-account is not reused.                          |

A new Sub-account that should be able to return needs the one-time Hyperliquid charge, the return gas and the pool's minimum deposit. That adds up to about 3.05 USDC beyond the margin you trade with. The app recommends funding at least that much. A smaller funding still trades, but a flat position cannot be returned until you add more.

## Registration

On HyperEVM, the relayer can pay the gas for registering your main wallet, so a wallet with no HYPE can register. The relayer accepts a sponsored registration only when all of these hold:

* the call is exactly `registerAddress` and its signature recovers to a wallet;
* the wallet holds at least 1 USDC on HyperEVM;
* the wallet holds too little HYPE to register with its own gas;
* the relayer still has its HYPE reserve for funding jobs, which come first;
* the daily caps are not used up.

The relayer's defaults are 3 sponsored registrations for each IP address and 100 in total for each UTC day, with a reserve of 0.01 HYPE. The operator can change them. Only your main wallet registers. A Private Sub-account is never registered.

On Ethereum you pay your own gas to register.

## Disclosure network

| Item                       | Value                                                                       |
| -------------------------- | --------------------------------------------------------------------------- |
| Revokers                   | One, id 0, active on both mainnet pools                                     |
| Decom guardians            | 7 of 10 must answer                                                         |
| A guardian's request check | The request is no older than 60 seconds                                     |
| Publishing                 | Partial decryptions go straight to the revoker. Nothing is posted publicly. |

See [Accountable privacy and disclosure](/defi/learn/concepts/accountable-privacy-and-disclosure.md) for how a transaction is de-anonymized, and [Palliora integration](/defi/learn/concepts/palliora-integration.md) for where the revoker keeps the report.

## Who can change these settings

The pool owner is a hardware-wallet account. It can pause the pool, upgrade the pool implementation, register assets, adaptors and revokers, and change the limits above. A second account, the pauser, can pause the pool. Both addresses are in [Network reference](/defi/reference/network-reference.md). The pool is upgradeable, so users trust the owner to upgrade it only with care. Without an upgrade, funds leave the pool only through a valid proof, and the owner has no function that moves a user's notes.

When the pool is paused, registration, transactions and tree updates revert. Read `paused()` on the pool to check.

## Next

* [Fees](/defi/reference/fees.md)
* [Security and audits](/defi/reference/security-and-audits.md)


---

# 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.palliora.org/defi/reference/status-and-limits.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.
