Incident,
29 ETH.
Source: De.Fi incident database.
- Audits before it
- 6.
- Audits since
- 3, the latest dated 21 Sep 2025.
As of 21 Oct 2026, Onyx Protocol has 9 audit reports by 2 security firms on Trustblock; the latest is by PeckShield, dated 21 Sep 2025. Those reports list no open critical findings. It also holds 1 deployed contract on 1 chain and 1 incident (latest 31 Oct 2023).
Record last updated . It holds audits and findings, contracts and incidents up to Oct 2026. Trustblock does not review code.
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| Onyx: Onyx DAO Registry audit | Security firm: PeckShield | Date: | Scope: Not recorded (see the report) | No open critical findings | Open · GitHub |
| Onyx audit | Security firm: PeckShield | Date: | Scope: Not recorded (see the report) | No open critical findings | Open · GitHub |
| XCN Token (Base) - Audit | Security firm: CertiK | Date: | Scope: Not recorded (see the report) | No open critical findings | Open · skynet.certik.com |
| Onyx Protocol - Audit | Security firm: CertiK | Date: | Scope: Files named in the report | No open critical findings | Open · skynet.certik.com |
| XCN Swap - Audit | Security firm: CertiK | Date: | Scope: Files named in the report | No open critical findings | Open · skynet.certik.com |
| Chain Staking | Security firm: CertiK | Date: | Scope: Files named in the report | No open critical findings | Open · skynet.certik.com |
| Chain - XCN Token | Security firm: CertiK | Date: | Scope: Files named in the report | No open critical findings | Open · skynet.certik.com |
| Chain Team Treasury Timelock | Security firm: CertiK | Date: | Scope: Files named in the report | No open critical findings | Open · skynet.certik.com |
| Chain Token | Security firm: CertiK | Date: | Scope: 1 address on Ethereum | No open critical findings | Open · skynet.certik.com |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 7 | 2 | 4 |
| Medium | 4 | 0 | 4 |
| Low | 21 | 3 | 17 |
In the contract `OptimismMintableERC20`, the `_bridge` contract has authority over the functions shown in the diagram below. Any compromise to the `_bridge` contract may allow the hacker to take advantage of this authority and mint tokens to arbitrary addresses or burn tokens from arbitrary addresses .  The scope of the audit treats third party entities as black boxes and assumes their functional correctness. However, in the real world, third parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of third parties can possibly create severe impacts.
Open the report20B of the 68B max supply is sent to the contract deployer when deploying the contract. This could be a centralization risk as the deployer can distribute `XCN` tokens without obtaining the consensus of the community.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the reportAttached through a shared contract address. Our incident data ends in Oct 2026.
29 ETH.
Source: De.Fi incident database.
| Address | Chain | Source code |
|---|---|---|
| 0x41c3…3ca90x41c37a4683d6a05adb31c39d71348a8403b13ca9 | Chain: Ethereum | Source code: Verified source |
Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.
Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="onyx-protocol"></div></body>
Paste the code where the label should appear. It uses no API credit and updates by itself.
Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us