Skip to content
Back to blog

Uniocean: Smart Contract Audits, V1 and V2

4 min read
Uniocean: Smart Contract Audits, V1 and V2

Uniocean is a decentralized price forecast platform. Users stake USDC or USDT on a predicted asset price, events settle against an oracle price, and rewards are distributed on-chain. The protocol runs on Polygon PoS and is written for any EVM-compatible network.

FailSafe has audited Uniocean twice: the original V1 contracts before launch, and the V2 upgrade in September 2026.

September 2026: V2 Upgrade Audit

V2 is a storage-compatible upgrade of the live V1 contract. It adds per-event participation limits, per-event pausing, batched reward payouts, and a validator quorum for settlement. Uniocean maintains two variants of V2, one sourcing settlement prices from Pyth Network and one from Uniocean's own oracle adapter, so FailSafe delivered a report for each.

The review combined manual code review with checks against live on-chain state, so each finding states whether it is reachable on the current deployment. Both variants share the same six findings: one Critical, two High, and three Low.

Findings and status

  • Critical, Acknowledged. Events created under V1 would read zero in the four fields V2 adds, changing how predictions, cancellations, and platform fees behave for those events after the upgrade. No V1 events exist on the production contract, and the upgrade procedure now checks this before it proceeds.
  • High, Resolved. One recipient whose transfer failed, for example a frozen stablecoin address, could halt an entire batch of reward payouts. Payouts are now isolated per recipient, failures are recorded on-chain, and affected users stay eligible to be paid later.
  • High, Acknowledged. The operator can cancel an event at any point before the final price is recorded. Uniocean keeps this as an emergency control. Events above the participation threshold cannot be cancelled, and cancelled events refund every stake.
  • Low, Resolved. Stake transfers now confirm the amount actually received, so a token that charged a transfer fee would be rejected rather than leave the reward pool short.
  • Low, Acknowledged. Enabling the settlement authorizer was a separate step from the upgrade. The upgrade script now enables and verifies it before the contract resumes service.
  • Low, Acknowledged. Reward finalization requires one authorizer signature, while settlement requires an authorizer plus a validator quorum. Uniocean treats finalization as a separate operation by design.

The Uniocean oracle variant's report covers the same contract logic. Its oracle adapter was introduced after the audited commit and was outside the scope of this review.

Download the V2 Audit Report, Pyth Oracle (PDF)

Download the V2 Audit Report, Uniocean Oracle (PDF)

April 2026: V1 Launch Audit

The first engagement covered the core smart contracts and the oracle integration ahead of launch, in two reports.

Core Platform Security

The review found 8 issues (1 Medium, 5 Low, 2 Informational), centred on signature validation, upgradeability gaps, and gas exhaustion during batch refund claims. The Uniocean team resolved all eight before deployment.

Download the Core Platform Audit Report (PDF)

Oracle Integration

The review of the UnioceanValuePrediction price oracle integration found one Low-severity issue: the NatSpec documentation contradicted the code's requirements for recording final asset prices. It was corrected so oracle operators would not hit unexpected transaction failures.

Download the Oracle Integration Audit Report (PDF)

Outcome

Uniocean fixed every V1 finding before launch. For V2, two findings were fixed in code and four were accepted, with the Critical and the authorizer finding covered by checks in the upgrade procedure rather than in the contract itself. Each report records the developer's response and FailSafe's assessment for every finding.

Audit Your Protocol with FailSafe

FailSafe audits smart contracts and runs continuous, exploit-validated testing across the applications and infrastructure around them.

Talk to the Security Team

Need an assessment for your environment?

Talk with FailSafe about the application, evidence and testing scope your team needs.