-
Notifications
You must be signed in to change notification settings - Fork 321
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-???? | NFT and Token Authentication #917
base: master
Are you sure you want to change the base?
CIP-???? | NFT and Token Authentication #917
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@emir-olgun this is a vital application that needs a solid standard for it.
Please also have a look at the method proposed in #294 (@Padierfind) - since the methods in that proposal went quite far through community review and approval before the author abandoned the document.
First you will have to follow the document structure defined in CIP-0001. It looks like you have copied the text from an old CIP but will observe that CIPs today follow a different structure, which even the older CIPs have been edited to adopt. We can review this more fully when you've made your best effort to adjust to that format: https://github.com/cardano-foundation/CIPs/blob/master/CIP-0001/README.md#document
# CIP-?: NFT and Token Authentication | ||
|
||
--- | ||
- **CIP**: ? | ||
- **Title**: NFT and Token Authentication | ||
- **Authors**: Emir Olgun <emirolgun@gmail.com> | ||
- **Discussions-To**: https://github.com/littlefish-foundation/CIPs/discussions | ||
- **Status**: Proposed | ||
- **Created**: 2024-09-17 | ||
- **License**: CC-BY-4.0 | ||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# CIP-?: NFT and Token Authentication | |
--- | |
- **CIP**: ? | |
- **Title**: NFT and Token Authentication | |
- **Authors**: Emir Olgun <emirolgun@gmail.com> | |
- **Discussions-To**: https://github.com/littlefish-foundation/CIPs/discussions | |
- **Status**: Proposed | |
- **Created**: 2024-09-17 | |
- **License**: CC-BY-4.0 | |
--- | |
--- | |
CIP: ? | |
Title: NFT and Token Authentication | |
Authors: | |
- Emir Olgun <emirolgun@gmail.com> | |
Discussions: | |
- https://github.com/cardano-foundation/CIPs/pull/917 | |
Implementors: [] | |
Status: Proposed | |
Created: 2024-09-17 | |
License: CC-BY-4.0 | |
--- |
The most important change (besides the wrong document structure below): this is not a human readable list, but rather a YAML metadata section: https://github.com/cardano-foundation/CIPs/blob/master/CIP-0001/README.md#header-preamble
@@ -0,0 +1,154 @@ | |||
# CIP-?: NFT and Token Authentication |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# CIP-?: NFT and Token Authentication |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes @emir-olgun - as already suggested in #917 (comment), it's a requirement that this H1 be removed which in any case is redundant with the CIP title in the file metadata.
@emir-olgun after initial discussion of this submission at the CIP Editors' meeting today, we can't move ahead with this unless you engage about the basic format issues & try to respond about the already posted comments. Please take the above suggestions into account & otherwise this should be marked |
@emir-olgun marking this |
Metadata Standard for using NFT and Tokens for authentication.
(rendered latest version)