Boston Dynamic INU
0xdd28583bC0E941fDeC877a98C451069f8E05f1c6 0xdd28...05f1c6

Static analysis Dynamic analysis Symbolic Execution SWC check

Boston Dynamics is a leading engineering and robotics design company. founded in 1992 and headquartered in Waltham, Massachusetts. The company is known for developing advanced robots that are capable of autonomous movement and perform a wide range of tasks. Some of Boston Dynamics' most notable robots include the humanoid robot Atlas, the four-legged SpotMini robot, and the bipedal robot called Handle. These robots have been developed for a variety of applications, including search and rescue, construction, and logistics. Boston Dynamics has a reputation for creating highly advanced and agile robots that are able to navigate challenging environments and perform tasks with a high degree of accuracy and precision. The company has collaborated with a number of organizations and institutions, including the US military, to develop and test its robots for a range of applications.

Contract address
0xdd28...05f1c6
Network Ethereum Mainnet
License MIT
Compiler v0.8.17 v0.8.17+commit.8df45f5f
Type ERC20
Language Solidity
Request date 2023/01/11
Revision date 2023/01/11
Critical
Passed
High
Passed
Medium
Passed

Owner privileges

No critical 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 cannot mint It is not 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 burn function within the contract.
Ownership is not renounced Contract can be manipulated by owner functions.
Comments

No Audit Comments.

Audit Scope

This audit covered the following files listed below with a SHA-1 Hash. The above token Team provided us with the files that needs to be tested.

We will verify the following claims:
  • Correct implementation of Token standard
  • Deployer cannot mint any new tokens
  • Deployer cannot burn or lock user funds
  • Deployer cannot pause the contract
  • Overall checkup (Smart Contract Security)
The auditing process follows a routine series of steps:
  • Review of the specifications, sources, and instructions provided to SolidProof to make sure we understand the size, scope, and functionality of the smart contract.
  • Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
  • Comparison to specification, which is the process of checking whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
  • Test coverage analysis, which is the process of determining whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
  • Symbolic execution, which is analysing a program to determine what inputs causes each part of a program to execute.
  • Best practices review, which is a review of the smart contracts to improve efficiency, effectiveness, clarify, maintainability, security, and control based on the established industry and academic practices, recommendations, and research.
  • Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.

A file with a different Hash has been modified, intentionally or otherwise, after the security review. A different Hash could be (but not necessarily) an indication of a changed condition or potential vulnerability that was not within the scope of this review.

Functions
public

59

State variables
public

9

Total lines
of code

1565

Capabilities
Hover on items

Audit Details

Throughout the review process, care was taken to evaluate the repository for security-related issues, code quality, and adherence to speciïŹcation and best practices. To do so, reviewed line-by-line by our team of expert pentesters and smart contract developers, documenting any issues as there were discovered.

Risk represents the probability that a certain source-threat will exploit vulnerability, and the impact of that event on the organization or system. Risk Level is computed based on CVSS version 3.0.

low Issues

Pending

#1 Issue

Local variables shadowing (shadowing-local)

BostonDynamicsInu.sol

L1054

L1367

Description

Rename the local variables that shadow another component.

Pending

#2 Issue

Floating Pragma

BostonDynamicsInu.sol

-

Description

The current pragma Solidity directive is “^0.8.0". Contracts should be deployed with the same compiler version and flags that they have been tested thoroughly. Locking the pragma helps to ensure that contracts do not accidentally get deployed using other versions

Pending

#3 Issue

Contract doesn’t import npm packages from source (like OpenZeppelin etc.)

BostonDynamicsInu.sol

-

Description

We recommend importing all packages from npm directly without flattening the contract. Functions could be modified or can be susceptible to vulnerabilities

informational Issues

Pending

#1 Issue

Functions that are not used (dead-code)

BostonDynamicsInu.sol

L494-496

L504-510

L523-529

L537-548

L583-585

L593-602

L556-558

L566-575

L441-451

L469-474

L610-630

L106-108

L376-385

L336-338

L402-411

L207-213

L249-254

L261-266

L232-242

L220-225

Description

Remove unused functions.

optimization Issues

Pending

#1 Issue

Public function that could be declared external (external-function)

BostonDynamicsInu.sol

L165-167

L173-176

L1024-1026

L1028-1030

L1032-1034

L1036-1038

L1045-1052

L1054-1061

L1063-1070

L1072-1087

L1089-1100

L1102-1116

L1118-1120

L1122-1124

L1126-1136

L1138-1151

L1362-1364

Description

Use the `external` attribute for functions never called from the contract.

Diagrams

Disclaimer

SolidProof.io reports are not, nor should be considered, an “endorsement” or “disapproval” of any particular project or team. These reports are not, nor should be considered, an indication of the economics or value of any “product” or “asset” created by any team. SolidProof.io do not cover testing or auditing the integration with external contract or services (such as Unicrypt, Uniswap, PancakeSwap etc’...)

SolidProof.io Audits do not provide any warranty or guarantee regarding the absolute bug- free nature of the technology analyzed, nor do they provide any indication of the technology proprietors. SolidProof Audits should not be used in any way to make decisions around investment or involvement with any particular project. These reports in no way provide investment advice, nor should be leveraged as investment advice of any sort.

SolidProof.io Reports represent an extensive auditing process intending to help our customers increase the quality of their code while reducing the high level of risk presented by cryptographic tokens and blockchain technology. Blockchain technology and cryptographic assets present a high level of ongoing risk. SolidProof’s position is that each company and individual are responsible for their own due diligence and continuous security. SolidProof in no way claims any guarantee of security or functionality of the technology we agree to analyze.