
USX
Bounty Range
$3,000 - $100,000
external program
USX is a fully collateralized neodollar developed by Scroll, designed to merge the best of traditional finance (TradFi) and decentralized finance (DeFi) to deliver stable, sustainable rewards. Unlike conventional stablecoins, USX introduces a new paradigm — it is private, gasless, and spendable in real life. This is made possible through Cloak, Scroll's privacy layer, along with chain-level customizations and integrated payment partners.
For more information about USX, please visit https://www.usx.capital/
USX provides rewards in USDC on Ethereum, denominated in USD.
Smart Contract
Websites and Applications
Mainnet assets: Reward amount is 10% of the funds directly affected up to a maximum of $100,000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of $50,000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report.
Web/Apps: Critical web/apps bugs are rewarded a flat amount of $5,000.
If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attack will be considered for a reward.
The amount of funds at risk will be calculated with the impact of the first attack being at 100% and then a reduction of 25% from the amount of the first attack for every 1800 blocks the attack needs for subsequent attacks from the first attack, rounded down.
High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of $5,000 to $10,000 with the reward calculated based on 100% of the funds at risk, though capped at the maximum high reward.
In the event of temporary freezing, the reward doubles from the full frozen value for every additional 24h that the funds are temporarily frozen, up until a max cap of the high reward.
Payouts are handled by the USX team directly and are denominated in USD. However, payments are done in USDC on Ethereum.
The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability.
USX will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:
USX adheres to the Primacy of Impact for the following impacts:
Primacy of Impact means that the impact is prioritized rather than a specific asset. This encourages security researchers to report on all bugs with an in-scope impact, even if the affected assets are not in scope.
When submitting a report on Immunefi's dashboard, the security researcher should select the Primacy of Impact asset placeholder. If the team behind this project has multiple programs, those other programs are not covered under Primacy of Impact for this program. Instead, check if those other projects have a bug bounty program on Immunefi.
If the project has any testnet and/or mock files, those will not be covered under Primacy of Impact.
All other impacts are considered under the Primacy of Rules, which means that they are bound by the terms and conditions set within this program.
Proof of concept is always required for all severities.
Category 2: Notice Required
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. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity.
Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report, including Chain Rollbacks, Pre-Impact Bug Monitoring, Attack Investment Amount, Attacks With A Financial Risk To The Attacker, and When Is An Impactful Attack Downgraded To Griefing.