A cross-chain-oriented hash function library updating system

Abstract

The application relates to a cross-chain-oriented hash function library updating system and relates to the field of blockchains, and comprises a hash function storage contract, a hash function management contract and a local hash function library, wherein the hash function storage contract and the hash function management contract are located on a blockchain; each hash function storage contract stores a contract management permission account, a hash function name and a hash function code; the hash function management contract comprises an account list of management permissions, the account list of management permissions stores a plurality of hash function names and contract management permission accounts corresponding to the hash function names; and the local hash function library comprises an updating interface; the updating interface judges whether a current account is a contract management permission account through the hash function management contract, and when the current account is a contract management permission account of a hash function to be updated, the hash function storage contract of the hash function to be updated and the local hash function library are updated. The application improves the availability and security of hash function updating.

Description

A Hash Function Library Update System for Cross-Chain Operations Technical Field

[0001] This invention relates to the field of blockchain technology, and in particular to a hash function library update system for cross-chain applications. Background Technology

[0002] Cross-chain technology is a crucial technological means to connect various blockchain systems, enabling inter-chain information exchange and maximizing the value of blockchain data. The most critical step in the cross-chain process is cross-chain data verification, which is a prerequisite for functions such as cross-chain asset transfer and cross-chain asset locking. Cross-chain data verification requires using corresponding hash functions based on the design of different blockchain systems to verify data stored in hash value form.

[0003] A hash function is a type of function that maps data of arbitrary length to data of fixed length. The output fixed-length data is called a hash value or message digest, and the input arbitrary-length data is called the preimage of the hash value. Hash functions possess one-wayness, collision resistance, and avalanche effect, and are used in blockchain for data storage, verification, and consensus algorithms.

[0004] Currently, the use of hash functions in cross-chain verification already includes solutions that use contracts to write hash functions. However, this approach suffers from high computational costs within contracts, a limited number of supported hash functions, and difficulties in updating hash functions. To address these issues, a hash function library solution for cross-chain verification has been proposed. This solution moves hash function computation from the contract to an external virtual machine, significantly reducing the cost of hash operations and providing more hash functions for cross-chain verification, thus making it applicable to a wider range of blockchain systems. However, since the hash function library is not on-chain, updates can only be performed through hard forks, which are unacceptable in real-world blockchain systems, resulting in significant usability issues. Furthermore, this solution lacks an effective update mechanism. Summary of the Invention

[0005] The purpose of this invention is to provide a hash function library update system for cross-chain communication, which improves the availability and security of hash function updates.

[0006] To achieve the above objectives, the present invention provides the following solution:

[0007] A cross-chain hash function library update system includes: a hash function storage contract, a hash function management contract, and a local hash function library, wherein the hash function storage contract and the hash function management contract are located on the blockchain, and the local hash function library is located on a local server;

[0008] Each hash function storage contract is used to store a hash function, and each hash function storage contract stores the contract management permission account, the hash function name, and the hash function code;

[0009] The hash function management contract includes a list of accounts with management authority, which stores multiple hash function names and the contract management authority accounts corresponding to each hash function name.

[0010] The local hash function library is used to store various hash function codes. The local hash function library includes an update interface. The update interface is used to determine whether the current account is a contract management authority account for the hash function to be updated through the hash function management contract. When the current account is a contract management authority account for the hash function to be updated, the hash function storage contract and the local hash function library for the hash function to be updated are updated.

[0011] Optionally, the local hash function library further includes a calling interface, which is used by the local server to call the hash function code in the local hash function library.

[0012] Optionally, the hash function management contract is also used to store a mapping of hash function storage contract addresses corresponding to each hash function name;

[0013] The update interface is also used to manage the mapping of hash function storage contract addresses in the contract through the hash function, and to determine whether the hash function to be updated exists in the hash function storage contract.

[0014] Optionally, the name of each hash function serves as a unique identifier for each hash function.

[0015] Optionally, the update operation of the hash function to be updated includes adding a hash function, renaming a hash function, updating a hash function, and removing a hash function.

