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

<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

Name

Please input a title

Short description of the vulnerability and the affected asset.

The core team is situated in country(ies) that received low aggregated ratings in terms of international judicial cooperation, criminal justice system, anti-money laundering, and corruption. This contextual data suggests an increased difficulty and complexity in preventing and mitigating fraud.

The core team is situated in country(ies) that received medium aggregated ratings in terms of international judicial cooperation, criminal justice system, anti-money laundering, and corruption. This contextual data suggests a medium level of geographic accountability, thus reducing and mitigating the risk of fraud.

The core team is situated in country(ies) that received the best aggregated ratings in terms of international judicial cooperation, criminal justice system, anti-money laundering, and corruption. This contextual data suggests the highest level of geographic accountability, thus maximizing the risk reduction and mitigation.

Vulnerability Title

Centralization Related Risks

Missing Emit Events

Unknown Source of Contract Balance

Unknown implementation of contract `BPContract`

Unable to Unlock Tokens

`initUnlocked` Not Included in `distributedAmount`

Redundant Code Components

Missing Error Messages

Incompatibility With Deflationary Tokens

Variables That Could Be Declared as Immutable

Inconsistent Comments and Code

Incorrect Comments

Gamerse (2022 scope) 

Staking.sol

LFGToken.sol

LFGVesting.sol

Centralization Risk

`add()` Function Not Restricted

Potential Loss of Pool Rewards

Inconsistency Between Comment and Code

Lack of Explicit Pool Validity Checks

Unhandled Return Value

Initial Token Distribution

Lacks `_initUnlocked` Input Validation

Gamerse

contracts

LFGMasterChef.sol

Migrations.sol

interfaces

ILFGVesting.sol

migration

Top 10% Watchlisted

Top 10% Security Score

Top 10% Community Score

Top 10% Market Score

Top 10% Operation Score

Gamerse 

Leaderboards

Due Diligence Tools

Resources

KYC Status