<username>{{ maskedUsername }}</username><space /><text>just voted for</text><space /><projectLogo /><space /><projectName>{{ projectName }}</projectName>

Bug Bounty rewards are grouped by severity and the impact of the vulnerability. Examples and descriptions of the type of vulnerabilities that correspond to each severity level can be found below. The payout amount has a 5 tier structure with separate scalesfor website/apps and smart contracts.

Description of vulnerability and your proof of concept or validation steps

Short description of the vulnerability and the affected asset.

Vulnerability Title

The linked variables could be declared as `constant` since these state variables are never modified.

Variables That Could Be Declared as `constant`

`public` functions that are never called by the contract could be declared as `external`. `external` functions are more efficient than `public` functions.

Improper Usage of `public` and `external` Type

All of the FoxtrotCommand tokens are sent to the contract deployer when deploying the contract. This could be a centralization risk as the deployer can distribute FoxtrotCommand tokens without obtaining the consensus of the community.

Initial Token Distribution

The contract has unlocked compiler version. An unlocked compiler version in the source code of the contract permits the user to compile it at or above a particular version. This, in turn, leads to differences in the generated bytecode between compilations due to different compiler versions. This can lead to an ambiguity when debugging as compiler specific bugs may occur in the codebase that would be hard to identify over a span of multiple compiler versions rather than a specific one.

Unlocked Compiler Version

In the function `setFoundationAddress()` and `setFoundationFee()`, modifier `authorized` is called through the modifier name without `()`. However, all the rest of the functions that decorated with `authorized` modifier adopted the modifier name with `()`, i.e. `authorized()`, in the project.

Inconsistent Comments and Code

In the contract `OAuth` the role `_owner` has authority over the functions shown in the diagram below.

![](https://accelerator-tasks-prod.s3.amazonaws.com/5d64aa0402d847719ed0991b3293184f/diagrams/centralization-OAuth-_owner.svg)

---

In the contract `FoxtrotCommand`, the role `authorized` has authority over the functions shown as following:

- `setLiquidityPair()`
- `secureTransfer()`
- `pause()`
- `unpause()`
- `snapshot()`


Any compromise to the privileged account may allow the hacker to take advantage of this authority and update the sensitive settings and execute sensitive functions of the projects.


Centralization Related Risks

There should always be events emitted in the sensitive functions that are controlled by centralization roles.

Leaderboards

Due Diligence Tools

Resources