Xochi
Trade

Xochi whitepaper

Private execution for people and autonomous agents on Ethereum

Technical contracts, fee definitions and cryptographic formats live in the technical appendix.

Somos axolotls

Xochi takes its name from Lake Xochimilco, the axolotl's only native habitat.

In Julio Cortázar's short story "Axolotl," a man watches the animals through aquarium glass until he realizes he is on the other side. The glass never moved. His idea of which side he was on did.

Public networks have a similar way of changing the observer and the observed. Wallets leave trails. Orders reveal positions before they move. Agents repeat patterns that anyone can study. People and agents are not the same, but both are small inside systems built to watch, sort and extract from them.

Axolotls are famous for regeneration. That gift only matters while their habitat survives, and Lake Xochimilco is disappearing around them. We feel some of that in ourselves. We are losing room to recover, change direction and begin again without carrying a permanent public record of every mistake.

Somos axolotls. We need one another, and we need dark water.

Xochi is our attempt to make some of that water. It does not promise total invisibility. It gives a person or an agent somewhere to state what they need, find a solver and move before the whole market gets a chance to act on the plan.

What Xochi is

Xochi is an intent-based execution venue. A user signs the result they want. A solver finds the route, sources liquidity and settles the trade.

The order goes directly to the execution service instead of sitting in a public order book or mempool. That private space between the signed intent and its settlement is the dark pool.

People and agents use the same intent format. Xochi does not take the other side of their trades.

Available assets and routes change with liquidity. The live quote and capability response are the authority. This paper will not pretend a static list can stay current.

Why orders need darkness

On a public chain, a pending swap is also a tip. It tells searchers what is about to move and gives them time to trade around it. A treasury rotating a position can move the market against itself before the trade settles.

Agents have the same problem at machine speed. Their payments and inventory changes form patterns. Once those patterns are visible, other systems can price against them or route around them.

Privacy should not require leaving Ethereum, and compliance should not require handing one operator a complete identity and transaction history. Xochi is built around a narrower exchange: show the facts a trade needs, and keep the rest private.

How a trade works

  1. You ask for an outcome and a destination.
  2. Xochi returns the expected output, fee and settlement method.
  3. You sign those exact terms, including the assets, amounts, destination and expiry.
  4. A solver fills the order from its own inventory or external liquidity, then settles the result.

The user does not have to choose bridges or execution venues. The solver gets no authority beyond the signed terms. If it cannot fill the order under those terms, Xochi rejects the order.

Fees and limits belong in the quote, not in prose that goes stale.

Where privacy ends

Xochi protects the order before execution. The solver still sees it because the solver has to fill it. If the solver uses an external onchain venue, that activity can leave a public footprint.

A public payout goes to the wallet named in the intent. A stealth payout uses a one-time receiving account defined with ERC-5564 and claimed through account abstraction. This makes separate payments harder to connect to one recipient.

Stealth does not hide the asset or amount. Settlement still happens on a public chain. Xochi is not an anonymity system, and we should not describe it as one.

The privacy policy is the authority for data access, retention and third-party boundaries.

People and agents

A wallet is enough to request, sign and execute an intent. No Xochi account is required.

Xochi ID is optional. It is a passkey identity with no username or email. A wallet proves ownership when needed instead of becoming a permanent public profile tied to the account.

An agent can act as a Guest with its own keys. It can also act under a Mandate signed by a Xochi ID holder. The mandate limits the amount, expiry and number of calls. Xochi checks it on every request. The agent never receives the person's passkey or unrestricted control of the wallet.

People and agents are not interchangeable. They can still share the same language for authority: this key may do this thing, within these limits, until this time.

Xochi's ZK Compliance Oracle, ERC-8262

Compliance usually starts by asking for the underlying data. Xochi's ZK Compliance Oracle, ERC-8262 (opens in new tab), asks whether a proof can be enough.

A proof can establish that a credential is valid, a value falls below a risk threshold or an address is not in a prohibited set. The verifier gets the statement, its public context and the proof. It does not need the identity document, exact score or private history behind it.

A provider supplies or signs the signal. The user proves a fact about that signal. The verifier decides whether the fact is enough for the action. The proof does not make the policy decision.

This matters because Xochi should not become a warehouse for everyone's identity and screening data. Selective disclosure is only useful if the unselected data stays somewhere else.

ERC-8262 is a proposed standard and is separate from the current trade path. Regulatory acceptance is not guaranteed.

Fees

The quote shows the full cost before the user signs. That cost includes execution, venue and routing fees. A solver should not fill below its cost floor, and a user should not have to discover the fee after authorization.

Privacy should not be a luxury surcharge. Better terms should come from better execution and narrowly proved trust, not from asking users to expose more personal data than the trade needs.

The technical appendix contains the protocol's fee definitions. The live quote is the authority for a specific trade.

What you still have to trust

Private execution removes some exposure. It does not remove trust.

  • Your wallet must show the terms you are actually signing.
  • The solver learns the order and must stay within those terms.
  • Public chains reveal settlement data.
  • External venues reveal whatever the solver puts onchain.
  • A compliance proof is only as sound as its circuit, public inputs and signal provider.
  • A mandate is only as safe as its limits and the agent key holding it.

We would rather name those boundaries than hide them behind the word "private."

What we are trying to build

A person or an agent should be able to ask for an outcome without narrating the route to everyone watching. They should know the terms before signing. If a counterparty needs a compliance fact, it should get that fact rather than the private data behind it.

Ethereum provides settlement. Solvers provide liquidity. Xochi provides the dark water between intent and settlement.

That water is not empty. Xochi sees the order. The solver acts on it. The chain records the result. Reality stays visible at those boundaries. The dark water gives weak things enough cover to coordinate.

Somos axolotls. We need each other if people and agents are going to keep any room to regenerate.

Further reading

  • Technical appendix
  • Intent API contract (opens in new tab)
  • Privacy policy
  • ERC-8262 discussion (opens in new tab)
  • ERC-5564 stealth addresses (opens in new tab)
  • ERC-4337 account abstraction (opens in new tab)

This document is informational and is not financial, legal or investment advice. Xochi's ZK Compliance Oracle is novel and has no established regulatory precedent.

HomeLearnWhitepaperTermsPrivacyCookies & analytics