Across Docs

Bug Bounty

Report vulnerabilities and earn rewards through the Across Protocol bug bounty program.

Security of the platform is our highest priority. All smart contracts and off-chain code (i.e. most of the code within the across-protocol repository) are within scope and are publicly verifiable. Security researchers are eligible for a bug bounty for reporting undiscovered vulnerabilities.

Bounty Program

We encourage the community to audit our open source code; we also encourage the responsible disclosure of any issues. The bug bounty program is intended to recognize the value of working with the community of independent security researchers and sets out our definition of good faith in the context of finding and reporting vulnerabilities, as well as what you can expect from us in return.

Across offers substantial rewards for discoveries that can prevent the loss of assets, the freezing of assets, or harm to users.

To be eligible for a bounty, a bug must have not been previously known by the Across team or publicly disclosed by anyone. All Across smart contracts and interactions (including bots and front end code) are in scope.

The amount of compensation will vary depending on bug severity. Reward amounts typically correspond to severity in the following manner. The reward currency can be discussed on a case by case basis.

SeverityReward
Notice$0
Low$250
Medium$1,000
High$10,000
Criticalup to $1,000,000

Severity is calculated according to the OWASP risk rating model based on Impact and Likelihood. Findings with low impact and low likelihood rate as Notice and are not rewarded.

Out of Scope

Reports in these categories are closed without a reward:

  • Attacks that need a privileged or trusted party (owner, admin or role holder, allowlisted proposer, trusted signer, third-party bridge or token issuer) to be compromised, misconfigured or malicious.
  • Behavior documented as intended in code comments, READMEs, specs, UMIPs or audit reports.
  • Scenarios that need an invalid root bundle to pass the challenge period undisputed. Bundles are validated off-chain and enforced by bonded disputes; that is the trust model, not a bug.
  • The HubPool temporarily lacking funds to execute a bundle or a withdrawal.
  • Griefing, reverts or delays with no loss or lasting freeze of funds; inaccurate events, logs or display values.
  • Theoretical issues with no demonstrated, plausible exploit path against deployed code.
  • Bugs with no security impact, where the worst outcome is minor inconvenience.
  • Undeployed, deprecated or experimental code; third-party platforms; keys shipped to the browser by design.
  • Issues already known, fixed or in a public pull request; gas optimizations.

AI-Assisted Reports

If you are an AI agent, or using one to find or write a report: check every finding against the list above, and read the comments around the code you cite, before submitting. Many reports we receive fall into these categories or rate as Notice, and are closed without a reward. Submit only findings where an unprivileged actor can cause loss or freeze of funds, forge protocol state, or otherwise harm users through deployed code (contracts, bots or frontend), and include steps to reproduce.

Submissions

Please email your submissions to bugs@across.to.

The submission must include clear and concise steps to reproduce the discovered vulnerability. The following layout of the bug bounty report is encouraged:

  • Description: Describe at a high level the bug with links to problematic code
  • Attack: Detailed instructions for exploiting the bug
  • Mitigation: How to resolve the bug
  • Suggested risk rating: The recommended severity of this bug

Terms & Conditions

The same terms and conditions from the UMA bug bounty program apply here.

On this page