dTRINITY audit competition- rewards up to $80,000 in $USDC

Starting June 16th, 2025, at 15:00 GMT to July 4th, 2025, at 15:00 GMT

We invite all white hat hackers to join the hunt on dTRINITY 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 June 16th 2025, a new vault will open in the Hats dApp — dTRINITY protocol audit competition. Participants can check the scope of the contracts and start searching for bugs.

Introducing the world’s first subsidized stablecoin protocol, designed to transform credit markets!

dTRINITY (short for “DeFi Trinity”) is a decentralized protocol featuring dUSD, the first stablecoin that pays you to borrow.

• Fully backed by a non-custodial reserve of stablecoins and yield-bearing stablecoins. Mint/redeem permissionlessly, 1:1.
• Reserve earnings are redirected to d USD borrowers on dLEND and other integrated lending protocols as interest rebates.
• Superior lending and borrowing rates compared to unsubsidized stablecoins like USDC and USDT.

Into the competition:

The competition code language is Solidity, with approximately ~4100 nSLOC.

In this competition, the submission will be on Arbitrum chain, meaning you will need a ETH to submit reports.

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 — join now and be the first to know!

Audit competition rewards

• Deposited Amount: The deposited amount is $100,000 USDC, making the available prize pool $80,000in $USDC.
• Hats gov 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 (equals 0.5 point)
• Medium Severity: $5000 (equals 10 points)
• High Severity: $50,000 (equals 100 points)

*For simplicity, there is a relation between the points and the cap. If the point cap is $500 USDC, it equals 0.63% of the maximum rewards allocation.

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 0.5 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:

• 200 Low Severity: 100 points
• 3 Medium Severity: 30 points
• 1 High Severity: 100 points

Total points: 230

In this scenario:

• Value of 1 Point = $80,000/230 = ~$348
  The rewards for this example will be as follows:
• 200 Low (100 points): ~$174 per 1 Low.
• 3 Medium (30 points): ~$3480 per 1 Medium.
• 1 High (100 points): ~$34,800 per 1 High.

Example #2

• 10 Low Severity: 5 points
• 1 Medium: 10 points

Total points: 15

In this scenario:

• Value of 1 Point = $80,000/15 Total points = ~$5,333
• The results exceed the max reward per low severity, so the value of a point is adjusted to the max cap.
• The rewards for this example will be as follows:
• 10 Low (5 points): ~$250 each low
• 1 Medium (10 points): $5000

Severities

High Severity

Issues that will qualify for this bracket will be assigned 100 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

Medium Severity

Issues that will qualify for this bracket will be assigned 10 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 0.5 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 “dTRINITY 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.
• This is a Complete Audit Cycle at Hats Finance encourages a more robust security process — from finding vulnerabilities to fixing and testing them. This approach:
• Increases the quality and readiness of sponsor code.
• Rewards researchers with additional points and higher standing.
• Promotes a decentralized development spirit where security meets practical implementation.

Please review how you can leverage the Complete Audit Cycle in their Hats Finance audit competitions.

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
• Please check the box “PoC is not applicable” if you can’t add PoC.
• 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) demonstrating the vulnerability.
• Revised Code File (Optional): 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 the guidelines gets a bounty for that issue (issues already received or out of scope will not receive a reward).
• The competition starts on June 16th at 15:00 GMT and ends on July 7th 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 $80,000 USDC 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 a dispute to the committee team within three days 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 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 the dTRINITY 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