A decentralized identity authentication-based cross-chain transfer system for digital assets for Web3.0

Abstract

This invention relates to blockchain technology and cross-chain transactions of transaction data, specifically to a decentralized identity authentication-based digital asset cross-chain transfer system for Web3.0. The system includes a main chain network for storing and verifying metadata and ownership information of transaction data; a sub-chain network for storing and verifying state information and transaction records of transaction data; a PoTS consensus module for enabling cross-chain transfer of transaction data between the main chain network and the sub-chain network; and a user interface module for providing users with an interface for managing transaction data and conducting cross-chain transactions. This invention enables the transfer and exchange of transaction data between different blockchain networks, improving the liquidity and security of transaction data, reducing the cost and latency of cross-chain transactions, and increasing the reliability and scalability of cross-chain transactions.

Description

Technical Field

[0001] This invention relates to blockchain technology and cross-chain transactions of transaction data, specifically to a decentralized identity authentication digital asset cross-chain transfer system for Web3.0. Background Technology

[0002] Blockchain technology is a distributed ledger technology that utilizes cryptographic principles and a distributed consensus mechanism to achieve decentralization, immutability, and traceability, possessing high security, transparency, and trustworthiness. Blockchain technology can support the storage and trading of various transaction data, one special type of which is non-fungible tokens (NFTs, or simply digital tokens). These are unique and non-fungible transaction data that can represent various items or services in fields such as digital art and game assets. Transaction data is highly innovative and diverse, providing users with rich value and experiences.

[0003] However, due to the isolation and incompatibility between blockchain networks, the liquidity of transaction data is low across different blockchain networks, limiting the application scenarios and market size of transaction data. To address this issue, several cross-chain transaction solutions have emerged, enabling the transfer and exchange of transaction data between different blockchain networks. Currently, there are three main cross-chain transaction solutions: relay solutions, Hashed Timelock Contract (HTLC) solutions, and sidechain / subchain solutions.

[0004] A relay scheme refers to the transfer and exchange of transaction data between different blockchain networks through a centralized or decentralized relay node or institution. The advantages of this scheme are its simplicity and high efficiency; the disadvantages are that it requires trust in a third party, presents security risks, and has a tendency towards centralization.

[0005] The HTLC (Hash-based Cloud Computing) scheme refers to the transfer and exchange of transaction data by establishing smart contracts based on hash locking and time locking on different blockchain networks, under certain conditions. The advantages of this scheme are decentralization and high security; the disadvantages are complex implementation, low efficiency, and the need for mutual agreement between the parties involved.

[0006] Sidechain / subchain solutions involve establishing one or more sidechain or subchain networks on the main chain network. Transaction data is transferred and exchanged on these sidechains or subchains, and synchronized with the main chain network through a consensus mechanism. The advantages of this solution are high scalability and efficiency; the disadvantages are low security and the need to trust the sidechain or subchain network. Summary of the Invention

[0007] To effectively address some issues with existing cross-chain transaction solutions, this invention proposes a decentralized identity authentication-based digital asset cross-chain transfer system for Web3.0, comprising a main chain network, multiple sub-chain networks, a PoTS consensus module, and a user interface module; wherein:

[0008] The mainnet network is used to store and verify metadata and ownership information for transaction data;

[0009] The sub-chain network is used to store and verify the state information and transaction records of transaction data;

[0010] The PoTS consensus module is used to enable cross-chain transfer of transaction data between the main chain network and the sub-chain network.

[0011] The user interface module provides users with an interface for managing transaction data and conducting cross-chain transactions.

[0012] Furthermore, the PoTS consensus module includes a PoS consensus submodule, a Plasma consensus submodule, a cross-chain transfer submodule, a cross-chain monitoring submodule, and a cross-chain optimization submodule; among which:

[0013] The PoS consensus submodule is used to select block producers on the main chain network based on the stake of nodes, and to verify and confirm the blocks submitted by the block producers.

[0014] The Plasma consensus submodule is used to select block producers on the subchain network based on the staking of nodes, and to verify and confirm the blocks submitted by the block producers.

[0015] The cross-chain transfer submodule is used to transfer transaction data between the main chain network and the sub-chain network.

[0016] The cross-chain monitoring submodule is used to monitor and verify cross-chain transactions between the main chain network and the sub-chain network;

[0017] The cross-chain optimization submodule is used to optimize and improve cross-chain transactions between the main chain network and the sub-chain network.

