XOXNO Bug Bounty Program

XOXNO is an innovative DeFi protocol deployed on MultiversX, combining a liquid staking contract for $EGLD and a lending protocol. The project started as an NFT marketplace and has leveraged its infrastructure into merging NFTs and DeFi via tokenization of lending accounts.

Rewards

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.

Rewards by Threat Level

Smart Contract - Critical

• Maximum: $50,000
• Minimum: $5,000

Smart Contract - High

• Maximum: $5,000
• Minimum: $3,500

Smart Contract - Medium

• Maximum: $3,500
• Minimum: $2,000

Smart Contract - Low

• Maximum: $1,500
• Minimum: $1,000

Critical Reward Calculation

For critical smart contract bugs on mainnet assets, the reward amount is 10% of the funds directly affected up to a maximum of $50,000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. A minimum reward of $5,000 is awarded to incentivize security researchers against withholding a critical bug report.

For critical smart contract bugs on testnet assets, the reward is paid as a flat amount of $5,000, as there are no actual funds at risk on the testnet.

Repeatable Attack Limitations

• 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 300 blocks the attack needs for subsequent attacks from the first attack, rounded down.

High Level Report Calculation

• High impacts concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of $3,500 to $5,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.

Reward Payment Terms

Payouts are handled by the XOXNO team directly and are denominated in USD. However, payments are made in USDC on ETH.

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.

KYC Requirement

XOXNO will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:

• Full name
• Date of birth
• Proof of address (either a redacted bank statement with address or a recent utility bill)
• Copy of Passport or other Government issued ID

Eligibility Criteria

Security researchers who wish to participate must adhere to the rules of engagement set forth in this program and cannot be:

• On OFAC's SDN list
• Official contributor, both past or present
• Employees and/or individuals closely associated with the project
• Security auditors that directly or indirectly participated in the audit review

Responsible Publication

XOXNO adheres to Category 2 - Notice Required. This policy determines what information researchers are allowed to make public from their submitted bug reports.

Primacy of Impact vs Primacy of Rules

XOXNO adheres to the Primacy of Impact for the following impacts:

• Smart Contract / Critical
• Smart Contract / High
• Smart Contract / Medium
• Smart Contract / Low

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 (PoC) Requirements

A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules. Proof of concept is required for all severities.

Prohibited Activities

• Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
• Any testing with pricing oracles or third-party smart contracts
• Attempting phishing or other social engineering attacks against employees and/or customers
• Any testing with third-party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
• Any denial of service attacks that are executed against project assets
• Automated testing of services that generates significant amounts of traffic
• Public disclosure of an unpatched vulnerability in an embargoed bounty
• Any other actions prohibited by the Immunefi Rules

Feasibility Limitations

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. 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.

Immunefi has developed feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.