> For the complete documentation index, see [llms.txt](https://docs.wpusdt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wpusdt.com/wpusdt/wrapping-fee-structure.md).
# Wrapping Fee Structure
This fee is integral to the ecosystem, ensuring that participants who contribute to the network's security and functionality are rewarded. Here's how the fee is distributed and utilized:
**Fee Allocation:**
* **Validator Nodes:** A portion of the wrapping fee is allocated to Validator Nodes. These nodes play a crucial role in hosting validators to secure the wrapping process, ensuring transactions are processed efficiently and securely.
* **JULD Stakers:** Another segment of the fee benefits JULD stakers, rewarding them for their commitment to the network by staking their tokens.
* **Liquidity Provision:** Lastly, a part of the fee is used to enhance the liquidity of JULD on-chain. This ensures a stable and fluid market for JULD, facilitating easier transactions and exchanges for users.
**Fee Rate:**
* The wrapping fee is set at 0.3%, which aligns with the average market rate for swap fees. This rate is competitively priced, especially when compared to the fees associated with other privacy-enhancing features available in the market.
**Additional Resources:**
For a detailed understanding of how the wrapping fee is utilized within our ecosystem, a flow chart is provided below. Additionally, for more information about the JULD token and its role within the JulSwap platform, please refer to the official documentation available at [JulSwap Documentation](https://docs.julswap.com/juld-token).
This fee structure not only supports the operational and security needs of the wpUSDT network but also contributes to the overall health and liquidity of the JULD market, creating a symbiotic relationship between wpUSDT users, validators, and JULD stakeholders.
---
# 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://docs.wpusdt.com/wpusdt/wrapping-fee-structure.md?ask=&goal=
```
`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.