[0018] Furthermore, the cross-chain transfer submodule includes a cross-chain request processing unit, a cross-chain locking unit, a cross-chain unlocking unit, a cross-chain confirmation unit, a cross-chain revocation unit, and a cross-chain fee unit; wherein:

[0019] The cross-chain request processing unit is used to receive and process cross-chain transfer requests for transaction data initiated by users.

[0020] Cross-chain locking units are used to lock transaction data to be transferred on the source chain network and generate corresponding locking proofs.

[0021] The cross-chain unlocking unit is used to unlock locked transaction data on the target chain network based on the locking proof and generate the corresponding unlocking proof.

[0022] The cross-chain confirmation unit is used to release locked transaction data on the source chain network based on the unlocking proof and update the corresponding ownership information;

[0023] The cross-chain revocation unit is used to revoke the escrowed transaction data on the source chain network and the target chain network according to the user's request or timeout conditions, and return it to the original owner;

[0024] Cross-chain fee units are used to charge users fees or distribute rewards on the source chain network and the target chain network based on users' transaction behavior and system rules.

[0025] Furthermore, the cross-chain monitoring submodule includes a cross-chain reward and punishment unit, a cross-chain proof generation unit, a cross-chain proof verification unit, and a cross-chain anomaly handling unit; among which:

[0026] The cross-chain reward and punishment unit is used to reward or punish nodes on the main chain network and sub-chain network based on their cross-chain transaction behavior and the system's rules. This includes: increasing or decreasing a node's equity, staking, allocating or deducting a node's fees or rewards.

[0027] The cross-chain proof generation unit is used to generate and submit corresponding cross-chain proofs on the main chain network and sub-chain networks. Cross-chain proofs include locking proofs, unlocking proofs, and custody proofs.

[0028] The cross-chain proof verification unit is used to verify and confirm the corresponding cross-chain proofs on the main chain network and the sub-chain network;

[0029] The cross-chain anomaly handling unit is used to handle and resolve anomalies that occur during cross-chain transactions on the main chain network and sub-chain networks. Anomalies include timeouts, double-spending, and fraud.

[0030] Furthermore, the cross-chain optimization submodule includes a cross-chain routing selection unit, a cross-chain batch processing unit, a cross-chain parallel processing unit, and a cross-chain dynamic adjustment unit; wherein:

[0031] The cross-chain routing selection unit is used to select the optimal cross-chain routing based on user needs and system status, that is, to select the most suitable source chain network and target chain network for cross-chain transactions;

[0032] The cross-chain batch processing unit is used to process multiple cross-chain transactions in batches according to user needs and system status, that is, to merge multiple cross-chain transactions into one or more blocks for submission and verification;

[0033] The cross-chain parallel processing unit is used to process multiple cross-chain transactions in parallel according to user needs and system status, that is, to assign multiple cross-chain transactions to different block producers or validators for submission and verification.

[0034] The cross-chain dynamic adjustment unit is used to dynamically adjust the parameters of cross-chain transactions according to user needs and system status. The parameters of cross-chain transactions include adjusting the cross-chain transaction fee parameters, reward parameters, timeout parameters, and confirmation parameters.

[0035] Furthermore, the user interface module includes a transaction data display unit, a transaction data operation unit, a cross-chain transaction initiation unit, a cross-chain transaction monitoring unit, a cross-chain transaction evaluation unit, and a cross-chain transaction recommendation unit; wherein:

[0036] The transaction data display unit is used to display the transaction data that users own on different blockchain networks;

[0037] The transaction data operation unit provides users with the functions of creating, modifying, deleting, transferring, and exchanging transaction data.

[0038] Cross-chain transaction initiation unit, which provides users with the function of initiating cross-chain transfer or cross-chain exchange of transaction data;

[0039] The cross-chain transaction monitoring unit provides users with the ability to monitor the status and results of cross-chain transfers or exchanges of transaction data.

[0040] The cross-chain transaction evaluation unit is used to provide users with the function of evaluating and providing feedback on the cross-chain transfer or exchange of transaction data;

[0041] The cross-chain transaction recommendation unit is used to recommend and optimize the routing, price, and time of cross-chain transfers or exchanges of transaction data based on user needs and preferences.

[0042] This invention also proposes a method for cross-chain transfer of digital assets with decentralized identity authentication for Web3.0, including a system for cross-chain transfer of digital assets with decentralized identity authentication for Web3.0. The method specifically includes:

