July 2022

Audit Details

Audited project

Blockchain Land

Deployer address


Client contacts

Blockchain Land


Binance Smart Chain



This is a limited report on our findings based on our analysis, in accordance with good industry practice as at the date of this report, in relation to cybersecurity vulnerabilities and issues in the framework and algorithms based on smart contracts, the details of which are set out in this report. In order to get a full view of our analysis, it is crucial for you to read the full report. While we have done our best in conducting our analysis and producing this report, it is important to note that you should not rely on this report and cannot claim against us on the basis of what it says or doesn’t say, or how we produced it, and it is important for you to conduct your own independent investigations before making any decisions. We go into more detail on this in the below disclaimer below – please make sure to read it in full.
DISCLAIMER: By reading this report or any part of it, you agree to the terms of this disclaimer. If you do not agree to the terms, then please immediately cease reading this report, and delete and destroy any and all copies of this report downloaded and/or printed by you. This report is provided for information purposes only and on a non-reliance basis, and does not constitute investment advice. No one shall have any right to rely on the report or its contents, and TechRate and its affiliates (including holding companies, shareholders, subsidiaries, employees, directors, officers and other representatives) (HackSafe) owe no duty of care towards you or any other person, nor does HackSafe make any warranty or representation to any person on the accuracy or completeness of the report. The report is provided “as is”, without any conditions, warranties or other terms of any kind except as set out in this disclaimer, and HackSafe hereby excludes all representations, warranties, conditions and other terms (including, without limitation, the warranties implied by law of satisfactory quality, fitness for purpose and the use of reasonable care and skill) which, but for this clause, might have effect in relation to the report. Except and only to the extent that it is prohibited by law, HackSafe hereby excludes all liability and responsibility, and neither you nor any other person shall have any claim against HackSafe, for any amount or kind of loss or damage that may result to you or any other person (including without limitation, any direct, indirect, special, punitive, consequential or pure economic loss or damages, or any loss of income, profits, goodwill, data, contracts, use of money, or business interruption, and whether in delict, tort (including without limitation negligence), contract, breach of statutory duty, misrepresentation (whether innocent or negligent) or otherwise under any claim of any nature whatsoever in any jurisdiction) in any way arising from or connected with this report and the use, inability to use or the results of use of this report, and any reliance on this report
The analysis of the security is purely based on the smart contracts alone. No applications or operations were reviewed for security. No product code has been reviewed.


Step 1 - In-Depth Manual Review

Manual line-by-line code reviews to ensure the logic behind each function is sound and safe from various attack vectors. This is the most important and lengthy portion of the audit process (as automated tools often cannot find the nuances that lead to exploits such as flash loan attacks).

Step 2 - Automated Testing

Simulation of a variety of interactions with your Smart Contract on a test blockchain leveraging a combination of automated test tools and manual testing to determine if any security vulnerabilities exist.

Step 3 – Leadership Review

The engineers assigned to the audit will schedule meetings with our leadership team to review the contracts, any comments or findings, and ask questions to further apply adversarial thinking to discuss less common attack vectors.

Step 4 - Resolution of Issues

Consulting with the team to provide our recommendations to ensure the code’s security and optimize its gas efficiency, if possible. We assist project team’s in resolving any outstanding issues or implementing our recommendations.

Step 5 - Published Audit Report

Boiling down results and findings into an easy-to-read report tailored to the project. Our audit reports highlight resolved issues and any risks that exist to the project or its users, along with any remaining suggested remediation measures. Diagrams are included at the end of each report to help users understand the interactions which occur within the project.


HackSafe was commissioned by Blockchain Land to perform an audit of smart contract:

The purpose of the audit was to achieve the

The information in this report should be understand the risk exposure of the smart contract, and as a guide to improve the security posture of the smart contract by remediating the issues that were identified.

Contracts Details

Token contract details for 05.07.2022

Token Type

: BEP20

Contract name

: Token

Compiler version

: v0.8.10+commit.fc410830

Total supply

: 7,210,000,000

Token ticker



: 18

Token Holders

: 1

Top 100 token holder’s dominance

: 100.00%

Transactions count

: 1

Contract deployer address

:  0xFACE67a28694fe815c5EFB46b32B0506d0f6b568

Social profiles

Claimed Smart Contract Features

Claimed Feature Detail

Tokenomics :

: Blockchain Land
: 18
: BEP20
Max Total supply
: 7,210,000,000
Contract address
: 0x471A5e862af35D2148bd8 b505b361b1DDf5fFef1

Our Observation

YES, this is valid.

Audit Summary

According to the standard audit assessment, Customer`s solidity smart contracts are“Well Secure”. This token contract does contain owner control, which do not make it fully decentralized as owner does have control over smart contract.


We used various tools like Slither, Mythril and Remix IDE. At the same time this finding is based on critical analysis of the manual audit. All issues found during automated and manual analysis were manually reviewed and applicable vulnerabilities are presented in the issues checking status.
We found 0 critical, 0 high, 0 medium and 0 low and some very low-level issues.

Blockchain Land Distribution

Blockchain Land

Blockchain Land Top 01 Token Holders

Blockchain Land1

Blockchain Land Contract Overview

Blockchain Land2

Contract functions details

+ [Int] IERC20

+ [Int] IERC20Metadata (IERC20)

+ Context

+ ERC20 (Context, IERC20, IERC20Metadata)

+ Token (ERC20)

($) = payable function

# = non-constant function

Issues Checking Status

Unlocked Compiler Version
Missing Input Validation
Race conditions and Reentrancy. Cross-function race conditions.
Possible delays in data delivery
Oracle calls.
Timestamp dependence.
Integer Overflow and Underflow
DoS with Revert.
DoS with block gas limit.
Methods execution permissions.
Economy model of the contract
Private user data leaks.
Malicious Event log
Scoping and Declarations.
Uninitialized storage pointers.
Arithmetic accuracy.
Design Logic.
Safe Open Zeppelin contracts implementation and usage.
Incorrect Naming State Variable
Compiler version too old

Severity Definitions

Risk Level
Critical vulnerabilities are usually straightforward to exploit and can lead to assets loss or data manipulations.
High-level vulnerabilities are difficult to exploit; however, they also have a significant impact on smart contract execution, e.g., public access to crucial functions
Medium-level vulnerabilities are important to fix; however, they can't lead to assets loss or data manipulations.
Low-level vulnerabilities are mostly related to outdated, unused, etc. code snippets that can't have a significant impact on execution.

Security Issues

Critical Severity Issues

No critical severity issue found.

High Severity Issues

No high severity issue found.

Medium Severity Issues

No medium severity issues found.

Low Severity Issues

No low severity issue found.


Owner Privileges :

This smart contract has some functions which can be executed by the Admin (Owner) only. If the admin wallet private key would be compromised, then it would create trouble. Following are Admin functions and burner functions:


Smart contract contains no severity issues! The further transfer and operations with the fund raised are not related to this particular contract.
HackSafe note: Please check the disclaimer above and note, the audit makes no statements or warranties on business model, investment attractiveness or code sustainability. The report is provided for the only contract mentioned in the report and does not include any other potential contracts deployed by Owner.

Send your project now

Fill the details to be connected with our experts.

Send your project now

Fill the details to be connected with our experts.