Valinity Formal Verification

CertiKFiles named in the report

CertiK reviewed Valinity (Valinity Formal Verification) on 15 Dec 2022: 2 findings, 0 critical; 1 marked fixed, 1 open.

No open critical findings
Open the reportOpen Valinity’s security record

Report hosted on skynet.certik.com.

Trustblock does not review code.

Findings2

Statuses are the security firm’s own, from its report.

SeverityOpenAcknowledgedFixed
Critical000
High001
Medium000
Low100
LowDelay between offer creation and executionOpen

The floor price is supposed to increase or stay the same after the `tradeOffer()` function call. However, some time can elapse between the creation of an offer and the invocation of `tradeOffer`, which allowes for a scenario where the execution of `tradeOffer()` would bring down the floor price. Let's assume that `createOffer()` was called when the floor price was `x` with `price = 2*x`. Then the floor price increased and went above `2*x`. At this point, when the floor price is greater than `2*x`, if the function `tradeOffer()` is called, it would bring down the value of the floor price. Therefore, it is not possible to formally verify that the floor price is nondecreasing, except by making an assumption that the price at the time of the trade is still above the floor.

Contracts in scope

No deployed address is recorded for this audit.

The report names a repository or files. Open the report to see its scope.

Repository and files the report names (5)

  • contracts/token/MFCToken.sol
  • contracts/exchange/MFCExchangeCap.sol
  • contracts/exchange/MFCExchange.sol
  • contracts/exchange/ExchangeCheck.sol
  • contracts/exchange/MFCExchangeFloor.sol

Part of Valinity’s security record

Valinity
Audits4 audits by 1 firmLast audit Oct 2023, by CertiK.
Critical findingsNo open critical findingsAcross 4 reports.
Open Valinity’s security record

Security firm

CertiK

1,044 projects reviewed · 1,375 reports · latest May 2025

See CertiK’s audits

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