Sequence

QuantstampFiles named in the report

Quantstamp reviewed Sequence on 12 Jan 2024: 14 findings, 0 critical; 10 marked fixed, 4 acknowledged; 1 more marked mitigated.

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

Report hosted on certificate.quantstamp.com.

Trustblock does not review code.

Findings23

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

SeverityOpenAcknowledgedFixedMitigated
Critical0000
High0000
Medium0020
Low0481

Marked Informational or Undetermined by the firm. Not counted as findings.

InformationalMissing Events to Signal State ChangesAcknowledged

Events are important for signalling state changes in a contract. This helps debug the contract in the event of any attacks or critical bugs and helps indicate to users any configuration changes in the contract. A non-exhaustive list of functions where events can be useful includes: 1. `ERC20Items.setNameAndSymbol()` 1. `ERC721BaseToken.setNameAndSymbol()` 1. `ERC721BaseToken.setBaseMetadataURI()` 1. `ERC721BaseToken.setContractURI()` 1. `ERC1155BaseToken. setBaseMetadataURI()` 1. `ERC1155BaseToken.setContractName()` 1. `ERC1155BaseToken.setContractURI()`

InformationalUnlocked PragmaAcknowledged

Every Solidity file specifies in the header a version number of the format `pragma solidity (^)0.8.*`. The caret (`^`) before the version number implies an unlocked pragma, meaning that the compiler will use the specified version and above, hence the term "unlocked". The pragma versions used throughout the codebase should not be unlocked and set to the same version to ensure that they are all compiled by the same compiler version.

UndeterminedUser Can Create Several Offers Without Giving AllowanceAcknowledged

When a user creates an offer, `_createOrder()` verifies that enough allowance was provided to cover the new order. However, he can create more offers as long as their total amount is equal or less than the allowance of the contract. `isOrderValid()` can be affected as well, as it verifies each order independently.

Informational'Dead' CodeFixed

"Dead" code refers to code which is never executed and hence makes no impact on the final result of running a program. Dead code raises a concern, since either the code is unnecessary or the necessary code's results were ignored. 1. `ERC1155Sale._ERC20_TRANSFERFROM_SELECTOR` is never used in `ERC1155Sale`. 2. `ERC721Sale._ERC20_TRANSFERFROM_SELECTOR` is never used in `ERC721Sale`.

InformationalDeprecated FunctionsFixed

Several initializers in the codebase call `_setupRole()` to assign privileged roles to certain addresses, instead of using `_grantRole()`. Both functions have the same effect, as `_setupRole()` just calls `_grantRole()`. `_setupRole()` will be deprecated in `v5.0.0` of OpenZeppelin contracts, and its use is not recommended in the current version used by the codebase (`v4.9.3`). See `_setupRole()` comment: ``` NOTE: This function is deprecated in favor of {_grantRole}. ```

InformationalGas Optimization: Cache VariablesFixed

Repeatedly accessing certain variables can be gas-intensive. To optimize gas usage, values frequently accessed should be stored in memory variables. Consider storing the value in a memory variable and reference the memory variable for the following variables: 1. `requests.length` from `Orderbook.createOrderBatch()` 2. `ordersIds.length` from `Orderbook.acceptOrderBatch()` 3. `ordersIds.length` from `Orderbook.getOrderBatch()` 4. `ordersIds.length` from `Orderbook.isOrderValidBatch()`

InformationalGas Optimization: Use `calldata` Instead of `memory`Fixed

Solidity's `calldata` is a read-only byte-addressable space where function arguments reside. It is more cost-effective to employ `calldata` over `memory`. This is because `calldata` is not stored in memory but is directly accessed from the function call data, resulting in gas savings. It is recommended to change the `memory` to `calldata` in the mentioned functions: 1. `createOrder()` 2. `createOrderBatch()` 3. `_createOrder()` 4. `acceptOrder()` 5. `_acceptOrder()` 6. `acceptOrderBatch()` 7. `getOrderBatch()` 8. `cancelOrderBatch()` 9. `isOrderValidBatch()`

InformationalOutdated CommentsFixed

In several factory contracts, the following comment can be found: ``` @dev As `proxyOwner` owns the proxy, it will be unable to call the [...] functions. ``` However, the Sequence factories implement a modified Transparent Proxy pattern, where the administrator can also call the implementation, apart from the administration functions.

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 (4)

  • marketplace-contracts /contracts/*
  • wallet-contracts /contracts/TrustFactory.sol
  • wallet-contracts /contracts/Trust.sol
  • contracts-library /src/tokens/*

Part of Sequence’s security record

Sequence
Audits3 audits by 1 firmLast audit Dec 2025, by Quantstamp.
Critical findingsNo open critical findingsAcross 3 reports.
Open Sequence’s security record

Security firm

Quantstamp

240 projects reviewed · 338 reports · latest Nov 2026

See Quantstamp’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