[0043] S1. When receiving a user's request for cross-chain transfer or cross-chain exchange of transaction data;

[0044] S2. Lock or hold the transaction data to be transferred or exchanged on the source chain network and generate corresponding proofs;

[0045] S3. On the target chain network, unlock or exchange locked or escrowed transaction data based on proof, and update the corresponding ownership information;

[0046] S4. Release or revoke locked or escrowed transaction data on the source chain network based on proof, and update the corresponding ownership information.

[0047] This invention enables the transfer and exchange of transaction data between different blockchain networks, improving the liquidity and security of transaction data, reducing the cost and latency of cross-chain transactions, and increasing the reliability and scalability of cross-chain transactions. Attached Figure Description

[0048] Figure 1 This is a schematic diagram of the structure of the digital cross-chain transaction system based on PoTS consensus according to the present invention;

[0049] Figure 2 This is a schematic diagram of the structure of the PoTS consensus module of the present invention;

[0050] Figure 3 This is a schematic diagram of the cross-chain transfer submodule of the present invention;

[0051] Figure 4 This is a schematic diagram of the cross-chain monitoring submodule of the present invention;

[0052] Figure 5 This is a schematic diagram of the cross-chain optimization submodule of the present invention;

[0053] Figure 6 This is a structural schematic diagram of the user interface module of the present invention;

[0054] Figure 7 This is a flowchart illustrating the digital cross-chain transaction method based on PoTS consensus according to the present invention. Detailed Implementation

[0055] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0056] This invention provides a decentralized identity authentication-based cross-chain transfer system for digital assets oriented towards Web3.0, comprising a main chain network, multiple sub-chain networks, a PoTS consensus module, and a user interface module; wherein:

[0057] The mainnet network is used to store and verify metadata and ownership information for transaction data;

[0058] The sub-chain network is used to store and verify the state information and transaction records of transaction data;

[0059] The PoTS consensus module is used to enable cross-chain transfer of transaction data between the main chain network and the sub-chain network.

[0060] The user interface module provides users with an interface for managing transaction data and conducting cross-chain transactions.

[0061] As attached Figure 1 As shown, this embodiment provides a decentralized identity authentication digital asset cross-chain transfer system for Web3.0. In this embodiment, digital assets refer to data traded between data owners and data requesters in the network. The system includes a main chain network, multiple sub-chain networks, a PoTS consensus module, and a user interface module.

[0062] In this embodiment, the main chain network is a network built on blockchain technology for storing and verifying metadata and ownership information of transaction data. The metadata refers to the basic attributes and characteristics of the transaction data, such as name, number, type, description, and source. Ownership information refers to the ownership and control of the transaction data, such as the holder, creator, and authorizer. The main chain network can use any suitable blockchain technology, such as Ethereum, Polkadot, or EOS, and supports the execution of smart contracts. The chaincode includes the following interfaces:

[0063] The StorageMetadata() interface is used to store metadata and ownership information of transaction data on the mainnet. This storage interface records this information within the blockchain's data structure, ensuring its security and immutability.

[0064] The ValidateMetadata() interface is used to verify the validity and correctness of transaction data's metadata and ownership information. This interface allows you to validate data stored on the blockchain to ensure its integrity and consistency.

[0065] The QueryMetadata() interface is used to retrieve and manage metadata information for transaction data. Through this interface, you can query the basic attributes and characteristics of transaction data, such as name, ID, type, description, and source.

[0066] The ValidateOwnership() interface is used to manage ownership information for transaction data, including the holder, creator, and authorizer. Through this interface, ownership information can be tracked and updated, ensuring proper ownership and control of the transaction data.

[0067] In this embodiment, each subchain network is a network built on blockchain technology, used to store and verify the state information and transaction records of transaction data. State information refers to the current status and changes of transaction data, such as location, state, and value. Transaction records refer to the historical operations and behaviors of transaction data, such as transfers, exchanges, and uses. The subchain network can employ any suitable blockchain technology and supports the execution of smart contracts. The chaincode includes the following interfaces:

[0068] The StorageState() interface is used to store transaction state information and transaction records on a subchain network. This storage interface records this information within the blockchain's data structure, ensuring its security and immutability.

[0069] The ValidateState() interface is used to verify the validity and correctness of transaction data's state information and transaction records. Through this interface, data stored on the blockchain can be validated to ensure its integrity and consistency.

