# Fee Structure

Quack Swap’s fee model is designed to be **simple, transparent, and predictable**. Our goal is to give users full clarity on costs before they commit to any swap.

#### **1. Network Fees (Gas Fees)** <a href="#id-1.-network-fees-gas-fees" id="id-1.-network-fees-gas-fees"></a>

Every blockchain transaction requires a **network fee** (“gas”), which is paid directly to the blockchain. Quack Swap never profits from gas — 100% of these fees go to the network validators.

* Gas fees vary by network (e.g., Ethereum vs. Solana).
* These are estimated and displayed at the quote stage.
* To ensure reliability, our routing engine sets slightly higher gas limits than raw estimates to prevent failed transactions, while unused gas is automatically refunded (as per mechanisms like Ethereum’s EIP-3529).

#### **2. Partner Fees** <a href="#id-2.-partner-fees" id="id-2.-partner-fees"></a>

Quack Swap integrates with decentralized exchanges (DEXs), liquidity pools, and bridges, each of which sets its own protocol fee.

* These fees are built into the routing process.
* They vary based on token liquidity, market volatility, and route complexity.
* Quack Swap displays them upfront in the transaction quote.

#### **3.** Quack **Swap Fee** <a href="#id-3.-quantum-swap-fee" id="id-3.-quantum-swap-fee"></a>

Quack Swap applies a **small platform fee** on each transaction.

* Fees are always taken **from the input token** — never from your output. *Example:* if you are swapping **ETH → SOL**, the small fee is deducted in **ETH** at the time of sending.
* This ensures clarity: you know exactly how much of your input token is being used.
* A portion of this fee may also be allocated toward **community initiatives, token buybacks/burns, or growth programs** as outlined in our roadmap.

#### **Transparency Commitment** <a href="#transparency-commitment" id="transparency-commitment"></a>

* All fees (network, partner, and platform) are included in the **initial route quote**.
* No hidden deductions, no surprises after execution.
* Routes are optimized to ensure the **lowest possible cost** for the user while maintaining reliability and security.


---

# 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://quack-swap.gitbook.io/quack-swap-docs/technology-and-roadmap/whitepaper/fee-structure.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.