SHELTERZ Info

At the beginning of 2022, when there was a shortage of OTA (booking services) in the Russian Federation, we decided to strengthen our website and tried to figure out how to increase the LTV (returnability) of customers so that they always book hotels only with us. We have come up with a loyalty system that gives not just a banal cashback of 10-15-20%, but which will produce the effect of a "miracle" and return all the money spent to customers. We decided to share the profits with our users and came up with a multi-level system of algorithms that takes into account behavioral factors, elements of the pension system, factors of engagement and activity, which distributes points in such a way as to gradually provide 100% cashback to each participant. We saw good business results, LTV grew 5 times, and we began to fully load our hotels through our website. So we decided to create a booking service from it and connect with other hotels there.

SHELTERZ Logo

TrustNet Score

The TrustNet Score evaluates crypto projects based on audit results, security, KYC verification, and social media presence. This score offers a quick, transparent view of a project's credibility, helping users make informed decisions in the Web3 space.

65.50
Poor Excellent

Real-Time Threat Detection

Real-time threat detection, powered by Cyvers.io, is currently not activated for this project.

This advanced feature provides continuous monitoring and instant alerts to safeguard your assets from potential security threats. Real-time detection enhances your project's security by proactively identifying and mitigating risks. For more information, click here.

Security Assessments

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x3206...500b
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2022/08/05
Revision date In progress

Summary and Final Words

No crucial issues found

The contract does not contain issues of high or medium criticality. This means that no known vulnerabilities were found in the source code.

Contract owner can mint

It is possible to mint new tokens.

Contract owner cannot blacklist addresses.

It is not possible to lock user funds by blacklisting addresses.

Contract owner cannot set high fees

The fees, if applicable, can be a maximum of 25% or lower. The contract can therefore not be locked. Please take a look in the comment section for more details.

Contract cannot be locked

Owner cannot lock any user funds.

Token cannot be burned

There is no burning within the contract without any allowances

Ownership is not renounced

The owner retains significant control, which could potentially be used to modify key contract parameters.

Scope of Work

This audit encompasses the evaluation of the files listed below, each verified with a SHA-1 Hash. The team referenced above has provided the necessary files for assessment.

The auditing process consists of the following systematic steps:

  1. Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
  2. Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
  3. Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
  4. Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
  5. Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
  6. Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
  7. Actionable Recommendations: Provide detailed, specific, and actionable steps to secure and optimize the smart contracts.

A file with a different Hash has been intentionally or otherwise modified after the security review. A different Hash may indicate a changed condition or potential vulnerability that was not within the scope of this review.

Final Words

The following provides a concise summary of the audit report, accompanied by insightful comments from the auditor. This overview captures the key findings and observations, offering valuable context and clarity.


Owner can mint new tokens

Tokens can be burned only if the caller has allowance

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

low Issues | 2 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
BEP20Token.sol
L419
L574
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Old compiler version
BEP20Token.sol
L3
Description

Old solidity versions have known vulnerabilities and it's not recommended to use them. We recommend using the latest compiler version

informational Issues | 1 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
BEP20Token.sol
L553-559
L588-591
L113-116
L212-214
L227-234
L247-249
L262-265
L187-199
L158-160
Description

Remove unused functions.