CIP-Blueprint NFT

Placeholder for CIP-Blueprint NFT

(Work in progress)

CIP: ?
Title: CIP-Blueprint NFT
Authors: Roar Holte roar.holte@youblob.com
Comments-URI: CIP-Blueprint NFT
Discord: Youblob
Ideascale proposal: Online Makerspace
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

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

  • A Blueprint NFT is a NFT that introduces;
    • New ownership models to a NFT
    • New incentive models to a NFT
    • New attachment solutions, such as products and FT to be included within a NFT
    • New information channels between manufacturer and maker (i.e.; industry and consumer)
    • New library functions to show actual value generation around idea sharing and collaboration
    • New solution to combine all major subjects within a Blueprint NFT (chemistry, biology, math, electronics, mechanics etc…)
    • Lowering the threshold so everyone can create NFT’s without the technological know-how.
    • Extended (and simplified) metadata mapping for product iterations

IPFS_Blockfrost
blueprint_process
[img: initial Blueprint categorization, product linking and other functions before it is converted to a NFT]

User Journey Pre-requisites

User Journey

Terminology

Motivation

Specification

Convert a Blueprint to Blueprint NFT

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.

Copyright

This CIP is licensed under CC-BY-4.0