Subsmate Info

Additionally, Subsmate Profile NFTs contain a subscribe module. This module contains the logic that allows different accounts to be issued subscribe NFTs to record their relationship to the main profile on-chain.

Subsmate 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.

81.70
PoorExcellent

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.

TrustNet DataPulse

Loading...
Mobula Logo Data provided by mobula.io. Need data? Get your API.
Loading...

We are presently engaged in detailed discussions with our partners to finalize the arrangements. Information regarding presales will be made available on this platform in the near future. We appreciate your patience and look forward to sharing the upcoming opportunities with you soon!

We are currently in discussions with our partners to finalize the details. Information on token locking and vesting schedules will be provided on this platform soon. We appreciate your patience and look forward to sharing these upcoming opportunities with you shortly.

In the meantime, we’ve already integrated the LP lock overview from UNCX.network. Please visit the CEX/DEX tab for more information.

Security Assessments

Select the audit
Static AnalysisDynamic AnalysisSymbolic ExecutionSWC CheckManual Review
Contract address
0xbf54...ED1E
Network
Arbitrum - Testnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/03/21
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 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.

Token transfer can be locked

Owner can lock user funds with owner functions.

Token cannot be burned

There is no burn function within the contract.

Ownership is not renounced

Contract can be manipulated by owner functions.

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.


Ownership Privileges
  • Change sale status at any time, which means that the owner can start or cancel the sale at any point in time
  • Withdraw USDC from the contract
  • Change lockTime, finishTime, and startTime of the sale at any point in time which may result in the locking of the user's funds because if the lockTime is changeable then users won't be able to claim their tokens. Note that these values can also be set to zero which will result in funds available to claim right after deposits.
  • Set the max allocation amount to any arbitrary value including zero and stop users from buying tokens
  • Add a new vesting round with any arbitrary value of '_claimPercent'
  • The owner can withdraw sale tokens from the presale contract.

Note - The owner can basically buy the tokens for "free" from the presale contract because it is possible for the owner to withdraw the USDC sent while buying tokens. Moreover, keep in mind that the owner controls every aspect of the presale contract.

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

low Issues | 1 findings

Pending

#1 low Issue
Missing Events Arithmetic (events-maths)
SubsmatePublicSale.sol
L1099-1101
L1103-1109
L1111-1117
L1119-1125
Description

Emit an event for critical parameter changes.

optimization Issues | 1 findings

Pending

#1 optimization Issue
Public function that could be declared external (external-function)
SubsmatePublicSale.sol
L904-906
L912-915
L1055-1057
Description

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

informational Issues | 1 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
SubsmatePublicSale.sol
L233-245
L87-89
L97-103
L116-122
L130-139
L172-174
L182-189
L147-149
L157-164
L38-44
L62-67
L221-231
L197-213
L838-840
L501-511
L442-455
L466-477
L457-464
L479-493
L418-424
L426-433
L706-715
L666-668
L732-741
L622-624
L683-692
L537-543
L579-584
L591-596
L562-572
L550-555
Description

Remove unused functions.