KodaDot NFT explorer
Short Description: This project will extend KodaDot (rewrite original PolkadotJS in VueJS) with an NFT explorer. The NFT explorer main idea is to incorporate the workflow of exploring, issuing, querying and sending NFTs between users. Our idea is wrapped around the possibility and accessibility, to easily create a marketplace for anyone who is non-technically savvy to be able to use it from a mobile device.
1. Context of the proposal
The goal of this project is to create a universal NFT explorer and marketplace interface later for non-fungible tokens on Kusama. With the final outcome of this proposal, users will be able to mint, transfer, and burn NFTs on the network. On top of this, transfer functionality will be extended with buy and sell features, which will be later translated into a marketplace. We are looking to filter options for galleries to be curated and anyone to participate.
Our primary deliverable will be an extension of KodaDot: an NFT explorer as open source library for future NFT pallets operators to use.
The team would like to embrace various properties of ownership and rental manipulation for various use-cases, not just art. ERC-1155 (i.e batch operations of ERC-20 and ERC-721), ERC-1633 (timeshares, co-ownership, fractional ownership), ERC994 (delegation), ERC-998(composable NFT), ERC-809(renting), ERC-1201(tokenize ownership and rental rights) and in future cover this integrations in our NFT explorer.
2. Problem statement
Unique Network or RMRK.app proposed solutions to mint NFTs, however there is little to no UX right now to mint, transfer, filter, list and trade NFTs inside the original interface.
Although a PoC gallery is being developed as part of the NFT Strategy for Kusama, having a user-friendly interface will allow a simpler onboarding process for non-tech savvy users into the world of non-fungible assets.
3. Functional objectives
- User is able to view, manage and operate non-fungible assets;
- Create components allowing upcoming Substrate pallet provider to easily adopt KodaDOT: NFT Explorer;
- Users would be able explore and interact with assets in AR/VR world
- Future-compatible open source library front-end library.
- Attract new user base to Kusama ecosystem through AR/VR functionality [1]
- Experiment over new usages of NFTs applications, i.e. bundle scene as NFT
6. The team behind it
- Matej Nemcek (@yangwao) - Co-Founder of KodaDot, VueJS background, more info hypersignal.xyz
- Viktor Valastin (@vikiival) - Co-Founder of KodaDot, Publication about carsharing dApp on ETH using ERC721 token composition. Working for a company which is creating car-management software(React, Spring) and R&D in blockchain.
Team Code Repos
Team LinkedIn Profiles
Work being already done towards this proposal
Comments (3)
Comments (3)
Made a write-up on our road here, if someone is wondering what've been up to till now medium.com/kodadot/kodadot-nft-explorer-f2c3a326a856
I'm not sure I agree with the price tag, it seems steep for Milestone 1 since I plan to develop most of this functionality anyway in a reference toolkit. I'd recommend halving that amount. M2 is also a bit too expensive for my taste considering the reach of such an implementation will have (little to none in the beginning and for a long time, but is excellent marketing), but I'm willing to support it because it's "out there". M3 seems reasonable, and I think some funds from M1 and M2 are actually better redirected into M3.
In terms of the proposal content:
Possibility to create collection of NFTs (lists on twitter) and create decentralized links to share it with others
This is already in RMRK specs, because the primary unit is the Collection.
Deploy separate web page which would be embeddable into other existing web applications using
I would rather see a page generator in your toolkit which can generate a gallery/UI based on some user preferences (i.e. only show NFTs by these addresses), and then makes that embeddable. I'd rather not have people depend on your server for these embeds. Indeed, I'd rather they be auto-IPFS-ed.
All in all I like this very much and want to see it come alive, and I'd love to work closely with you guys to bring this to reality.
Made a write-up on our road here, if someone is wondering what've been up to till now medium.com/kodadot/kodadot-nft-explorer-f2c3a326a856
I'm not sure I agree with the price tag, it seems steep for Milestone 1 since I plan to develop most of this functionality anyway in a reference toolkit. I'd recommend halving that amount. M2 is also a bit too expensive for my taste considering the reach of such an implementation will have (little to none in the beginning and for a long time, but is excellent marketing), but I'm willing to support it because it's "out there". M3 seems reasonable, and I think some funds from M1 and M2 are actually better redirected into M3.
In terms of the proposal content:
This is already in RMRK specs, because the primary unit is the Collection.
I would rather see a page generator in your toolkit which can generate a gallery/UI based on some user preferences (i.e. only show NFTs by these addresses), and then makes that embeddable. I'd rather not have people depend on your server for these embeds. Indeed, I'd rather they be auto-IPFS-ed.
All in all I like this very much and want to see it come alive, and I'd love to work closely with you guys to bring this to reality.