Boost Protocol

Rating

Score51.00

Services

Sec. Infrastructure Overview

Current Bug Bounty:

No Bug Bounty

Bug Bounty Max Payout: 0 $

Has paid White Hats before:

Date of Last Audit: 1 Jan 1

Recent Security Incidents

Incident
Amount Lost
Date

Secured By

The Protocol is secured by

Name
Type
Website
0
View

Past Audits

Number of Audits

1

Number of Vul. Found

9

Date of Last Audit

1 Jan 1

Past Audit Reports

Last codebase change was on: 1 Jan 1

Company
Date
Number of Vul Found
Link
1 Jan 1
0
View Report

Show Code Locations

Show all Vulnerabilities

Vulnerabilities reported in past audits

Severity
Title
Location
Link
REDUCTED
REDUCTED
REDUCTED
View Report

Code Structure

Lines of Code

0

Amount of Contracts

64

External Integrations

0 Code Summery

The main purpose of the Boost application is to serve as a distributed incentives network that allows wallets to deploy incentive offers for on-chain actions. Users can learn about the Boost ecosystem and how it operates, making it accessible for newcomers. The Boost App acts as the primary frontend client for discovering and receiving these incentive offers, catering to crypto users looking to earn rewards. Developers can utilize the Boost SDK and API to build on the Boost Protocol, while projects already supported can follow guides to deploy their own boosts. Additionally, rollups can integrate Boost by deploying Edge contracts and registering their networks within the ecosystem.

Show Dependency Graph

Code Structure & Dependency

Show Codefile metrics

Centralization

Decentralization Score

10 out of 20

Contract Upgradability

No upgradability

Frontend

Go to Dapp

Maintenance Score

0.00

Poor

Excellent

Admin / Governance Functions

Timelocks

Uses Timelocks

Pauseability

No pause

Admin Wallet

admin can directly clawback assets from the budget. `IN`n additionally manage authorized users on the budget. Admin can set or update fees

No Pause Mechanism

You can choose to deploy a boost immediately or you can schedule it at an exact time or date in the future. A boost can be active for a maximum of 30 days

Recommendations

Regardless of future integrations a ManagedBudget should only be able to have funds moved out of itself through the existing defined functions in the contract (clawback, disburse). Assuming an ERC20Incentive and SignerValidator regardless of future modules or integrations given these two modules for a boost the only path to disburse funds should be through boostCore:claimIncentive or directly through clawback.

User Rating

Avg. User Rating

No ratings

No ratings yet

Submit your review

Protocols on SCAS can't offer incentives to hide reviews

Disclaimer:

SCAS conducts security assessments on the provided source code exclusively. Conduct your own due diligence before deciding to use any info listed at this page.

In case you find any information on this report is incorrect, please fill out following form:Feedback