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

# Pools and screening

The private lane's parts and who holds what: 0xbow's Privacy Pools deployed unchanged by gage, the screener and its lists, the borrow router and its caps, and the levers that stop it.

The private lane joins three parts: 0xbow's Privacy Pools, which gage deployed unchanged on Robinhood Chain; gage's screener, which decides which deposits can be withdrawn privately; and gage's `PrivateBorrowRouter`, which turns a withdrawal proof into a loan in one transaction. Deposits, loan terms and positions stay public onchain. The steps a borrower sees are on [Borrow privately](https://docs.gage.cash/borrow/private.md). Addresses are on [Contract addresses](https://docs.gage.cash/protocol/addresses.md), and with the verifiers and the Entrypoint's implementation on the [bounty target inventory](https://docs.gage.cash/protocol/bounty-targets.md).

## The pools

* **0xbow Privacy Pools v1.3.0**, unchanged and built byte for byte as 0xbow builds it: the Entrypoint (behind a proxy), its two verifiers, and one pool per token. 0xbow has no deployment on Robinhood Chain, so gage deployed this one. The Poseidon libraries the pools link to were already on chain; gage did not deploy them.
* **One pool per token, memes and RH ECO tokens only:** PONS, CASHCAT, STONKBROKER, DELTA and HOOKR. USDG never enters a pool, and no Stock Token has one. Since 4 November 2026 the router lends against PONS, DELTA and HOOKR only: CASHCAT and STONKBROKER have a cap of zero (below), and their pools remain for take-backs.
* **A deposit is public:** its wallet, token, amount and time. So are every withdrawal, loan term and position.
* **An approved deposit can be withdrawn privately.** These are 0xbow's standard pools, not a borrow-only variant: a withdrawal proves that it comes from a deposit in the set the screener approved, without saying which, and it can pay any address. gage's app uses a withdrawal only to borrow (the router below); anyone calling the pool contracts directly can withdraw an approved deposit to another wallet. Screening is the control: only an approved deposit can be withdrawn privately.
* **Minimum deposit:** 320 PONS, 850 CASHCAT, 18,000 STONKBROKER, 7,800 DELTA and 4,100 HOOKR, about 100 USDG of each when the pools opened. **Pool fees:** none. The vetting fee on a deposit and the most a relayer may take from a withdrawal are both 0.
* **Taking back.** Whoever made a deposit can always take back what is left of it publicly, to the wallet it came from (0xbow's ragequit), with the deposit's secrets. Neither the screener nor the Entrypoint's owner can stop it.

## The screener

gage runs the screener as the pools' association-set provider. It publishes which deposits are approved, posts the approved set's root on chain, and signs the attestation the router requires before any borrow.

**What it checks, on the depositing wallet:**

| List                | Source                                                                                                                                            | Refreshed                       |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------- |
| Sanctions           | OFAC's SDN list, from the Treasury's own file                                                                                                     | Daily                           |
| Thefts and phishing | The FBI's attributions of public thefts, and ScamSniffer's open list of phishing and drainer wallets                                              | Daily                           |
| The token's team    | Each pool token's team wallets (its deployer, first recipients, disclosed team and vesting wallets) and wallets that received the token from them | Reviewed at least every 30 days |

A wallet on any list is declined, and its deposit can only be taken back. That is how a token's team is kept from borrowing against its own token through the lane, within the limits below.

**The hold.** 10 minutes for a deposit worth at most 1,000 USDG from an established wallet (at least 10 transactions sent, activity at least 30 days before the deposit); 48 hours for every other deposit. The hold is a wait for the lists to catch up with the news: a thief's wallets are often named hours or days after a theft. Approvals go on chain in an update at most every 15 minutes and count once 20 blocks deep.

**It fails closed.** A sanctions or theft list older than 26 hours stops approvals; so does a team list older than 30 days, for its token. A refreshed list that shrinks by more than a tenth is refused and the last good copy kept, until that copy too is older than 26 hours. A deposit found exposed later is revoked at once and backs no further borrow.

**What screening does not prove.** It checks the depositing wallet: one hop, and direct transfers from known team wallets within 90 days. Tokens passed through another wallet, bought by wallets a team funded, or moved through an exchange pass. Revocation reaches only what is still in the pool. The router's per-token caps bound what a miss can borrow.

## The router

`PrivateBorrowRouter` takes a withdrawal proof and, in the same transaction, withdraws that piece from the pool, lists it for the wallet the proof names, and funds it with a plan the rate service signed ahead of the listing. Anyone may send the call: the proof fixes the borrower and the terms, never the moment or which rate-signed plan funds them, so a sender chooses those within the borrower's own cap until the terms' funding deadline, which the app sets ten minutes out. Before anything moves it checks that:

* the pool is the one the Entrypoint registers for the token;
* the proof's root is the Entrypoint's latest and the screener attested it for this token, this router and this chain, for at most 2 minutes (a bound in the code);
* the pool delivers exactly the amount withdrawn: a token that taxes transfers is refused;
* the principal open through the router against the token stays within that token's cap: 50,000 USDG each for PONS, DELTA and HOOKR today, and zero for CASHCAT and STONKBROKER, which borrow privately no more; at most 10,000,000 USDG (a bound in the code).

It takes nothing from the caller and ends every call holding what it started with: nothing.

## Who holds what

| Role             | Held by                                               | Can                                                                                                 | Cannot                                                     |
| ---------------- | ----------------------------------------------------- | --------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- |
| Entrypoint owner | The Safe `0x30e8E13E62DFcd063AF763aB29501FeE74C4918e` | Upgrade the Entrypoint, register or wind down a pool, set fees on future deposits, name the postman | Move a deposit, or stop a take-back                        |
| Router owner     | The Safe                                              | Set each token's cap within its bound, set the attester or clear it                                 | Move funds: the router holds none                          |
| Postman          | A key of the screener                                 | Post the approved set's root                                                                        | Open a borrow alone: the router also needs the attestation |
| Attester         | A key of the screener                                 | Sign the two-minute attestation                                                                     | Change a loan's borrower or terms                          |
| Relayer          | A key of the screener                                 | Send a borrow and pay its gas, choosing when and with which signed plan before its deadline         | Change the borrower or the terms                           |

The pools themselves have no owner and cannot be upgraded.

## Levers that stop it

* **The screener stops attesting:** private borrowing ends within two minutes. Deposits and take-backs go on.
* **The Safe clears the attester:** every private borrow is refused at once.
* **The Safe sets a token's cap to zero:** new private loans against that token stop, as for CASHCAT and STONKBROKER today. Loans already open are untouched, and deposits can still be taken back.
* **Closing the lane** withdraws the router's admission as an entry router and as a filler. Open loans repay, reclaim and settle like any other.

None of them touches a loan already made, or a deposit.

## Status

The lane shipped unaudited at launch, `PrivateBorrowRouter` and gage's deployment of 0xbow's contracts alike, and joins gage's next audit. 0xbow's code is deployed unchanged. Source verification is not an audit; see [Audits and status](https://docs.gage.cash/protocol/status.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.gage.cash/protocol/private-lane.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.
