<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

Dependency on gSOL Token

Unit Test Documentation

Discussion of `appIdParam`

Lack of Condition-fail Action in Subroutine `b_delete_app`

`setup_bridge` Can Be Called Multiple Times

Problematic `GroupSize` Validation

Duplicated Checks on Transaction Type

Redundant Statements

Fee Paid to Owner Addresses

Testnet AssetID and Address

Glitter Finance (Algorand) Addendum

gf-escrow-program.teal

gf-clear-program.teal

gf-approval-program.teal

Glitter Finance (Algorand)

No distinction between fees and locked amount

Unit test documentation

Consider refactoring duplicated code performing Access Control checks

Incomplete usage of SPL Associated Token Account in `init/finalize_token_bridge`

Incomplete usage of SPL Associated Token Account in `release_token`

Incorrect comment on PDA creation

Generic error on specific check

Missing Input Validation for fees in `add_bridge_asset`

Incorrect instruction documentation for `AddBridgeAsset`

Unnecessary variable reference

Escrow amount ignored

Import standard function instead of copying its code

Unmatched refund destination on token bridge disapproval

Fee should be deducted, not added

Unnecessary check on executable address

Use Rust idiomatic strong typing

Inconsistent error messages

Should `DecodeError<T> BridgeError::type_of()` always return same regardless of `<T>`

`solana_program::declare_id!(...)` for TESTNET and DEVNET to be enabled via compilation feature flag

`unpack` should be unit-tested, preferably with corresponding `pack`

Incorrect instruction documentation

Circumventable validators approval for Solana-to-Algorand token bridge flow

Missing multi-signature lifecycle management

Constraint on sensible accounts ownership

Glitter Finance (Solana)

states.rs

errors.rs

processor.rs

instructions.rs

entrypoint.rs

utils.rs

lib.rs

validations.rs

CertiK Skynet

Top 10% Security Score

Top 10% Code Security Score

Top 10% Community Score

Top 10% Fundamental Score

Glitter is a brand changing innovator bridge that brings the everyday user into the crypto world seamlessly

Glitter Finance 

XGLI

Glitter

Leaderboards

Due Diligence Tools

Resources

KYC Status