Smart Contract Audit Report
DefiGold is a new BEP-20 on the Binance Smart Chain.
For this audit, we reviewed the project team's DGOLD contract at 0x24AeF4416Ff267AfC2d9Fe9141C1002555bed0a6 on the Binance Smart Chain Mainnet.
All findings have been resolved.
Date: April 10th, 2023.
Updated: April 12th, 2023 to reflect the contract's Mainnet address.
Updated: April 28th, 2023 to reflect the contract's newly deployed Mainnet address.
Finding #1 - ERC20 - Informational (Resolved)Description: The following line in the updateWeight() function is redundant as
user.lastAccountingTimestampSecis already updated for the user in the updateAccountingUser() function.
Recommendation: The team could remove the above line from the updateWeight() function for additional gas savings on each transfer.
user.lastAccountingTimestampSec = block.timestamp;
Resolution: The team has implemented the above recommendation.
Finding #2 - ERC20 - Informational (Resolved)Description: The
_initialWeightPerTokenstate variable cannot be modified but is not declared constant.
Recommendation: The above state variable could be declared constant for additional gas savings on each reference.
Resolution: The team has declared
Finding #3 - ERC20 - Informational (Resolved)Description: Although the SafeMath library is utilized, the contract is implemented with Solidity v0.8.x which has built-in overflow checks.
Recommendation: SafeMath could be safely removed to reduce contract size, deployment costs, and gas costs on all transactions that utilize it.
Resolution: The team has removed the SafeMath library from the contract.
- The total supply of the token is set to 79 million $GOLD [79,000,000].
- No mint or burn functions are accessible, though the circulating supply can be decreased by sending tokens to the 0x..dead address.
- At the time of writing this report, 100% of the total supply belongs to the owner.
- A minted weight value for each transfer is calculated based on the number of tokens being transferred and the token's current circulating supply.
- The minted weight value is added to both the recipient's and the contract's total weight. Both the recipient's and the contract's total weight-seconds values are updated based on each of their total weights and the amount of time that has passed since their weights were previously calculated.
- A new "hodl" is added on behalf of the recipient which stores the transfer's minted weight value and time of the transaction.
- A burned weight value is calculated based on the number of tokens being transferred and the token's current circulating supply.
- The burned weight value is decreased from the weight value of the sender's last hodl(s).
- Both the sender's and the contract's total weight and weight-seconds values are decreased by the calculated burn amounts.
- The weight values associated with the contract and each user can be used off-chain by the team.
- The owner can exclude and include accounts from the weight functionality on transfers at any time.
- The owner can update the BitFund address at any time.
- As the contract is implemented with Solidity v0.8.x, it is protected from overflows/underflows.
- The contract complies with the BEP-20 token standard.
|Arbitrary Jump/Storage Write||N/A||PASS|
|Centralization of Control||N/A||PASS|
|Delegate Call to Untrusted Contract||N/A||PASS|
|Dependence on Predictable Variables||N/A||PASS|
|Improper Authorization Scheme||N/A||PASS|
|Outdated Compiler Version||N/A||PASS|
|Overall Contract Safety||PASS|
($) = payable function # = non-constant function Int = Internal Ext = External Pub = Public + [Int] IERC20 - [Ext] totalSupply - [Ext] balanceOf - [Ext] transfer # - [Ext] allowance - [Ext] approve # - [Ext] transferFrom # + [Int] IERC20Metadata (IERC20) - [Ext] name - [Ext] symbol - [Ext] decimals + Context - [Int] _msgSender - [Int] _msgData + Ownable (Context) - [Pub]
# - [Pub] owner - [Int] _checkOwner - [Pub] renounceOwnership # - modifiers: onlyOwner - [Pub] transferOwnership # - modifiers: onlyOwner - [Int] _transferOwnership # + [Int] IFactory - [Ext] createPair # - [Ext] getPair + [Int] IRouter - [Ext] factory - [Ext] WETH + DGOLD (Ownable, IERC20, IERC20Metadata) - [Pub] # - [Pub] name - [Pub] symbol - [Pub] decimals - [Pub] totalSupply - [Pub] balanceOf - [Pub] transfer # - [Pub] allowance - [Pub] approve # - [Pub] transferFrom # - [Pub] increaseAllowance # - [Pub] decreaseAllowance # - [Int] totalAmount - [Int] updateAccountingTotal # - [Int] updateAccountingUser # - [Int] updateWeight # - [Int] _transfer # - [Int] _mint # - [Int] _approve # - [Int] _spendAllowance # - [Int] _beforeTokenTransfer # - [Int] _afterTokenTransfer # - [Ext] setWeightExempt # - modifiers: onlyOwner - [Ext] setBitFund # - modifiers: onlyOwner - [Ext] getWeightsInfo
SourceHat (formerly Solidity Finance - founded in 2020) has quickly grown to have one of the most experienced and well-equipped smart contract auditing teams in the industry. Our team has conducted 1700+ solidity smart contract audits covering all major project types and protocols, securing a total of over $50 billion U.S. dollars in on-chain value!
Our firm is well-reputed in the community and is trusted as a top smart contract auditing company for the review of solidity code, no matter how complex. Our team of experienced solidity smart contract auditors performs audits for tokens, NFTs, crowdsales, marketplaces, gambling games, financial protocols, and more!
Contact us today to get a free quote for a smart contract audit of your project!
What is a SourceHat Audit?
Typically, a smart contract audit is a comprehensive review process designed to discover logical errors, security vulnerabilities, and optimization opportunities within code. A SourceHat Audit takes this a step further by verifying economic logic to ensure the stability of smart contracts and highlighting privileged functionality to create a report that is easy to understand for developers and community members alike.
How Do I Interpret the Findings?
Each of our Findings will be labeled with a Severity level. We always recommend the team resolve High, Medium, and Low severity findings prior to deploying the code to the mainnet. Here is a breakdown on what each Severity level means for the project:
- High severity indicates that the issue puts a large number of users' funds at risk and has a high probability of exploitation, or the smart contract contains serious logical issues which can prevent the code from operating as intended.
- Medium severity issues are those which place at least some users' funds at risk and has a medium to high probability of exploitation.
- Low severity issues have a relatively minor risk association; these issues have a low probability of occurring or may have a minimal impact.
- Informational issues pose no immediate risk, but inform the project team of opportunities for gas optimizations and following smart contract security best practices.