# Overview

Cocoon is a private permissioned blockchain for institutional finance — purpose-built so that banks, asset managers, and their clients can settle tokenized assets and cash with full regulatory compliance, without exposing transaction details to the public.

{% hint style="info" %}
**Privacy with public proofs.** Transaction data never leaves your infrastructure. Only cryptographic proofs and state roots are posted to Ethereum — converting *"trust us, our database is correct"* into *"verify that our committed state evolved correctly."*
{% endhint %}

## What Cocoon Does

Conventional blockchains force a trade-off: public chains expose every transfer to anyone with a node, while private chains sacrifice the settlement finality and neutrality of a public ledger. Cocoon breaks that trade-off.

|                        | Traditional approach                               | Cocoon approach                                                        |
| ---------------------- | -------------------------------------------------- | ---------------------------------------------------------------------- |
| Transaction visibility | Public to all, or siloed in a single operator's DB | Private within permissioned operator infrastructure                    |
| Settlement proof       | Trust the operator                                 | ZK proofs verified on Ethereum                                         |
| Access control         | Contract or function level at best                 | Contract, function, and **argument level**                             |
| Selective disclosure   | Access control only — share everything or nothing  | ZK proof per disclosed data point — verifiable without raw data access |
| Compliance             | Manual, post-trade                                 | Enforced on-chain at transfer time via identity claims                 |
| Cash leg               | Off-chain bank transfer                            | Confidential digital cash (DBC) settled atomically                     |
| Identity               | Centralised KYC database                           | Portable on-chain identity, selective document disclosure              |

Operators — banks or asset managers — run Cocoon inside their own infrastructure. Their clients' positions, transfers, and documents stay there. Ethereum receives only the cryptographic fingerprints needed for independent settlement verification.

## Products

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Tokenized Money Market Fund</strong></td><td>Available now. Issue, transfer, and redeem MMF shares as ERC-3643 permissioned tokens with atomic DBC cash settlement and built-in compliance checks.</td><td><a href="/pages/dqHDTul0vG2kElPufXNU">/pages/dqHDTul0vG2kElPufXNU</a></td></tr><tr><td><strong>Intraday Repo &#x26; Collateral Management</strong></td><td>In development. Collateralised short-term lending with intraday margining, automated substitution, and tri-party settlement — all settled on Cocoon.</td><td><a href="/pages/CYf3cUvmPnl2fqDzS4i0">/pages/CYf3cUvmPnl2fqDzS4i0</a></td></tr><tr><td><strong>Cross-Border Payments</strong></td><td>In development. FX-linked DBC transfers across operator nodes with near-instant settlement finality anchored to Ethereum.</td><td><a href="/pages/accoQh0UufftJTcwaTlr">/pages/accoQh0UufftJTcwaTlr</a></td></tr></tbody></table>

## Who Cocoon Is For

**Financial institutions** — banks and asset managers who need to offer tokenized products to institutional clients while meeting their own regulatory and data-residency obligations. Cocoon runs entirely inside your existing infrastructure boundary.

**Compliance and legal teams** — every transfer is gated by on-chain identity claims (KYC/AML status, accreditation, jurisdiction). Compliance rules are code, not convention. Audit trails are cryptographically verifiable without requiring public disclosure.

**Developers and platform engineers** — Cocoon is built on Erigon's modular component framework. Each layer (identity, cash, proving, tokens) is an independently deployable component with a stable RPC interface. Existing Ethereum tooling works out of the box.

**Regulators and auditors** — ZK proofs posted to Ethereum give independent assurance of correct state transitions without needing access to raw transaction data. Selective disclosure lets institutions share exactly what is required for examination, nothing more.

## Navigate the Documentation

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>How It Works</strong></td><td>Architecture overview: the four-layer stack, privacy model, and transaction lifecycle.</td><td><a href="/pages/FEuA5hVGSO2ufembhYhy">/pages/FEuA5hVGSO2ufembhYhy</a></td></tr><tr><td><strong>Use Cases</strong></td><td>Detailed guides for each financial product built on Cocoon.</td><td><a href="/pages/8IW744gITN0LOlfrsMO0">/pages/8IW744gITN0LOlfrsMO0</a></td></tr><tr><td><strong>Components</strong></td><td>Reference for every platform component: tokens, cash, identity, ZK proving, and more.</td><td><a href="/pages/CoIiN7mavHP0NQtuej0d">/pages/CoIiN7mavHP0NQtuej0d</a></td></tr><tr><td><strong>Operator Guide</strong></td><td>Deploy and configure Cocoon inside your infrastructure.</td><td><a href="/pages/jTzNDumBns5FvZ8pb6cR">/pages/jTzNDumBns5FvZ8pb6cR</a></td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://cocoon.erigon.tech/getting-started/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.