> 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/lacuna-labs/emergency-exit.md).

# Emergency Exit

*For coercion and a compromised device.*

A private balance can still be a single point of failure. EmergencyExit is Lacuna's answer to coercion and a compromised device.

## The problem

If your device is compromised, or you are being coerced, the usual options are both bad: withdraw everything to a public address  recovering funds but destroying privacy or do nothing. Neither is acceptable for money you depend on.

## Fragmentation across hidden wallets

In a single action, EmergencyExit splits your balance across multiple hidden wallets without the funds ever leaving the pool. These destinations are not a stored list  your device derives them from your own keys at the moment you trigger the exit, following a strategy you set in advance. Key generation happens on the device, never on-chain.

*Fig. 8 — One trigger fragments a balance into several unlinked wallets, derived on the device, with funds remaining inside the pool throughout.*

## Two-phase execution & destination binding

The exit runs in two phases. The first records your intent, notifies your chosen contacts, commits to the destination set, and opens a short cancellation window. The second, after the window, redistributes the funds  guarded so that only you or an authorised helper can complete it, and so the destinations fixed in phase one cannot be substituted by anyone who observed the trigger.

## Recovery

Afterward you recover wallet by wallet to a fresh address, using a recovery secret established in advance. Recovery is authorised only for the owner, and only against that pre-registered secret.

## Security properties

* **Funds stay in the pool** during fragmentation never publicly exposed.
* **Destinations are fixed** at trigger and cannot be swapped out.
* **Only the owner** or an authorised helper can execute or recover.
* **Device-derived** destinations there is no list to steal.


---

# 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/lacuna-labs/emergency-exit.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.