Krampus Info

TBA

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

89.95
PoorExcellent

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

Loading...
Mobula Logo Data provided by mobula.io. Need data? Get your API.
Loading...

We are presently engaged in detailed discussions with our partners to finalize the arrangements. Information regarding presales will be made available on this platform in the near future. We appreciate your patience and look forward to sharing the upcoming opportunities with you soon!

We are currently in discussions with our partners to finalize the details. Information on token locking and vesting schedules will be provided on this platform soon. We appreciate your patience and look forward to sharing these upcoming opportunities with you shortly.

In the meantime, we’ve already integrated the LP lock overview from UNCX.network. Please visit the CEX/DEX tab for more information.

Security Assessments

Static AnalysisDynamic AnalysisSymbolic ExecutionSWC CheckManual Review
Contract address
0xA6B7...0BFD
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2022/11/11
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 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:

  • Authorize/Unauthorize addresses to perform certain actions in the  contract
  • Set max wallet percent, maximum transaction percent, and fees but within limitations.
  • Enable trading but cannot disable it again.
  • Disable burning but cannot enable it again.
  • Set fee receivers and SwapBack settings.

There can be multiple authorities in the contract which means that there will be some extent of authority in the contract after renouncing ownership. For Example, the owner can authorize 'n' number of accounts and all of them can perform the following actions:

  • Clear stuck tokens but not the native ones
  • Manage Fee exemption, maximum wallet limit, and Maximum transaction limit exemption
  • Set multipliers
  • Call the Hell function which will burn some LP and not more than 10% of total

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 Events Arithmetic (events-maths)
KRAMPUS.sol
L487-493
L495-503
Description

Emit an event for critical parameter changes.

Pending

#2 low Issue
Contract doesn’t import npm packages from source (like OpenZeppelin etc.)
KRAMPUS.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 | 1 findings

Pending

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

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

informational Issues | 3 findings

Pending

#1 informational Issue
Function initializing state variables (function-init-state)
KRAMPUS.sol
L203
L204
L217
L238
Description

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

#2 informational Issue
Unused state variables (unused-state)
KRAMPUS.sol
L73
Description

Remove unused state variables.

Pending

#3 informational Issue
Unused return values (unused-return)
KRAMPUS.sol
L408-449
Description

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