> 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/alby-hub/faq/should-i-open-multiple-channels-with-the-same-counterparty.md).

# Should I open multiple channels with the same counterparty?

You might have encountered the situation where you need more receiving capacity or want to increase your lightning balance, and you plan to open a new channel as you did before.

However there are some things to consider.

1. Opening new channels is expensive. Consider swapping out or rebalancing existing channels.
2. You increase your dependence on a single counterparty. Can you open a channel with a different counterparty instead?

## Swap out

This will increase your receiving capacity by transfering bitcoin from your wallet balance to your on-chain balance: [Swaps](/user-guide/alby-hub/wallet/swaps.md#swap-out)

## Rebalancing **🧑‍🔧**

If you have more than one channel, consider rebalancing them. This redistributes your bitcoin across channels: [Can I rebalance funds from one channel to another?](/user-guide/alby-hub/faq/can-i-rebalance-funds-from-one-channel-to-another.md)<br>

## Choose Another Counterparty [🤓](https://emojipedia.org/nerd-face)

You can check which counterparty nodes you have channels with on your "Node" page. Then, when opening a new channel, you can select another counterparty when you choose the "Advanced" option.

By default Alby Hub will try to pick a new counterparty for you to reduce dependency on one channel partner and improve your [node health](/user-guide/alby-hub/node/node-health.md).

**Thanks. We appreciate that you went through the first steps yourself. 💛**


---

# 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/alby-hub/faq/should-i-open-multiple-channels-with-the-same-counterparty.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.