Subscribe to lizgeorge
Subscribe to lizgeorge
Share Dialog
Share Dialog


<100 subscribers
<100 subscribers
EIF update for the week :
As the final week for project submission approaches, development was strictly based on successful deployment of contracts and testing the development environment.
Implementation of CarbonCreditMarketplace contract which includes the following functionalities :
Initialization the Carbon Credit Marketplace contract with the NFT contract address.
Creates a listing for a Carbon Credit NFT.
Removes a listing for a Carbon Credit NFT.
Buys a Carbon Credit NFT from a listing.
Tested all the contracts in local node and written deployment scripts in Hardhat.
Challenges I ran into
✅ Duplicate Unique IDs The possibility of duplicate unique IDs could undermine the credibility of carbon credits traded on the platform.
Solution : Implemented secure hashing algorithms and a mapping to store and verify unique IDs. This approach successfully addressed the issue and ensured the uniqueness and integrity of each carbon credit NFT.
✅ Data Integrity Ensuring the accuracy and reliability of the carbon credit data is critical to the platform's success.
Solution: Introduced validation checks for the information associated with each carbon credit before minting the NFT. This process included verifying the origin, eligibility, and carbon reduction impact of the project or activity, ensuring the credibility of the carbon credits.
✅ Unauthorized Access Limiting access to critical functions in the smart contracts was necessary to prevent unauthorized minting or modifications of carbon credits.
Solution: Implemented proper access control using OpenZeppelin's Ownable contract or Role-Based Access Control (RBAC) to restrict access to critical functions. This measure helped maintain the integrity of the platform and prevented unauthorized actions.
✅ User Interface Challenges in having a smooth frontend deployment due to technical difficulties.
Checkout my project proposal here.
EIF update for the week :
As the final week for project submission approaches, development was strictly based on successful deployment of contracts and testing the development environment.
Implementation of CarbonCreditMarketplace contract which includes the following functionalities :
Initialization the Carbon Credit Marketplace contract with the NFT contract address.
Creates a listing for a Carbon Credit NFT.
Removes a listing for a Carbon Credit NFT.
Buys a Carbon Credit NFT from a listing.
Tested all the contracts in local node and written deployment scripts in Hardhat.
Challenges I ran into
✅ Duplicate Unique IDs The possibility of duplicate unique IDs could undermine the credibility of carbon credits traded on the platform.
Solution : Implemented secure hashing algorithms and a mapping to store and verify unique IDs. This approach successfully addressed the issue and ensured the uniqueness and integrity of each carbon credit NFT.
✅ Data Integrity Ensuring the accuracy and reliability of the carbon credit data is critical to the platform's success.
Solution: Introduced validation checks for the information associated with each carbon credit before minting the NFT. This process included verifying the origin, eligibility, and carbon reduction impact of the project or activity, ensuring the credibility of the carbon credits.
✅ Unauthorized Access Limiting access to critical functions in the smart contracts was necessary to prevent unauthorized minting or modifications of carbon credits.
Solution: Implemented proper access control using OpenZeppelin's Ownable contract or Role-Based Access Control (RBAC) to restrict access to critical functions. This measure helped maintain the integrity of the platform and prevented unauthorized actions.
✅ User Interface Challenges in having a smooth frontend deployment due to technical difficulties.
Checkout my project proposal here.
No activity yet