A consortium chain cross-chain method based on an access control mechanism

Abstract

The application belongs to the technical field of blockchains, and particularly relates to a cross-chain method of a consortium chain based on an access control mechanism, comprising the following steps: constructing a cross-chain consortium system group, respectively initializing the consortium chains, and deploying a cross-chain user registration contract, a cross-chain contract, a storage contract, a service access component, and a cross-chain gateway system to each consortium chain; the service access component runs a routine representing the corresponding relationship between the cross-chain user ID allowed by the consortium chain and the contract set allowed to be accessed thereby, the cross-chain user registration contract of the consortium chain is called in the execution process of the routine, the consortium chain runs a consensus algorithm, and the legal cross-chain user is stored on a chain; in the cross-chain consortium system group, the legal user on the consortium chain cross-chain calls the cross-chain contract on the consortium chain; the application can improve the security of the cross-chain system, eliminate the abuse of illegal cross-chain requests, and ensure the non-tamperability of cross-chain data and the auditability of cross-chain data.

Description

Technical Field

[0001] This invention belongs to the field of blockchain technology, specifically relating to a cross-chain method for consortium blockchains based on access control mechanisms. Background Technology

[0002] In recent years, blockchain technology has experienced unprecedented rapid development. During this process, numerous blockchain systems with varying architectures, consensus algorithms, and communication protocols have emerged worldwide. Consortium blockchains, situated between public and private blockchains, possess partial decentralized characteristics. They are jointly initiated and maintained by several institutions, and are only open to members of a specific group and a limited number of third parties. Participants in consortium blockchains are pre-selected or directly designated. Within the consortium blockchain, certain nodes are designated for record-keeping, and the generation of each block is jointly determined by designated sorting nodes. Users can participate in transactions but do not directly participate in the record-keeping process. Cross-chain technology connects homogeneous or heterogeneous blockchain systems, enabling asset and data interoperability, and serves as a bridge for the expansion and connection of blockchains.

[0003] In existing technologies, such as the cross-chain interaction method and the cross-chain interaction auditing method, patent number 202111663493.3, issued on December 31, 2021, by Alipay (Hangzhou) Information Technology Co., Ltd., address the need for cross-chain interaction between blockchain subnets in scenarios where the mainnet of a blockchain has multiple blockchain subnets. While this method can ensure the legality and validity of cross-chain interactions between blockchain subnets and prevent malicious node behavior, it suffers from the problem of unauthenticated cross-chain requests. Another example is the cross-chain asset transaction method, system, and device based on a relay chain, patent number 202211208434.1, issued on September 30, 2022, by Hangzhou Yunxiang Network Technology Co., Ltd. This patent addresses potential practicality and security issues in heterogeneous blockchain asset transactions by proposing a transaction on-chain process, transaction verification method, multi-layered relay chain architecture, and cross-chain asset transaction process. It can meet the needs of cross-chain asset transactions in multi-chain scenarios and enable multi-party data sharing and computing power sharing. However, it suffers from the problem of over-reliance on the relay chain architecture.

[0004] The existing technologies described above all suffer from the following problems: They lack corresponding restrictions on cross-chain behavior, leading to security issues for participating consortium blockchain systems. Most existing solutions rely on relay blockchain systems as intermediaries for cross-chain operations, resulting in high resource consumption and complex architectures. Summary of the Invention

[0005] To address the problems of existing technologies, this invention proposes a cross-chain method for consortium blockchains based on an access control mechanism, characterized by comprising:

[0006] As needed, participate in the cross-chain consortium set S consortium Building a cross-chain consortium system group CCS = {B i , i∈S consortium}, respectively for consortium blockchain B i Perform the corresponding system initialization B i,init and to each consortium blockchain B i Deploy the cross-chain user access control registration contract Cregis i Cross-chain contracts Ccross i Csave (Certificate of Evidence) i Service access component SP i and cross-chain gateway system G i ;