[0016] Optionally, the hash function addition includes the following steps:

[0017] The hash function management contract is used to determine whether the current account has the contract management authority for the hash function to be updated;

[0018] If the current account is not a contract management account, an error message will appear indicating that the addition failed.

[0019] If the current account is a contract management privilege account, then determine whether the hash function storage contract of the hash function to be updated exists;

[0020] If the hash function storage contract for the hash function to be updated exists, then an error message will be displayed indicating that the addition failed.

[0021] If the hash function storage contract for the hash function to be updated does not exist, then the hash function storage contract for the hash function to be updated is created, and the result of successful addition is sent to the local hash function library;

[0022] When the local hash function library receives a successful addition result, it adds the hash function name and hash function code of the hash function to be updated to the local hash function library.

[0023] Optionally, renaming the hash function includes the following steps:

[0024] The hash function management contract is used to determine whether the current account has the contract management authority for the hash function to be updated;

[0025] If the current account is not a contract management account, a message will be displayed indicating that the name change failed.

[0026] If the current account is a contract management privilege account, then determine whether the hash function storage contract of the hash function to be updated exists;

[0027] If the hash function storage contract for the hash function to be updated does not exist, a renaming failure message will be displayed.

[0028] If the hash function storage contract for the hash function to be updated exists, then the hash function name in the hash function storage contract and the hash function management contract for the hash function to be updated is renamed according to the preset name, and the result of the successful renaming is sent to the local hash function library;

[0029] When the local hash function library receives a successful renaming result, it renames the hash function name of the hash function to be updated in the local hash function library according to the preset name.

[0030] Optionally, the hash function update includes the following steps:

[0031] The hash function management contract is used to determine whether the current account has the contract management authority for the hash function to be updated;

[0032] If the current account is not a contract management account, an update failure message will be displayed.

[0033] If the current account is a contract management privilege account, then determine whether the hash function storage contract of the hash function to be updated exists;

[0034] If the hash function storage contract for the hash function to be updated does not exist, an update failure message will be displayed.

[0035] If the hash function storage contract for the hash function to be updated exists, the corresponding hash function code in the hash function storage contract for the hash function to be updated is modified according to the preset hash function code, and the result of successful update is sent to the local hash function library;

[0036] When the local hash function library receives a successful update result, it modifies the hash function code of the hash function to be updated in the local hash function library according to the preset hash function code.

[0037] Optionally, the hash function removal includes the following steps:

[0038] The hash function management contract is used to determine whether the current account has the contract management authority for the hash function to be updated;

[0039] If the current account is not a contract management account, a message will be displayed indicating that the removal failed.

[0040] If the current account is a contract management privilege account, then determine whether the hash function storage contract of the hash function to be updated exists;

[0041] If the hash function storage contract for the hash function to be updated does not exist, a removal failure message will be displayed.

[0042] If the hash function storage contract for the hash function to be updated exists, then the hash function storage contract for the hash function to be updated is destroyed, and the result of successful removal is sent to the local hash function library;

[0043] When the local hash function library receives a successful removal result, it deletes the file whose hash function needs to be updated from the local hash function library.

[0044] According to specific embodiments provided by the present invention, the present invention discloses the following technical effects:

[0045] This invention discloses a hash function library update system for cross-chain applications. It stores the contract management permission accounts for each hash function through a hash function storage contract, and manages the hash function storage contract according to the hash function management contract. It interacts with the hash function management contract through the update interface of the local hash function library to achieve unified updates of on-chain hash functions and local hash functions, thereby improving the availability and security of hash function updates. Attached Figure Description

[0046] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0047] Figure 1 is a schematic diagram of the structure of a hash function library update system for cross-chain communication according to the present invention;

[0048] Figure 2 is a schematic diagram of the hash function addition process of the present invention;

[0049] Figure 3 is a schematic diagram of the hash function renaming process of the present invention;

[0050] Figure 4 is a schematic diagram of the hash function update process of the present invention;

