# Token Security

## Has UpBots been audited?

Yes, MBXN smart contracts were audited by Red4Sec and Priority Token.

{% file src="/files/-MOGGqvpkZQm0NApgIzQ" %}
UBXT audit - Red4Sec
{% endfile %}

{% file src="/files/-MOGHyBzKo7e2V26bykH" %}
UBXT audit - Priority Token
{% endfile %}

## Are there admin keys for the MBXN Smart-contracts?

The Smart-Contract can be upgraded by the admin, but in a limited way and within a precise framework already defined in the Smart-Contract.

Under no circumstances, new tokens can be created. No other fundamental modification can be changed.

Modifications may concern the addition of rights of the holders (Voting, etc ...), the % of fees to transactions and other elements to improve the user experience on the interface.

## How are tokens held in reserve by UpBots?

All measures are taken to protect to the maximum extent possible the tokens and capital held by UpBots.

All current and future UpBots funds are held in multi-sig wallets, each created for a specific purpose and with specific restrictions on the number of validations required for a transaction confirmation or locking period.

#### MBXN Addresses M**BXT Smart-Contract** - **BSC Network** : 0x719323e2f539D35fd7e549DDcCB43E6bDBA08E17

<br>


---

# 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://upbots.gitbook.io/upbots/about/token-audit.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.