> For the complete documentation index, see [llms.txt](https://olla-exchange.gitbook.io/intro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://olla-exchange.gitbook.io/intro/1.-introduction-to-olla.md).
# 1. Introduction to Olla
### Overview
Olla is a privacy-first crypto exchange and DeFi ecosystem powered by OChain.
Olla is designed for users, traders, builders, and institutions who want to trade, bridge, manage, and execute digital assets with stronger privacy, control, and selective disclosure.
Most crypto platforms help users access digital assets. However, access alone is no longer enough.
Across public blockchains, wallet balances, transfers, swaps, bridge movements, DCA activity, limit orders, and treasury flows can be monitored, clustered, and analyzed. This creates a deeper problem for users and institutions: digital asset activity can become part of a public financial graph.
Olla is being built to address this problem through a privacy-first exchange and DeFi ecosystem where users can choose shielded or unshielded activity, protect asset movement, reduce financial graph exposure, and selectively disclose information when proof is required.
The goal is not only to help users access digital assets.
The goal is to protect how users hold, move, bridge, trade, execute, and prove digital asset activity.
### The Core Direction
Olla’s core direction is privacy-first digital asset execution.
This means Olla is designed around the full asset journey:
**Hold → Move → Bridge → Trade → Execute → Prove**
Each part of the ecosystem supports this direction:
**OWallet**\
A privacy-first wallet and asset control layer for managing digital assets with stronger control, shielded or unshielded account direction, and selective visibility.
**OBridge**\
A private, risk-aware cross-chain movement layer designed to support asset movement across supported networks while reducing unnecessary exposure of user intent and wallet activity.
**Aggregator Platform**\
A trading and execution layer for swaps, limit orders, DCA, routing, and future private execution flows.
**OChain**\
The confidential execution layer behind Olla, designed to support shielded or unshielded activity, selective disclosure, financial graph protection, private cross-chain movement, privacy-preserving proof systems, and quantum-resistant infrastructure.
### Why Olla Exists
Digital assets are becoming part of real financial infrastructure.
As adoption grows, users and institutions need more than speed, liquidity, or simple access. They need systems that protect financial behavior, trading strategy, wallet activity, cross-chain movement, and treasury operations.
Public execution creates several challenges:
* Wallet balances and activity can be monitored.
* Trading strategies can be exposed through swaps, orders, and execution patterns.
* Bridge movements can reveal cross-chain intent.
* Treasury flows can expose operational decisions.
* Public transaction activity can attract bots, front-running, and surveillance.
* Institutions may hesitate to use DeFi when activity is too visible.
Olla is built around the belief that the next phase of crypto infrastructure must support privacy, control, execution, and proof.
### Privacy by Default, Disclosure by Choice
Olla does not treat privacy as a single feature.
Privacy is part of the ecosystem design.
OChain is intended to support shielded or unshielded execution, allowing users and institutions to choose the level of transparency required for their situation.
The principle is simple:
Shielded when needed.\
Transparent when chosen.\
Provable when required.
This direction allows Olla to support privacy-first activity while still recognizing the importance of proof, auditability, reserve visibility, and compliance-supporting disclosure where appropriate.
### Mission
Olla’s mission is to build privacy-first crypto exchange and DeFi infrastructure for the next era of digital assets.
The ecosystem is designed to help users trade, bridge, manage, and execute digital assets without unnecessarily exposing their full financial graph.
Olla aims to combine:
* Privacy-first exchange and DeFi infrastructure
* Shielded or unshielded execution
* Private cross-chain movement
* Selective disclosure
* Financial graph protection
* Privacy-preserving proof systems
* Quantum-resistant and crypto-agile infrastructure
* Bitcoin and oxBTC integration as part of a broader multi-asset ecosystem
### Looking Ahead
Olla is being developed as a long-term ecosystem across wallet, bridge, trading, and chain infrastructure.
The next stage focuses on OChain confidential execution development, OWallet privacy-first wallet direction, OBridge private cross-chain movement, Aggregator Platform execution flows, Bitcoin and oxBTC integration, security review, testing readiness, and broader ecosystem preparation.
Olla is not being built only for today’s crypto activity.
It is being built for a future where digital asset users and institutions need privacy-first execution, selective proof, cross-chain movement, and resilient infrastructure.
---
# 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://olla-exchange.gitbook.io/intro/1.-introduction-to-olla.md?ask=&goal=
```
`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.