Digital Mark Info

The Digital-Mark is a meme coin that combines the purchasing power and historical significance of the Deutsche Mark (1948 to 2001) with the modern technology of cryptocurrencies, giving people back a sense of security, appreciation and purchasing power. With a total volume of 1.2 billion tokens, Digital-Mark has created an entertainment coin that evokes the 'good old days' with humor and nostalgia. Digital-Mark brings a smile to our faces every day.

Digital Mark 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.

79.82
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
0xeE84...ecA3
Network
Ethereum - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2025/11/12
Revision date 2025/11/12

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.

Contract is upgradeable

The contract uses a proxy pattern or similar mechanism, enabling future upgrades. This can introduce risks if the upgrade mechanism is not securely managed.

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
  • The DEFAULT_ADMIN_ROLE can set the maximum total supply.
The smart contract was developed utilizing the DropERC20 template provided by thirdweb, a platform known for its pre-audited and battle-tested smart contract infrastructure. The underlying base contracts have been subject to an independent security audit by a third-party firm to identify potential vulnerabilities. The full report from this audit can be found at the following IPFS address: https://ipfs.io/ipfs/QmfKqeUfUgNwFn5B1fUAxzikj89mneZEETKrF7JfaJg5St.
While leveraging audited code provides a strong security foundation, it is essential to review the findings of the external audit. 
A thorough understanding of these documented findings is crucial for assessing the overall risk profile of the deployed contract and the operational security required by the project administrators.

Note - This Audit report consists of a security analysis of the Digital MARK smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited one token contract for the Digital MARK team. Other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing.

Files and details

Findings and Audit result

medium Issues | 1 findings

Resolved

#1 medium Issue
Centralization of Power via DEFAULT_ADMIN_ROLE Held by EOA
DropERC20.sol
L1-252
Description

The address 0xa5bB4A40d4CC2E8675300DfC3ED66529930341E3 holds the DEFAULT_ADMIN_ROLE, making it the ultimate administrator with the ability to perform irreversible actions. This includes upgrading the contract's logic, changing token sale parameters, redirecting funds, and minting an unlimited number of new tokens (as the maxTotalSupply is uncapped).

informational Issues | 1 findings

Pending

#1 informational Issue
Floating pragma solidity version.
DropERC20.sol
L2
Description

While a floating pragma offers flexibility during development, it is a potential security risk for deployed contracts. It introduces ambiguity about the precise compiler version used for deployment. Newer compiler versions can introduce subtle changes, optimizations, or even bugs that may affect the behavior of the smart contract in unforeseen ways compared to the version it was tested with. This makes it more difficult to verify that the deployed bytecode corresponds exactly to the audited source code and could expose the contract to compiler-specific vulnerabilities that are discovered in the future.