Placeholder for CC0 NFT
(Work in progress)
CIP: ?
Title: CC0 NFT
Authors: Roar Holte roar.holte@youblob.com
Comments-URI: https://forum.cardano.org [use optional tag: nft-blueprint]
Discord: Youblob
Status: Draft
Type: Standards
Created: 2023-08-12
License: CC-BY-4.0
Requires: CIP25 & CIP86
Relation: This effort will be presented for the Cardano Summit Hackathon 2023 [https://cardano.hackerearth.com/]
Material
Whitepaper: Whitepaper
Videos: https://www.youtube.com/@youblobdotcom
Beta release: https://www.youblob.com [can test blueprint functionality]
Mock-ups: https://www.figma.com/file/AnrAqPskGEO8CtpVio1R6Z/Youblob
Dora BUIDL: Youblob | Buidls | DoraHacks
Cardano Source code: Bitbucket
Abstract
- My initial plan was to create a totally new licence around Blueprint NFT’s use-cases and its collaborative effort, but then I came across Creative Commons Zero [CC0 1.0] which I found to be a very good fit for this purpose and already standardized.
CC0 1.0; You can copy, modify, distribute and perform the work, even for commercial purposes, all without asking permission.
So even though we allow for full openness (even for Copycats), smart contracts in the backend of Blueprint publications will be handled automatically, giving reference and pushes incentives to the correct contributors.
The licence is needed to allow/enable Rapid Prototyping in Blueprints, along with AI generated prototypes.
Meaning a User can take an existing Blueprint and copy it into their own Blueprint, make small edits and publish it with their own iterations, where the copied Blueprint is part of the incentive solution in the new iteration.
User Journey Pre-requisites
User Journey
Terminology
Motivation
Specification
Metadata
Metadata JSON schema
Metadata example including the transaction metadata label
Rationale
The format of the content field is required to be an array of 64 bytes chunks, as this is the maximum size of a JSON field in the Cardano ledger.
Tools, such as wallets, are required to recompose the content of the message.
The current Cardano protocol parameter for maximum transaction size, that will hold the metadata, is around 16KB.
Backwards compatibility
No backwards compatibility breaking changes are introduced.
Reference implementation
We leave the decisions, such as what and how to display communication messages, up to downstream tools and wallets.
- For simple implementation reference, refer to CIP12 communication tool examples
Copyright
This CIP is licensed under CC-BY-4.0