<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

FanVerse

Uniswap

Centralization Risks in fanvStaking.sol

Unchecked ERC-20 `transfer()`/`transferFrom()` Call

External Dependency

Variables That Could Be Declared as `constant`

User-Defined Getters

Uninitialized Local Variable

Unlocked Compiler Version

Redundant Statements

Discussion on `multiplier`

FanVerse Staking

fanvStaking.sol

Missing emit events

Improper usage of `public` and `external` type

Unlocked compiler version

Incorrect error message

Incorrect function names

Initial token distribution

Unknown externally owned account(EOA)

Third party dependencies

Centralized risk in `addLiquidity()`

Potential reentrancy attack

Potential sandwich attacks

Variable could be declared as `constant`

Missing input validation

Centralization related risks

Redundant codes

Lack of reasonable boundary

Lack of checking the `_isExcluded[account]` exist or not

Logical issue of the variables `tradingOpen` and `launchedAt`

FanVerse Coin

FanVerse Coin.sol

CertiK Skynet

Leaderboards

Due Diligence Tools

Resources

KYC Status

Centralization Scanning

Contract Uncertainty

Owner Privilege

Trading Constraint