Blockchain Token Protocol Using Melt-and-Mint Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Blockchain-based digital cash systems face challenges in validating recent token transactions efficiently, particularly due to the need for extensive checks and the potential bottlenecks created by delegated entities during peak times.
Innovation Solution
A 'melt and mint' protocol is introduced, allowing tokens to be 'melted' (removed) and 'minted' (re-issued) with reduced checks by delegated entities, minimizing their role to only validate tokens between specific transactions, thus reducing the number of checks required for validation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a centralized database or server is used to manage digital tokens, then the system architecture is simple and easy to manage, but the system becomes a single point of failure and is vulnerable to hacking and data manipulation
Solution Approach 1:
The patent segments the centralized database into a distributed network of nodes, where each node maintains a copy of the blockchain ledger. This segmentation eliminates the single point of failure by distributing data across multiple independent entities, thereby improving reliability while accepting increased architectural complexity as a trade-off for security and resilience.
Solution Approach 2:
The patent introduces cryptographic hashing and consensus algorithms as intermediaries between nodes to validate and secure transactions. These intermediary mechanisms enable nodes to trust each other without requiring a centralized authority, improving reliability through decentralized verification while adding complexity to the system architecture.
2Reliability
If complex cryptographic algorithms and consensus mechanisms are implemented to ensure security, then the system becomes more secure and decentralized, but the processing time and computational resources increase
Solution Approach 1:
The patent implements periodic consensus rounds where nodes validate transactions in batches rather than continuously. This periodic action allows the system to maintain high security through cryptographic verification while reducing average processing time by processing transactions in efficient batches during scheduled consensus events.
Solution Approach 2:
The patent applies partial verification where not all nodes need to validate every transaction completely. Instead, a subset of nodes performs full cryptographic verification while others perform lighter checks, achieving adequate security without the full computational overhead of complete verification by all nodes, thus reducing processing time.
3Reliability
If all transactions are recorded on the blockchain ledger, then transparency and immutability are improved, but the storage requirements and network bandwidth consumption increase
Solution Approach 1:
The patent extracts only the essential transaction data (hashes, timestamps, and critical metadata) onto the blockchain ledger, while storing full transaction details in off-chain databases. This extraction maintains data integrity and immutability for critical information while significantly reducing storage requirements and network bandwidth consumption by keeping detailed data outside the blockchain.
Solution Approach 2:
The patent uses cryptographic hashing to create compact copies of transaction data that are stored on the blockchain. Instead of storing full transaction records, nodes store hash copies that verify data integrity without requiring the actual transaction data to be replicated across all nodes, thereby maintaining data integrity while reducing storage volume.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A computer-implemented method of performing a token protocol using a blockchain, comprising: obtaining a token melt transaction comprising a first input signed by a first party, wherein the first input references a respective output of a first token transfer transaction, wherein the respective output is locked to a first public key of the first party and comprises a first token amount, and a first output locked to a melting public key of the delegated entity and comprising the first token amount; creating a token mint transaction comprising a respective input signed by the delegated entity using a signature corresponding to a minting public key, and a respective output locking a respective amount of the digital asset sufficient to fund one or more respective token transfer transactions, wherein the respective output is locked to a second public key of the first party and comprises the first token amount.