
Daimo Pay
Bounty Range
$1,000 - $20,000
external program
Daimo Pay is a intent-based system for crypto payments. In particular, it supports fast 1:1 transfers from any major stablecoin across chains.
Supported Networks:
Maximum Bounty: $20,000
Live Since: 06 June 2025
Daimo Pay provides rewards in USDC on Arbitrum, denominated in USD.
Smart Contract
Critical
High
Low
For critical smart contract bugs, the reward amount is 10% of the funds directly affected up to the listed maximum. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. There is also a listed minimum reward in order to incentivize security researchers against withholding a critical bug report.
High impacts concerning theft/permanent freezing of funds are rewarded within the listed range. The reward is calculated based on 100% of the funds at risk, capped at the maximum high reward.
The assets in scope for this bounty are specifically our Daimo smart contracts.
Not in scope:
Special case:
Daimo Pay is a intent-based system for crypto payments. In particular, it supports fast 1:1 transfers from any major stablecoin across chains.
The purpose of this bug bounty is to build confidence in the Daimo Pay intent address contract system.
We will treat all contract issues that result in loss of user funds as critical.
Temporarily frozen funds count as vulnerabilities only if they occur:
There are a variety of (known, expected) ways that funds can be frozen temporarily due to user error (for example, double-paying the same intent address twice). These are not vulnerabilities.
| Auditor | Link | Completed at |
|---|---|---|
| Nethermind | https://github.com/user-attachments/files/20544714/NM-0500-Daimo-Pay-final-report.pdf | 25 April 2025 |
The submission of KYC information is a requirement for payout processing. Participants must adhere to the Eligibility Criteria.
Proof of concept is always required for all severities.
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. Therefore, Immunefi has developed feasibility limitation standards which by default state what security researchers and projects can or cannot cite when reviewing a bug report.