Wistaverse Info

www.wistaverse.com

Wistaverse is an innovative tool for shared democracy. Reinventing social actions using blockchain technologies and the metaverse to unite, protect and give a voice to people. Your wallet is your digital identity, your avatar is your digital self. Come protest in the Wistaverse in a fully immersive live event with your community. Make sure your voice is heard no matter your age, your health condition or your geographic location.

Overall Score
93.75
Poor Excellent
Wistaverse Logo

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.

On-Chain Insights

Smart Contract Audit

Select the audit
Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x3720...Ed35
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/05/31
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 can be burned

There is a function to burn tokens in 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.


This BSC contract is a bridged contract, the mint function is here to allow tokens to be transferred from polygon and the max overall supply will never exceed 42 000 000.

Minter privileges

  •  minter can mint new tokens when tokens are bridged from polygon 

Burner privileges

  • can burn tokens from an arbitrary address without allowance

FeeManager privileges

  • fees cannot exceed 0.5%

WhitelisteManager privileges

  • update an address as whitelisted

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
Local variables shadowing (shadowing-local)
TokenWISTA.sol
L1407
L1408
L1466
L1466
Description

Rename the local variables that shadow another component.

optimization Issues | 2 findings

Pending

#1 optimization Issue
Public function that could be declared external (external-function)
TokenWISTA.sol
L383-385
L396-398
L414-418
L656-658
L664-666
L681-683
L688-690
L695-697
L707-710
L726-729
L744-758
L772-775
L791-799
L1417-1420
L1422-1425
Description

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

Pending

#2 optimization Issue
Declare explicit types
TokenWISTA.sol
L1531
Description

Change all "uint" types to an explicit type of "uint256" that the contract uses the types consistently.

informational Issues | 2 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
TokenWISTA.sol
L447-451
L117-119
L1334-1346
L1265-1278
L1375-1377
L1321-1324
L1356-1358
L1368-1370
L1308-1310
L1292-1294
L1382-1390
L1066-1068
L1108-1110
L1164-1173
L1124-1126
L1190-1199
L1080-1082
L1141-1150
L995-1001
L1037-1042
L1049-1054
L1020-1030
L1008-1013
L224-235
L199-219
Description

Remove unused functions.

Pending

#2 informational Issue
Missing dead address check
TokenWISTA.sol
L1482
Description

The "FeeManager" can set the "feeCollector" address to the dead address. It is recommended to check for a dead address also. Otherwise, the fees will be sent to the dead address, and the fees will be lost.