[0051] Figure 5 is a schematic diagram of the hash function removal process of the present invention;

[0052] Figure 6 is a schematic diagram of the local hash function library update process of the present invention. Detailed Implementation

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

[0054] The purpose of this invention is to provide a hash function library update system for cross-chain communication, which improves the availability and security of hash function updates.

[0055] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0056] Figure 1 is a schematic diagram of the structure of a cross-chain hash function library update system according to the present invention. As shown in Figure 1, a cross-chain hash function library update system includes: a hash function storage contract 102, a hash function management contract 101, and a local hash function library 103. The hash function storage contract 102 and the hash function management contract 101 are located on the blockchain and belong to the on-chain contract part. The local hash function library 103 is located on a local server.

[0057] Hash function storage contract 102 is used to store hash function code on the blockchain. Each hash function storage contract 102 stores one hash function and contains a contract management permission account, a hash function name, and a hash function code. The hash function code stored in hash function storage contract 102 is a compressed hash function code. Hash function storage contract 102 also stores the hash function update time. The hash function name serves as a unique identifier for the hash function. Because the transaction associated with hash function storage contract 102 is recorded on the blockchain, it ensures that all trusted nodes update uniformly. Hash function storage contract 102 provides methods for obtaining and updating hash functions, with the update method only callable by the owner. Hash function storage contract 102 is created solely through hash function management contract 101, which is set as the owner during creation.

[0058] In the local hash function library 103, there is a one-to-one correspondence between hash functions and hash function storage contracts 102, as shown in Figure 1. Hash function 1 corresponds to contract (hash function storage contract 102)1, hash function 2 corresponds to contract (hash function storage contract 102)2, and hash function n corresponds to contract (hash function storage contract 102)n.

[0059] The hash function management contract 101 is used to manage the hash functions stored in the contract. The hash function management contract 101 includes a list of accounts with management authority, which stores multiple hash function names and the contract management authority accounts corresponding to each hash function name. The hash function management contract 101 is also used to store a mapping of the hash function storage contract 102 address corresponding to each hash function name.

[0060] The hash function management contract 101 provides methods for adding hash functions to the chain, as well as methods for retrieving, renaming, updating, and removing hash functions already stored on the chain. The method for retrieving hash functions can be called by any account, while the methods for adding, renaming, updating, and removing hash functions can only be called by accounts with contract management permissions, preventing malicious accounts from tampering with hash functions.

[0061] The local hash function library 103 stores the code implementations of various hash functions, providing hash function calls for cross-chain verification.

[0062] The local hash function library 103 is used to store various hash function codes, with each hash function stored as a separate code file. The local hash function library 103 includes update interfaces and call interfaces.

[0063] The update interface is used to interact with contracts (hash function management contract 101 and hash function storage contract 102), including updating hash functions from contracts, adding hash functions to contracts, and renaming, updating, and removing hash functions from contracts. The local hash function library 103 stores a mapping between local hash function names and update times, used for updating local hash functions.

[0064] The update interface is used to determine whether the current account is a contract management permission account for the hash function to be updated through the hash function management contract 101. When the current account is a contract management permission account for the hash function to be updated, the hash function storage contract 102 and the local hash function library 103 for the hash function to be updated are updated.

[0065] The calling interface is used by the local server to call the hash function code in the local hash function library 103.

[0066] The update interface is also used to manage the mapping of the hash function storage contract 102 address in contract 101 through the hash function, and to determine whether the hash function to be updated exists in the hash function storage contract 102.

[0067] The update operations for the hash function to be updated include adding a hash function, renaming a hash function, updating a hash function, and removing a hash function.

[0068] As shown in Figure 2, the addition of the hash function includes the following steps:

[0069] Enter the name and code of the hash function to be added into the local hash function library 103.

[0070] The local hash function library 103 uses a compression algorithm to compress the hash function code, taking the hash function name and the compressed hash function code as parameters. The local hash function library 103 calls the hash function management contract 101 to add the hash function method through the update interface.

