[Contract] OpenZeppelin-Based NFT-Fungible Batch Distribution Contract for Starshop

[aguilar1x]

🎯 Objective

Design and implement an NFT-fungible batch distribution smart contract using OpenZeppelin’s Stellar contracts, allowing sellers to mint and transfer NFTs in batches to buyers as part of the purchase process in the Starshop marketplace. This contract leverages role-based access control and OpenZeppelin’s standard library to ensure security, scalability, and compatibility with Stellar.

---

🏗 Contract structure

nft-fungible-batch-contract/src/

  lib.rs             // Exports and main entry
  mint.rs            // NFT creation and batch mint logic
  transfer.rs        // Token transfer functionality
  roles.rs           // Role-based access control (admin, minter)
  events.rs          // Standardized event emission
  storage.rs         // State management per token and role

---

🗂 Requirements

1. Core NFT Logic

• Fungible-like NFTs using unique token IDs
• Sellers can mint NFTs in batches to buyers (mint_batch)
• Each call defines quantity of tokens delivered to one user
• All NFTs are transferible once received
• NFTs are not tied to metadata unless extended

2. Role Management

• Roles: DEFAULT_ADMIN_ROLE, MINTER_ROLE
• Only sellers with MINTER_ROLE can call mint_batch
• Only ADMIN_ROLE can assign or revoke MINTER_ROLE
• Role assignment is event-emitting and access-controlled
• Use OpenZeppelin’s AccessControl module

3. Minting & Claim Logic

• mint_batch(recipient, quantity) validates inputs:

  • recipient must be valid address
  • quantity > 0
  • caller must have MINTER_ROLE

• Each NFT minted must have unique token ID

• Emits NFTMinted and NFTBatchMinted events with full details

• Can be extended to support product-based mapping if needed

4. Transfer Functionality

• NFTs are fully transferible by recipients

• transfer(from, to, token_id) must:

  • Check ownership
  • Prevent unauthorized transfers
  • Emit Transfer event

• Compatible with future listing or trading functionalities in Starshop

5. Initialization Logic

• Contract is initialized once via initialize()
• Sets the first ADMIN_ROLE
• Marks the contract as initialized using storage guard
• Reinitialization attempt must revert
• Emits ContractInitialized once

6. State & Storage Isolation

• Use well-structured key prefixes per section:

  • role:{address}
  • token:{id}
  • owner:{address}:{token_id}

• Persistent mapping of token ownership and supply

• Storage keys must be isolated and non-overlapping

7. Event Emission

• Emit detailed events for all on-chain actions:

  • ContractInitialized
  • NFTMinted(token_id, recipient)
  • NFTBatchMinted(quantity, recipient)
  • Transfer(from, to, token_id)
  • RoleGranted(role, account)
  • RoleRevoked(role, account)

• Events support Starshop frontend and Stellar listeners

---

🔍 Clarity

• Batch minting reflects seller intent and product logic
• Ownership is clearly trackable and auditable
• Role-based access ensures secure and decentralized control
• Minting, transferring, and initialization flows are distinct and well-guarded
• State reflects real-time ownership and contract state

---

🔗 References

• OpenZeppelin Stellar Contracts
• OpenZeppelin Wizard for Stellar

---

📌 Additional Notes

• Compatible with Starshop’s buyer/seller roles

• Can be extended to include:

  • NFT metadata per product or tier
  • Burnable logic (revoke, invalidate)
  • Vesting or unlock conditions

• Consider integration with payment validation module via Stellar XLM in future

---

[psychemist]

Hi. I have experience creating robust and securely tested smart contracts for the StarShop repository. I would love to implement this NFT distribution feature. ETA: ~24 hours after asssigment

[ryzen-xp]

Hi,
I am proficient Blockchain developer expert in Cairo , Rust and Solidity and also in web development.
I have contributed many starknet ,stellar projects and more .
please /assign Me this issue .
Thank You !!
ETA: 24 hours

[Bosun-Josh121]

I am applying to this issue via OnlyDust platform.

My background and how it can be leveraged:
software engineering background, backend & smart contract dev (https://app.onlydust.com/users/Bosun-Josh121/overview)
with robust experience in writing soroban contracts

I am confident in fulfilling the stated requirements and functions. Will work on feedback & recommendation ensuring contact. Can deliver within 48hrs upon assignment

Recommended by OnlyDust for high-quality and dependable contributions.

[Jemiiah]

I would be happy to take this issue. i'm a Rust developer, and i'd like to improve my rust skills by working on the issue, and i would be abide by the rules set to do this issue

Recommended by OnlyDust for outstanding experience and quality contributions.

[FrankiePower]

I am SuperFranky, longtime contributor on onlydust and stellar projects. I am a frontend and blockchain developer and contributed to a variety of interesting projects in the space. My expertise is in React, Next.js, Solidity, Rust, Soroban and Cairo. I have previously built a product rating and review system smart contract on stellar with tests and as such I am very qualified for this task.

ETA: 24 HRS

[aguilar1x]

Hi, the issue has been assigned to you, you can start working on it now. You have to report your progress in less than 2 days, this in order to be aware that the contributor is developing the issue.

If you have any questions, don't hesitate to ask! 🚀

@Jemiiah

[Jemiiah]

Thank youuu, @aguilar1x. just seeing that i'm assigned the issue, I would continue to work on right away