iGold
ISLAMICOIN is the largest Islamic technology project that utilizes blockchain technology, in addition to media, commercial, financial, entertainment and charitable projects. The project aims to build an Islamic blockchain that helps achieve financial independence for individuals, companies and charitable organizations in the global Islamic community in addition to building a Decentralized Autonomous Organization (DAO) that operates according to Islamic Sharia in its content and transactions.
Owner privileges
Comments
Ownership/Admin Privileges
- Add/Remove admins
- Set/Update NFT contract address
- Pause the contract but only when the gold price is zero
- Set the Physical Gold Fee to any arbitrary value. Note that this is the price/fee users have to pay in order to receive physical gold
- Set USDT address, ISLAMI address, Gold Price Address, and ISLAMI Price Address
- Admin address can increase the gold reserve amount to any arbitrary value.
- Owner address can decrease the gold reserve amount to any arbitrary value.
- Withdraw tokens from the contract that are not in the vault, only the ones sent by mistake to the contract
Note - Moreover, the code of the two interfaces that are used in the contract 'IPMMContract', and 'IiGoldNFT' was not in the audit scope and we cannot comment on the security of it
Audit Scope
This audit covered the following files listed below with a SHA-1 Hash. The above token Team provided us with the files that needs to be tested.
We will verify the following claims:- Correct implementation of Token standard
- Deployer cannot mint any new tokens
- Deployer cannot burn or lock user funds
- Deployer cannot pause the contract
- Overall checkup (Smart Contract Security)
- Review of the specifications, sources, and instructions provided to SolidProof to make sure we understand the size, scope, and functionality of the smart contract.
- Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
- Comparison to specification, which is the process of checking whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
- Test coverage analysis, which is the process of determining whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
- Symbolic execution, which is analysing a program to determine what inputs causes each part of a program to execute.
- Best practices review, which is a review of the smart contracts to improve efficiency, effectiveness, clarify, maintainability, security, and control based on the established industry and academic practices, recommendations, and research.
- Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.
A file with a different Hash has been modified, intentionally or otherwise, after the security review. A different Hash could be (but not necessarily) an indication of a changed condition or potential vulnerability that was not within the scope of this review.
Functions
public
57
State variables
public
14
Total lines
of code
1306
Capabilities
Hover on items
Audit Details
Throughout the review process, care was taken to evaluate the repository for security-related issues, code quality, and adherence to speciïŹcation and best practices. To do so, reviewed line-by-line by our team of expert pentesters and smart contract developers, documenting any issues as there were discovered.
Risk represents the probability that a certain source-threat will exploit vulnerability, and the impact of that event on the organization or system. Risk Level is computed based on CVSS version 3.0.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L288-290
L228-237
L188-190
L254-263
L205-214
L59-65
L101-106
L113-118
L84-94
L72-77
Remove unused functions.
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
L354-356
L362-365
L555-557
L563-565
L580-582
L606-610
L629-633
L651-660
L674-678
L694-703
L1109-1112
L1169-1195
Use the `external` attribute for functions never called from the contract.
Disclaimer
SolidProof.io reports are not, nor should be considered, an âendorsementâ or âdisapprovalâ of any particular project or team. These reports are not, nor should be considered, an indication of the economics or value of any âproductâ or âassetâ created by any team. SolidProof.io do not cover testing or auditing the integration with external contract or services (such as Unicrypt, Uniswap, PancakeSwap etcâ...)
SolidProof.io Audits do not provide any warranty or guarantee regarding the absolute bug- free nature of the technology analyzed, nor do they provide any indication of the technology proprietors. SolidProof Audits should not be used in any way to make decisions around investment or involvement with any particular project. These reports in no way provide investment advice, nor should be leveraged as investment advice of any sort.
SolidProof.io Reports represent an extensive auditing process intending to help our customers increase the quality of their code while reducing the high level of risk presented by cryptographic tokens and blockchain technology. Blockchain technology and cryptographic assets present a high level of ongoing risk. SolidProofâs position is that each company and individual are responsible for their own due diligence and continuous security. SolidProof in no way claims any guarantee of security or functionality of the technology we agree to analyze.