# What is horizontal scaling

### What is Horizontal Scaling

In Web3, horizontal scalability refers to scaling blockchains for desired performance. More specifically, scaling the ability of a blockchain to process transactions and achieve consensus across an increasing number of users at *desired* latencies and throughput. IPC-BTC is one such scaling solution, alongside other popular layer two solutions, like [sidechains](https://ethereum.org/en/developers/docs/scaling/sidechains/) and [rollups](https://ethereum.org/en/developers/docs/scaling/#rollups).

Horizontal scaling expands a network’s capacity by increasing the number of nodes participating in the network rather than upgrading the capacity of the existing ones.  The horizontal scaling approach distributes workloads more evenly and preserves decentralization through increasing node/network participation, which directly reflects on the strength of the network's  security and aligns with Web3 principles of openness and inclusivity.

<figure><img src="/files/q9TRTQNll9Q5r2QOX7yL" alt=""><figcaption><p>Simplified graphical representation for horizontal scaling</p></figcaption></figure>

In contrast, vertical scaling improves performance by upgrading node hardware but risks centralization by raising entry barriers and concentrating control among fewer, wealthier participants. While horizontal scaling is more complex to implement, it ensures higher throughput and resilience without compromising decentralization, making it the preferred strategy for scaling blockchain infrastructure sustainably.

{% hint style="info" %}
Want to learn more about horizontal scaling?&#x20;
{% endhint %}


---

# Agent Instructions: 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://bitcoin-scaling-labs-docs.gitbook.io/ipc-btc-scaling-docs/horizontal-scaling/quickstart.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.
