EtherPOS Info

etherpos.io

EtherPOS is a crypto token that runs fully on Binance Smart Chain (BSC), then EtherPOS complies with the most advanced smart contract protocol standards. EtherPOS is inspired by using a technical protocol similar to Ethereum. Proof-of-stake protocols are a class of consensus mechanisms for blockchains that work by selecting validators in proportion to the number of their holdings in the associated cryptocurrency. This is done to avoid the computational costs of the proof-of-work scheme.

Overall Score
81.37
Poor Excellent
EtherPOS 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.

TrustNet DataPulse

Smart Contract Audit

Select the audit
Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0xa0D7...f02E
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/01/19
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 can blacklist addresses

It is 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:
  • Set a New token contract which will allow the owner to call the "_setBalance" function. Thus, only the token contract will be able to call the _actualRewards function which will result in users' getting their funds back from the contract
  • Set a stable contract address
  • Set Trash Address
  • Set the balance of an Account based on their actual rewards.
  • Set the package to any arbitrary value
  • Withdraw the contract's balance. This means that the owner is able to withdraw the staked tokens of the users for the blacklisted accounts the "_newToken" value is set to zero on L378.
  • The accounts will be blacklisted after the deposit or extension if the package amount becomes greater than "_maxLogicalUnit". Thus, there will be no virtual rewards for anyone because
  • The owner is also able to lock user tokens by disabling the staking(Pausing) in the contract.

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
Missing Zero Address Validation (missing-zero-check)
ETHERPOS.sol
L141
L175
Description

Check that the address is not zero.

Pending

#2 low Issue
Missing Events
ETHERPOS.sol
LAll(There are no events in the contract)
Description

Emit events for critical parameter cahnges

informational Issues | 3 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
ETHERPOS.sol
L23-27
L44-46
L47-51
L52-54
L55-58
Description

Remove unused functions.

Pending

#2 informational Issue
Unused state variables (unused-state)
ETHERPOS.sol
L149
Description

Remove unused state variables.

Pending

#3 informational Issue
Uninitialized local variables (uninitialized-local)
ETHERPOS.sol
L422
Description

Initialize all the variables. If a variable is meant to be initialized to zero, explicitly set it to zero to improve code readability.