EtherPOS Info
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
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
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
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)
Check that the address is not zero.
Pending
#2 low Issue
Missing Events
Emit events for critical parameter cahnges
informational Issues | 3 findings
Pending
#1 informational Issue
Functions that are not used (dead-code)
Remove unused functions.
Pending
#2 informational Issue
Unused state variables (unused-state)
Remove unused state variables.
Pending
#3 informational Issue
Uninitialized local variables (uninitialized-local)
Initialize all the variables. If a variable is meant to be initialized to zero, explicitly set it to zero to improve code readability.
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:
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.