> For the complete documentation index, see [llms.txt](https://paragon-protocol.gitbook.io/paragon-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://paragon-protocol.gitbook.io/paragon-protocol/core-products/paragon-shield.md).

# Paragon Shield

When enabled, trades are routed through a private relay and executed via protected pathways instead of being exposed to the public mempool.

### Private Execution & Protected Routing

Paragon Shield combines:

* private order flow
* batching
* solver-based routing
* aggregated liquidity (including 1inch)

to improve execution quality while reducing exposure to MEV.

***

### What Makes Paragon Different

Paragon is not limited to a single liquidity source.

Trades can be routed across:

* Paragon liquidity pools
* external liquidity (via 1inch integration)
* solver-optimized paths

This allows:

* better pricing
* deeper liquidity access
* more efficient execution

***

### What You Get

* **No public exposure before execution**\
  → orders are not broadcast to the public mempool
* **Reduced sandwich risk**\
  → batching removes typical frontrunning timing
* **Execution validation**\
  → trades must meet minimum output or revert / fallback
* **User-controlled execution modes**\
  → choose between standard and advanced routing

***

### How It Works

#### 1. Private Submission

Two modes are available:

**Classic Swap**

* routed via private relay
* not exposed publicly before execution

**Flow (Intent Mode)**

* user signs an intent
* trades can be batched and optimized

***

#### 2. Routing & Optimization

Solvers search for the best execution path across:

* Paragon pools
* external DEXs (via 1inch)
* multi-hop routes

All routes are:

* validated
* optimized
* protected

***

#### 3. Execution

* trades are executed atomically
* reduced frontrunning window
* consistent execution rules

***

#### 4. Settlement

On-chain settlement:

* verifies execution outcome
* records execution data
* logs Proof-of-Best-Execution (PoBE)

***

### Aggregation Layer

Paragon integrates external liquidity via:

👉 1inch

This enables:

* access to deeper liquidity
* cross-DEX routing
* improved pricing beyond native pools

***

### Multi-Venue Routing (Evolution)

* **Phase 1** → 1inch aggregation
* **Phase 2** → Paragon + external routing
* **Phase 3** → solver-level optimization

***

### Privacy Levels

**Shield Lite (Default)**

* private relay
* anti-sandwich batching
* fastest execution

**Shield Private**

* full intent mode
* no public mempool exposure

**Shield Stealth (Advanced)**

* delayed route visibility
* additional protection for large trades

***

### Fees & Gas

* no additional Shield fee
* standard swap fees apply

**Flow mode**

* optional protocol cut may apply at execution level

**Gas**

* similar to standard swaps
* may increase slightly during batching

***

### Compatibility

* tokens → ERC-20 compatible
* wallets → any EVM wallet
* chain → BNB Chain (testnet → mainnet)

***

### Limitations

* does not remove market volatility risk
* trades may revert if minimum output is not met
* execution depends on available liquidity

***

### Proof-of-Best-Execution (PoBE)

Each trade records:

* minimum expected output
* actual execution output
* execution improvement (if any)

This is displayed as:

👉 “You saved X%”

and is fully verifiable on-chain.

***

### Security

* verified smart contracts
* multisig + timelock controls
* solver allowlisting and monitoring
* emergency pause mechanisms

***

### Integration

Paragon Shield connects to:

* Flow (execution layer)
* governance systems
* Agent Volt (automation layer)

***

### Summary

Paragon Shield provides:

* private transaction routing
* MEV risk reduction
* solver-based execution
* aggregated liquidity access

Paragon Shield is the protection layer that enables safer and more efficient execution across the protocol.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://paragon-protocol.gitbook.io/paragon-protocol/core-products/paragon-shield.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.