TourismX contract 0x882e…8c96 on BNB Chain

0x882e295c4b851df7a347679dab8c2489e9e58c96

As of 21 Nov 2026, Trustblock’s record holds 0x882e295c4b851df7a347679dab8c2489e9e58c96 on BNB Chain as a contract of TourismX. 1 audit report on Trustblock lists this address: CertiK, 12 Oct 2022. 8 findings in it are recorded as open or acknowledged.

Audit reports that list this address1

Each report’s scope as stored on Trustblock names this address on BNB Chain.

AuditSecurity firmDateCommit named in the reportReport
TourismX (TRMX ) - AuditCertiKNot recorded (see the report)Open

Open and acknowledged findings in these reports8

2 High, 6 Low. In the firm’s own words; statuses are the firm’s, from each report.

HighCentralization Risks in TokenVesting.solTourismX (TRMX ) - Audit · CertiKOpen

Several contracts throughout the project, implement and rely on privileged roles to modify configuration variables. Having this role and functionality allows the project to implement dynamic adjustments to the protocol that can be beneficial to both the deployer and users. However, it also introduces a single point of failure that can compromise the whole protocol. In the `TokenVesting` contract, the role `_owner` has authority over the following functions: - `TokenVesting.setSellContract`: Changes the contract that interacts with the contract `TokenVesting` - `TokenVesting.createVestingSchedule`: Create vesting schedules - `TokenVesting.revoke`: Revoke vesting schedules - `TokenVesting.withdraw`: Withdraw `_token` up to the amount not vested In the `TokenVesting` contract, the address `sellContract` has authority over the following function: - `TokenVesting.createVestingSchedule`: Create vesting schedules In the `TourismXToken` contract, the role `_owner` has authority over the following functions: - `TourismXToken.pause`: Pause token transfer - `TourismXToken.unpause`" Unpause token transfer In the `Sell` contract, the role `_owner` has authority over the following functions: - `Sell.setVestingContract`: Change the `vestingContract` to be called - `Sell.setPayToken`: Change the `payToken` used to start vesting - `Sell.setDuration`: Change the duration period to vesting reward - `Sell.setTokenPrice`: Change the price of the vesting token - `Sell.setSlicePeriodSeconds`: Change the time required to unlock a portion of the vesting reward - `Sell.setCliff`: Change the minimum time required to earn the vesting reward - `Sell.setRevocable`: Change whether a vesting schedule can be revoked or not

The audit on Trustblock · Open the report
HighInitial Token DistributionTourismX (TRMX ) - Audit · CertiKOpen

Despite the comment on line 787 stating all tokens are minted and "transferred to the multi-sig owner wallet", all the tokens were initially minted to eight addresses and the [owner](https://bscscan.com/address/0xc2c6cefb6656ab6225dbef06ce1d9472643d2b96) of the contract is not a multi-sig wallet. Having the tokens minted to a few selected addresses poses a centralization risk and allows the addresses to drastically manipulate the supply and potentially price of the token. Furthermore, any compromise to these addresses can heavily impact the project.

The audit on Trustblock · Open the report
LowFunction Should Be Declared ExternalTourismX (TRMX ) - Audit · CertiKOpen

Functions with external visibility are gas efficient compared to functions with public visibility. The following functions are declared `public` despite not being called internally and therefore can be declared `external` instead. In the contract `TokenVesting`: - `TokenVesting.setSellContract` - `TokenVesting.createVestingSchedule` - `TokenVesting.revoke` - `TokenVesting.withdraw` - `TokenVesting.getVestingSchedules` - `TokenVesting.getVestingSchedulesByOwner` - `TokenVesting.getAllVestingSchedules` - `TokenVesting.getLastVestingScheduleForHolder` In the contract `Sell`: - `Sell.setVestingContract` - `Sell.setPayToken` - `Sell.setDuration` - `Sell.setTokenPrice` - `Sell.setSlicePeriodSeconds` - `Sell.setCliff` - `Sell.setRevocable` - `Sell.buy`

The audit on Trustblock · Open the report
LowLack of input validationTourismX (TRMX ) - Audit · CertiKOpen

Several inputs are lacking input validation such as checking if an address is not zero or the start time is greater than the current block time. Other checks that may benefit include checking duration is greater than cliff. Such checks minimize unintended mistakes such as typos and help to keep the smart contract from functioning properly and as intended.

The audit on Trustblock · Open the report
LowMissing eventsTourismX (TRMX ) - Audit · CertiKOpen

Events are missing throughout the project and should be emitted whenever state variables are modified and/or core functions are called. Having events benefit those monitoring the protocol to easily filter relevant events. The following functions can benefit from emitting events: In the contract `TokenVesting`: - `TokenVesting.setSellContract` - `TokenVesting.createVestingSchedule` - `TokenVesting.revoke` - `TokenVesting.withdraw` - `TokenVesting.release` In the contract `Sell`: - `Sell.constructor` - `Sell.setVestingContract` - `Sell.setPayToken` - `Sell.setDuration` - `Sell.setTokenPrice` - `Sell.setSlicePeriodSeconds` - `Sell.setCliff` - `Sell.setRevocable` - `Sell.buy`

The audit on Trustblock · Open the report
LowUnnecessary BNB related implementationTourismX (TRMX ) - Audit · CertiKOpen

Despite the contract not requiring or using BNB, `fallback` and `receive` functions are implemented and addresses are casted to payable addresses. If a user unintentionally sends the BNB, there is currently no way of withdrawing this BNB and will be stuck in the contract.

The audit on Trustblock · Open the report
LowUnnecessary use of SafeMathTourismX (TRMX ) - Audit · CertiKOpen

As of Solidity version 0.8, arithmetic operations that result in overflow and underflow will automatically be reverted. Therefore the use of SafeMath is unnecessary and regular arithmetic operators such as `+`, `-`, `*`, and `/` can be used without integers underflowing or overflowing.

The audit on Trustblock · Open the report
LowUnused return valueTourismX (TRMX ) - Audit · CertiKOpen

The current implementation does not revert the transaction when the transfer fails by returning a `false` value. If `payToken` is ever changed in the future, this can unexpectedly lead to the creation of vesting schedules despite the `payToken` not having properly transferred.

The audit on Trustblock · Open the report

The TourismX security record · Every TourismX address · This address on the explorer