oceanprotocol / pm

Zenhub needs each issue associated with one repo. This repo is a workaround, to mark issues that span >1 repos.
4 stars 0 forks source link

Add manual image upload to our data NFT minting for V4 #160

Closed LoznianuAnamaria closed 6 months ago

LoznianuAnamaria commented 2 years ago

@AnaLoznianu commented on Thu May 26 2022

Add manual image upload to our data NFT minting for V4 (next to our default waves-artwork-set).

Could be something nice for everyone to try out the Ocean Market, minting "your own dataNFT as profile pic" for fun, caring about further functionality/ opportunities later, like creating datatoken (or adding features/to data unions/services we build/3rd party services/).

Creating this mostly for discussions...


@mihaisc commented on Thu May 26 2022

There are already ideas for using data nft as credentials or as profile . In first case you have the nft you have access to something. In second you use the data nft to store your profile data (it can be used as an alternative to ens )


@malvonme commented on Mon May 30 2022

Hi all, Hi @AnaLoznianu,

thank you for raising this to the market team!

This is meant as a potential low-effort test-balloon, feeling the water of what people, developers, builders actually can and want to do with our data NFT, "flavors" of how to create data supply (and demand), deriving further features from there (user centric design).

It could serve for several purposes: A) Pimping the data NFT you mint as a pass-on-asset (e.g. in case you mint it for someone else, like an artist/musician) B) Create 1 data NFT baseIP for your project, or NFT club, as an owner, and "brand" it right away (user love/endorsement) C) Experiment with first limited NFT editions that include early data functionality, creating opportunity now, building on it later.

I compiled a lil bootleg post on this (content in sync with Trent): https://mirror.xyz/cryptowally.eth/cl0azXM44ndABXhoHsJY0PWJdew2GD63j6um9-FmFqk


@malvonme commented on Mon May 30 2022

PS: If NFT is still new/unrelateable to you, maybe you like this (NFT profile pic trend in a nutshell): https://mirror.xyz/cryptowally.eth/YkaO0vPgwzzaYsZft7ONTmqURVwzgG2iCtjGj3Wxsxk


@malvonme commented on Mon May 30 2022

A community member just made a graphic, giving you the fastest way to the concept/idea https://twitter.com/AquaNauxt/status/1531296780687749124?s=20&t=1Jnqt3Ch7KuJ7pv6H3f8Yg

FUBCSTJXoAAxP3k


@AnaLoznianu commented on Tue Jul 05 2022

This is already possible by overriding the tokenURI. There are published assets with custom images: https://market.oceanprotocol.com/asset/did:op:39b9fa755de838a1a912e8589f64ce1601157cc2f1418ee9a3e77b7c7342f986 so for now, we will not focus our efforts in this direction.


@malvonme commented on Tue Jul 05 2022

I understand.

Just for some context: The goal behind this was to increase actionability of the data we collect (and collect more data overall), not just an image to the data NFT, in a seamless manner.

Seamless as in: "bring the data to the user, have the users carry their new data-store to the platforms".

Like: have the data that you supply (write user settings/parameter) as a platform closest possible to the data you CONSUME (read additional settings/parameters stored by other platforms "through" my data NFT). It was supposed to be a early fun test (mint "your" NFT as data NFT), and by that, as a trojan horse, a complementary move to our current strategy of "build the market and wait for supply and demand, incentivize demand".

But as said: I understand if this is no priority.

Thanks for considering, Ana.


@malvonme commented on Wed Jul 06 2022

User request: https://discord.com/channels/612953348487905282/612953349003673629/994173261464219668


@kremalicious commented on Wed Jul 06 2022

  1. Build a landing page reading out user's Data NFTs
  2. Allow updating of selected NFT metadata, here image or image_data key within tokenURI, via ocean.js nft.setMetadata()
  3. Go to Ocean DAO, ask for funds
  4. Fun and profit

This utility file might be good place to start to see what one would need: https://github.com/oceanprotocol/market/blob/main/src/@utils/nft.ts


@malvonme commented on Wed Jul 06 2022

Awesome @kremalicious, thank you!! Will insta-share with community

w1kke commented 2 years ago

How is it going to be taken care of that users will not upload existing NFTs that might be worth a ton and then selling their DataNFTs as copies of these NFTs? Or is this no concern?

mihaisc commented 2 years ago

Sorry @w1kke not sure i understand what you are trying to say, can you please rephrase it.

w1kke commented 2 years ago

What if people upload images of Bored Ape Yacht Club NFTs or Crypto Punks - this will cause confusion with newbies who might not understand the concept of NFTs.

malvonme commented 2 years ago

--

mihaisc commented 2 years ago

That's true. At a stack level we can't control that, people can do whatever they want, it's decentralized. This is why we don't really see the need to develop and enable this in our market. The focus of dataNFT is data , not the image. I think we are of the same mind here :)

w1kke commented 2 years ago

Maybe an explicit warning in the marketplace where the image can be uploaded and also where it is displayed could be good? Or something that is always added as an overlay in a corner to show that this is not the original image like a watermark for Ocean DataNFT avatars?

I did not want to stop this project, this topic just came up in our own discussions for a DataNFT Tutorial + Dashboard page and I wanted to know your thoughts on this issue.

I think it is a great idea to showcase what can be done with ERC725 that cannot be done with ERC721 - basically showing why Ocean's DataNFTs are more useful.

w1kke commented 2 years ago

@malvonme I would not have to care much or get involved really, I am doing that because I care. I get the feeling you are misunderstanding my intentions. I see this as my duty as an Ocean Protocol ecosystem member to raise my concerns where they come up. A collective of yes-men is not beneficial.

malvonme commented 2 years ago

I removed myself from this discussion. Thank you.