Security

Afraswap Team is committed to security of the users and their funds and takes a security first approach, the team has taken multiple initiatives to make the contracts to be as transparent as possible and leaving no option open for wrongdoings by the team.

No Migrator code

Migrator code is huge cause of security concern for users nowadays, many big exchanges have it as an feature to assist for any future contract changes.

But this code can be used maliciously as well to steal the funds staked by users into the masterchef contract. To remove the possibility of this Afraswap team decided to remove the migrator code completely. Thus making it impossible for a rugpull by the team.

What about upgrades?

We are currently confident about our code and will be getting it audited to prove our claim of security. In case of any upgrade due to any improvements users will have to follow through some manual steps to get the migration completed , but we believe that is a small price to pay in the future to secure and protect our users today, and we believe the users will agree as well.

Gnosis Safe

The Afraswap Team would be using a Gnosis safe for any contract interaction , and more over using a timelock to lock each change and to notify any changes to users before they happen. Using the gnosis safe allows each action to be atleast approved by 3 different team members , out of our 5 core team members . Thus ensuring that there is no single point of access for the contracts.

Timelock

A timelock will be created and would be responsible for queuing and execution of all actions. The timelock will ensure each action is locked for atleast 12hours before being executed. We believe 12 hours is currently enough team for the community to verify all actions. We will be creating notification channels to notify the users of any transactions that are queued or executed.