> For the complete documentation index, see [llms.txt](https://nsk-swap.gitbook.io/nsk-swap/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nsk-swap.gitbook.io/nsk-swap/market-analysis/market-challenges.md).

# Market Challenges

* **Scalability:** \
  Some decentralized swap protocols face scalability challenges due to the limitations of blockchain networks, resulting in high fees and slower transaction times during periods of high demand.<br>
* **User Experience:**\
  &#x20;Improving the user experience of decentralized swaps remains a challenge, as some platforms may require technical knowledge or lack intuitive interfaces, hindering mainstream adoption.<br>
* **Regulatory Landscape:** \
  The decentralized nature of swaps raises regulatory concerns in various jurisdictions, leading to uncertainties and potential regulatory hurdles for decentralized swap platforms.


---

# 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://nsk-swap.gitbook.io/nsk-swap/market-analysis/market-challenges.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.