<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

Incompatibility With Deflationary Tokens

Too Many Digits

Centralization Related Risks in `RedeemHelper`

`token1` May Not Be TEM 

Centralization Related Risks in `StakingDistributor`

Duplicate Recipients

Centralization Related Risks in `Staking`

Lack of Access Control on `claim()`

Centralization Related Risks in `SwordToken`

Redundant Statements

Possibly Incomplete `circulatingSupply()`

Centralization Related Risks in `BondDepository` and `BondDepositoryBNB`

Lack of Access Control on `redeem()` and `redeemAll()`

Possibility to Manipulate Bonds Amount in Case of Pair Illiquidity

Ineffective `isContract()` Check

Lack of Return Value Handling

Lack of Error Messages

Wrong Address in `_mint()` Function

Unused function `addressToString()`

Incoherent Error Message

Lack of Input Validation

Centralization Related Risks in `Treasury`

Lack of Check on `blocksNeededForQueue`

Unnecessary Usage of Boolean Equality

Centralization Related Risks  in `TemplarToken`

Pull-Over-Push Pattern

Lack of Event Emitting

Ambiguous Function Visibility

Templar Dao

contracts

StakingHelper.sol

BondDepositoryBNB.sol

BondDepository.sol

SwordToken.sol

TemplarToken.sol

StakingDistributor.sol

StandardBondingCalculator.sol

RedeemHelper.sol

Staking.sol

TemplarDAO

StakingWarmup.sol

projects

Treasury.sol

Templar DAO 

Leaderboards

Due Diligence Tools

Resources

KYC Status