ikemHood
commented
3 weeks ago I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Hey, I am ikem Peter. a fullstack software developer with 3+ years of working experience, I would love to help out with this issue...
How I plan on tackling this issue
To approach this issue, I'd start by focusing on the data structures and storage. I'd update the Storage struct in our smart contract to include new fields for managing NFT series and artist metadata. This would involve adding mappings or lists to track created series by their unique IDs, as well as associated artist information. I'd make sure these new structures can efficiently store and retrieve the series name, description, base URI, and artist details like name, bio, and profile links.
Next, I'd implement the create_series function. This function would take in the series details and artist metadata as inputs, generate a unique ID for the new series, and store all this information in our updated contract state. I'd include validation to ensure series names are unique and handle any potential errors. After implementation, I'd write comprehensive unit tests to verify the function works correctly, including tests for successful creation, duplicate name attempts, and various edge cases. Throughout this process, I'd keep the code clean, well-documented, and optimized for gas efficiency on Starknet.
od-hunter
Abeeujah
PedroCo3lho
onlydustapp[bot]
caseywescott
Description:
We need to implement a function to allow the creation of NFT series within the smart contract, including metadata for the artist who created the series. This will enable artists to create and manage multiple series of NFTs, with each series associated with artist-specific information such as name, bio, and profile links.
Tasks:
1. Define the Series Data Structure:
Create a new data structure in the smart contract to store information about each series. This structure should include fields for the series name, description, base URI, and any other necessary metadata.
struct Series { name: felt252, description: felt252, base_uri: felt252, }
2. Define an ArtistMetadata struct to store artist-specific information:
struct ArtistMetadata { name: felt252, bio: felt252, profile_link: felt252, }
3. Define a Function to Create Series:
The function signature is as follows:
fn create_series(ref self: ContractState, name: felt252, description: felt252, artist_info: ArtistMetadata, base_uri: felt252, ) -> u256 { // Function implementation goes here }
Implement the create_series function to:
Update ContractState:
Modify the ContractState to include mappings or lists that track all created series and their associated artist metadata by their unique IDs.
Validation and Error Handling:
Ensure that series names are unique within the contract to avoid conflicts. Implement error handling to manage cases where invalid or duplicate data is provided.
Testing:
Write unit tests to verify the functionality of the create_series function, including the handling of artist metadata.
Test cases should include:
4. Update Storage Struct to Support NFT Series and Artist Metadata
To implement the series creation functionality with artist metadata, we need to update the Storage struct to include additional fields for managing both NFT series and associated artist information. This update will allow the smart contract to store and manage multiple series, each with its own metadata and linked artist data.
Current Storage Struct:
[storage]
struct Storage { _name: felt252, _symbol: felt252, _owners: LegacyMap<u256, ContractAddress>, _balances: LegacyMap<ContractAddress, u256>, _token_approvals: LegacyMap<u256, ContractAddress>, _operator_approvals: LegacyMap<(ContractAddress, ContractAddress), bool>, _token_uri: LegacyMap<u256, felt252>, _owner: ContractAddress, }
Add Series to the Storage Struct:
Update the Storage struct to include the following fields for series and artist management
[storage]
struct Storage { _name: felt252, _symbol: felt252, _owners: LegacyMap<u256, ContractAddress>, _balances: LegacyMap<ContractAddress, u256>, _token_approvals: LegacyMap<u256, ContractAddress>, _operator_approvals: LegacyMap<(ContractAddress, ContractAddress), bool>, _token_uri: LegacyMap<u256, felt252>, _owner: ContractAddress, _series_counter: u256, // Counter to track the number of series created _series_data: LegacyMap<u256, Series>, // Mapping of series ID to Series struct }
Explanation:
_series_counter: A counter that increments with each new series created, ensuring each series has a unique ID. _series_data: A mapping from series ID to a Series struct, which will store the series metadata, including artist information.
Expected Outcome:
After implementing these changes, the contract will be capable of storing and managing multiple NFT series, each with its own unique metadata, including artist-specific information, enabling enhanced functionality for the p5mint platform.