Merged
Conversation
Contributor
Author
|
closes #7 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Develop an ERC-721 smart contract for a "Verified Contributor" badge system. This badge will be awarded to contributors upon reaching specific milestones (such as writing guides or assisting others) and must be non-transferable (soulbound). The contract should leverage both the ERC721 and ERC721URIStorage standards for NFT and metadata management.
Requirements
ERC721 Implementation:
Create a contract inheriting from ERC721 and ERC721URIStorage.
Enable minting of badges to contributors who meet milestone criteria.
Soulbound Functionality:
Override all transfer and approval functions to prevent badge transfers, making the tokens soulbound.
Ensure badges cannot be transferred, sold, or delegated.
Badge Awarding Logic:
Implement internal logic or modifiers to check if a contributor qualifies for a badge.
Ensure only authorized accounts (e.g., contract owner or admin) can mint badges.
Metadata:
Store and retrieve badge metadata using the ERC721URIStorage standard.
Documentation:
Update project documentation with deployment, minting, and usage instructions.
Acceptance Criteria
The contract is deployed and integrates ERC721URIStorage.
Badges can be minted to contributors and are non-transferable.
All transfer and approval functions are disabled or reverted.
Metadata is accessible via tokenURI.
Documentation is updated with clear usage instructions.