Daimo Pay-logo

Daimo Pay

|

Daimo Pay is a intent-based system for crypto payments. In particular, it supports fast 1:1 transfers from any major stablecoin across chains.

ETH
Arbitrum
Base
Polygon
Linea
Optimism
Infrastructure
Solidity
Maximum Bounty
$20,000
Live Since
06 June 2025
Last Updated
25 June 2025
  • Triaged by Immunefi

  • PoC Required

  • KYC required

Select the category you'd like to explore

Assets in Scope

Target
Type
Smart Contract - daimoPayAxelarBridgerAddress
Added on
24 June 2025
Target
Type
Smart Contract - daimoPayCctpBridgerAddress
Added on
24 June 2025
Target
Type
Smart Contract - daimoPayCctpV2BridgerAddress
Added on
24 June 2025
Target
Type
Smart Contract - daimoPayBridgerAddress
Added on
24 June 2025
Target
Type
Smart Contract - daimoPayRelayerAddress
Added on
24 June 2025
Target
Type
Smart Contract - payIntentAddress
Added on
6 June 2025
Target
Type
Smart Contract - DaimoPay entry point
Added on
6 June 2025
Target
Type
Smart Contract - daimoPayExecutorAddress
Added on
6 June 2025
Target
Type
Smart Contract - payIntentFactoryAddress
Added on
6 June 2025

Impacts in Scope

Severity
Critical
Title

Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results

Severity
Critical
Title

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Severity
Critical
Title

Permanent freezing of funds

Severity
High
Title

Temporary freezing of funds

Severity
Low
Title

Contract fails to deliver promised returns, but doesn't lose value

Out of scope

Default Out of Scope and rules

Smart Contract specific

  • Incorrect data supplied by third party oracles
    • Not to exclude oracle manipulation/flash loan attacks
  • Impacts requiring basic economic and governance attacks (e.g. 51% attack)
  • Lack of liquidity impacts
  • Impacts from Sybil attacks
  • Impacts involving centralization risks

All categories

  • Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
  • Impacts caused by attacks requiring access to leaked keys/credentials
  • Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
  • Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
  • Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
  • Best practice recommendations
  • Feature requests
  • Impacts on test files and configuration files unless stated otherwise in the bug bounty program
  • Impacts requiring phishing or other social engineering attacks against project's employees and/or customers