[Milestone 2 Submission]: CollectiVerse #30
Description
Project title
CollectiVerse: Uniting Creators and Collectors in the NFT Space
Link to grant application issue
Milestone submission
| Milestone No. | Milestone Summary | Estimated Timeframe |
|---|---|---|
| 1 | Project Kick-off and Initial Development | 2 weeks |
| 2 | MVP Development and Testing | 4 weeks |
| 3 | Testing, Bug Fixes, and Deployment | 2 weeks |
Milestone 1
- Establish the project's infrastructure and development environment.
- Implement the basic interface for browsing and searching NFT listings.
Milestone 2
- Create the MVP version of the NFT marketplace, allowing users to mint, list, and purchase NFTs.
- Develop smart contracts for NFT creation and transfer.
Milestone 3
- Address any identified bugs or issues.
- Areas Needing Support:
- Security audits and code review to ensure the platform's robustness.
Link to the open-source code/delivery
https://github.com/kazpot/collectiverse
License
APACHE2
Documentation
https://github.com/kazpot/collectiverse/tree/main/docs
Further documentation
- Architecture overview and individual component details
Tests for critical functions
https://github.com/kazpot/collectiverse/tree/main/test
Other milestone deliverables
- I didn't include the auction feature in the initial milestone, but I have added the auction functionality.
Any additional information
The smart contract is deployed to Topos testnet, and the frontend is also deployed on Vercel for immediate testing through the UI. The database is in a usable state.
Frontend URl:
https://collectiverse-anon.vercel.app/
Exchange Contract Address: 0x3039131DCC9512FfA5683343b9080A5203599c6E
CollectiVerse NFT Contract Address: 0xb038da8fCF59d03a08FB31f4939C7d02E0adE114
Performance Issue
Due to the limitation of retrieving event logs 1000 blocks at a time using the json-rpc of the topos testnet's public chain, the performance is currently suboptimal. Currently, it takes > 3 minutes for functionalities where event logs are retrieved from the blockchain. For example, when you click the UPDATE button (update owned NFts) or ACCEPT button (accept bid price), the process begins asynchronously; however, if you perform another action without waiting for Metamask to respond, there is a potential risk of encountering errors in Metamask operations.
Affected areas:
- 07-accept-bid.md
- 10-update.md