Audit name:
[SCA] Moviedom / Moviedom-Token / Mar2025
Date:
Mar 24, 2025
Table of Content
Introduction
We express our gratitude to the Moviedom team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.
Moviedom merges blockchain with movies, music, mini multiplexes, global events, and artist management. It powers NFT marketplaces, streaming integration, and profit-sharing.
Document | |
|---|---|
| Name | Smart Contract Code Review and Security Analysis Report for Moviedom |
| Audited By | Nataliia Balashova |
| Approved By | Ivan Bondar |
| Website | www.moviedom.io→ |
| Changelog | 21/03/2025 - Preliminary Report, 24/03/2025 - Final Report |
| Platform | BSC |
| Language | Solidity |
| Tags | ERC20, Permit Token |
| Methodology | https://hackenio.cc/sc_methodology→ |
Document
- Name
- Smart Contract Code Review and Security Analysis Report for Moviedom
- Audited By
- Nataliia Balashova
- Approved By
- Ivan Bondar
- Website
- www.moviedom.io→
- Changelog
- 21/03/2025 - Preliminary Report, 24/03/2025 - Final Report
- Platform
- BSC
- Language
- Solidity
- Tags
- ERC20, Permit Token
- Methodology
- https://hackenio.cc/sc_methodology→
Review Scope | |
|---|---|
| Repository | https://github.com/Digital-v2/contract→ |
| Commit | eb1fbc3 |
Review Scope
- Repository
- https://github.com/Digital-v2/contract→
- Commit
- eb1fbc3
Audit Summary
The system users should acknowledge all the risks summed up in the risks section of the report
Documentation quality
Functional requirements are present.
Technical description is provided.
Code quality
The code duplicates commonly known contracts instead of reusing them.
The development environment is not configured.
Test coverage
Tests were not provided.
System Overview
MDOM facilitates decentralized movie and music production, NFT marketplaces, and global event management.
MovieDOMToken — A ERC-20 token that mints all initial supply to a deployer. Additional minting is not allowed. The contract also includes functionality that enables users to burn tokens from their own balance or another account (with proper allowance).
It has the following attributes:
Decimals: 18
Total supply: 1 billion tokens.
Potential Risks
Centralized Minting to a Single Address: The project concentrates minting tokens in a single address, raising the risk of fund mismanagement or theft, especially if key storage security is compromised.
Findings
Code ― | Title | Status | Severity | |
|---|---|---|---|---|
| F-2025-9288 | Public Functions That Should Be External | fixed | Observation | |
| F-2025-9287 | Floating Pragma | fixed | Observation |
Identify vulnerabilities in your smart contracts.
Appendix 1. Definitions
Severities
When auditing smart contracts, Hacken is using a risk-based approach that considers Likelihood, Impact, Exploitability and Complexity metrics to evaluate findings and score severities.
Reference on how risk scoring is done is available through the repository in our Github organization:
Severity | Description |
|---|---|
Critical | Critical vulnerabilities are usually straightforward to exploit and can lead to the loss of user funds or contract state manipulation. |
High | High vulnerabilities are usually harder to exploit, requiring specific conditions, or have a more limited scope, but can still lead to the loss of user funds or contract state manipulation. |
Medium | Medium vulnerabilities are usually limited to state manipulations and, in most cases, cannot lead to asset loss. Contradictions and requirements violations. Major deviations from best practices are also in this category. |
Low | Major deviations from best practices or major Gas inefficiency. These issues will not have a significant impact on code execution. |
Severity
- Critical
Description
- Critical vulnerabilities are usually straightforward to exploit and can lead to the loss of user funds or contract state manipulation.
Severity
- High
Description
- High vulnerabilities are usually harder to exploit, requiring specific conditions, or have a more limited scope, but can still lead to the loss of user funds or contract state manipulation.
Severity
- Medium
Description
- Medium vulnerabilities are usually limited to state manipulations and, in most cases, cannot lead to asset loss. Contradictions and requirements violations. Major deviations from best practices are also in this category.
Severity
- Low
Description
- Major deviations from best practices or major Gas inefficiency. These issues will not have a significant impact on code execution.
Potential Risks
The "Potential Risks" section identifies issues that are not direct security vulnerabilities but could still affect the project’s performance, reliability, or user trust. These risks arise from design choices, architectural decisions, or operational practices that, while not immediately exploitable, may lead to problems under certain conditions. Additionally, potential risks can impact the quality of the audit itself, as they may involve external factors or components beyond the scope of the audit, leading to incomplete assessments or oversight of key areas. This section aims to provide a broader perspective on factors that could affect the project's long-term security, functionality, and the comprehensiveness of the audit findings.
Appendix 2. Scope
The scope of the project includes the following smart contracts from the provided repository:
Scope Details | |
|---|---|
| Repository | https://github.com/Digital-v2/contract→ |
| Commit | eb1fbc34999b160b3b6612cc1ca0fcb2e24664d6 |
| Whitepaper | N/A |
| Requirements | https://moviedom-token.gitbook.io/moviedom-token→ |
| Technical Requirements | https://moviedom-token.gitbook.io/moviedom-token→ |
Scope Details
- Repository
- https://github.com/Digital-v2/contract→
- Commit
- eb1fbc34999b160b3b6612cc1ca0fcb2e24664d6
- Whitepaper
- N/A
- Technical Requirements
- https://moviedom-token.gitbook.io/moviedom-token→
Assets in Scope
MDOM/MovieDOMTokenv2.sol