Placeholder for CIP-FT function as a product within a Blueprint
(Work in progress)
CIP: ?
Title: CIP-FT function as a product within a Blueprint
Authors: Roar Holte roar.holte@youblob.com
Comments-URI: https://forum.cardano.org [use optional tag: nft-blueprint]
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 [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
Similar projects
IOHK had a project/whitepaper on something called “Cedita”? (I was unfortunately unable to find it, as they have reworked their website). But the project discussed using Bitcoin as a transaction fee for math if I remember correct. This was back in 2017.
Later stages have also included Wolfram Mathematica into the solution.
Through those and our effort, I would like to present a solution that can align some extra functionality that fit each system.
The initial idea behind all of this though originates behind a discussion I had with a University math professor from Bergen, Norway. Where he told me about one of his students had made a mathematical equation that could measure amount of oil being sent through pipes and written a thesis on it. The clue was that he charged 50 øre (0.047$) pr time the algorithm was run. And the Norwegian offshore industry figured they needed this, but they had to run it all the time with very short intervals to be able to see real time data in their own systems. So the student was set for life before even ending his studies.
So our goal here is to add Fungible Tokens as product placeholders for digital assets within a Blueprint NFT, where the consumer pays every time they run the product as a service.
Abstract
- A Fungible Token can be mapped to a product within a Blueprint NFT and offered as a service.
This conforms to purchasing a digital effort as a service, instead of a physical product.
F.ex everytime a User runs a code/algorithm/equation within a Blueprint.
This allows for micro transactions and will also be part of mapping out actual value generation through different efforts within a Blueprint.
Function can also be adapted to smart phones (and laptops) where Users can use sensor technology found within the smart phone to run different Blueprints as services, and get outputs on the go.
It also serves as an Authentication service around e-commerce product, where good actors can use it to validate authenticity towards consumers and their distributor chains. But is another discussion that needs its own CIP.
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