CertiK LogoCertiK Logo
XRUN logo
XRUN
AI
Metaverse
Gaming
Max Payout
$1,000
Project Overview

XRUN Security Bounty awards are granted solely at our exclusive discretion. Any awards not accepted within one year, or waived, shall become ineligible for issuance. At our sole discretion, we may donate the value of such waived or other ineligible awards consistent with our charitable giving programs and policies. XRUN reserves the right to immediately remove you from the XRUN Security Bounty program if you violate any of these terms and conditions as determined by XRUN, or if you violate any terms associated with the use of your XRUN ID. This includes sending any harassing, threatening, or unlawful messages to XRUN. Any such messages may be reported to relevant law enforcement entities. The XRUN Security Bounty program extends to security research covering all XRUN products and public-facing services, except research involving any of the following: XRUN Pay Any non-public-facing XRUN system Phishing, social engineering, or similar techniques The XRUN Security Bounty program does not extend to third-party services. You must not disrupt, compromise, inappropriately access, store, or damage: Data or property (including a device) that you do not own, unless the data or property owner has given you express, written consent to disrupt, compromise, or damage the data or property; or XRUN services in a manner that can adversely affect other users. Adverse effects solely impacting you are allowed. For a reported security vulnerability affecting any XRUN platform to be eligible for an XRUN Security Bounty award, you must not disclose it to anyone other than XRUN until after XRUN has released a software update and published a security advisory for the reported security vulnerability. A participant in the XRUN Security Bounty program will not be deemed to be in breach of applicable XRUN license provisions which provide that a user of XRUN software may not copy, decompile, reverse engineer, disassemble, attempt to derive the source code of, decrypt, modify, or create derivative works of such XRUN software, for in-scope actions performed by that participant where all of the following are met: The actions were performed strictly during participation in the XRUN Security Bounty program; The actions were performed during good-faith security research, which was — or was intended to be — responsibly reported to XRUN; and Neither the actions nor the participant have otherwise violated or exceeded the scope of these terms and conditions. You must comply with all applicable laws (including directives, regulations, and ordinances), including those of the country or region in which you reside or in which you download or use XRUN software or services. XRUN Security Bounty awards may not be paid to you if you are in any U.S. embargoed countries or on the U.S. Treasury Department’s list of Specially Designated Nationals, the U.S. Department of Commerce Denied Person’s List or Entity List, or any other restricted party lists. You are responsible for the payment of all applicable taxes.

Rewards by Severity
Smart Contract
The bounty will be paid out in USDT
Assets In-Scope
Target
Severity
Name
Smart Contract
XRUN polygon contract
In-Scope Vulnerabilities
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered in-scope, even if they affect something in the assets in scope table.
Smart Contract
Critical
Direct theft of project funds
other than unclaimed rewards.
Direct theft of user funds
other than unclaimed rewards.
Permanent freezing of funds.
Major
Theft or permanent freezing of unclaimed yield and rewards.
Medium
Unexpected logic executions (doesn’t lose value)
Smart contract unable to operate due to lack of funds or misconfiguration.
Low
Important gas optimizations
Smart contract functionality significantly differs from how it is described in its official documentation.
Smart contract fails to deliver promised returns - but doesn’t lose value
Missing events for functions that change critical parameters
Out-Of-Scope Vulnerabilities
The following vulnerabilities are excluded from the rewards for this bug bounty program:
  • Vulnerabilities that have already been exploited
  • Centralization-related vulnerabilities related to: private keys, privileged addresses, governance, credentials, etc.
Smart Contract
Incorrect data supplied by third party oracles (Not to exclude oracle manipulation/flash loan attacks)
Issues with no security or financial impact.
Program Rules
  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue - the issue will not be eligible for a reward.
  • Submit one vulnerability per report - unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur we only award the first report that was received (provided that it can be fully reproduced).
  • Make a good faith effort to avoid privacy violations - destruction of data - and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
The following activities are prohibited by this bug bounty program:
  • Automated testing of services that generate significant amounts of traffic.
FAQs
How do I search for active bounties?
A: Active bounties can be viewed here [CertiK URL], and by filtering for bounties on the Security Leaderboard. Projects will post bounties along with the assets in the scope of the bounties with a corresponding bounty reward.
How do I submit a bounty?
To submit a bug report, first register an account with us https://www.certik.com/auth/signup. Once your account is created, you can log in and select “Submit Bug” for the specific bounties you're interested in. You will be prompted to fill out a webform; follow the instructions and upon successful submission, you will receive an email confirmation with a reference ID.
Who do I contact if I'm having trouble with my bug report submission?
You can reach out to bugbounty@certik.com for updates and assistance with your bug bounty submission.
I submitted my bug report. What now?
Once your bug report is submitted, CertiK will evaluate the report and contact the respective project. Depending on the criteria stated within a bug bounty, a KYC may be required. With valid bug reports, you will be contacted to begin the process of evaluating the bug with the project.
How is KYC handled?
CertiK has a team of investigative professionals that will handle any needed KYC services for bug bounty submissions requiring KYC.
Why was my bug report submission rejected?
A description of dismissal will be available for any bug bounty that is rejected.
The project is being slow responding to my bug report. What are their required response times / SLAs?
There can be multiple bug bounty submissions therefore there might be some delay in process times.
How do payouts work?
Payments for successful bug bounties will be communicated directly via the project wherein wallet information can be exchanged.
Bounty Highlights
Assets in Scope1
Live SinceNov 1, 2024
Last Updated1y 1d ago
Funds Reserved$4,000
Max Payout$1,000
Skynet Score
82.13
A
KYC
Required
PoC
Required