> For the complete documentation index, see [llms.txt](https://docs.lacunalabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lacunalabs.io/the-problem-and-the-opportunity.md).

# the problem and the opportunity

*Transparency was the point. Now it is the problem.*

Blockchains were designed to be transparent so that anyone could verify them without trusting a central authority. That transparency is the source of their integrity — and, for money, the source of a serious problem. A public ledger does not distinguish between *verifiable* and *visible*: to prove a transaction is valid, it exposes the transaction to the world.

## The transparency problem

Every shielded asset on a transparent chain leaks the same things: the amount, the parties, and a permanent trail linking them. Sophisticated analysis clusters addresses, links them to identities through exchange deposits and timing, and reconstructs financial relationships that the people involved never agreed to publish. Once an address is tied to you, your entire history — past and future — is exposed.

*Fig. 2 — Lacuna's answer: a shared pool of indistinguishable commitments. Your activity hides among everyone else's — the larger the pool, the stronger the privacy.*

## The real cost

Exposure is not abstract; it has concrete consequences for every kind of user. For an **individual**, a public balance is an invitation: it enables targeting and extortion, lets anyone holding your address see your salary and savings, and makes ordinary payments — rent, medical costs, donations — permanently searchable by employers, counterparties, or strangers.

For a **business**, on-chain operations leak the operational core. Payroll reveals headcount and compensation; supplier payments reveal margins and relationships; treasury movements signal strategy before it is announced. A competitor needs no insider — the ledger is the insider. For a **trader or fund**, every position, entry, and counterparty is legible in real time, inviting front-running and copy-trading and steadily eroding any edge.

None of these parties is doing anything wrong. They simply need the ordinary confidentiality that cash, bank accounts, and brokerage statements already provide — and that public chains, alone among financial systems, fail to offer.

{% hint style="info" %}
**A concrete example.** A startup pays its team in stablecoins. Within weeks, anyone can reconstruct the company's entire payroll — who joined, who left, who earns what — and a competitor can watch hiring accelerate ahead of a launch that was never announced. Nothing was hacked. The information became public the moment each salary was paid.
{% endhint %}

## Why now

Two shifts turn a long-standing flaw into an urgent one. First, stablecoins have crossed from speculation into settlement: they now move volumes that rival mainstream payment networks, carrying payroll, remittances, and commerce that were never meant to be public. Second, autonomous agents are beginning to transact on their own — paying for data, compute, and services over emerging machine-payment rails — continuously and at scale.

Both trends push enormous, sensitive activity onto public ledgers. The more economic life moves on-chain, the less tolerable its transparency becomes. Privacy stops being a preference and becomes infrastructure.

## Why existing solutions fall short

Earlier approaches forced a choice between bad options: custodial mixers that take control of funds, desktop-bound tools too complex for ordinary use, or single-purpose pools with no path to swaps, bridging, or real applications. Lacuna is designed to remove that compromise — full-stack privacy, self-custodial by default, on a phone.


---

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

```
GET https://docs.lacunalabs.io/the-problem-and-the-opportunity.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.