[0007] Service Access Component (SP) i Run the access control registration routine register(ID, S) contract ={C i C i ∈

[0008] {Ccross i} n}), will (ID, S contract Key-value pairs are uploaded to the blockchain to represent the cross-chain user IDs allowed by the consortium blockchain and the set of contracts S that they are allowed to access. contract The corresponding relationship is invoked during the execution of the access control registration routine by the consortium blockchain B. i Cregis, a cross-chain user access control registration contract i Consortium blockchains run the consensus algorithm. i Legitimate cross-chain users will be recorded on the blockchain for evidence storage.

[0009] In the Cross-Chain Consortium System Cluster (CCS), consortium chain B a Valid user ID on a Cross-chain call to consortium blockchain B b Cross-chain contracts b ;

[0010] S1: User ID a Construct a cross-chain request Q = (ID) a Contract b Send to cross-chain gateway G a Cross-chain gateway G a Calling the service access component SP a The access control user verification function {0 / 1}<-check(IDa) performs a cross-chain initiator access control legality check. If the return value is false, the process terminates; otherwise, the subsequent cross-chain process continues.

[0011] S2: After the check passes, cross-chain gateway G a Run the find algorithm to locate the target gateway G. b The cross-chain request Q = (IDa, Contractb) is then forwarded and delivered to the target gateway G. b ;

[0012] S3: Target Gateway G b After parsing the cross-chain request Q = (IDa, Contractb), the service access component SP is called. b Waiting for service access component SP b The returned result;

[0013] S4: Service Access Component (SP) b The cross-chain request access control function {0 / 1}<-checkCross(ID,Contract) is invoked to perform a cross-chain target party access control validity check on the cross-chain request. If the return value is false, the process terminates; otherwise, the function R<-exec(Contract) is executed to obtain the result R, which is then returned to the service access component SP. b ;

[0014] S5: Service Access Component (SP) b The result R is then delivered to the target gateway G. b Target gateway G b Run the find algorithm to locate the cross-chain gateway G. a The cross-chain result R is then forwarded to the cross-chain gateway G. a ;

[0015] S6: Service Access Component (SP) a Call the R<-save(ID,timestamp,R) function to store the cross-chain result on the consortium blockchain Ba;

[0016] S7: User ID a Through cross-chain gateway G a Calling the service access component SP a The R<-read(ID,timestamp) function reads the cross-chain result R.

[0017] The beneficial effects of this invention are:

[0018] In the initial construction of the consortium blockchain of this invention, negotiations among the various consortium blockchain institutions are required. Each consortium blockchain obtains an access control mapping relationship between a cross-chain user ID and a cross-chain contract set Setcross, i.e., a key-value pair. Then, each consortium blockchain uploads this mapping relationship data to the blockchain. During the cross-chain phase, after each cross-chain gateway receives a cross-chain request Q = (IDa, Contractb), it sends the cross-chain request to the service access component. In the service access component, the checkcross access control verification function is called to verify the access control of IDa and Contractb. The verification process involves reading the valid cross-chain user ID and the cross-chain contract set Setcross mapping relationship written on the blockchain during the initialization phase, and then traversing these key-value pairs to check whether the cross-chain user IDa in this cross-chain request has a corresponding cross-chain contract Contractb. If a match is found, the cross-chain request is allowed; if not, the cross-chain request is considered illegal and is rejected. This access control mechanism fills the gap in access control for cross-chain behavior in consortium blockchain cross-chain solutions, improves the security of consortium blockchain cross-chain methods, and protects the privacy of consortium blockchain contracts and data involved in cross-chain operations.

[0019] This invention improves the security of the cross-chain system by having a cross-chain user initiate a cross-chain request through a cross-chain gateway system. The cross-chain gateway system queries the cross-chain service access component to determine whether the user, the initiator of the cross-chain request, is permitted to initiate the cross-chain request. After successful verification, the cross-chain gateway system parses the cross-chain request and forwards it to the cross-chain gateway system of the target consortium blockchain. Upon receiving the request, the target cross-chain gateway hands it over to the target cross-chain service access component. The component verifies the cross-chain request by polling the list of legitimate cross-chain control methods obtained from the connected consortium blockchains. After successful verification, it calls the specific business contract of the cross-chain system and returns the result to the target cross-chain gateway. The target cross-chain gateway then returns the result to the cross-chain gateway of the request initiator. The initiator's cross-chain gateway calls its own service access component to upload the cross-chain result to the blockchain and save the result. This improves the security of the cross-chain system, prevents the abuse of illegal cross-chain requests, and ensures the immutability and auditability of cross-chain data. Attached Figure Description

[0020] Figure 1 This is a flowchart of a consortium blockchain cross-chain method based on an access control mechanism according to the present invention. Detailed Implementation

[0021] 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.

[0022] A cross-chain method for consortium blockchains based on access control mechanisms, such as... Figure 1 As shown, it includes:

[0023] As needed, participate in the cross-chain consortium set S consortium Building a cross-chain consortium system group CCS = {B i , i∈S consortium}, respectively for consortium blockchain B i Perform the corresponding system initialization B i,init and to each consortium blockchain B i Deploy the cross-chain user access control registration contract Cregis i Cross-chain contracts Ccross i Csave (Certificate of Evidence) i Service access component SP i and cross-chain gateway system G i ;

[0024] Service Access Component (SP) i Run the access control registration routine register(ID, S) contract ={C i C i ∈

[0025] {Ccross i} n}), will (ID, S contract Key-value pairs are uploaded to the blockchain to represent the cross-chain user IDs allowed by the consortium blockchain and the set of contracts S that they are allowed to access. contract The corresponding relationship is invoked during the execution of the access control registration routine by the consortium blockchain B. i Cregis, a cross-chain user access control registration contract i Consortium blockchains run the consensus algorithm. i Legitimate cross-chain users will be recorded on the blockchain for evidence storage.

[0026] In the Cross-Chain Consortium System Cluster (CCS), consortium chain B a Valid user ID on a Cross-chain call to consortium blockchain B b Cross-chain contracts b ;

[0027] S1: User ID a Construct a cross-chain request Q = (ID) a Contract b Send to cross-chain gateway G a Cross-chain gateway G a Calling the service access component SP a The access control user verification function {0 / 1}<-check(IDa) performs a cross-chain initiator access control legality check. If the return value is false, i.e., the return value is 0, the process terminates; otherwise, the subsequent cross-chain process continues.

[0028] S2: After the check passes, cross-chain gateway G a Run the find algorithm to locate the target gateway G. b The cross-chain request Q = (IDa, Contractb) is then forwarded and delivered to the target gateway G. b ;

[0029] S3: Target Gateway G b After parsing the cross-chain request Q = (IDa, Contractb), the service access component SP is called. b Waiting for service access component SP b The returned result;

[0030] S4: Service Access Component (SP) b The cross-chain request access control verification function {0 / 1}<-checkCross(ID,Contract) is invoked to perform a cross-chain target party access control legality check on the cross-chain request. If the return value is false (i.e., the return value is 0), the process terminates; otherwise, the function R<-exec(Contract) is executed to obtain the result R, and the result R is returned to the service access component SP. b ;

[0031] S5: Service Access Component (SP) b The result R is then delivered to the target gateway G. b Target gateway G b Run the find algorithm to locate the cross-chain gateway G. a The cross-chain result R is then forwarded to the cross-chain gateway G. a ;

[0032] S6: Service Access Component (SP) a Call the R<-save(ID,timestamp,R) function to store the cross-chain result on the consortium blockchain Ba;

[0033] S7: User ID a Through cross-chain gateway G a Calling the service access component SP aThe R<-read(ID,timestamp) function reads the cross-chain result R.

[0034] In this implementation, for consortium blockchain B i Perform the corresponding system initialization B i,init This includes: deploying network nodes, deploying consensus protocols, initializing chain certificates, generating genesis blocks, and starting the blockchain network.

[0035] In this implementation,

[0036] The cross-chain user access control registration contract Credis i , including: Set registeduser <-registUser(ID) is a cross-chain user access control registration function. (ID, Set...) contract `<-mapUserContracts(ID,S(contract))` is a cross-chain user-cross-chain contract access control registration function; `{0 / 1}<-check(ID)` is a cross-chain user access control verification function; `{0 / 1}<-checkCross(ID,Contract)` is a cross-chain request access control verification function; and `(ID,Set)` is a (ID,S(contract) ... contract The `readAll()` function is used to read access control information.

[0037] The Set registeduser The `registUser(ID)` function is used to register cross-chain user IDs. i To consortium blockchain B i Up, and through consortium blockchain B i Running consensus algorithm i Get the set of legal users. registeduser ;

[0038] The (ID,Set) contract The `mapUserContracts(ID, S(contract))` function is a cross-chain user-contract access control registration function used to map cross-chain user IDs. i To the set of cross-chain contracts that it is allowed to access contract That is, Set contract ={C i C i ∈{Ccross i} n};

[0039] The {0 / 1}<-check(ID) cross-chain user access control verification function is used to check whether the user ID is in the valid user set Set. registeduser middle;

[0040] The {0 / 1}<-checkCross(ID,Contract) cross-chain request access control verification function is used to check the cross-chain user ID. i Is there a corresponding contract that matches this?

[0041] The (ID,Set) contract The `readAll()` function is used to read access control information and iterate through the (ID, Set) records stored on the consortium blockchain. contract Key-value pairs yield the authorized cross-chain user IDs and cross-chain contract sets (Set) allowed by the consortium blockchain. contract The mapping relationship.

[0042] In this implementation, the cross-chain contract Ccross i For consortium blockchain B i The contract can be selected and accessed across chains by external consortium blockchain systems.

[0043] In this implementation, the evidence storage contract Csave is a contract specifically used for storing cross-chain results R, and its main functions are save(ID, timestamp, R) and read(ID, timestamp).

[0044] In this implementation, the service access component SP i This includes: the register(ID, Set(contract)) access control registration function, and the (ID, Set) function. contract The functions are: `R<-init()` for access control initialization and reading, `R<-exec(Contract)` for cross-chain contract calls, `R<-save(ID,timestamp,R)` for cross-chain result storage, and `R<-read(ID,timestamp)` for reading cross-chain results.

[0045] The register(ID, Set(contract)) access control registration function takes a user ID and a cross-chain contract set S as input parameters. contract ={C i C i ∈{Ccross i} n}, through the consortium blockchain software development kit (SDK), i.e., the access interface provided by the consortium blockchain, the cross-chain user registration contract Cregis is called. i and run the consensus algorithm. i On-chain;

[0046] The (ID,Set) contractThe `<-init()` access control initialization function is called during initialization to invoke the cross-chain user registration contract `Cregis` via the consortium blockchain SDK. i (ID, Set) contract The `<-readAll()` function reads the existing cross-chain legitimate user contract mapping set S. ID-contract ={(ID) i Set contracti )|ID i ∈Set registeduser Set contracti ={C i C i ∈{Ccross i} n}};

[0047] The R<-exec(Contract) cross-chain contract call function is used to call the contract Contract = {C, C∈C} through the access interface provided by the consortium blockchain. regisi ∪C savei ∪{Ccross i} n} and return the execution result of the Contract;

