Enzyme Onyx Bug Bounty Program

Onyx by Enzyme Finance is a tokenization protocol for asset management vehicles. It facilitates bespoke ERC20 shares issuance, including fees and tools for valuation accounting.

Before submitting a report, please review our Bug Bounty program guidelines carefully. Reports that only cover issues already listed in the program scope will be closed and marked as spam.

Smart contracts may have both a currently deployed version and the latest audited version that is scheduled for deployment. These are labeled as follows:

• Live — the smart contract that is currently deployed and in use
• Latest audited — the most recently audited smart contract, not yet deployed but planned for future release

If no labels are present, it means the deployed (live) smart contract is already up to date with the latest audited version.

Program Details

Maximum Bounty: $200,000 Live Since: 04 September 2025 Last Updated: 24 March 2026

Rewards

Enzyme Onyx provides rewards in USDC on Ethereum, denominated in USD.

Rewards by Threat Level

Smart Contract

• Critical: Max: $200,000 | Min: $20,000
• High: Max: $20,000 | Min: $5,000
• Medium: Max: $5,000 | Min: $1,000

Critical Reward Calculation

Mainnet assets: Reward amount is 10% of the funds directly affected up to a maximum of $200,000.

Minimum reward to discourage security researchers from withholding a bug report: $20,000

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

Audits

Eligibility & Requirements

KYC: Not required for payout processing.

Proof of Concept: Proof of concept is always 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. 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:

• Chain Rollbacks
• Pre-Impact Bug Monitoring
• Attack Investment Amount
• Attacks With A Financial Risk To The Attacker
• When Is An Impactful Attack Downgraded To Griefing?

---