<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

Centralized Control of Contract Upgrade

Centralization Related Risks in `Blueshift Core`

Unchecked Return Value

Dangerous usage of tx.origin

Missing access restrictions on function `removeReserve()`

Missing Restrictions on fee and factor settings

Discrepancy between functions `getAmountIn()` and `getAmountOut()`

Potential reentrancy risk

Financial Model risk

State variable `ReserveCount` is updated by mistake when an existing token is added to the reserve

Third Party Dependencies

Missing Checks for Argument

Potential risks in function `sellExactTokens`

Inaccurate Usage of operator `delete`

Centralization Related Risks in `Blueshift Farm`

Blueshift

TestERC20Token.sol

BlueshiftLPTMinter.sol

FarmingFactory.sol

BlueshiftGovernanceRouter.sol

BlueshiftOracle.sol

BlueshiftPortfolio.sol

BlueshiftPortfolioManager.sol

StakingV2.sol

BlueshiftLiquidityReserve.sol

BlueshiftPair.sol

BlueshiftPairFactory.sol

FarmingV2.sol

BlueshiftOracleFactory.sol

BlueshiftLPTMinterFactory.sol

AutoStakingV2.sol

MinterV2.sol

BlueshiftToken.sol

BlueshiftRouter.sol

Earning.sol

DefaultExternalOracle.sol

BlueshiftERC20.sol

BlueshiftPortfolioAndPairRegistry.sol

StakingFactory.sol

BlueshiftReserveFactory.sol

BlueshiftPortfolioFactory.sol

Initial Token Distribution

Hardcoded UTxO

Typo

Blues Token 

one-shot-currency.hs

BlueShift

OneShotCurrency.hs

Currency

Top 10% Code Security Score

Top 10% Community Score

Top 10% Fundamental Score

Leaderboards

Due Diligence Tools

Resources

KYC Status