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

# Networks and what is live

Usance is built to settle on [X Layer](https://web3.okx.com/xlayer), OKX's Ethereum L2. This page is the honest account of what actually runs today. The principle is simple. Anything Usance cannot do yet is disabled in the product with the reason shown, and never replaced by a simulation dressed up as the real thing.

## Testnet today

Usance is deployed on **X Layer testnet (chain 1952)**. The tokens it works with there, `tUSTB` and `tUSD`, are **labelled test stand-ins with no monetary value**. They are not FOBXX, OUSG, ARCOIN, USDC, or any issuer's token. Testnet exists to prove the mechanics end to end: reading a filing, committing a Passport, recognising a conservative value, borrowing and repaying, liquidating a breached account, and running a bounded agent, all on-chain and all with public receipts.

**X Layer mainnet (chain 196)** contracts are **not yet broadcast**, because the deployer is unfunded. So there is nothing with real value to execute against yet. That is a deployment step, and the mechanics are already proven on testnet.

## What is live, what needs access, what is not on X Layer

| Capability                          | State              | Note                                                                                                    |
| ----------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------- |
| X Layer settlement                  | **Live**           | Chain 196 / 1952, verified against the live RPC.                                                        |
| Chainlink price feeds               | **Live**           | 26 Data Feeds on X Layer, read back on-chain.                                                           |
| Evidence → Passport → capacity      | **Live**           | Deterministic, and independent implementations agree to the wei.                                        |
| Builder Code attribution            | **Live**           | ERC-8021 suffix on every write path.                                                                    |
| Delegated mandates + Sentinels      | **Live (testnet)** | Bounded delegation and an autonomous repay proven on testnet.                                           |
| ChainGPT extraction                 | **Live**           | Verified against the live API. Public Passports are built single-source by design, so they stay capped. |
| Exchange OS execution (hedge/trade) | **Needs access**   | No builder deployment access, so those actions are off and nothing is simulated in their place.         |
| Chainlink Data Streams              | **Not on X Layer** | Adapter retained. Nothing routes through it.                                                            |

Every claim above is reproducible against the network.

## The path to mainnet

The plan to make Usance usable with real value from day one:

1. **Deploy to X Layer mainnet (196)** using the same scripts proven on testnet, with governance and guardian roles held by separate addresses, not the deployer.
2. **Admit a small set of real assets that exist on X Layer**, starting with **USDC** as settlement and collateral, and **xStocks** (the tokenized stocks X Layer is bringing liquidity to). Each asset needs a committed Passport built from its issuer's filing and a live price feed, and X Layer's Chainlink feeds already provide the pricing.
3. **Day-one user flow:** connect a wallet, deposit a supported real asset, see its recognised value, and borrow settlement liquidity against it, or arm a Safety Buffer Sentinel. Deposit, borrow, repay, and bounded automation are executable against real assets on day one.

Trading and hedging execution remain gated until external-venue access is granted. They stay disabled rather than faked until then.

## Configuring a deployment

The public site origin is set with `NEXT_PUBLIC_SITE_URL` (the production domain, `https://usance.xyz`), which is what social link previews and absolute URLs resolve against. Email capture stores addresses in Supabase via `SUPABASE_URL` and `SUPABASE_SERVICE_ROLE_KEY`. Until those are set, the subscribe form reports that it is not configured rather than pretending to store.


---

# 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.usance.xyz/understand-it/networks.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.