Back to discussions

#384 KodaDot NFT explorer

Proposer:
CuHW...oeSd
 
in Treasury
7th Dec '20

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.

Original proposal document

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

Team Code Repos

Team LinkedIn Profiles

Work being already done towards this proposal

Show More

Expert Image
No Expert Review Available!An Expert adds their valuable review for this post!An expert? Add your Review!
Please Log In to comment

3Comments
CuHW...oeSd
 
 
10th Dec '20

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

Di9w...Za8x
 
 
15th Dec '20

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.

CuHW...oeSd
 
 
17th Dec '20

Originally requested costs

M1 - 20_000€ M2 - 25_000€ M3 - 15_000€

Adjusted costs

M1 - 15_000€ M2 - 25_000€ M3 - 17_000€

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.

We can drop things like extend RMRK for appreciations and comments as you plan to do it and we can implement it in NFT explorer later and in return probably cut costs, go for 15k€ for Milestone 1. But so far, we've started work on Textile/ThreadsDB to avoid running indexer service, which could be a one-time investment and huge cut in the long term, for now, usable by anyone I guess. We are also doing here highly experimental implementation which could be used over any Substrate chain. What are your thoughts on this?

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".

Thanks for your appreciation. We worked hard to showcase our proof-of-work! 🥲 This is quite our bet that it would not exceed these costs as we would like to operate with someone in the industry to participate as well, this would also cover their time. I've noted it in the proposal. Mea culpa.

M3 seems reasonable, and I think some funds from M1 and M2 are actually better redirected into M3.

That's a good point, it's hard to predict for us right now as we did not had time and ability to run it ourselves. But we are in touch with Usetech and they will have ready documentation for us, sometime in mid-January.

Possibility to create collection of NFTs (lists on twitter) and create decentralized links to share it with others

Just for clarification; We thought to create a personally curated collection for users. Example: I want to show my friends Kusama Cube, Kusama Dodecahedron and other 2 arts from different collections. This personally curated collection should be shareable by link.

We see it as your collection is like per one car vendor, collection of particular (a1, a3, a4), but we want to create "collection" as vendor independent, (a1, x5, gle).

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.

As mentioned before this is the goal of a curated collection. Where we will provide a page generator to show NFTs particular by addresses or collections. We may did not made clarification clear enough, but the intent was there 😄. I've adjusted it and reflected on your comment there, let me know what do you think of it now.

I'd rather not have people depend on your server for these embeds.

This is a great topic on the table. We want to provide something infrastructure-agnostic and independent, where we also been looking at using Dat, to leverage the usage of DatDot. But, to reduce friction, we would like to bring a UX-first experience. Right now we are looking for something that would use Pinata or Textile/Buckets, we are already actively researching what would fit best!

UX-first experience If you played around with Slate, it's like an extension, right-click and create a collection and you can share some URL, pleasant experience.

But you have **a few options here how to share: **

UX-first URL https://slate.host/yangwao/berry (this is collection URL)

CID (own gateway required) - bafybeih7p3274e7n7lgo44bvzt6k7e4popiotsphij7g53z2wt3skx4l5q // you can check it through ipfs.io gw

Link - https://slate.host/yangwao/berry/cid:bafybeih7p3274e7n7lgo44bvzt6k7e4popiotsphij7g53z2wt3skx4l5q

Gateway URL - https://slate.textile.io/ipfs/bafybeih7p3274e7n7lgo44bvzt6k7e4popiotsphij7g53z2wt3skx4l5q

Indeed, I'd rather they be auto-IPFS-ed.

This could be done through Fleek.co (Netlify sort of) or using some pinata keys, we will try to determine which will be better UX for non-tech savvy users. Depends on how we make tutorials I guess or w/o tutorials experience would fit best. Our aim would be to play around from mobile.

Also speaking broadly, we can drop some budget, but don't expect some venture-backed experience after-all. To develop some great UX features takes time to figure out the design, architecture and lastly implement it to deliver it.


Discover similar proposals


Empty Icon

No Active Proposals