[0070] The QueryState() interface is used to retrieve and manage the state information of transaction data. Through this interface, you can query the current status and changes of transaction data, such as location, state, and value.

[0071] The QueryRecord() interface is used to retrieve and manage transaction records. Through this interface, you can query historical operations and behaviors of transaction data, such as transfers, exchanges, and usage.

[0072] In this embodiment, the PoTS consensus module is a cross-chain consensus algorithm based on Proof-of-Stake (PoS) and Plasma technologies, used to achieve cross-chain transfer of transaction data between the main chain network and the sub-chain network. This embodiment provides an implementation method for the PoTS consensus module, which includes a PoS consensus sub-module, a Plasma consensus sub-module, and a cross-chain transfer sub-module; wherein:

[0073] The PoS consensus submodule is a Proof-of-Stake (PoS)-based consensus algorithm used to select block producers on the mainnet network based on node stake, and to verify and confirm the blocks submitted by the block producers. Proof-of-Stake (PoS) is a consensus mechanism that uses node stake as the basis for block production and verification, improving the security and efficiency of the blockchain network. A node's stake can be the number or value of tokens held or staked by the node, or other metrics related to the node's contribution. The PoS consensus submodule can use any suitable PoS consensus algorithm when selecting block producers based on node stake, such as Era of Stake (PoA), Delegated Proof-of-Stake (DPoS), and Proof-of-Stake (PPoS). The chaincode includes the following interfaces:

[0074] BlockProducer(): Used to select block producers based on a node's stake. The block producer selection interface allows you to determine which nodes will participate in block production based on the amount or value of tokens held or staked, or other relevant metrics, ensuring fairness and security.

[0075] The ValidateBlock() interface is used to verify and confirm blocks submitted by block producers. Through this interface, blocks generated by block producers can be validated, including checking the block's validity, the legality of transactions, and other security and rule constraints.

[0076] The ImpawnEntity() interface is used for nodes to perform staking operations. Through the staking interface, nodes can lock up their tokens or their value to demonstrate their contribution to the network and their chance to earn blocks.

[0077] The `RewardEntity()` interface is used to reward nodes that participate in staking. Through this interface, rewards can be calculated and distributed based on a node's staked amount and contribution level, incentivizing node participation and continued contribution.

[0078] The PoSCA() interface is used to implement specific PoS consensus algorithms. Through this interface, you can define and execute specific consensus logic such as node stake selection, block verification, and reward distribution.

[0079] The Plasma consensus submodule is a consensus algorithm based on Plasma technology used to select block producers on the subchain network based on node staking, and to verify and confirm the blocks submitted by the block producers. Plasma technology is a technique that layers the main chain network and subchain networks, improving the scalability and efficiency of the blockchain network. Node staking refers to a node locking a certain amount or value of tokens on the main chain network to qualify for block production and verification on the subchain network. The Plasma consensus submodule can use any suitable Plasma consensus algorithm in the process of selecting block producers based on node staking, such as Minimum Viable Plasma (MVP), Plasma Cash, Plasma Debit, etc. The chaincode includes the following interfaces:

[0080] The `BlockProducerSub()` interface is used to select block producers based on a node's staking. This interface determines which nodes will participate in block production on the sub-chain network based on the amount or value of tokens locked by the node on the main chain network, ensuring fairness and security.

[0081] The `ValidateBlockSub()` interface is used to verify and confirm blocks submitted by block producers. Through this interface, blocks generated by block producers can be validated, including checking the block's validity, the legality of transactions, and other security and rule constraints.

[0082] The ImpawnEntitySub() interface is used by nodes to perform staking operations, locking a certain amount or value of tokens on the main chain network. Through the staking interface, nodes can demonstrate their contributions to the sub-chain network and gain the right to produce blocks.

[0083] The PlasmaCA() interface is used to implement specific Plasma consensus algorithms. Through this interface, you can define and execute specific consensus logic such as node staking selection, block verification, and reward distribution.

[0084] The `InteractWithMainchain()` interface is used to interact with the main chain network, including operations such as locking tokens, submitting blocks, and validating blocks. Through this main chain interaction interface, the state information and transaction records of sub-chain networks can be stored on the main chain, and coordinated and synchronized with the main chain.

[0085] The cross-chain transfer submodule is used for cross-chain transfer of transaction data between the main chain network and the sub-chain network. This submodule includes a cross-chain request processing unit, a cross-chain locking unit, a cross-chain unlocking unit, and a cross-chain confirmation unit; wherein:

