Web3 · Smart Contract Audit

Tixbase Security Audits

softstack has completed 3 smart contract audits for Tixbase between July 2022 and February 2023, reporting 8 findings in total (1 low and 7 informational), of which 1 were resolved or mitigated before the final reports. Every report is published in the softstack public audit archive.

Key facts

Client
Tixbase
Audits completed
3
First audited
Latest audit
Chains
Ethereum
Languages
JavaScript, Solidity

About the project

Tixbase developed NFT-TiX, a ticketing marketplace that issued event tickets as NFTs on Ethereum. The platform was designed to let organisers and buyers trade tickets directly, without the intermediary processors and central authority of conventional ticketing services. The nft-tix.com domain now serves a parked page and the marketplace no longer appears to operate.

Findings

Combined across all 3 reviews softstack has completed for Tixbase. Each report is broken out below.

0Critical
0High
0Medium
1Low
7Informational

1 of 8 findings resolved before the final reports.

Reports

Newest first. Every report covers its own scope and commit.

  1. NFT-TiX Event Factory v2 smart contract audit

    · commit d0c0dfb · 5 files

    PDF
    0Critical
    0High
    0Medium
    0Low
    3Informational

    0 of 3 resolved

    ScopeSource repositorygithub.com/nfttix/contracts

    Components reviewed

    5 modules · 5 files
    1. truffle-config.js
    2. hardhat.config.js
    3. Event.sol
    4. Registry.sol
    5. Factory.sol
    All 3 findings
    IDTitleSeverityStatus
    6.2.1Floating Pragma Version Identified

    It is recommended to specify a fixed compiler version to ensure that the bytecode produced does not vary between builds. This is especially important if you rely

    Informationalacknowledged
    6.2.2Storing Data Via baseURI

    In the current implementation the baseURI is not hardcoded or on-chain generated, means the owner/creator is free to choose the way how the metadata file is stored.

    Informationalacknowledged
    6.2.3Missing Natspec Documentation

    Solidity contracts can use a special form of comments to provide rich documentation for function, return variables, and more. This special form is named Ethereum Natural Language Specification Format(NatSpec).

    Informationalacknowledged
  2. NFT TiX Marketplace smart contract audit

    · commit 32b60c4 · 1 file

    PDF
    0Critical
    0High
    0Medium
    1Low
    1Informational

    1 of 2 resolved

    ScopeSource repositorygithub.com/chiru-labs/ERC721A

    Components reviewed

    1 module · 1 file
    1. Marketplace.sol
    All 2 findings
    IDTitleSeverityStatus
    6.2.1Centralization Risk

    One of the features of NFT TiX is the gassless listing of NFTs. That requires the user to sign a message, to list the ticket on the marketplace.

    Lowfixed
    6.2.2Missing Natspec Documentation

    Solidity contracts can use a special form of comments to provide rich documentation for function, return variables, and more. This special form is named Ethereum Natural Language Specification Format(NatSpec).

    Informationalacknowledged
  3. NFT-TiX Event Factory smart contract audit

    · 5 files

    PDF
    0Critical
    0High
    0Medium
    0Low
    3Informational

    0 of 3 resolved

    ScopeSource repositorygithub.com/nfttix/contracts

    Components reviewed

    5 modules · 5 files
    1. truffle-config.js
    2. hardhat.config.js
    3. Event.sol
    4. Registry.sol
    5. Factory.sol
    All 3 findings
    IDTitleSeverityStatus
    6.2.1Floating Pragma Version Identified

    It is recommended to specify a fixed compiler version to ensure that the bytecode produced does not vary between builds. This is especially important if you rely

    Informationalacknowledged
    6.2.2Storing Data Via baseURI

    In the current implementation the baseURI is not hardcoded or on-chain generated, means the owner/creator is free to choose the way how the metadata file is stored.

    Informationalacknowledged
    6.2.3Missing Natspec Documentation

    Solidity contracts can use a special form of comments to provide rich documentation for function, return variables, and more. This special form is named Ethereum Natural Language Specification Format(NatSpec).

    Informationalacknowledged

About this engagement

A smart contract audit reviews on-chain code for flaws an attacker could exploit. Engineers trace how assets move through the contracts, check who can call privileged functions, and test the arithmetic, external calls and upgrade paths. Each finding is rated by severity, and fixes are re-checked before the final report.

How softstack runs smart contract audits

Methodology

Review process

  1. Scoping and threat modelling

    The commit hash is frozen and the attack surface is mapped: asset flows, trust assumptions, privileged roles and the external systems the code depends on.

  2. Automated analysis

    Static analysers sweep the full codebase to surface known weakness patterns, unreachable states and deviations from established conventions.

  3. Manual code review

    Independent engineers read the code line by line, concentrating on business logic, access control, arithmetic and the handling of external calls.

  4. Adversarial testing

    Property-based fuzzing and invariant tests attack the assumptions the protocol relies on, targeting states that ordinary unit tests never reach.

  5. Reporting

    Every finding is documented with a severity rating, its impact, the steps to reproduce it and a concrete remediation the team can act on.

  6. Remediation verification

    Submitted fixes are re-reviewed against the original finding, and the final report records the resolved state of each one.

Standards and references

  • SWC RegistrySmart Contract Weakness Classification
  • CWECommon Weakness Enumeration

FAQ

Tixbase was audited by softstack GmbH, a German Web3 security and software company based in Flensburg and certified to ISO/IEC 27001 by TÜV SÜD. softstack has completed 3 smart contract audits for Tixbase between July 2022 and February 2023. The published reports are linked on this page and in the softstack public audit archive.

3 separate reviews, the first in July 2022 and the most recent in February 2023. Each one covers its own scope and commit, and is listed individually on this page.

8 findings across all 3 reviews: 1 low and 7 informational. 1 of 8 were resolved or mitigated before the final reports.

Each report covers the code as it stood at the commit it names, the most recent in February 2023. Any code changed after that point is outside the reviewed scope.

Related audits

Browse all security audits

Disclaimer

This audit represents a point-in-time security assessment of the reviewed codebase and is intended for informational purposes only. While Softstack applies industry-standard security review methodologies, no audit can guarantee the absence of vulnerabilities, bugs, or other security risks. This report does not constitute financial, legal, regulatory, or investment advice, nor does it endorse the project, its business model, products, or services. Security is an ongoing process, and we strongly recommend conducting a new assessment following any material code changes or at least every 6 months to address newly emerging threats, vulnerabilities, and ecosystem developments.