ArbKing Info
As owner of Cointalk Germany we decided to launch our first Project with our Community Members. We wanted to give our Community a safe place to ape and we are super excited to be on the Arbitrum-Chain. The Arbitrum-Chain is super fast and has lower fees compared to the Ethereum-Chain while also using ETH. We are the Kings and Queens of Arbitrum and now it’s our chance to take a position in this bear market because we are sure that this chain gonna blow up in the next bull run.
Team and KYC Verification
The KYC verification for this project is currently in progress.
The team has submitted their information and verification is pending.
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.
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.
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.
Contract cannot be locked
Owner cannot lock any user funds.
Token cannot be burned
There is no burning within the contract without any allowances
Ownership is renounced
The contract does not include owner functions that allow post-deployment modifications.
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:
- Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
- Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
- Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
- Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
- Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
- Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
- 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/Authority Privileges:
The contract has two modifiers after the ownership is renounced - onlyToken, and authorized
onlyToken (deployer or distributorOwner address) had the following privileges:
- Set distribution criteria, min period and min distribution to any arbitrary values including zero
- Set shares for any address
- Deposit ETH in the contract, and process dividends
- Claim dividend for a shareholder. Hence, the shareholders cannot claim the dividends by themselves
- Change distributor Owner address
- Withdraw ETH from the contract
authorized Addresses had the following privileges:
- Enable/Disable trading and lock user funds
- Enable/Disable the fee in the contract
- Set max wallet, and transaction limit
- End happy hour but cannot start it again
- Change fees, but cannot set it more than 25%
- Change swapBack settings and distribution criteria
- Process Dividends
- Set router, and pair address
- Include/Exclude wallets from fee, tx limit, and dividends
- Change Fee Receiver address
Since the ownership is renounced and the blacklist status is true, the blacklisted wallets can never be removed from the blacklist
Note - The privileges mentioned above are not applicable now as the ownership has been completely renounced. But we cannot confirm whether an authorised address exists or not.
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
low Issues | 3 findings
Pending
#1 low Issue
Missing Events Access Control (events-access)
Emit an event for critical parameter changes.
Pending
#2 low Issue
Missing Events Arithmetic (events-maths)
Emit an event for critical parameter changes.
Pending
#3 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
optimization Issues | 2 findings
Pending
#1 optimization Issue
State variables that could be declared constant (constable-states)
Add the `constant` attributes to state variables that never change.
Pending
#2 optimization Issue
Public function that could be declared external (external-function)
Use the `external` attribute for functions never called from the contract.
informational Issues | 4 findings
Pending
#1 informational Issue
Functions that are not used (dead-code)
Remove unused functions.
Pending
#2 informational Issue
Function initializing state variables (function-init-state)
Remove any initialization of state variables via non-constant state variables or function calls. If variables must be set upon contract deployment, locate initialization in the constructor instead.
Pending
#3 informational Issue
Unused return values (unused-return)
Ensure that all the return values of the function calls are used.
Pending
#4 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.