[0048] The R<-save(ID, timestamp, R) cross-chain result storage function is used to call the storage contract Csave through the consortium blockchain SDK. i The cross-chain evidence is stored (ID, timestamp, R) for users to read;

[0049] The R<-read(ID, timestamp) cross-chain result reading function is used to call the evidence storage contract Csave through the consortium blockchain SDK. i Read the cross-chain result.

[0050] In this implementation, the cross-chain gateway system G i Cross-chain gateway system connection information (Connection = {Data) is used to provide cross-chain interfaces to cross-chain users, forward cross-chain requests to target consortium blockchain gateways, and negotiate interconnection during the initialization of the cross-chain consortium blockchain system group (CCS). i (Consortium blockchain name, (cross-chain gateway system IP address: port))}, and stored in the gateway system G i middle.

[0051] In this implementation, the target gateway G b Run the find algorithm to locate the cross-chain gateway G. a ,include:

[0052] Target Gateway G bRun the find algorithm to parse the given cross-chain request and obtain the cross-chain gateway system information Connection. Based on the cross-chain gateway system information Connection, find the target consortium chain cross-chain gateway connection information Data = (consortium chain name, (cross-chain gateway system IP address: port)).

[0053] 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 cross-chain method for consortium blockchains based on an access control mechanism, characterized in that, include: As needed, participate in the cross-chain consortium set S consortium Building a cross-chain consortium system group CCS = {B i , i∈S consortium }, respectively for consortium blockchain B i Perform the corresponding system initialization B i,init and to each consortium blockchain B i Deploy the cross-chain user access control registration contract Cregis i Cross-chain contracts Ccross i Csave (Certificate of Evidence) i Service access component SP i and cross-chain gateway system G i ; Service Access Component (SP) i Run the access control registration routine register(ID, S) contract ={C i C i ∈ {Ccross i } n }), will (ID, S contract Key-value pairs are uploaded to the blockchain to represent the cross-chain user IDs allowed by the consortium blockchain and the set of contracts S that they are allowed to access. contract The corresponding relationship is invoked during the execution of the access control registration routine by the consortium blockchain B. i Cregis cross-chain user access control registration contract i Consortium blockchains run the consensus algorithm. i Legitimate cross-chain users will be recorded on the blockchain for evidence storage. In the Cross-Chain Consortium System Cluster (CCS), consortium chain B a Valid user ID on a Cross-chain call to consortium blockchain B b Cross-chain contracts b ; S1: User ID a Construct a cross-chain request Q = (ID) a Contract b Send to cross-chain gateway G a Cross-chain gateway G a Calling the service access component SP a The access control user verification function {0 / 1}<-check(IDa) performs a cross-chain initiator access control legality check. If the return value is false, the process terminates; otherwise, the subsequent cross-chain process continues. S2: After the check passes, cross-chain gateway G a Run the find algorithm to locate the target gateway G. b The cross-chain request Q = (IDa, Contractb) is then forwarded and delivered to the target gateway G. b ; S3: Target Gateway G b After parsing the cross-chain request Q = (IDa, Contractb), the service access component SP is called. b Waiting for service access component SP b The returned result; S4: Service Access Component (SP) b The cross-chain request access control function {0 / 1}<-checkCross(ID,Contract) is invoked to perform a cross-chain target party access control legality check on the cross-chain request. If the return value is false, the process terminates; otherwise, the cross-chain contract call function R<-exec(Contract) is executed to obtain the result R, and the result R is returned to the service access component SP. b ; S5: Service Access Component (SP) b The result R is then delivered to the target gateway G. b Target gateway G b Run the find algorithm to locate the cross-chain gateway G. a The cross-chain result R is then forwarded to the cross-chain gateway G. a ; S6: Service Access Component (SP) a Call the R<-save(ID,timestamp,R) function to store the cross-chain result on the consortium blockchain Ba; S7: User ID a Through cross-chain gateway G a Calling the service access component SP a The R<-read(ID,timestamp) function reads the cross-chain result R.

2. The cross-chain method for consortium blockchains based on an access control mechanism according to claim 1, characterized in that, For consortium blockchain B i Perform the corresponding system initialization B i,init This includes: deploying network nodes, deploying consensus protocols, initializing chain certificates, generating genesis blocks, and starting the blockchain network.

3. The cross-chain method for consortium blockchains based on access control mechanisms according to claim 1, characterized in that, The cross-chain user access control registration contract Credis i , including: Set registeduser <-registUser(ID) is a cross-chain user access control registration function. (ID, Set...) contract `<-mapUserContracts(ID,S(contract))` is a cross-chain user-cross-chain contract access control registration function; `{0 / 1}<-check(ID)` is a cross-chain user access control verification function; `{0 / 1}<-checkCross(ID,Contract)` is a cross-chain request access control verification function; and `(ID,Set)` is a (ID,S(contract) ... contract The `readAll()` function is used to read access control information. The Set registeduser The `registUser(ID)` function is used to register cross-chain user IDs. i To consortium blockchain B i Up, and through consortium blockchain B i Running consensus algorithm i Get the set of legal users. registeduser ; The (ID,Set) contract The `mapUserContracts(ID, S(contract))` function is a cross-chain user-contract access control registration function used to map cross-chain user IDs. i To the set of cross-chain contracts that it is allowed to access contract That is, Set contract ={C i C i ∈{Ccross i } n }; The {0 / 1}<-check(ID) cross-chain user access control verification function is used to check whether the user ID is in the valid user set Set. registeduser middle; The {0 / 1}<-checkCross(ID,Contract) cross-chain request access control verification function is used to check the cross-chain user ID. i Is there a corresponding contract that matches this? The (ID,Set) contract The `readAll()` function is used to read access control information and iterate through the (ID, Set) records stored on the consortium blockchain. contract Key-value pairs yield the authorized cross-chain user IDs and cross-chain contract sets (Set) allowed by the consortium blockchain. contract The mapping relationship.

4. The cross-chain method for consortium blockchains based on access control mechanisms according to claim 1, characterized in that, The cross-chain contract Ccross i For consortium blockchain B i The contract can be selected and accessed across chains by external consortium blockchain systems.

5. The cross-chain method for consortium blockchains based on access control mechanisms according to claim 1, characterized in that, The evidence storage contract Csave is a contract specifically used for storing cross-chain results R. Its main functions are save(ID, timestamp, R) and read(ID, timestamp).

6. The consortium blockchain cross-chain method based on access control mechanism according to claim 1, characterized in that, Service Access Component (SP) i This includes: the register(ID, Set(contract)) access control registration function, (ID, Set... contract The functions are: `R<-init()` for access control initialization and reading, `R<-exec(Contract)` for cross-chain contract calls, `R<-save(ID,timestamp,R)` for cross-chain result storage, and `R<-read(ID,timestamp)` for reading cross-chain results. The register(ID, Set(contract)) access control registration function takes a user ID and a cross-chain contract set S as input parameters. contract ={C i C i ∈{Ccross i } n The consortium blockchain uses its external access interface to call the cross-chain user registration contract Cregis. i and run the consensus algorithm. i On-chain; The (ID,Set) contract The `<-init()` access control initialization function is called during initialization to invoke the cross-chain user registration contract `Cregis` through the access interface provided by the consortium blockchain. i (ID, Set) contract The `<-readAll()` function reads the existing cross-chain legitimate user contract mapping set S. ID-contract ={(ID) i Set contracti )|ID i ∈Set registeduser Set contracti ={C i C i ∈{Ccross i } n }}; The R<-exec(Contract) cross-chain contract call function is used to call the contract Contract = {C, C∈C} through the access interface provided by the consortium blockchain. regisi ∪C savei ∪{Ccross i } n } and return the execution result of the Contract; The R<-save(ID, timestamp, R) cross-chain result storage function is used to call the storage contract Csave through the consortium blockchain SDK. i The cross-chain evidence is stored (ID, timestamp, R) for users to read; The R<-read(ID, timestamp) cross-chain result reading function is used to call the evidence storage contract Csave through the consortium blockchain SDK. i Read the cross-chain result.

7. The cross-chain method for consortium blockchains based on access control mechanisms according to claim 1, characterized in that, The cross-chain gateway system G i Cross-chain gateway system connection information (Connection = {Data) is used to provide cross-chain interfaces to cross-chain users, forward cross-chain requests to target consortium blockchain gateways, and negotiate interconnection during the initialization of the cross-chain consortium blockchain system group (CCS). i (Consortium blockchain name, (cross-chain gateway system IP address: port))}, and stored in the gateway system G i middle.

8. The cross-chain method for consortium blockchains based on access control mechanisms according to claim 1, characterized in that, Target Gateway G b Run the find algorithm to locate the cross-chain gateway G. a ,include: Target Gateway G b Run the find algorithm to parse the given cross-chain request and obtain the cross-chain gateway system information Connection. Based on the cross-chain gateway system information Connection, find the target consortium chain cross-chain gateway connection information Data = (consortium chain name, (cross-chain gateway system IP address: port)).

Images