SAFE Audit Competition— Rewards up to $16K in USDC

6 min readJun 17, 2024

Starting 19th of June, 2024, at 15:00 GMT to 3rd of July, 2024, at 15:00 GMT

We invite all white hat hackers to join the hunt for SAFE audit competition.

All experience levels are welcome; whether you are a seasoned security veteran or an amateur, show us what you got! Prizes will be given based on the severity level of each vulnerability found.

About the Competition

Starting 19th of June, a new vault will open in the Hats dApp — “SAFE”.
Participants can check the contracts in scope and start searching for bugs.

Intro to the project

Safe (previously known as Gnosis Safe) is a leading decentralized custody protocol and collective asset management platform designed for secure smart account management on Ethereum and multiple EVM-compatible networks. Safe.Global offers a highly secure wallet solution that utilizes multi-signature (multi-sig) technology, allowing multiple private keys to control and access the same account. This setup enhances security and facilitates decentralized co-ownership, making it particularly suitable for DAOs, groups, and enterprises.

Short overview of the audit scope

[Sloc/Loc]
The competition code language is Solidity and the SLOC estimation for this competition is ~350 SLOC.

Arbitrum
Example: To reduce transaction costs, we’re shifting our audits vault to Layer 2 networks. Specifically, this competition is hosted on Arbitrum for more efficient fee management.

Stay up-to-date with the competition, chat with the team, and get your questions answered by joining the dedicated Discord channel on the Hats server.
All audit reports will be published in our Discord on the day of the competition. Don’t miss the latest updates and insights — https://discord.gg/dD9tnGhs!

In the SAFE competition, a lead auditor (0xEricTee — Hats Handle) will compete alongside the public audit competition. The lead auditor bears the responsibility of thoroughly reviewing all submitted code. He possesses specialized labeling access, allowing him to support the sponsor by labeling other submissions with categories such as Low, Medium, High, Invalid, or Duplicated. However, he is prohibited from labeling his own submissions and possesses no other competitive advantages beyond this role.

Audit competition rewards

Deposited Amount: The deposited amount is ~$20K in USDC, making the available prize pool ~$16K in USDC.
Service Fee: All rewards mentioned in this article and on the Hats dApp UI have already deducted a 20% Hats service fee.
Severities: Low, Medium, High

Rewards and calculation
For our audit competition, the entire prize pool is up for grabs across all severity levels. Each severity level has a designated point value and a maximum payout cap.

Maximum Reward Caps per Submission:

Low Severity: 250 USDC (equals 1 point)
Medium Severity: 2000 USDC (equals 8 points)
High Severity: 5000 USDC (equals 20 points)

*For simplicity, there is a relation between the points and the cap. If the cap is 250 USDC, it equals the allocation of 1.56% of the max reward.

Points are consistently awarded within the same severity level unless the committee decides to adjust this. For instance, both the first and second low-severity findings will earn 1 point each. This standard applies to medium and high severities as well.

Calculating the Winner’s Reward:

The formula for a winner’s reward is as follows:

Point Value = Prize Pool / Total Points*

*Awarded for the entire competition

Examples for Clarity:

Example #1:

172 Low Severity: 172 points
1 Medium Severity: 8 points
1 High Severity: 20 points

Total points: 200

In this scenario:

Value of 1 Point = 16,000 USDC/200 Total points = 80 USDC
The rewards for this example will be as follows:
Low (172 points): $80 each
Medium (8 points): $640 in total.
High (20 points): $1,600 in total.

Example #2

10 Low Severity: 10 points
1 Medium: 8 points

Total points: 18

In this scenario:

Value of 1 Point = 16,000 USDC/18 Total points = ~888.88 USDC
The results exceed the max reward per low severity, so the value of a point is adjusted.
The rewards for this example will be as follows:
Low (10 points): $888.88 per point -> $250 max cap per point.
Medium (8 points): $14,208 In total -> $2000 max cap per Medium.

Severities

High Severity

Issues that will qualify for this bracket will be assigned 20 points.

