Carbify Info
Carbify is certified by Earthood and, thus, the United Nations and can officially license/certify projects and companies under The United Nations Framework Convention on Climate Change, which established an international environmental treaty. Carbify plants agroforestry systems in Brazil and Angola, with over 60,000 systems and 3 million trees planted. Each system, covering 12,5 to 30 square meters, includes diverse plants and trees. The main tree in each system is geotagged and recorded on the blockchain. CO2 absorption is tracked and recorded on the blockchain using fixed values from ecologists. Each kilogram of CO2 absorbed is linked to the responsible tree’s ID, allowing precise identification for each carbon offset certificate, offering superior transparency compared to traditional carbon credits. Carbify ensures undeniable proof of carbon offsets while addressing up to 10 Sustainable Development Goals (SDGs). Carbon debits are only sold after the absorption has occurred.
Team and KYC Verification
The team has securely submitted their personal information to SolidProof.io for verification.
In the event of any fraudulent activities, this information will be promptly reported to the relevant authorities to ensure accountability and compliance.
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.
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.
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.
Token transfer can be locked
Owner can lock user funds with owner functions.
Token cannot be burned
There is no burning within the contract without any allowances
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:
- Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
- Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
- Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
- Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
- Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
- Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
- 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
- Default Admin role - Can update Carbify admin role.
- Default Admin role - Can revoke Carbify admin role.
- Carbify Admin role - Can update the staking pool contract address.
- Carbify Admin role - Can update the Algebra pool contract address.
- Carbify Admin role - Can update unlock fee receiver address.
- Carbify Admin role - Can unlock NFT for the user.
- Carbify Admin role - Can unstake NFT for multiple users.
- Carbify Admin role - Can claim NFT for the user.
- Carbify Admin role - Can update the Merkle root in the contract.
- NFTREE Batch role - Can lock the single NFT Tree.
- NFTREE Batch role - Can lock multiple NFTs at once.
- NFTREE Batch role - Can unlock single or multiple NFTs from the contract.
- NFTREE Batch role - Can stake single or multiple NFTs in the contract.
- NFTREE Batch role - Can unstake single or multiple NFTs in the contract.
- NFTREE Batch role - Can claim tokens for the users.
- LANDPLOT role - Can stake a single NFT in the contract.
- Default Admin role - Can update the aco2 token contract address.
- Default Admin role - Can update the Max token IDs per transaction to any arbitrary value.
- Default Admin role - Can grant or revoke the staking contract role to any arbitrary address.
- Default Admin role - Can add the packages in the contract.
- Default Admin role - Can adjust the package pointers in the contract.
- Staking contract role - Can claim the CO2 tokens from the contract.
Note - This Audit report consists of a security analysis of the Carbify Staking 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 Carbify Staking 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
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
medium Issues | 4 findings
Pending
#1 medium Issue
The owner can lock staking.
The admin can update any arbitrary value in the max token ids per transaction including zero which is not recommended as this can lock the staking and un-staking of the token if the value is set to zero in the contract. There must be a check where this value cannot be set to zero
Pending
#2 medium Issue
Missing ‘isContract’ check.
The contract contains the functionality in which the admin of the contract can update any arbitrary address as the contract address which is not recommended as this can cause the failure of functionality if the address is set to any arbitrary address in the contract. There must be a check where the address can only be set to the contract address to avoid this scenario in the contract.
Pending
#3 medium Issue
Missing ‘isContract’ check.
The contract contains the functionality in which the admin of the contract can update any arbitrary address as the contract address which is not recommended as this can cause the failure of functionality if the address is set to any arbitrary address in the contract. There must be a check where the address can only be set to the contract address to avoid this scenario in the contract.
Pending
#4 medium Issue
Onchain price calculation.
The contract contains the functionality in which the price calculation in the contract is an on-chain calculation which is not recommended as an on-chain computations in Solidity are expensive, especially for complex logic. Also, on-chain price calculations are vulnerable to manipulation or attacks if not implemented carefully. For example, using unreliable or single-source data on-chain can expose the contract to Oracle attacks.
low Issues | 1 findings
Pending
#1 low Issue
Missing Zero Address Validation
Make sure to validate that the address passed in the function parameters is a “non-zero” or dead address.
informational Issues | 1 findings
Pending
#1 informational Issue
Floating Pragma solidity version
The contracts should be deployed with the same compiler version and flag that they have been tested thoroughly. Locking the pragma helps to ensure that contracts do not accidentally get deployed using other versions.