[0086] The cross-chain request processing unit is used to receive and process user-initiated cross-chain transfer requests for transaction data. This unit can select the optimal cross-chain route based on the user's needs and the system's status, i.e., select the most suitable source and target chain networks for the cross-chain transfer. Users can initiate cross-chain transfer requests for transaction data through the user interface module, specifying information such as the transaction data to be transferred, the target address, and the transfer quantity. The chaincode includes the following interfaces:

[0087] The EntityTransfer() interface is used to receive cross-chain transfer requests for transaction data initiated by users.

[0088] The SelectRouter() interface is used to select the optimal cross-chain router, determining the source and target blockchain networks. Through this interface, the most suitable source and target blockchain networks can be chosen based on user needs and system status to achieve cross-chain transfer of transaction data.

[0089] A cross-chain locking unit is a unit used to lock transaction data to be transferred on the source chain network and generate corresponding lock proofs. This unit can lock transaction data by executing smart contracts or sending transactions on the source chain network to prevent transaction data from being tampered with or double-spended during cross-chain transfer. A lock proof is evidence that the transaction data has been locked on the source chain network, and can be information such as block hashes, transaction hashes, and signatures generated on the source chain network. The chaincode includes the following interfaces:

[0090] The LockEntity() interface is used to lock transaction data to be transferred on the source chain network. Through this interface, smart contracts can be executed or transactions can be sent to lock transaction data, ensuring that the data is not tampered with or double-spended during cross-chain transfers.

[0091] The LockEntityProof() interface is used to generate proofs related to the locking of transaction data. Through this lock proof generation interface, evidence can be generated proving that transaction data has been locked on the source chain network, based on information such as block hashes, transaction hashes, and signatures generated on the source chain network.

[0092] A cross-chain unlocking unit is a unit used to unlock locked transaction data on a target blockchain network based on a locking proof and generate a corresponding unlocking proof. This unit can unlock transaction data by executing a smart contract or sending a transaction on the target blockchain network, thereby completing the creation or updating of transaction data on the target blockchain network. An unlocking proof is evidence that transaction data has been unlocked on the target blockchain network, and can be information such as block hashes, transaction hashes, and signatures generated on the target blockchain network. The chaincode includes the following interfaces:

[0093] The `UnlockEntity()` interface is used to unlock locked transaction data on the target blockchain network based on a locking proof. Through this interface, smart contracts can be executed or transactions can be sent to unlock transaction data, completing the creation or updating of the transaction data on the target blockchain network.

[0094] The `UnlockEntityProof()` interface is used to generate proof related to unlocking transaction data. Through this proof generation interface, evidence can be generated proving that transaction data has been unlocked on the target blockchain network, based on information such as block hashes, transaction hashes, and signatures generated on the target blockchain.

[0095] The cross-chain confirmation unit is used to release locked transaction data on the source chain network based on unlocking proofs and update the corresponding ownership information. This unit can release transaction data by executing smart contracts or sending transactions on the source chain network, thus completing the deletion or updating of transaction data on the source chain network. Ownership information refers to the ownership and control of the transaction data, such as the holder, creator, and authorizer. This chaincode includes the following interfaces:

[0096] The `ReleaseEntity()` interface is used to release locked transaction data on the source chain network based on an unlocking proof. Through this interface, smart contracts can be executed or transactions can be sent to release transaction data, thus deleting or updating the transaction data on the source chain network.

[0097] The UpdateOwnership() interface is used to update the ownership information of transaction data. Through this interface, the ownership information of transaction data can be updated based on the unlocking proof, including information such as the holder, creator, and authorizer.

[0098] In this embodiment, the user interface module is a module that provides users with an interface for managing transaction data and conducting cross-chain transactions. This module includes a transaction data display unit, a transaction data operation unit, a digital cross-chain transaction initiation unit, a digital cross-chain transaction monitoring unit, a digital cross-chain transaction evaluation unit, and a digital cross-chain transaction recommendation unit; wherein:

[0099] The transaction data display unit is used to showcase a user's transaction data across different blockchain networks. This unit allows users to categorize, sort, and filter transaction data according to their needs and preferences, facilitating their viewing and management of their transaction data. This interface module includes the following interfaces:

[0100] The AllDataById() interface is used to query all transaction data based on a user's unique DID and obtain ordered, categorized data.

[0101] The transaction data operation unit is a unit that provides users with functions such as creating, modifying, deleting, transferring, and exchanging transaction data. This unit can verify and process user input information according to user needs and system status to complete user operations on transaction data; the interface includes the following interfaces:

[0102] The ValidateOwner() interface is used to verify whether the user performing the operation is legitimate and whether they own the data being operated on.

[0103] The CreateData() interface is used to create data.

[0104] The UpdateData() interface is used to modify the data currently being operated on by the owner. Before calling this interface, the ValidateOwner() interface must be called to verify the legitimacy of the operator.

[0105] The DeleteData() interface is used to delete the data currently being operated on by the owner. Before calling this interface, the ValidateOwner() interface must be called to verify the operator's legitimacy.

[0106] The cross-chain transaction initiation unit is a unit that provides users with the function of initiating cross-chain transfers or exchanges of transaction data. This unit can verify and process the information input by the user according to the user's needs and the system status to complete the user's cross-chain transaction request for transaction data; the interface includes the following interfaces:

[0107] The OpData() interface is used to submit transfer and exchange requests. Before calling this interface, the ValidateOwner() interface must be called to verify the operator's legitimacy. After calling this interface, it will invoke the EntityTransfer() interface within the cross-chain request processing unit.

[0108] The cross-chain transaction monitoring unit is a function that provides users with the ability to monitor the status and results of cross-chain transfers or exchanges of transaction data. This unit can acquire and display the proofs and information generated by the cross-chain transfer submodule according to user needs and system status, allowing users to easily understand and grasp the cross-chain transaction status of their data. This interface includes the following:

[0109] The QueryTrStatus() interface is used to query the status of cross-chain transfers of transaction data. Through this interface, users can obtain the current status of the cross-chain transfer, such as in progress, completed, or failed.

[0110] The QueryTrResult() interface is used to query the results of cross-chain transfers of transaction data. Through this interface, users can obtain the final result of the cross-chain transfer, such as whether the transfer was successful or failed.

[0111] The QueryTrRecord() interface is used to retrieve the historical records of cross-chain transactions. Through this interface, users can view past cross-chain transaction records, including information such as the transfer time, on-chain transaction hash, and transfer quantity.

[0112] The cross-chain transaction evaluation unit is a function that provides users with the ability to evaluate and provide feedback on cross-chain transfers or exchanges of transaction data. This unit can verify and process user-inputted evaluations and feedback based on user needs and system status to complete the user's evaluation and feedback on cross-chain transactions. This interface includes the following: The SubmitReview() interface: used by users to submit evaluations and feedback on cross-chain transfers or exchanges of transaction data. Through this interface, users can input evaluation content, ratings, and other information to submit their evaluation and feedback to the system.

[0113] The ValidateReview() interface is used to validate user-submitted reviews and feedback. Through this interface, the system can verify user-submitted reviews to ensure their validity and legitimacy.

[0114] The ProcessReview() interface is used to process user-submitted reviews and feedback. Through this interface, the system can perform appropriate actions based on user reviews and feedback, such as recording reviews and updating ratings.

[0115] The QueryAllReview() interface is used to display user reviews and feedback to other users or relevant parties. Through this interface, the system can display user reviews and feedback on an appropriate screen for other users to reference and understand.

[0116] The QueryReviewById() interface is used to query user reviews and feedback on cross-chain transactions. Through this interface, users can retrieve their previous reviews and feedback for review and reference.

[0117] The cross-chain transaction recommendation unit is a functional unit used to recommend and optimize the routing, price, and time of cross-chain transfers or exchanges of transaction data based on user needs and preferences. This unit can analyze and process the proofs and information generated by the cross-chain transfer submodule according to user needs and system status to complete the recommendation and optimization of cross-chain transactions for user data. This interface includes the following interfaces:

[0118] The GetUserDemand() interface is used to retrieve a user's request information for cross-chain transfers or exchanges of transaction data. This interface allows you to obtain the user's requirements, such as the target chain, transfer quantity, and transfer type.

[0119] The RouterAnalysis() interface is used to analyze cross-chain routing between different chains. Through this interface, you can analyze cross-chain transfer routes between different chains based on user needs and system status, including factors such as chain connectivity, stability, and transaction fees.

[0120] The OptimizeTime() interface is used to optimize the time for cross-chain transfers or exchanges of transaction data. Through this interface, the timing of cross-chain transfers can be optimized based on user needs and system status to reduce transfer time or select the optimal transfer opportunity.

[0121] The `GenerateRecommendation()` interface is used to generate recommended results for cross-chain transfers or exchanges of transaction data. Through this interface, recommended cross-chain transfer schemes, including information such as routing, price, and time, can be generated based on user needs and system analysis results.

[0122] The `GetRecommendation()` interface is used to display the generated recommendation results to the user. Through this interface, the system can present cross-chain transfer recommendations to the user, allowing them to view and select the appropriate option.

[0123] This invention also relates to a method for cross-chain transfer of digital assets with decentralized identity authentication for Web3.0, including a system for cross-chain transfer of digital assets with decentralized identity authentication for Web3.0, as shown in the appendix. Figure 7 As shown, the method includes the following steps:

[0124] Step S1: Receive a user-initiated cross-chain transfer or exchange request for transaction data. Specifically, the user can initiate a cross-chain transfer or exchange request for transaction data through the user interface module, specifying information such as the transaction data to be transferred or exchanged, the target address, and the quantity to be transferred. If the cross-chain request processing unit receives and processes the user-initiated cross-chain transfer or exchange request, it selects the optimal cross-chain route based on the user's needs and the system's status. For example, if the user needs a method that saves more time or computing resources, the optimal routing path can be selected based on the user's chosen scheme, i.e., the most suitable source chain network and target chain network are selected for cross-chain transfer.

[0125] Step S2 involves locking the transaction data to be transferred or exchanged on the source chain network and generating corresponding proof. Specifically, the cross-chain locking unit locks the transaction data to be transferred or exchanged on the source chain network and generates corresponding locking proof. The locking proof is evidence that the transaction data has been locked on the source chain network, which can be information such as block hashes, transaction hashes, and signatures generated on the source chain network.

[0126] Step S3: Unlock the locked transaction data on the target blockchain network based on the proof and generate the corresponding proof. Specifically, the cross-chain unlocking unit unlocks the locked transaction data on the target blockchain network based on the locking proof and generates the corresponding unlocking proof; the unlocking proof refers to evidence that the transaction data has been unlocked on the target blockchain network, which can be information such as block hash, transaction hash, and signature generated on the target blockchain network.

[0127] Step S4 involves releasing the locked transaction data on the source chain network based on the proof and updating the corresponding ownership information. Specifically, the cross-chain confirmation unit releases the locked transaction data on the source chain network based on the unlocking proof and updates the corresponding ownership information. Ownership information refers to the ownership and control of the transaction data, such as the holder, creator, and authorizer.

[0128] The digital cross-chain transaction system and method based on PoTS consensus of this invention can effectively solve some problems existing in current cross-chain transaction solutions, and has high practicality and commercial value. This invention can be widely used in fields such as digital art and game assets, and has unique technical advantages and innovations, making it worthy of patent protection.

[0129] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A decentralized identity authentication-based cross-chain transfer system for digital assets oriented towards Web3.0, characterized in that, It includes a main chain network, multiple sub-chain networks, a PoTS consensus module, and a user interface module; wherein: The mainnet network is used to store and verify metadata and ownership information for transaction data; The sub-chain network is used to store and verify the state information and transaction records of transaction data; The PoTS consensus module is used to enable cross-chain transfer of transaction data between the main chain network and the sub-chain network. The PoTS consensus module includes a PoS consensus sub-module, a Plasma consensus sub-module, a cross-chain transfer sub-module, a cross-chain monitoring sub-module, and a cross-chain optimization sub-module. Among them: The PoS consensus submodule is used to select block producers on the main chain network based on the stake of nodes, and to verify and confirm the blocks submitted by the block producers. The Plasma consensus submodule is used to select block producers on the subchain network based on the staking of nodes, and to verify and confirm the blocks submitted by the block producers. The cross-chain transfer submodule is used for cross-chain transfer of transaction data between the main chain network and the sub-chain network. The cross-chain transfer submodule includes a cross-chain request processing unit, a cross-chain locking unit, a cross-chain unlocking unit, a cross-chain confirmation unit, a cross-chain revocation unit, and a cross-chain fee unit; wherein: The cross-chain request processing unit is used to receive and process cross-chain transfer requests for transaction data initiated by users. Cross-chain locking units are used to lock transaction data to be transferred on the source chain network and generate corresponding locking proofs. The cross-chain unlocking unit is used to unlock locked transaction data on the target chain network based on the locking proof and generate the corresponding unlocking proof. The cross-chain confirmation unit is used to release locked transaction data on the source chain network based on the unlocking proof and update the corresponding ownership information; The cross-chain revocation unit is used to revoke the escrowed transaction data on the source chain network and the target chain network according to the user's request or timeout conditions, and return it to the original owner; Cross-chain fee units are used to charge users fees or distribute rewards on the source chain network and the target chain network based on users' transaction behavior and system rules. The cross-chain monitoring submodule is used to monitor and verify cross-chain transactions between the main chain network and the sub-chain network; The cross-chain optimization submodule is used to optimize and improve cross-chain transactions between the main chain network and sub-chain networks. The cross-chain optimization submodule includes a cross-chain routing selection unit, a cross-chain batch processing unit, a cross-chain parallel processing unit, and a cross-chain dynamic adjustment unit; wherein: The cross-chain routing selection unit is used to select the optimal cross-chain routing based on user needs and system status, that is, to select the most suitable source chain network and target chain network for cross-chain transactions; The cross-chain batch processing unit is used to process multiple cross-chain transactions in batches according to user needs and system status, that is, to merge multiple cross-chain transactions into one or more blocks for submission and verification; The cross-chain parallel processing unit is used to process multiple cross-chain transactions in parallel according to user needs and system status, that is, to assign multiple cross-chain transactions to different block producers or validators for submission and verification. The cross-chain dynamic adjustment unit is used to dynamically adjust the parameters of cross-chain transactions according to user needs and system status. The parameters of cross-chain transactions include adjusting the cross-chain transaction fee parameters, reward parameters, timeout parameters, and confirmation parameters. The user interface module provides users with an interface for managing transaction data and conducting cross-chain transactions.

2. The decentralized identity authentication digital asset cross-chain transfer system for Web3.0 according to claim 1, characterized in that, The cross-chain monitoring submodule includes a cross-chain reward and punishment unit, a cross-chain proof generation unit, a cross-chain proof verification unit, and a cross-chain anomaly handling unit; among which: The cross-chain reward and punishment unit is used to reward or punish nodes on the main chain network and sub-chain network based on their cross-chain transaction behavior and the system's rules. This includes: increasing or decreasing a node's equity, staking, allocating or deducting a node's fees or rewards. The cross-chain proof generation unit is used to generate and submit corresponding cross-chain proofs on the main chain network and sub-chain networks. Cross-chain proofs include locking proofs, unlocking proofs, and custody proofs. The cross-chain proof verification unit is used to verify and confirm the corresponding cross-chain proofs on the main chain network and the sub-chain network; The cross-chain anomaly handling unit is used to handle and resolve anomalies that occur during cross-chain transactions on the main chain network and sub-chain networks. Anomalies include timeouts, double-spending, and fraud.

3. The decentralized identity authentication digital asset cross-chain transfer system for Web3.0 according to claim 1, characterized in that, The user interface module includes a transaction data display unit, a transaction data operation unit, a cross-chain transaction initiation unit, a cross-chain transaction monitoring unit, a cross-chain transaction evaluation unit, and a cross-chain transaction recommendation unit; among which: The transaction data display unit is used to display the transaction data that users own on different blockchain networks; The transaction data operation unit provides users with the functions of creating, modifying, deleting, transferring, and exchanging transaction data. Cross-chain transaction initiation unit, which provides users with the function of initiating cross-chain transfer or cross-chain exchange of transaction data; The cross-chain transaction monitoring unit provides users with the ability to monitor the status and results of cross-chain transfers or exchanges of transaction data. The cross-chain transaction evaluation unit is used to provide users with the function of evaluating and providing feedback on the cross-chain transfer or exchange of transaction data; The cross-chain transaction recommendation unit is used to recommend and optimize the routing, price, and time of cross-chain transfers or exchanges of transaction data based on user needs and preferences.

4. A method for cross-chain transfer of digital assets with decentralized identity authentication for Web3.0, characterized in that, The method of the decentralized identity authentication digital asset cross-chain transfer system for Web3.0, as described in claim 1, specifically includes: S1. Receive cross-chain transfer or cross-chain exchange requests for transaction data initiated by users; S2. Lock or hold the transaction data to be transferred or exchanged on the source chain network and generate corresponding proofs; S3. On the target chain network, unlock or exchange locked or escrowed transaction data based on proof, and update the corresponding ownership information; S4. Release or revoke locked or escrowed transaction data on the source chain network based on proof, and update the corresponding ownership information.

Images