> For the complete documentation index, see [llms.txt](https://homepage.gitbook.io/unified/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://homepage.gitbook.io/unified/solving-technical-challenges/security-considerations.md).

# Security considerations

{% hint style="info" %}
Another key challenge is the use of smart contract approvals and APIs to execute transactions (which is expected to occur in a future iteration of Unified).
{% endhint %}

In its initial iteration, Unified functions as purely **read-only**.  This minimizes security risks to users.  For avoidance of doubt, this means:

* **No smart contract approvals** are required to execute balance transfers on user wallets.
* Exchange APIs are **view-only**.

In its future iteration, the following security measures will be taken:

* The front-end of the platform will be safeguarded to prevent instances such as that of the [BadgerDao hack](https://rekt.news/badger-rekt/).
* 2FA implementation to access user accounts on the platform, so as to add an extra layer of security when exchange APIs that enable transactions are implemented.
* Limits on account activity, monitored by algorithms and bots, will flag and lock out suspicious account activity.
* Smart contract approvals will never be for infinite approvals, unless with the express choice of the user.


---

# 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://homepage.gitbook.io/unified/solving-technical-challenges/security-considerations.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.