Nakama Info

Nakama is a low tax rewards token on the BSC offering up to 90% of buy and sell tax back in Binance Pegged XRP rewards and also offers secondary rewards upon long-term staking commitment. Our first utility will be a casino platform powered by BitValley and utilizing ADAPT technology from Affinity Innovations, Inc

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

51.94
Poor Excellent

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.

Security Assessments

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x5451...0149
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/02/20
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.

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 not renounced

The owner retains significant control, which could potentially be used to modify key contract parameters.

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:
  • Enable Trading but cannot disable it
  • Set the Presale address and update it at any point in time, even during the presale.
  • Include/Exclude accounts from dividends, auto claims, and fees.
  • Allow wallets to make transfers before the trading is enabled
  • Enable/Disable limits in the contract
  • Set cooldown time, max wallet amount, and max transaction amount, gas for processing within a safe range.
  • Set the reward threshold (swap trigger amount) to any arbitrary value including zero.
  • Set marketing wallet address, and AMM pair address.
  • Allow/Disallow custom tokens and auto reinvest.
  • Update fees amount but not more than 10%.
  • Pause/Unpause Dividends
  • Update payout token address, SwissArmy address, dividend tracker, and NFT Rewards address at any point in time
  • Set the minimum token balance for dividends to any arbitrary value
  • Airdrop to wallets with own wallet's balance

Note: If the dividend tracker and payout addresses are changed then it may affect the functionality of the Token contract.

We recommend investors/users to do their own research before investing

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
Local variables shadowing (shadowing-local)
Nakama.sol
L451
L451
L1345
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
Nakama.sol
L757-760
L763-766
L769-773
L776-780
L783-785
L1234-1244
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Contract doesn’t import npm packages from source (like OpenZeppelin etc.)
Nakama.sol
-
Description

We recommend importing all packages from npm directly without flattening the contract. Functions could be modified or can be susceptible to vulnerabilities

optimization Issues | 2 findings

Pending

#1 optimization Issue
State variables that could be declared constant (constable-states)
Nakama.sol
L556
Description

Add the `constant` attributes to state variables that never change.

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
Nakama.sol
L111-113
L115-117
L119-121
L131-134
L136-138
L140-143
L145-150
L152-155
L157-161
L293-296
L474-476
L496-498
L504-506
L730-733
L736-738
L741-744
L783-785
L787-791
L793-795
L797-799
L801-803
L815-819
L821-825
L827-831
L833-856
L862-864
L866-868
L870-872
L958-981
L1188-1191
L1193-1195
L1197-1199
L1201-1203
L1205-1208
L1210-1212
L1214-1217
L1479-1488
L1513-1559
L1592-1594
L1596-1598
L1600-1602
Description

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)
Nakama.sol
L13-16
L514-520
L478-494
L1698-1700
L263-265
L267-270
L338-341
L318-324
L309-316
Description

Remove unused functions.

Pending

#2 informational Issue
Unused state variables (unused-state)
Nakama.sol
L307
Description

Remove unused state variables.

Pending

#3 informational Issue
Unused return values (unused-return)
Nakama.sol
L639-688
L889-891
L983-1123
L1219-1232
Description

Ensure that all the return values of the function calls are used.

Pending

#4 informational Issue
Uninitialized local variables (uninitialized-local)
Nakama.sol
L986
L1257
L1262
L1128
L987
L1607
L1093
L1115
L1115
L1126
L1258
L1115
L988
L1127
L1653
L989
Description

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