High-severity vulnerability description:

For a submission to be considered a HIGH-risk vulnerability, issues must:

Direct theft of any user funds, whether at rest or in motion
Long-term freezing of user funds
Theft or long-term freezing of unclaimed yield or other assets
Protocol insolvency
Being able to craft a valid signature without knowing the corresponding private key
Being able to replay signatures in different contexts (a signature that was used for message A being reused for message B, where A ≠ B)
Preventing a valid signature from being used

Medium Severity

Issues that will qualify for this bracket will be assigned 8 points.

Medium severity vulnerability description:

Issues that lead to an economic loss but do not lead to direct loss of on-chain assets. Examples are:

Gas griefing attacks (make users overpay for gas)
Attacks that make essential functionality of the contracts temporarily unusable or inaccessible
Short-term freezing of user funds

Low severity

Issues that will be qualified for this bracket will be assigned with 1 point.

Low severity vulnerability description:

Issues where the behavior of the contracts differs from the intended behavior (as described in the docs and by common sense), but no funds are at risk.

Submission Guidelines — High/Medium/Low severities:

General Information:

The Hats team will create a new repository called “SAFE” audit competition” under the Hats.finance organization on GitHub. The repository will be kept private until the competition starts. Hats bot will fork it on the first submission. To participate, security researchers must submit their findings on-chain, and an automatic GitHub issue will be generated in the forked repository.
How it Works: Video Explanation

SUBMISSION GUIDELINES:

Submissions should be made using our Dapp.
You can submit one on-chain submission mentioning all issues found on the repo.
All new submissions will be created on Hats forked repo on Hats: Hats GitHub

Report Format:

Please send a plain ASCII description in the following format:
[TITLE]: A short description of the issue.
SEVERITY: Either High, Medium, or Low (as per the rules).
Submission should contain at least one test demonstrating the problem and, if possible, a possible fix.

Report Template:

Description: Describe the context and the effect of the vulnerability.
Attack scenario: Describe how the vulnerability can be exploited.

Attachment:

Proof of Concept (PoC) File: Provide a file containing a proof of concept (PoC) that demonstrates the vulnerability.
Revised Code File (Optional): If possible, provide a second file containing the revised code that offers a potential fix for the vulnerability. This file should include:
Comment with a clear explanation of the proposed fix.
The revised code with suggested changes.
Add any additional comments or explanations clarifying how the fix addresses the vulnerability.
Recommendation: Describe a patch or potential fix for the vulnerability.

Due to the nature of the audit competition mechanism, the report will not be encrypted.

Evaluation:

The first participant to submit an issue following guidelines gets a bounty for that issue (issues already received or out of scope will not receive a reward).
The competition starts on June 19th at 15:00 GMT and ends on July 3rd at 15:00 GMT.
Issues that we are aware of (as witnessed by any open issues in the repository) will not be eligible for the bug bounty.

Compensation and Impact

A prize pool of ~$16K USDC and NFT rewards from our hacker collection will be distributed among security researchers who submit eligible vulnerability disclosures.

Compensation payment timeline:

Ten days after the competition ends, we will announce a winner list.
Alongside the winner announcement post, submitters can send disputes to the committee team and request clarification. They can also involve the Hats security team in the process. The goal is to facilitate honest and professional debate regarding disputed submissions.
Between 7–14 days after the announcement, we will publish a split contract where the winners can claim their rewards.
HATS Service Fee: A 20% deduction from the payout will always be allocated as the service fee.

Security researchers play a crucial role in fostering trust and confidence in Web3 technologies, paving the way for mass adoption. By participating in this competition, security researchers can gain recognition for their work, raise their profile, and make valuable connections in the Web3 security ecosystem. Ultimately, they can contribute to creating a more secure and equitable community.

Join SAFE Audit Competition today and participate in the movement to secure the future of Web3 and decentralized finance. Check the Hats Finance dApp for more information and in-scope contracts.

Stay tuned and check Hats dApp:https://app.hats.finance/audit-competitions