[0071] The hash function management contract 101 is used to determine whether the current account is the account with the contract management authority for the hash function to be updated.

[0072] If the current account is not a contract management permission account, an addition failure message will be displayed, and the result of the addition failure will be sent to the local hash function library 103.

[0073] If the current account is a contract management permission account, then determine whether the hash function storage contract 102 of the hash function to be updated exists, that is, check whether the corresponding hash function already exists in the address mapping of the stored hash function.

[0074] If the hash function storage contract 102 for the hash function to be updated exists, then an addition failure message is displayed, and the result of the addition failure is sent to the local hash function library 103.

[0075] If the hash function storage contract 102 for the hash function to be updated does not exist, then the hash function storage contract 102 for the hash function to be updated is created, and the creation time is recorded as the update time in the hash function storage contract 102. The result of successful addition is sent to the local hash function library 103.

[0076] When the local hash function library 103 receives a successful addition result, it adds the hash function name and hash function code of the hash function to be updated to the local hash function library 103 and stores them in the corresponding file. The hash function is recorded in a map, which is a data structure in code used to record the correspondence between objects. Here, the map is used to record the correspondence between the hash function identifier (hash function name) and the code. The hash function code is compiled, and a successful hash function addition is returned, ending the hash function addition process.

[0077] As shown in Figure 3, the hash function renaming includes the following steps:

[0078] Input the original hash function name (old hash function name in Figure 3) and the new hash function name (preset name, new name in Figure 3) into the local hash function library 103. The original hash function name and the new hash function name are used as parameters, and the local hash function library 103 calls the rename hash function method in the hash function management contract 101 through the update interface.

[0079] The hash function management contract 101 is used to determine whether the current account is the contract management permission account for the hash function to be updated (the hash function corresponding to the original hash function name).

[0080] If the current account is not a contract management permission account, a name change failure message will be displayed, and the name change failure result will be sent to the local hash function library 103.

[0081] If the current account is a contract management permission account, then it is determined whether the hash function storage contract 102 of the hash function to be updated exists, that is, the hash function management contract 101 checks whether the corresponding hash function already exists in the mapping of the stored hash function.

[0082] If the hash function storage contract 102 for the hash function to be updated does not exist, a renaming failure message is displayed, and the result of the renaming failure is sent to the local hash function library 103.

[0083] If the hash function storage contract 102 for the hash function to be updated exists, then it is determined whether the new hash function name is available (whether it is a unique identifier). If the new hash function name is not available, then a renaming failure is indicated, and the result of the renaming failure is sent to the local hash function library 103.

[0084] If a new hash function name is available, the corresponding hash function names in the hash function storage contract 102 and the hash function management contract 101 of the hash function to be updated are modified according to the preset names, and the result of successful renaming is sent to the local hash function library 103.

[0085] When the local hash function library 103 receives a successful renaming result, it renames the hash function name of the hash function to be updated according to the preset name in the local hash function library 103, modifies the mapping in the local hash function library 103, changes the corresponding original hash function name to the new hash function name, returns a successful renaming of the hash function, and ends the hash function renaming process.

[0086] As shown in Figure 4, the hash function update includes the following steps:

[0087] Input the name and code of the hash function to be updated into the local hash function library 103. The local hash function library 103 compresses the hash function code using a compression algorithm. Using the hash function name and the compressed hash function code as parameters, the local hash function library 103 calls the update hash function method in the hash function management contract 101 through the update interface.

[0088] The hash function management contract 101 is used to determine whether the current account is the account with the contract management authority for the hash function to be updated.

[0089] If the current account is not a contract management permission account, an update failure message will be displayed, and the update failure result will be sent to the local hash function library 103.

[0090] If the current account is a contract management permission account, then determine whether the hash function storage contract 102 of the hash function to be updated exists.

[0091] If the hash function storage contract 102 for the hash function to be updated does not exist, an update failure message is displayed, and the update failure result is sent to the local hash function library 103.

