> For the complete documentation index, see [llms.txt](https://trovio.gitbook.io/trovio-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://trovio.gitbook.io/trovio-whitepaper/getting-started/quickstart.md).

# 2. Problem Statement

### 2.1 Key Pain Points in Digital Finance

Today’s decentralized finance ecosystem suffers from:

* **High transaction fees**
* **Slow processing times**
* **Scattered wallet infrastructure**
* **Unclear security practices**
* **Poor merchant adoption**
* **Confusing user experience**

<div align="left"><figure><img src="/files/Cq4pwVlOShxehOC8PjR8" alt="" width="375"><figcaption></figcaption></figure></div>

### **2.2 Challenges in Current Wallet / Pay / Swap Systems**

Most existing solutions force users to navigate:

* Multiple apps
* Multiple seed phrases
* Inconsistent swap routes
* No real-time fee optimization
* Limited payment capabilities
* Weak compliance layers

Trovio eliminates this fragmentation.


---

# 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://trovio.gitbook.io/trovio-whitepaper/getting-started/quickstart.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.