# 🚫Community Protection

### **Anti-whale community protection**

Here at JavaSwap we’ve implemented multiple protection mechanisms to maximise security

and to ensure the best interests of the community. This is why we take our security with utmost seriousness, we are auditing all our smart contracts. Therefore, we have implemented the following mechanisms to ensure the stability of our ecosystem:&#x20;

One of the features we’re providing to protect the community is that we will utilise anti-whale mechanisms to prevent whales from hoarding massive amounts of JAVA. The maximum amount of JAVA that can be purchased without triggering the anti-whale mechanism is 1,000 USDC per transaction, but if you want more tokens, then the price will incrementally increase. The higher the demand, the higher the price. \
.&#x20;

![](https://1460720230-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MivkA2TPMnWA0sespBA%2F-MkJFEHggQfEAjO20QTa%2F-MkJL8OwNUW68TGRoOKW%2FPRICE%20vs.%20USDC.png?alt=media\&token=9cb094cc-2b46-4dbb-9694-6c5eec00e6e6)

Another anti-whale feature is that our presale prevents whales from buying massive amounts at a discounted price by limiting the orders per account, so a whale can not use an account to purchase lots of small orders to keep the initial token offering price at 1 USDC for 4 JAVA or its equivalent in MATIC. Since JAVA is the people’s token, we have created a fair and level playing field to ensure that smaller community members will flourish and that a small group of whales will not dominate and hold a large majority of the token supply.&#x20;

### **Anti-bot mechanism**

We use a sophisticated CAPTCHA system to prevent bots from placing any orders.

### **Potential Risks**

Disclaimer: Only spend what you can afford to lose. All financial assets have risks.

All projects carry a degree of risk, here at JavaSwap we have sought to prevent, mitigate and combat potential risks, yet some level of risk is inherent in all projects. We are currently undergoing rigorous auditing of smart contracts by several parties as code quality is of foremost importance to the team. Despite this, there are always risks when using an AMM. Understanding these risks is the responsibility of all community users.&#x20;

Here are some potential risks:&#x20;

Smart contract exploits - Although this is extremely unlikely, a new zero day exploit could be discovered in the smart contract, or despite all of our audits a potential exploit could have eluded the security teams.

Impermanent loss- You could have impermanent loss when providing liquidity to Liquidity Pools. If you don’t understand impermanent loss and its associated risks, check out our medium article titled DeFi risks.

Hackers - Hackers are always a looming threat for every CEX, DEX and AMM, however we have sought to mitigate against this via meticulous code quality, rigorous security and smart contract audits. All of these combine to vastly diminish the chances a hacker successfully exploits a bug in our code.

JAVA token value loss- There is also the potential risk that JAVA once purchased could decline in value.\