[0092] If the hash function storage contract 102 for the hash function to be updated exists, the corresponding hash function code in the hash function storage contract 102 for the hash function to be updated will be modified according to the preset hash function code, that is, the new hash function code will be stored in the hash function storage contract 102, and the current time will be used as the update time in the hash function storage contract 102, and the result of successful update will be sent to the local hash function library 103.

[0093] When the local hash function library 103 receives a successful update result, it modifies the hash function code of the hash function to be updated in the local hash function library 103 according to the preset hash function code, that is, saves the new hash function code to the corresponding hash function file, compiles the new hash function code, returns a successful update of the hash function, and ends the hash function update process.

[0094] As shown in Figure 5, the hash function removal includes the following steps:

[0095] Input the name of the hash function to be removed into the local hash function library 103. Using the input hash function name as a parameter, the local hash function library 103 calls the remove hash function method in the hash function management contract 101 through the update interface.

[0096] The hash function management contract 101 is used to determine whether the current account is the account with the contract management authority for the hash function to be updated.

[0097] If the current account is not a contract management permission account, a removal failure message will be displayed, and the result of the removal failure will be sent to the local hash function library 103.

[0098] If the current account is a contract management permission account, then determine whether the hash function storage contract 102 of the hash function to be updated exists.

[0099] If the hash function storage contract 102 for the hash function to be updated does not exist, a removal failure message is displayed, and the result of the removal failure is sent to the local hash function library 103.

[0100] If the hash function storage contract 102 for the hash function to be updated exists, then the hash function storage contract 102 for the hash function to be updated is destroyed, the mapping of the hash function to be updated is deleted from the hash function management contract 101, and the result of successful removal is sent to the local hash function library 103.

[0101] When the local hash function library 103 receives a successful removal result, it deletes the file containing the hash function to be updated from the local hash function library 103, removing the hash function from the mapping. The hash function code is then compiled, and a successful removal result is returned, ending the hash function removal process.

[0102] The update interface also includes a method for updating the local hash function library 103, as shown in Figure 6. The update of the local hash function library 103 includes the following steps:

[0103] The local hash function library 103 calls the method in the hash function management contract 101 to obtain all hash functions, and gets all hash function names and update times.

[0104] Compare all the obtained hash function names and update times with the hash function names and update times in the local hash function library 103, and select the hash functions that need to be added, updated, or removed. Remove hash functions that are not in the hash function management contract 101 from the local hash function library 103, obtain the hash function code to be added and updated from the hash function management contract 101, add and update it to the local hash function file, and update the mapping in the hash function library. Compile the hash function code to end the process of updating the local hash function library 103.

[0105] The hash function library in Figures 2 to 6 is the local hash function library 103.

[0106] This invention discloses a hash function library update system for cross-chain applications. It stores hash functions through contracts, and the local hash function library interacts with the contracts to update the local hash function library from the contracts, add new hash functions to the contracts, and rename, update, and remove existing hash functions. This invention solves the problem of consistent updates on trusted nodes for cross-chain hash function libraries, avoids hard forks in update methods, and addresses the usability issue of using external hash function libraries for cross-chain verification.

[0107] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0108] This document uses specific examples to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. Furthermore, those skilled in the art will recognize that, based on the ideas of the present invention, there will be changes in the specific implementation methods and application scope. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A hash function library update system for cross-chain communication, characterized in that, include: The system comprises a hash function storage contract, a hash function management contract, and a local hash function library. The hash function storage contract and the hash function management contract are located on the blockchain, while the local hash function library is located on a local server. Each hash function storage contract stores one type of hash function and contains a contract management authority account, a hash function name, and a hash function code. The hash function management contract includes a list of accounts with management authority, which stores multiple hash function names and the corresponding contract management authority accounts for each hash function name. The local hash function library stores multiple hash function codes and includes an update interface. The update interface is used to determine whether the current account is a contract management authority account for the hash function to be updated through the hash function management contract. If the current account is a contract management authority account for the hash function to be updated, the hash function storage contract and the local hash function library for the hash function to be updated are updated. By interacting with the hash function management contract through the update interface of the local hash function library, unified updates of on-chain hash functions and local hash functions can be achieved.

