Bitcoin NFT Protocol Using OP_RETURN Metadata Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The Bitcoin ecosystem lacks native support for Non-Fungible Tokens (NFTs) due to its limited functionality compared to Ethereum, particularly in storing metadata and executing NFT-related transactions, which restricts the use of NFTs within the Bitcoin blockchain.

Innovation Solution

Implementing a Colored Coin-based NFT protocol using the OP_RETURN Bitcoin Script opcode, where metadata is stored to represent asset manipulation, and Unspent Transaction Outputs (UTXOs) are used for asset issuing and transferring, defining specific transaction types (GENESIS COLLECTION, COLLECTION MINT, GENESIS NFT, and NFT SEND) to facilitate NFT operations within the Bitcoin blockchain.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If Bitcoin Script language is used for NFT implementation, then lower transaction fees are achieved, but functionality for storing metadata and executing NFT transactions is limited

Engineering Contradiction:
Improvetransaction feeVSAvoidfunctionality for storing metadata and executing NFT transactions
Core Design Contradiction:
Loss of energyVSAdaptability or versatility

Solution Approach 1:

The patent segments NFT functionality into distinct transaction types (GENESIS COLLECTION, COLLECTION MINT, GENESIS NFT, NFT SEND) with specific metadata structures. Each transaction type handles a specific aspect of NFT operations, allowing the system to achieve complex functionality through composed simple transactions rather than requiring a single complex smart contract language.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces metadata as an intermediary structure stored in OP_RETURN outputs. This metadata acts as a mediator that carries NFT-related information (asset references, ownership details, manipulation instructions) between transactions, enabling functionality similar to Ethereum smart contracts while using Bitcoin's simpler scripting language.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If metadata is stored in OP_RETURN to represent NFT assets, then NFT functionality is enabled, but metadata size constraints limit the amount of information that can be stored

Engineering Contradiction:
ImproveNFT functionalityVSAvoidmetadata size
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent extracts only the essential NFT-related information into the OP_RETURN metadata (such as asset references, ownership identifiers, and transaction type indicators), while storing larger asset data externally. This allows the blockchain to maintain NFT functionality with minimal metadata storage requirements, adhering to Bitcoin's size constraints.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent moves from storing all NFT data on-chain to a hybrid approach where essential NFT metadata is stored on-chain in OP_RETURN outputs, while detailed asset information is stored off-chain. This dimensional shift from purely on-chain storage to distributed storage enables larger NFT functionality without increasing blockchain storage requirements.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Reliability

If strict metadata structure definition is implemented, then consensus among users is achieved, but complexity of protocol implementation increases

Engineering Contradiction:
Improveconsensus among usersVSAvoidprotocol implementation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent defines strict metadata structures tailored to each specific NFT transaction type (GENESIS COLLECTION, COLLECTION MINT, GENESIS NFT, NFT SEND). Each transaction type has its own optimized metadata schema with only the fields necessary for that specific operation, achieving consensus through localized structure definitions rather than a single complex universal structure.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent uses different metadata structures for different transaction types, changing the parameters and fields included based on the specific NFT operation being performed. This allows the protocol to maintain strict consensus requirements while adapting the metadata complexity to match the specific transaction needs, reducing overall implementation complexity.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11538028B1Implementing non-fungible tokens using bitcoin
Publication Date: 2022.12.27 DULUB ALEXEI
  • US11538028B1 patent drawing
  • US11538028B1 patent drawing
  • US11538028B1 patent drawing

AI summary

A novel method and instruction set for storing and trading Non-Fungible Tokens (NFTs), on Bitcoin blockchain. As proof of NFT ownership, proposed methods allow a user to perform the following operations with an NFT: (1) store NFT token on Bitcoin blockchain; (2) securely associate NFT data unit with digital assets (photos, video, audio, digital documents, etc.); (3) grouping many NFT tokens together to a collection with a single unique identifier; (4) safely sell and buy an NFT using Bitcoin ecosystem. These actions and validation of the transactions are performed using Bitcoin transactions.