> For the complete documentation index, see [llms.txt](https://guides.getalby.com/user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.getalby.com/user-guide/browser-extension/features/liquid.md).

# Liquid

The Liquid Network is a Bitcoin sidechain. Use Alby to manage your liquid private keys and interact with the Liquid Network.

## Getting started

Your Liquid private key is securely derived from the Master Key enbling you to safely use supporting Liquid web clients. Your private keys only live in Alby and will never be shared. Liquid clients only request permissions to for example sign events.

To get started, make sure you have a Master Key.

{% embed url="<https://guides.getalby.com/overall-guide/alby-browser-extension/features/master-key>" %}

## How to send Liquid transactions

The Alby Browser Extension lets you use Liquid web clients to hold, send, and receive Liquid assets (e.g. L-BTC) on the Liquid network. When sending payments, the web app asks you to sign a transaction, while your Liquid key always remains stored locally in your browser. Transactions on the Liquid network are enabled through Partially Signed Elements Transactions (PSETs) with the Alby Extension.

## 📖 Further resources

* [Liquid official site](https://blockstream.com/liquid/)
* [PSET: Constructing Confidential Transactions](https://medium.com/blockstream/pset-constructing-confidential-transactions-437109bb4ac5)

## Liquid web clients

* [Alby Liquid Wallet](https://louisinger.github.io/alby-liquid-wallet/) (beta)


---

# 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://guides.getalby.com/user-guide/browser-extension/features/liquid.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.