2. The hash function library update system for cross-chain communication according to claim 1, characterized in that, The local hash function library also includes a calling interface, which is used by the local server to call the hash function code in the local hash function library.

3. The hash function library update system for cross-chain communication according to claim 1, characterized in that, The hash function management contract is also used to store the mapping of hash function storage contract addresses corresponding to each hash function name; the update interface is also used to determine whether the hash function to be updated exists in the hash function storage contract by using the mapping of hash function storage contract addresses in the hash function management contract.

4. The hash function library update system for cross-chain communication according to claim 1, characterized in that, Each hash function name serves as a unique identifier for each hash function.

5. The hash function library update system for cross-chain communication according to claim 1, characterized in that, The update operations for the hash function to be updated include adding a hash function, renaming a hash function, updating a hash function, and removing a hash function.

6. The hash function library update system for cross-chain communication according to claim 5, characterized in that, The hash function addition includes the following steps: The hash function management contract determines whether the current account is the account with contract management authority for the hash function to be updated; if the current account is not a contract management authority account, an addition failure message is displayed; if the current account is a contract management authority account, it determines whether the hash function storage contract for the hash function to be updated exists; if the hash function storage contract for the hash function to be updated exists, an addition failure message is displayed; if the hash function storage contract for the hash function to be updated does not exist, the hash function storage contract for the hash function to be updated is created, and the result of successful addition is sent to the local hash function library; when the local hash function library receives the result of successful addition, the hash function name and hash function code of the hash function to be updated are added to the local hash function library.

7. The hash function library update system for cross-chain communication according to claim 5, characterized in that, The hash function renaming process includes the following steps: The hash function management contract determines whether the current account is the contract management authority account for the hash function to be updated; if the current account is not a contract management authority account, a renaming failure message is displayed; if the current account is a contract management authority account, it determines whether the hash function storage contract for the hash function to be updated exists; if the hash function storage contract for the hash function to be updated does not exist, a renaming failure message is displayed; if the hash function storage contract for the hash function to be updated exists, the corresponding hash function names in the hash function storage contract and the hash function management contract are renamed according to a preset name, and the successful renaming result is sent to the local hash function library; when the local hash function library receives the successful renaming result, the hash function name of the hash function to be updated is renamed according to the preset name in the local hash function library.

8. The hash function library update system for cross-chain communication according to claim 5, characterized in that, The hash function update includes the following steps: The hash function management contract determines whether the current account is the contract management authority account for the hash function to be updated; if the current account is not the contract management authority account, an update failure message is displayed; if the current account is the contract management authority account, it determines whether the hash function storage contract for the hash function to be updated exists; if the hash function storage contract for the hash function to be updated does not exist, an update failure message is displayed; if the hash function storage contract for the hash function to be updated exists, the corresponding hash function code in the hash function storage contract for the hash function to be updated is modified according to a preset hash function code, and the update success result is sent to the local hash function library; when the local hash function library receives the update success result, the hash function code for the hash function to be updated is modified according to the preset hash function code in the local hash function library.

9. The hash function library update system for cross-chain communication according to claim 5, characterized in that, The hash function removal includes the following steps: The hash function management contract determines whether the current account is the account with contract management authority for the hash function to be updated; if the current account is not a contract management authority account, a removal failure message is displayed; if the current account is a contract management authority account, it determines whether the hash function storage contract for the hash function to be updated exists; if the hash function storage contract for the hash function to be updated does not exist, a removal failure message is displayed; if the hash function storage contract for the hash function to be updated exists, the hash function storage contract for the hash function to be updated is destroyed, and a successful removal result is sent to the local hash function library; when the local hash function library receives the successful removal result, the file of the hash function to be updated is deleted from the local hash function library.

Images