GetUnite / liquidity-direction-protocol

10 stars 2 forks source link

Bug Bounty Program - LOW TIER #11

Open 0xtuytuy opened 2 years ago

0xtuytuy commented 2 years ago

Bounty Table

Please use this structured bounty table for general guidance. All final decisions are at the discretion of Alluo DAO and the community.

Severity Payment (50% in $ALLUO 50% in $ALLUOLP) Gitcoing link
Low $250 Dework funding
Medium $500 Dework funding
High $5,000 Dework funding
Critical $25,000 Dework funding

This issue is specifically for the Low Tier

If you would like to work on a tier that is higher please submit work to the relevant issue. Once submitted, work will be reviewed and at the discretion of the Alluo DAO following the OWASP model and then assigned to the correct Severity Level.

OWSASP framework matrix

Response Targets

Alluo will make a best effort to meet the following SLAs for Contributors participating in our program:

Type of Response SLA in business days:

The features and improvements that the Core-Contributors team is working on are available on our public roadmap.

More documentation about the protocol and how it is working are a work in progress.

If you have any questions, feel free to reach out on Discord

Scope

All public assets, smart contracts and others that are public in the Alluo's Github repo are part of the scope.

Installation & Setup

We have guides available for how to get a deploy all the code locally in each separate repository. Generally, the Core-Contributor use Hardhat as a framework. See each repo for step-by-step walk-throughs.

Feel free to reach out to our Discord for help.

Program Rules

gitcoinbot commented 2 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


This issue now has a funding of 250.0 USDC (250.0 USD @ $1.0/USDC) attached to it.

gitcoinbot commented 2 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


Work has been started.

These users each claimed they can complete the work by 264 years, 8 months from now. Please review their action plans below:

1) harrytgerman has started work.

As my initial screening didn't reveal a major security concern for public functions, i would focus my efforts on input validation (on-chain or off-chain) as admin input is complex and has a potential risk. Found some minor efficiency improvements.

Learn more on the Gitcoin Issue Details page.