> For the complete documentation index, see [llms.txt](https://docs.lacunalabs.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lacunalabs.xyz/the-lacuna-wallet/setting-up-your-wallet.md).

# Setting Up Your Wallet

Set up your Lacuna wallet, create a non-custodial crypto wallet, set a secure PIN, and back up your recovery phrase.

## Set Up Your Lacuna Wallet

Set up your Lacuna wallet in a few minutes. Create a non-custodial wallet, set a secure PIN, and back up your recovery phrase before your first private crypto transaction.

## Create A New Wallet

On first launch, choose **Create Wallet**. Lacuna generates your keys locally on the device.

## Set A Secure Wallet PIN

Set a PIN to protect access to your crypto wallet. The PIN stays on your device and is never sent anywhere.

## Back Up Your Recovery Phrase

Write down your recovery phrase and store it offline. Do not save it as a screenshot or in cloud notes. This phrase is the only way to restore your non-custodial wallet. Lacuna cannot recover it for you. See [Backup & Recovery](/the-lacuna-wallet/backup-recovery.md).

## Start Using Private Transactions

Once your wallet is created and backed up, fund your public address and tap **Shield**. This moves funds into Lacuna's shielded pool for private transactions. For the full setup flow, see [Quickstart](/getting-started/quickstart.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lacunalabs.xyz/the-lacuna-wallet/setting-up-your-wallet.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
