Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CIP-0044? | Additional factors for NFT market verification #226

Closed
wants to merge 2 commits into from

Conversation

nicholseric
Copy link

Additional factors for facilitating NFT market verification

Discussed in discord and forum:

20220209 21:24 Discussion on Discord in Blade adahandle channel:
Special thanks to gorath for suggestions on making additional tags available for manual verification or those not wanting to use a Handle.
Thanks to BenOJosh for asking hard questions.
20200213 Discussion on CIP Proposal for discussion " Market CNFT policyID verification " with @HeptaSean and @LonacheG
Tweeted @ many marketplaces and community members to come and engage:
https://twitter.com/hadaloha/status/1493435217716998147
https://twitter.com/hadaloha/status/1492719282769121280
https://twitter.com/hadaloha/status/1492715689513132034
https://twitter.com/hadaloha/status/1491639230430208002
https://twitter.com/hadaloha/status/1491559058926555138
Also posted in a few other discord channels.

Additional factors for facilitating NFT market verification

Discussed in discord and forum:

20220209 21:24 Discussion on Discord in Blade adahandle channel:
Special thanks to gorath for suggestions on making additional tags available for manual verification or those not wanting to use a Handle.
Thanks to BenOJosh for asking hard questions.
20200213 Discussion on [CIP Proposal for discussion " Market CNFT policyID verification "](https://forum.cardano.org/t/cip-proposal-for-discussion-market-cnft-policyid-verification/95268) with @HeptaSean and @LonacheG
Tweeted @ many marketplaces and community members to come and engage:
https://twitter.com/hadaloha/status/1493435217716998147
https://twitter.com/hadaloha/status/1492719282769121280
https://twitter.com/hadaloha/status/1492715689513132034
https://twitter.com/hadaloha/status/1491639230430208002
https://twitter.com/hadaloha/status/1491559058926555138
Also posted in a few other discord channels.
@KtorZ KtorZ changed the title Additional factors for NFT market verification CIP-44? | Additional factors for NFT market verification Mar 17, 2022
@KtorZ KtorZ changed the title CIP-44? | Additional factors for NFT market verification CIP-0044? | Additional factors for NFT market verification May 11, 2022
@KtorZ
Copy link
Member

KtorZ commented May 11, 2022

@mangelsjover let's maybe have this one on the agenda for the next CIP meeting; I feel like we kind of missed to include it earlier.

@@ -0,0 +1,80 @@
|CIP|Title|Authors|Comments-Summary|Comments-URI|Status|Type|Created|License|Requires|
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is another, simpler header format which doesn't rely on fields matching in a table. I hope @KtorZ @SebastienGllmt will correct me if I'm wrong but I think the parsing of CIP information depends on a header format like this (seen at the beginning of the raw Markdown for each of our merged CIP's):

---
CIP: 1
Title: CIP process
Authors: ...

Copy link
Collaborator

@rphair rphair left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nicholseric can you please move this text in your branch to a *.md file so it's formatted with Markdown, to help us view it at the upcoming meeting? Ultimately it should be in a README.md in its own subdirectory beginning with CIP but without an exact CIP name. 🙏

@nicholseric
Copy link
Author

@nicholseric can you please move this text in your branch to a *.md file so it's formatted with Markdown, to help us view it at the upcoming meeting? Ultimately it should be in a README.md in its own subdirectory beginning with CIP but without an exact CIP name. 🙏

Hows this?

https://github.com/nicholseric/CIPs/tree/master/CIP-0044%3F

@rphair
Copy link
Collaborator

rphair commented May 12, 2022

Hows this?

@nicholseric that's fine for now 😎


By creating a new tag for the distinct purpose of policyID verification, Cardano Asset makers, and Marketplaces can uniformly verify their policyID’s with predictable results. By creating the instructions on a single, no name asset, all marketplaces will know the correct location of the policyID verification asset, without having to further locate it. By enforcing the requirement of honoring only the latest mint, Cardano NFT creators can move or change their social media accounts and collection information. It is easy to work with this new standard, and does not require an in depth understanding of smart contracts. One URL could potentially support multiple policyID’s. Marketplaces could choose to have these automated verified collections queue into a human review.

20220209 21:24 Discussion on Discord in Blade adahandle channel:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this section needs to be part of the CIP


```
{
"808": {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be good to specify this further with actual types and also describe how you handle the transaction metadata size limitations (ex: is "create" always just a string? Can it be an array to get over the 64 byte limit?)

@rphair
Copy link
Collaborator

rphair commented Jun 28, 2022

from CIP meeting today: editors will make some enquiries to get feedback from NFT marketplace administrators.

@rphair
Copy link
Collaborator

rphair commented Jul 1, 2022

today's IO Dev Digest has linked back to this thread, calling for "community feedback" - https://mailchi.mp/iohk/dev-april-digest-675582

@mangelsjover
Copy link
Contributor

mangelsjover commented Jul 5, 2022

The following NFT marketplaces have been approached for feedback:

  • jpeg.store
  • cnft.io
  • tokhun.io

@KtorZ KtorZ added the Waiting for Author Proposal showing lack of activity or participation from their authors. label Nov 30, 2022
@KtorZ
Copy link
Member

KtorZ commented Jan 17, 2023

@AntMeyer1 have we gotten any feedback from NFT marketplaces on this?

@KtorZ
Copy link
Member

KtorZ commented Feb 21, 2023

Closing this for the sake of keeping the repository tidy. There hasn't been any sign of life / discussions around this proposal in a while.

@KtorZ KtorZ closed this Feb 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Waiting for Author Proposal showing lack of activity or participation from their authors.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants