Granted Patent B2

US 12,659,133 · App. 18/387,336 · Granted Jun 16, 2026

Inventor: Gengliang Zhu (Shenzhen, CN)

Assignee: TENCENT TECHNOLOGY (SHENZHEN) COMPANY LIMITED

H04L9/0819G06Q20/38G06Q20/40H04L9/50

Abstract

Claims (60)

1 . An asset transferring method based on multiple blockchains, the multiple blockchains comprising a first chain, a second chain, and a target chain, the method being performed by a first consensus node in a first chain network corresponding to the first chain and a second consensus node in a second chain network corresponding to the second chain, and the method comprising:

obtaining, by the first consensus node, a first cross-chain asset transfer-out request transmitted by a service object for a first cross-chain transfer-out transaction, the first cross-chain asset transfer-out request carrying service data information configured for the service object;

writing, by the first consensus node, transaction data of the first cross-chain transfer-out transaction into a first cross-chain bridge contract on the first chain; and

in response to determining, by the first consensus node, that the service object has a cross-chain asset transfer-out permission based on the first cross-chain bridge contract and the service data information:

invoking, by the first consensus node, a first asset contract on the first chain to lock a first asset;

generating, by the first consensus node, a first cross-chain event corresponding to the first cross-chain transfer-out transaction, wherein the first cross-chain event is used for instructing a cross-chain relay to transmit, in response to obtaining a first cross-chain transfer-in transaction corresponding to the first cross-chain transfer-out transaction through construction, the first cross-chain transfer-in transaction to a second consensus node in the second chain network corresponding to the second chain;

receiving, by the first consensus node, a second cross-chain transfer-in transaction transmitted by the cross-chain relay for a second asset, wherein the second cross-chain transfer-in transaction is constructed in response to the cross-chain relay reading a second cross-chain event corresponding to a second cross-chain transfer-out transaction from the second consensus node, and the second cross-chain event is generated by the second consensus node based on the second cross-chain transfer-out transaction submitted by the service object for the second asset;

writing, by the first consensus node, transaction data of the second cross-chain transfer-in transaction into the first cross-chain bridge contract, and performing transaction verification on the second cross-chain transfer-in transaction based on the first cross-chain bridge contract to obtain a first transaction verification result; and

invoking, by the first consensus node, in response to the first transaction verification result indicating that the transaction verification succeeds and by using an asset contract invocation method in the first cross-chain bridge contract, the first asset contract to unlock the locked first asset on the first chain.

2 . The method according to claim 1 , wherein the invoking a first asset contract on the first chain to lock the first asset, and generating a first cross-chain event corresponding to the first cross-chain transfer-out transaction comprises:

invoking, by the first consensus node, a cross-chain permission query method in the first cross-chain bridge contract, to generate a transfer-out permission verification request, wherein the transfer-out permission verification request is used for causing a target consensus node to invoke a cross-chain authorization management contract on the target chain to query source configuration data information of the service object;

receiving, by the first consensus node, the source configuration data information returned by the target consensus node, and performing information comparison on the source configuration data information and the service data information to obtain an information comparison result;

determining, by the first consensus node, that the service object has the cross-chain asset transfer-out permission in response to the information comparison result indicating that the comparison succeeds;

invoking, by the first consensus node, the first asset contract to switch an asset state of the first asset from a first state to a second state; and

generating, by the first consensus node, the first cross-chain event corresponding to the first cross-chain transfer-out transaction in response to the asset state of the first asset being the second state.

3 . The method according to claim 1 , wherein the second cross-chain transfer-in transaction is a transaction in a first cross-chain transaction request transmitted by the cross-chain relay; the first cross-chain transaction request carries first transaction signature information obtained by the cross-chain relay by signing the second cross-chain transfer-in transaction through private key information; and

the writing transaction data of the second cross-chain transfer-in transaction into the first cross-chain bridge contract, and performing transaction verification on the second cross-chain transfer-in transaction based on the first cross-chain bridge contract to obtain a first transaction verification result comprises:

using, by the first consensus node, the second cross-chain transfer-in transaction obtained from the first cross-chain transaction request as a to-be-processed transaction, and writing transaction data of the to-be-processed transaction into the first cross-chain bridge contract;

invoking, by the first consensus node, a signature verification method in the first cross-chain bridge contract to obtain public key information corresponding to the private key information of the cross-chain relay, and performing signature verification on the first transaction signature information based on the public key information; using the second cross-chain transfer-in transaction corresponding to the first transaction signature information as a to-be-verified transaction in response to that the signature verification succeeds; and

performing, by the first consensus node, transaction comparison on the to-be-processed transaction and the to-be-verified transaction by using a transaction comparison method in the first cross-chain bridge contract, to obtain a first transaction comparison result, and using the first transaction comparison result as the first transaction verification result.

4 . The method according to claim 1 , wherein an asset attribute state of the first asset is a first attribute state; and in response to a mapping asset attribute state of the second asset being changed from the first attribute state to a second attribute state, the method further comprises:

changing, by the first consensus node, in response to invoking the first asset contract to unlock the locked first asset on the first chain, the asset attribute state of the first asset from the first attribute state to the second attribute state.

5 . The method according to claim 1 , wherein the method further comprises:

specifying, by the first consensus node, an asset use permission of the first asset corresponding to the first cross-chain transfer-out transaction in response to writing the transaction data of the first cross-chain transfer-out transaction into the first cross-chain bridge contract.

6 . The method according to claim 1 , wherein the method further comprises:

obtaining, by the second consensus node, the first cross-chain transfer-in transaction transmitted by the cross-chain relay for the first asset after the cross-chain relay reads the first cross-chain event corresponding to the first cross-chain transfer-out transaction from the first consensus node;

writing, by the second consensus node, transaction data of the first cross-chain transfer-in transaction into a second cross-chain bridge contract on the second chain; and

invoking, by the second consensus node, a second asset contract indicated by the second cross-chain bridge contract, to cast a second asset having same asset content as the first asset on the second chain.

7 . The method according to claim 6 , wherein the invoking a second asset contract indicated by the second cross-chain bridge contract, to cast a second asset having same asset content as the first asset on the second chain comprises:

performing, by the second consensus node, in response to invoking the second cross-chain bridge contract to execute the first cross-chain transfer-in transaction, transaction verification on the first cross-chain transfer-in transaction to obtain a second transaction verification result; and

invoking, by the second consensus node, in response to the second transaction verification result indicating that the transaction verification succeeds, the second asset contract indicated by the second cross-chain bridge contract, to cast the second asset having the same asset content as the first asset on the second chain.

8 . The method according to claim 7 , wherein the first cross-chain transfer-in transaction is a transaction in a second cross-chain transaction request transmitted by the cross-chain relay; the second cross-chain transaction request carries second transaction signature information obtained by the cross-chain relay by signing the first cross-chain transfer-in transaction through private key information; and

the performing, by the second consensus node, transaction verification on the first cross-chain transfer-in transaction to obtain a second transaction verification result comprises:

using, by the second consensus node, the first cross-chain transfer-in transaction obtained from the second cross-chain transaction request as a reference transaction;

invoking, by the second consensus node, a signature verification method in the second cross-chain bridge contract to obtain public key information corresponding to the private key information of the cross-chain relay, and performing signature verification on the second transaction signature information based on the public key information; using the first cross-chain transfer-in transaction corresponding to the second transaction signature information as a to-be-matched transaction in response to that the signature verification succeeds; and

performing, by the second consensus node, transaction comparison on the reference transaction and the to-be-matched transaction by using a transaction comparison method in the second cross-chain bridge contract, to obtain a second transaction comparison result, and using the second transaction comparison result as the second transaction verification result.

9 . The method according to claim 6 , wherein the method further comprises:

invoking, by the second consensus node, in response to casting the second asset having the same asset content as the first asset on the second chain, an event generation method in the second cross-chain bridge contract, to obtain an event identifier of the first cross-chain event from the second cross-chain transaction request transmitted by the cross-chain relay based on the first cross-chain transfer-in transaction, and generating a cross-chain transaction completion event associated with the event identifier, wherein the cross-chain transaction completion event is used for representing that the first asset is successfully transferred from the first chain to the second chain.

10 . The method according to claim 9 , wherein the method further comprises:

obtaining, by the second consensus node, an event query request transmitted by the service object for the first cross-chain event, wherein the event query request carries the event identifier of the first cross-chain event; and

