<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 Risks in Vemate.sol

Initial owner balance is the `_totalSupply`

Missing Zero Address Validation

Unused Return Value

Missing Input Validation

Function `setSwapTolerancePercent()` Allows For High Slippage

Unused State Variable

Variables That Could Be Declared as `constant`

Contract Size Exceeds 24576 Bytes

Only Update Necessary Storage Variables

`_approve()` Function Call Can Be Unchecked

Update To Sender Balance Can Be Made `unchecked`

Comparison to Boolean Constant

Declaration Naming Convention

Function Initializing State

Shadowing Local Variable

Too Many Digits

Usage of `block.timestamp`

Missing Emit Events

Inconsistent Comment and Code

Unnecessary `require` Statement

Use `_msgSender()` from `Ownable`

Inconsistency in `lockedBetweenSells` and `lockedBetweenBuys`  Requirements

`maxTxAmount` Initialized at `_totalSupply` Amount

Function and Variable Naming Doesn't Match the Operating Environment

Commented Out Code 

Antibot Mechanism

Changes to Functionality in Contract Update

Vemate

Vemate.sol

Top 10% Security Score

Top 10% Fundamental Score

Vemate is the most versatile and dynamic application on the market which supplies trading analysis tools, market information, fractional and tokenised NFT trading as well as the only fully integrated Crypto - NFT bridging marketplace.


Vemate 

Leaderboards

Due Diligence Tools

Resources

KYC Status