<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

Privileged function allows owner to withdraw tokens

OpenZeppelin library code included in source code

Missing emit events

Variables that could be declared as `constant`

Unlocked compiler version

Privileged Low-level Call

Third Party Dependencies

Inconsistent Fee Limit

Excessive allowance granted

Lack of access restriction on function `deposit()`

`tx.origin` is used for authorization

Lack of access restriction on function `harvest()`

Potentially incorrect EOA checking

Lack of input validation

`removeStrategyFromIndex()` does not really remove element from array

Incorrect type `uint8` used

Incorrect search logic

Errors from external contracts are ignored silently

No Minimum `_approvalDelay` for Strategy Upgrade

Lack of access restriction on function `earn()`

Dangerous `makeCustomTxn()` Function

Privileged functions allow strategist to withdraw tokens

Incorrect usage of try-catch statement

Grim Finance

GrimSentinel.sol

GrimFinanceV2

projects

SingleAssetStrategy.sol

LpAssetStrategyV2.sol

GrimVaultV2.sol

Top 10% Code Security Score

Grim Finance 

Leaderboards

Due Diligence Tools

Resources

KYC Status