Blockchain Token Locking Scripts for Native-Asset Coupling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing blockchain token creation methods decouple newly created tokens from their native assets, requiring burdensome coordination and preventing mass adoption.
Innovation Solution
Tokens are represented by single units of underlying digital assets, with a locking script that includes a variable and constant component, ensuring self-immutability and preservation of token amount until redemption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If tokens are created using additional data fields in transaction outputs, then tokens can be defined and transferred on the blockchain, but the tokens become decoupled from native assets requiring burdensome coordination
Solution Approach 1:
The patent merges the token data structure with the native asset transaction structure by embedding token-specific data fields directly within the transaction output script. This integration ensures that tokens remain coupled with native assets throughout their lifecycle, eliminating the need for separate coordination mechanisms while maintaining token functionality.
Solution Approach 2:
The transaction output structure is designed to serve dual purposes: it functions both as a native asset transfer and as a token definition/transfer mechanism. By making the transaction structure universal, the patent eliminates the need for separate token coordination systems, allowing the same infrastructure to handle both native assets and tokens seamlessly.
2Adaptability or versatility
If tokens are created as separate from native assets, then tokens can have independent functionality, but mass adoption is prevented due to coordination requirements
Solution Approach 1:
The token system is designed to be self-sufficient by embedding all necessary token definition and enforcement logic directly within the transaction script. The token mechanics are self-executing and self-validating, requiring no external coordination or separate management systems, thereby simplifying operations and enabling mass adoption.
Solution Approach 2:
The token locking script is divided into variable components (token-specific parameters) and constant components (enforcement rules). This segmentation allows flexible token functionality through variable parameters while maintaining simple, standardized enforcement mechanisms through constant rules, making the system both versatile and easy to operate.
3Adaptability or versatility
If token amount can be altered or leaked, then token flexibility increases, but token security and integrity are compromised
Solution Approach 1:
The token locking script employs dynamic evaluation where the token amount is verified against the actual transaction output amount at execution time. This dynamic check ensures that while token amounts can be flexibly defined in the script, any attempt to alter or leak amounts during transaction execution will be detected and rejected, maintaining both flexibility and integrity.
Solution Approach 2:
The token mechanics include built-in feedback verification that checks whether the token amount specified in the locking script matches the actual amount locked in the transaction output. This feedback mechanism prevents amount leakage or unauthorized alteration by immediately detecting discrepancies and invalidating the transaction, thereby preserving token integrity while allowing flexible amount definition.
Data Source
AI summary
A token transaction comprising a first token output, the first token output comprising a first token locking script and a first token amount, wherein the first token locking script comprises a variable component and a constant component, wherein the variable component comprises a first payment address, embedded in a payment template, and wherein the constant component comprises a token mechanics sub-component.