# Liberty SHIELD vs Liberty Swap

Liberty has evolved from a single application into a **full protocol layer** with the launch of **Liberty SHIELD** — a unified privacy and routing infrastructure designed to power the next generation of cross-chain and private DeFi.

This page explains the fundamental difference between **Liberty Swap** and **Liberty SHIELD**, and how they work together.

### What is Liberty SHIELD?

**Liberty SHIELD** is a **privacy and routing infrastructure layer**.

It is designed to be:

* **Chain-agnostic**
* **dApp-agnostic**
* **Privacy-first**

Liberty SHIELD allows **any application, on any blockchain**, to interact with **Railgun and other privacy protocols** through a single unified layer.

Instead of every dApp needing to:

* integrate Railgun
* manage relayers
* handle gas abstraction
* route liquidity across chains
* coordinate private settlement

…all of this is handled by **Liberty SHIELD**.

It acts as the **private financial operating system** for Web3.

***

### What does Liberty SHIELD do?

Liberty SHIELD provides a single interface for:

* Shielding assets into privacy pools (Railgun and other ZK systems)
* Unshielding assets back to public blockchains
* Routing funds across chains while preserving privacy
* Abstracting gas, relayers, and fragmented liquidity
* Orchestrating private execution and settlement

In other words:

> **Liberty SHIELD turns privacy into a shared infrastructure instead of a feature that every app has to build from scratch.**

***

### What is Liberty Swap?

**Liberty Swap** is a **single application** built on top of **Liberty SHIELD**.

It uses SHIELD to provide:

* Private swaps
* Private cross-chain routing
* Railgun-powered anonymity
* Gas and relayer abstraction

Liberty Swap does **not** implement privacy itself.

It simply **calls the Liberty SHIELD protocol** to:

* move assets into privacy
* route them across chains
* swap them
* and return them back to users

Think of Liberty Swap as:

> A **frontend and trading interface** powered by Liberty SHIELD’s infrastructure.

***

### Key Difference

|                           | **Liberty SHIELD**                                           | **Liberty Swap**               |
| ------------------------- | ------------------------------------------------------------ | ------------------------------ |
| What it is                | Protocol & infrastructure layer                              | User-facing dApp               |
| Purpose                   | Enable private routing, shielding, and execution for any app | Provide private swaps to users |
| Who uses it               | Developers, protocols, dApps                                 | Traders, users                 |
| Integrates Railgun        | Yes (natively)                                               | Yes (via SHIELD)               |
| Cross-chain routing       | Built-in                                                     | Uses SHIELD                    |
| Gas & relayer abstraction | Built-in                                                     | Uses SHIELD                    |
| Can other apps use it?    | Yes                                                          | No — it is just one app        |

***

### Why this architecture matters

Without Liberty SHIELD, every privacy-enabled dApp would need to:

* Integrate Railgun manually
* Run its own relayers
* Manage gas across chains
* Handle fragmented liquidity
* Build custom privacy logic

This is slow, expensive, and fragile.

Liberty SHIELD solves this by creating a **shared privacy and routing layer** that all apps can use.

This allows:

* Faster development
* More secure privacy
* More liquidity
* More composability

***

### The Big Picture

Liberty is no longer just a swap app.

It is now a **protocol stack**:

> **Liberty SHIELD = the private cross-chain infrastructure**\
> **Liberty Swap = one application built on top of it**

This architecture allows Liberty to scale beyond a single product into a **privacy-native financial network** where any dApp can become private by default.


---

# 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://docs.libertyswap.finance/general-information/introduction/liberty-shield-vs-liberty-swap.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.