As of 3 Nov 2026, UnchainX has 3 audit reports by 2 security firms on Trustblock; the latest is by CertiK, dated 9 Sep 2024. Those reports list no open critical findings. It also holds 1 deployed contract on 1 chain.
Record last updated . It holds audits, findings and contracts up to Nov 2026, and incidents up to Oct 2026. Trustblock does not review code.
Newest first
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| Unchain X Circular Ecosystem | Security firm: CertiK | Date: | Scope: Files named in the report | 2 critical findings, fixed | Open · skynet.certik.com |
| Unchain-X | Security firm: CertiK | Date: | Scope: 1 address on BNB Chain | No open critical findings | Open · skynet.certik.com |
| Unchain-X: LaunchpadStaking audit | Security firm: PeckShield | Date: | Scope: Not recorded (see the report) | No open critical findings | Open · GitHub |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 2 |
| High | 2 | 1 | 5 |
| Medium | 1 | 0 | 4 |
| Low | 1 | 0 | 26 |
### TimeLockController In the contract `TimeLockController`, the role `owner` and `executor` have authority over the functions shown in the diagram below. Any compromise to the `owner` or `executor` account may allow the hacker to take advantage of this authority and enqueue any transaction, execute any transaction already in the queue, or cancel operations.  --- In addition, the `owner` and `executor` have authority over the function `setExecutor()`. Any compromise to the `owner` or `executor` account may allow the hacker to take advantage of this authority and set the `executor` to a contract or address they have the sole control over. --- In addition, the `owner` has authority over the function `setOwner()`. Any compromise to the `owner` account may allow the hacker to take advantage of this authority and set the `owner` to a contract or address they have the sole control over. --- ### XRecycling In the contract `XRecycling`, the role `owner` has authority over the functions shown in the diagram below. Any compromise to the `owner` account may allow the hacker to take advantage of this authority and preallocate voting power.  --- In the contract `XRecycling`, the role `ownerorexecutor` has authority over the functions shown in the diagram below. Any compromise to the `ownerorexecutor` account may allow the hacker to take advantage of this authority and initialize the contract and set its allocation as well as initialize the minting configuration.  --- In addition, the contract `XRecycling` depends on being given the correct authority in the `halvingProtocol` and the `halvingProtocol` containing enough funds for the accumulated rewards. --- ### RelayERC20 In the contract `RelayERC20`, the role `minter` has authority over the functions `mint()`. Any compromise to the `minter` address may allow the hacker to take advantage of this authority and mint an arbitrary amount of tokens to any address they control.
Open the report| Address | Chain | Source code |
|---|---|---|
| 0x4f05…ea6f0x4f0572ca0bf96f5ae17b7062d97cea3f35bdea6f | Chain: BNB Chain | 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="unchain-x"></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