Bifurcated NFTs for Secure Digital File Approval
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems lack a secure and efficient method to verify and approve digital files, particularly in scenarios requiring multiple approvals from different entities.
Innovation Solution
The use of bifurcated non-fungible tokens (NFTs) to provide a secure approval mechanism, where each approver is assigned a unique NFT that is used to authenticate and approve digital files by placing their NFT in an approval block on a blockchain.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional approval methods are used for digital files, then the approval process is simple to implement, but the security and authenticity verification of approvals is insufficient
Solution Approach 1:
The patent uses digital copies of physical approval signatures in the form of NFTs. Each approver's unique signature is captured as a digital imprint and tokenized as an NFT, which can be repeatedly used to authenticate approvals without requiring the physical signature each time. This copying approach maintains security while enabling automated verification processes.
Solution Approach 2:
The patent replaces manual physical signature collection and verification with blockchain-based NFT authentication. Instead of mechanically collecting wet signatures and manually verifying identities, the system uses cryptographic NFTs that automatically verify authenticity through smart contracts, eliminating the need for manual intervention and significantly enhancing security.
2Reliability
If multiple approvers are required for important files, then the approval security is improved, but the approval process time and complexity increase
Solution Approach 1:
The patent performs preliminary actions by pre-issuing NFTs to all potential approvers before the approval process begins. Each approver receives their authentication NFT in advance, so when a file requires approval, the verification process immediately uses these pre-configured credentials rather than requiring identity verification at the moment of approval. This eliminates delays in multi-approval workflows.
Solution Approach 2:
The patent enables self-service approval where approvers can independently authenticate and approve files using their NFTs without requiring coordination with other approvers or manual verification. The smart contracts automatically track which approvers have signed off, eliminating the need for administrative oversight and reducing the time required for multi-approval processes.
3Measurement precision
If unique identification is provided for each non-fungible token, then the authenticity verification is improved, but the system complexity for managing multiple tokens increases
Solution Approach 1:
The patent creates a universal NFT authentication system where a single NFT structure serves multiple functions: it identifies the approver, verifies their authority, records their approval, and enables audit tracking. This multi-functional design eliminates the need for separate systems for each function, reducing overall complexity despite the precision required for authenticity verification.
Solution Approach 2:
The patent introduces the blockchain as an intermediary layer that manages the complexity of NFT issuance, storage, and verification. Rather than requiring the approval system to directly manage token lifecycles, the blockchain intermediary handles token creation, validation, and tracking automatically through smart contracts, simplifying the overall system architecture while maintaining high verification precision.
Data Source
AI summary
Systems for using bifurcated non-fungible tokens for transaction approval are provided. Systems may include a blockchain, a memory and a processor. The processor may, in a pre-approval stage: mint an identity block for each approver included in a plurality of approvers, upload each identity block to the blockchain and assign a non-fungible token to each approver. The processor may, in an approval stage: receive a file for approval; label the file with a file identifier; identify a subset of approvers for file approval; mint an approval block including the file identifier and an entry slot for each non-fungible token associated with each approver included include in the subset; initiate an approval process by the subset of approvers; receive the non-fungible token that identifies the approver; place each received token within an entry slot of the approval block; upload the approval block to a blockchain; validate the approval block and close the approval block.