> For the complete documentation index, see [llms.txt](https://arborswap.gitbook.io/product-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://arborswap.gitbook.io/product-docs/important/safu-contract-badge.md).

# Safu contract/badge

The SAFU Badge on Arborswap signifies that a project is protected against manipulation by the developer to harm investors or gain an unfair advantage. The SAFU Badge is granted to projects that have completed the KYC process and have their LP (liquidity provider) tokens held by RoburnaLabs. This ensures that the project's LP tokens are securely managed by a trusted entity, promoting transparency and accountability in the DeFi ecosystem. The SAFU Badge serves as a mark of confidence for investors, signaling that the project has taken measures to safeguard their interests and prioritize investor protection on Arborswap.

##

## Criteria of a SAFU Project

* Projects must do KYC with ArborSwap
* Arborswap will secure the LP and Team tokens in a multisig for enhanced security and protection.

**Owner Privileges**

* RoburnaLabs developer must hold the contract ownership for 30 days minimum
* RoburnaLabs developer must pause trading until listing time
* RoburnaLabs developer must own the staking ownership. Staking dapp must be audited.
* Owner can not be able to mint new tokens
* Owner can not be able to pause trading
* Owner can not be able to set max transaction limit lower than 0.1% of circulating supply
* Only RoburnaLabs dev may blacklist snipers during the 7 days of holding ownership. After 7 days or when ownership is transferred, the blacklist must be non-functioning.
* Owner can not be able to claim the contract’s balance of its own token
* Owner can not be able to set max wallet limit lower than 1% of circulating supply
* Owner can not increase taxes in the first 7 days from listing
* Anything that can be changed by the owner can not limit or stop trading for the investors. (Anti-bot without time limit, Transaction time lock without limit, sell limit based on holder balance, etc.)

## Tokenomics

* Tax cannot be higher 10% buy or sell (max 10% each side)
* No unlock tokens in first 30 days from listing
* The minimum liquidity lockup period is 365 days, and any exceptions to this rule require prior agreement regarding migration to the Roburna mainnet. In the event of a migration agreement, the ArborSwap development team will hold the LP until the migration takes place.
* Liquidity percent 60% at least
* Private sale bonus shouldn't be greater than 10% from presale/fair launch rate
* Private sale can be sent at the start of launch. The first send cannot exceed 20% of the liquidity's value in BNB in tokens. The next two days 50% of the remainder of the private sale in tokens can be sent each day.
* Listing rate should be equal to presale/fair-launch/subscription rate
* RoburnaLabs developer must control unlock tokens (RoburnaLabs developer will help projects to distribute seed, private sale tokens)
* RoburnaLabs developer needs to confirm if the project had a private sale. If there was a real private sale, RoburnaLabs developer can distribute tokens for private sale investors.
* No airdrop tokens in first 30 days from listing (No giveaways, contest tokens)
* For migration from old contracts, new tokens may not be distributed to old holders until 30 days from listing

## Contract

* Contract must be audited by a trusted partner
* Buybacks should be automated
* Burns should be automated
* Auto liquidity should go to an unreachable address. (Dead address etc.)
* Contract should not malfunction in any circumstances
* No proxy contracts

Common Problems That Cause Contracts to Crash

* Failed transactions that are caused by mathematical errors
* Swap settings and parameters should always be in a safe range

\
\ <br>


---

# 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://arborswap.gitbook.io/product-docs/important/safu-contract-badge.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.