returning, by the second consensus node, an event completion notification message for the first cross-chain event to the service object in response to the cross-chain transaction completion event associated with the event identifier is-being queried by using an event query method in the second cross-chain bridge contract.

11 . The method according to claim 10 , wherein the method further comprises:

obtaining, by the second consensus node, a derivative service execution request transmitted by the service object based on the event completion notification message;

invoking, by the second consensus node, based on a derivative service in the derivative service execution request, the second cross-chain bridge contract to obtain a transaction parameter in the first cross-chain transfer-in transaction, wherein the transaction parameter is determined based on an asset use permission of the first asset corresponding to the first cross-chain transfer-in transaction; and

allowing, by the second consensus node, in response to determining that the service object has a permission of invoking a derivative service contract on the second chain based on the transaction parameter, the service object to invoke the derivative service contract to execute a derivative service corresponding to the second asset.

12 . The method according to claim 11 , wherein the transaction parameter comprises an asset transfer parameter; the asset transfer parameter is used for indicating to transfer the second asset from the service object to a derivative service object corresponding to a derivative service associated with the service object; and the method further comprises:

changing, by the second consensus node, in response to invoking the derivative service contract to execute the derivative service corresponding to the second asset, a mapping asset attribute state of the second asset from a first attribute state to a second attribute state on the second chain in response to determining to transfer the second asset from the service object to the derivative service object based on the asset transfer parameter.

13 . The method according to claim 6 , wherein the method further comprises:

obtaining, by the second consensus node, a second cross-chain asset transfer-out request transmitted by the service object for a second cross-chain transfer-out transaction, wherein the second cross-chain asset transfer-out request carries the service data information; and the second cross-chain asset transfer-out request is used for indicating the second consensus node to transfer the second asset from the second chain back to the first chain through the cross-chain relay;

writing, by the second consensus node, transaction data of the second cross-chain transfer-out transaction carried in the second cross-chain asset transfer-out request into the second cross-chain bridge contract on the second chain; and

invoking, by the second consensus node, in response to determining that the service object has a cross-chain asset transfer-back permission based on the second cross-chain bridge contract and the service data information, the second asset contract to lock the second asset, and generating a second cross-chain event corresponding to the second cross-chain transfer-out transaction, wherein the second cross-chain event is used for indicating the cross-chain relay to transmit, in response to obtaining a second cross-chain transfer-in transaction corresponding to the second cross-chain transfer-out transaction through construction, the second cross-chain transfer-in transaction to the first consensus node; and the first consensus node is configured to invoke, in response to writing transaction data of the second cross-chain transfer-in transaction into the first cross-chain bridge contract on the first chain, the first asset contract indicated by the first cross-chain bridge contract to unlock the locked first asset on the first chain.

14 . The method according to claim 13 , wherein the invoking, in response to determining that the service object has a cross-chain asset transfer-back permission based on the second cross-chain bridge contract and the service data information, the second asset contract to lock the second asset, and generating a second cross-chain event corresponding to the second cross-chain transfer-out transaction comprises:

invoking, by the second consensus node, a cross-chain permission query method in the second cross-chain bridge contract, to generate a transfer-back permission verification request, wherein the transfer-back permission verification request is used for indicating a target consensus node to invoke a cross-chain authorization management contract on the target chain to query source configuration data information of the service object;

receiving, by the second consensus node, the source configuration data information returned by the target consensus node based on the transfer-back permission verification request, and performing information comparison on the source configuration data information and the service data information to obtain an information comparison result;

determining, by the second consensus node, that the service object has the cross-chain asset transfer-back permission in response to the information comparison result indicating that the comparison succeeds; and

invoking, by the second consensus node, the second asset contract to switch an asset state of the second asset from a first state to a second state, and generating the second cross-chain event corresponding to the second cross-chain transfer-out transaction in response to the asset state of the second asset being the second state.

15 . A computer device, comprising a memory and a processor, wherein

the memory is connected to the processor, the memory is configured to store a computer program, and the processor is configured to execute the computer program to perform operations associated with the first consensus node according to claim 1 .

16 . A computer device, comprising a memory and a processor, wherein

the memory is connected to the processor, the memory is configured to store a computer program, and the processor is configured to execute the computer program to perform operations associated with the second consensus node according to claim 6 .

Assignments (1)

Priority Claims (1)

Continuity (3)

References Cited (19)