Travel helper

Client :
Travel helper
Published :
August 18th, 2018
Status :
Finalised
Auditors :
QuillAudits
Authenticity :
QuillAudits
Disclaimer :

Note that Security audit enables the discovery of vulnerabilities that were overlooked during development and areas where additional measures are necessary but does not make any statements that guarantees the safety of the project’s contracts and it’s viability. Quillhash performs extensive auditing in order to discover as many vulnerabilities as possible. This audit is not intended to be taken as an endorsement of the platform, team or company.

1. Introduction

This Audit Report highlights the overall security of TravelHelper Smart Contracts. With this report, we have tried to ensure the reliability of their smart contract by complete assessment of their smart contract codebase.

1.1 Auditing Approach and Methodologies applied

Quillhash team has performed thorough testing of the project starting with analysing the code design patterns in which we reviewed the smart contract architecture to ensure it is structured and safe use of third party smart contracts and libraries.

Our team then performed a formal line by line inspection of the Smart Contract in order to find any potential issue like race conditions, transaction-ordering dependence, timestamp dependence, and denial of service attacks.

In the Unit testing Phase we coded/conducted Custom unit tests written for each function in the contract to verify that each function works as expected. In Automated Testing, We tested the Smart Contract with our in-house developed tools to identify vulnerabilities and security flaws.

The code was tested in collaboration of our multiple team members and this included :

  1. Testing the functionality of the Smart Contract to determine proper logic has been followed throughout.
  2. Analyzing the complexity of the code by thorough, manual review of the code, line-by-line.
  3. Deploying the code on testnet using multiple clients to run live tests.
  4. Analysing failure preparations to check how the Smart Contract performs in case of bugs and vulnerabilities.
  5. Checking whether all the libraries used in the code are on the latest version.
  6. Analyzing the security of the on-chain data.

2. Security Level references

Every issue in this report was assigned a severity level from the following:

High severity issues will probably bring problems and should be fixed.

Medium severity issues could potentially bring problems and should eventually be fixed.

Low severity issues are minor details and warnings that can remain unfixed but would be better fixed at some point in the future.

2.1 High severity issues:-

Unmet condition in burnTokensForSale():

There is a require(tokens > 0) statement in the burnTokensForSale() function,where tokens is the balance of crowdsale contract so it means that this function can only succeed when all tokens will be sold .In crowdsale function there is a function finalizeAndBurn() which burns the tokens first and then finalize the sale, finalizing the sale means that investors can transfer their tokens after finalizing the sale.So the bug here is that if all tokens will be sold than this function will never succeed as it will be revert in burnTokensForSale() and investors will never able to transfer their tokens.

2.2 Medium severity issues:-

No medium severity issues are found.

2.3 Low severity issues:-

  1. Solidity version should be fixed in smart contracts.For ex:- It should be pragma solidity 0.4.24​ and not ​ pragma solidity ^0.4.24
  2. Transfer Events are not emitted in activateSaleContract() function in token contract.

3. Final Comments

  1. Contract should be properly commented.It is not commented in some places. It is advised to comment the code as it is good practice.
  2. Use of block number instead of timestamp is done perfectly.

4. Conclusion

All the changes suggested by our team has been applied by TravelHelper.So their contracts are secure now as of our investigation and their audited contracts are already deployed on main net.