CN114297171A - Account data reading and writing method and device - Google Patents
Account data reading and writing method and device Download PDFInfo
- Publication number
- CN114297171A CN114297171A CN202111669830.XA CN202111669830A CN114297171A CN 114297171 A CN114297171 A CN 114297171A CN 202111669830 A CN202111669830 A CN 202111669830A CN 114297171 A CN114297171 A CN 114297171A
- Authority
- CN
- China
- Prior art keywords
- account
- blockchain
- database
- target
- target account
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 104
- 238000003860 storage Methods 0.000 claims description 14
- 230000005540 biological transmission Effects 0.000 claims description 5
- 230000008569 process Effects 0.000 description 31
- 238000010586 diagram Methods 0.000 description 20
- 230000007246 mechanism Effects 0.000 description 12
- 230000004044 response Effects 0.000 description 12
- 238000012545 processing Methods 0.000 description 11
- 230000006870 function Effects 0.000 description 10
- 238000012544 monitoring process Methods 0.000 description 10
- 238000004590 computer program Methods 0.000 description 9
- 230000002829 reductive effect Effects 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 7
- 230000003993 interaction Effects 0.000 description 5
- 230000008520 organization Effects 0.000 description 5
- 230000009471 action Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 3
- RTZKZFJDLAIYFH-UHFFFAOYSA-N Diethyl ether Chemical compound CCOCC RTZKZFJDLAIYFH-UHFFFAOYSA-N 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 239000003999 initiator Substances 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000008034 disappearance Effects 0.000 description 1
- 229910021389 graphene Inorganic materials 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000002427 irreversible effect Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000005304 joining Methods 0.000 description 1
- 230000000670 limiting effect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000036961 partial effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
One or more embodiments of the present specification provide a method and an apparatus for reading and writing account data. The method is applied to a first block chain node in a first block chain network, block chain link points of other block chain networks are also deployed in node equipment where the first block chain link point is located, and the node equipment maintains a common database corresponding to a plurality of block chain nodes, wherein the common database is used for recording account data of common accounts among the plurality of block chain networks, and the method comprises the following steps: acquiring a read-write request aiming at a target account; and under the condition that the account data of the target account is recorded in the public database, searching the target account from the public database and executing read-write operation on the account data of the target account.
Description
Technical Field
One or more embodiments of the present disclosure relate to the field of blockchain technologies, and in particular, to a method and an apparatus for reading and writing account data.
Background
The block chain technique is built on top of a point-to-point network. Nodes in the blockchain network utilize a chained data structure to validate and store data and employ a distributed node consensus algorithm to generate and update data. In some blockchain networks, node members corresponding to a part of nodes sometimes have a need to participate in multiple blockchain networks, that is, a plurality of blockchain nodes belonging to different blockchain networks may be deployed in a certain node device at the same time. In this scenario, the node device needs to manage account data of blockchain accounts in different blockchain networks in which it participates.
Disclosure of Invention
In view of this, one or more embodiments of the present disclosure provide a method and an apparatus for reading and writing account data.
In order to achieve the above purpose, one or more embodiments of the present disclosure provide the following technical solutions:
according to a first aspect of one or more embodiments of the present specification, a method for reading and writing account data is provided, where the method is applied to a first blockchain node in a first blockchain network, a node device where the first blockchain node is located is also deployed with blockchain nodes of other blockchain networks, and the node device maintains a common database corresponding to multiple blockchain nodes, where the common database is used to record account data of common accounts between multiple blockchain networks, and the method includes:
acquiring a read-write request aiming at a target account;
and under the condition that the account data of the target account is recorded in the public database, searching the target account from the public database and executing read-write operation on the account data of the target account.
According to a second aspect of one or more embodiments of the present specification, a method for reading and writing account data is provided, which is applied to a node device, where a plurality of blockchain nodes respectively belonging to different blockchain networks are deployed in the node device, and the node device maintains a common database corresponding to the plurality of blockchain nodes, where the common database is used to record account data of a common account between the plurality of blockchain networks, where the method includes:
acquiring a read-write request aiming at a target account;
and under the condition that the account data of the target account is recorded in the public database, searching the target account from the public database and executing read-write operation on the account data of the target account.
According to a third aspect of one or more embodiments of the present specification, there is provided an account data reading and writing apparatus, which is applied to a first blockchain node in a first blockchain network, where a node device where the first blockchain node is located is also deployed with blockchain nodes of other blockchain networks, and the node device maintains a common database corresponding to multiple blockchain nodes, where the common database is used to record account data of common accounts between multiple blockchain networks, the apparatus including:
the request acquisition module is used for acquiring a read-write request aiming at a target account;
the first reading and writing module is used for searching the target account from the public database and executing reading and writing operation on the account data of the target account under the condition that the account data of the target account is recorded in the public database.
According to a fourth aspect of one or more embodiments of the present specification, an account data read/write apparatus is provided, which is applied to a node device, where a plurality of blockchain nodes respectively belonging to different blockchain networks are deployed in the node device, and the node device maintains a common database corresponding to the plurality of blockchain nodes, where the common database is used to record account data of a common account among the plurality of blockchain networks, and the apparatus includes:
the request acquisition module is used for acquiring a read-write request aiming at a target account;
the first reading and writing module is used for searching the target account from the public database and executing reading and writing operation on the account data of the target account under the condition that the account data of the target account is recorded in the public database.
According to a fifth aspect of one or more embodiments herein, there is provided an electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor implements the method as described in the first or second aspect by executing the executable instructions.
According to a sixth aspect of one or more embodiments of the present description, there is provided a computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method as described in the first or second aspect.
In summary, according to the technical solution of the present specification, when a plurality of blockchain nodes respectively belonging to different blockchain networks are deployed in a node device, the node device further maintains a common database corresponding to the plurality of blockchain nodes, where the common database is used to record account data of a common account between the plurality of blockchain networks. Based on the recording mode of the account data, for the obtained read-write request for the target account, the first block link point or the node device may search the target account from the public database and perform read-write operation on the account data of the target account when the account data of the target account is recorded in the public database.
Through the above manner, the node device can store the account data of the common account between different blockchain networks in the common database, and perform read-write operation on the account data of the account recorded in the common database in response to the read-write request for the common account. Therefore, the multiple blockchain networks can maintain the common account together, a shared management scheme for the common account is realized, the multiple independent blockchain networks can have the shared common account, the account system under the scene of the multiple blockchain networks is simplified to a certain extent, and the workload of maintaining the account by the node equipment is reduced. Moreover, due to the sharing characteristic of the common account, the operation result of the read-write operation performed by the first block chain network on the account data of the target account can also be used (for example, read) by other block chain networks, so that the unified operation of different block chain nodes on the same account is realized, and the management and utilization efficiency of the common account is improved.
Drawings
FIG. 1 is a schematic diagram of creating an intelligent contract, provided by an exemplary embodiment.
FIG. 2 is a schematic diagram of a calling smart contract provided by an exemplary embodiment.
FIG. 3 is a schematic diagram of creating and invoking an intelligent contract according to an exemplary embodiment.
FIG. 4 is a structural diagram of a multi-level tree structure according to an exemplary embodiment.
Fig. 5 is a schematic diagram illustrating a database deployment scenario in a node device according to an exemplary embodiment.
Fig. 6 is a flowchart of a method for reading and writing account data according to an exemplary embodiment.
Fig. 7 is a flowchart of another method for reading and writing account data according to an exemplary embodiment.
Fig. 8 is a schematic structural diagram of an apparatus according to an exemplary embodiment.
Fig. 9 is a block diagram of a device for reading and writing account data according to an exemplary embodiment.
Fig. 10 is a block diagram of another apparatus for reading and writing account data according to an exemplary embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of one or more embodiments of the specification, as detailed in the claims which follow.
It should be noted that: in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described herein. In some other embodiments, the method may include more or fewer steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.
Blockchains are generally divided into three types: public chain (Public Blockchain), Private chain (Private Blockchain) and alliance chain (Consortium Blockchain). In addition, there are various types of combinations, such as private chain + federation chain, federation chain + public chain, and other different combinations. The most decentralized of these is the public chain. The public chain is represented by bitcoin and ether house, and the participators joining the public chain can read the data record on the chain, participate in transaction, compete for accounting right of new blocks, and the like. Furthermore, each participant (i.e., node) is free to join and leave the network and perform related operations. Private chains are the opposite, with the network's write rights controlled by an organization or organization and the data read rights specified by the organization. Briefly, a private chain can be a weakly centralized system with strictly limited and few participating nodes. This type of blockchain is more suitable for use within a particular establishment. A federation chain is a block chain between a public chain and a private chain, and "partial decentralization" can be achieved. Each node in a federation chain typically has a physical organization or organization corresponding to it; participants jointly maintain blockchain operation by authorizing to join the network and forming a benefit-related alliance.
Whether public, private, or alliance, may provide the functionality of an intelligent contract. An intelligent contract on a blockchain is a contract that can be executed on a blockchain system triggered by a transaction. An intelligent contract may be defined in the form of code.
Taking the ethernet as an example, the support user creates and invokes some complex logic in the ethernet network, which is the biggest challenge of ethernet to distinguish from bitcoin blockchain technology. The core of the ethernet plant as a programmable blockchain is the ethernet plant virtual machine (EVM), each ethernet plant node can run the EVM. The EVM is a well-behaved virtual machine, which means that a variety of complex logic can be implemented through it. The user issuing and invoking smart contracts in the etherhouse is running on the EVM. In fact, what the virtual machine directly runs is virtual machine code (virtual machine bytecode, hereinafter referred to as "bytecode"). The intelligent contracts deployed on the blockchain may be in the form of bytecodes.
For example, as shown in fig. 1, after Bob sends a transaction containing information to create an intelligent contract to the ethernet network, the EVM of node 1 may execute the transaction and generate a corresponding contract instance. The "0 x6f8ae93 …" in fig. 1 represents the address of the contract, the data field of the transaction holds the byte code, and the to field of the transaction is empty. After agreement is reached between the nodes through the consensus mechanism, this contract is successfully created and can be invoked in subsequent procedures. After the contract is created, a contract account corresponding to the intelligent contract appears on the blockchain and has a specific address, and the contract code is stored in the contract account. The behavior of the intelligent contract is controlled by the contract code. In other words, an intelligent contract causes a virtual account to be generated on a blockchain that contains a contract code and an account store (Storage).
As shown in fig. 2, still taking an ethernet house as an example, after Bob sends a transaction for invoking an intelligent contract to the ethernet house network, the EVM of a certain node may execute the transaction and generate a corresponding contract instance. The from field of the transaction in FIG. 2 is the address of the account of the initiator of the transaction (i.e., Bob), the "0 x6f8ae93 …" in the to field represents the address of the smart contract being invoked, and the value field is the value in EtherFang that is kept in the data field of the transaction as the method and parameters for invoking the smart contract. After invoking the smart contract, the value of balance may change. Subsequently, a client can view the current value of balance through a blockchain node (e.g., node 6 in fig. 2). The intelligent contract is independently executed at each node in the blockchain network in a specified mode, and all execution records and data are stored on the blockchain, so that after the transaction is completed, transaction certificates which cannot be tampered and cannot be lost are stored on the blockchain.
A schematic diagram of creating an intelligent contract and invoking the intelligent contract is shown in fig. 3. To create an intelligent contract in an ethernet workshop, the intelligent contract needs to be compiled, compiled into byte codes, deployed to a block chain and the like. The intelligent contract is called in the Ethernet workshop, a transaction pointing to the intelligent contract address is initiated, and the intelligent contract codes are operated in the virtual machine of each node in the Ethernet workshop in a distributed mode.
It should be noted that, in addition to the creation of the smart contracts by the users, the smart contracts may also be set by the system in the creation block. Such contracts are generally referred to as foundational contracts. In general, the data structures, parameters, attributes and methods of some blockchain networks may be set in the startup contract. Further, an account with system administrator privileges may create a contract at the system level, or modify a contract at the system level (simply referred to as a system contract). In addition to EVM in the ethernet, different blockchain networks may employ various virtual machines, which is not limited herein.
After executing a transaction that invokes a smart contract, a node in the blockchain network generates a corresponding receipt (receipt) for recording information related to executing the smart contract. In this way, information about the contract execution results may be obtained by querying the receipt of the transaction. The contract execution result may be represented as an event (event) in the receipt. The message mechanism can realize message passing through an event in a receipt so as to trigger the blockchain node or a node device deploying the blockchain node to execute corresponding processing.
The structure of the event may be, for example:
Event：
[topic][data]
[topic][data]
......
in the above example, the number of events may be one or more; wherein, each event respectively comprises fields of a subject (topic) and data (data). The blockchain node or the node device deploying the blockchain node may perform the preset processing by monitoring the topic of the event, in case that the predefined topic is monitored, or read the related content from the data field of the corresponding event, and may perform the preset processing based on the read content.
In the event mechanism, it is equivalent to that there is a client with a monitoring function at a monitoring party (e.g. a user with a monitoring requirement), for example, an SDK or the like for implementing the monitoring function is run on the client, and the client monitors events generated by the blockchain node, and the blockchain node only needs to generate a receipt normally. The passage of transaction information may be accomplished in other ways than through the event mechanism described above. For example, the monitoring code can be embedded in a blockchain platform code running at blockchain nodes, so that the monitoring code can monitor one or more data of transaction content of blockchain transactions, contract states of intelligent contracts, receipts generated by contracts and the like, and send the monitored data to a predefined monitoring party. Since the snoop code is deployed in the blockchain platform code, rather than at the snooper's client, this implementation based on snoop code is relatively more proactive than the event mechanism. The above monitoring code may be added by a developer of the blockchain platform in the development process, or may be embedded by the monitoring party based on the own requirement, which is not limited in this specification.
The blockchain technology is different from the traditional technology in one of decentralization characteristics, namely accounting is performed on each node, or distributed accounting is performed, and the traditional centralized accounting is not performed. To be a difficult-to-defeat, open, non-falsifiable data record decentralized honest and trusted system, the blockchain system needs to be secure, unambiguous, and irreversible in the shortest possible time for distributed data records. In different types of blockchain networks, in order to keep the ledger consistent among the nodes recording the ledger, a consensus algorithm is generally adopted to ensure that the consensus mechanism is the aforementioned mechanism. For example, a common mechanism of block granularity can be implemented between block nodes, such as after a node (e.g., a unique node) generates a block, if the generated block is recognized by other nodes, other nodes record the same block. For another example, a common mechanism of transaction granularity may be implemented between the blockchain nodes, such as after a node (e.g., a unique node) acquires a blockchain transaction, if the blockchain transaction is approved by other nodes, each node that approves the blockchain transaction may add the blockchain transaction to the latest block maintained by itself, and finally, each node may be ensured to generate the same latest block. The consensus mechanism is a mechanism for the blockchain node to achieve a global consensus on the block information (or called blockdata), which can ensure that the latest block is accurately added to the blockchain. The current mainstream consensus mechanisms include: proof of Work (POW), Proof of stock (POS), Proof of commission rights (DPOS), Practical Byzantine Fault Tolerance (PBFT) algorithm, HoneyBadgerBFT algorithm, etc.
Due to the decentralized characteristic of the blockchain network, all blockchain nodes in the blockchain network can maintain the same blockchain data, and the special requirements of part of nodes cannot be met. Taking a federation chain as an example, all federation members (i.e., node members in a federation) may form a blockchain network, and all federation members respectively have corresponding blockchain nodes in the blockchain network, and may obtain all transactions and related data occurring on the blockchain network through the corresponding blockchain nodes. However, in some cases, there may be some federating members that also participate in forming other blockchain networks, so that these members also deploy other blockchain nodes in the node devices where the corresponding blockchain nodes in the blockchain networks are located.
For example, there may be some federating members who wish to complete some transactions with privacy requirements, which may both wish to be able to verify on the blockchain or to take advantage of other advantages of blockchain technology, and avoid other federating members from viewing the transactions and related data. Although the federating members can additionally create a new blockchain network, which is similar to the blockchain network including all federating members, it is very time-consuming to create a new blockchain network from scratch, and the creation process or the post-creation configuration process of the blockchain network is very time-consuming. The demand between the members of the federation is often temporary or has a certain timeliness, so that the newly-built blockchain network can quickly lose significance due to the disappearance of the demand, thereby further increasing the link establishment cost of the blockchain network. The demands among the federating members often change, and the federating members corresponding to each demand often differ, so that a new blockchain network may need to be created every time a federating member changes, thereby causing a great waste of resources and time.
For this purpose, the created blockchain network may be used as a blockchain master network, and a blockchain sub-network may be created on the basis of the blockchain master network. Then, in a federation chain scenario such as that described above, federation members may create a required blockchain subnet on the basis of a blockchain master based on their own needs, with already participating in the blockchain master. Because the blockchain subnets are established on the basis of the blockchain main network, compared with a process of completely and independently establishing a blockchain network, the process of establishing the blockchain subnets greatly reduces consumed resources, required time consumption and the like, and has high flexibility.
The process of quickly creating a blockchain subnet based on a blockchain master network is briefly described as follows: each main network node in the block chain main network respectively acquires a transaction for creating a block chain sub-network so as to reveal configuration information, and when the configuration information contains identity information of a node member corresponding to a first main network node, a node device of the first main network node is deployed based on the creation block containing the configuration information and starts a first sub-network node belonging to the block chain sub-network.
The transaction for creating the blockchain subnet can be initiated by an administrator of the blockchain main network, that is, the administrator is only allowed to create the blockchain subnet on the basis of the blockchain main network, and the creation authority of the blockchain subnet is prevented from being opened to an ordinary user, so that the security problem caused by the creation authority is prevented. In some cases, a general user of the blockchain main network may also be allowed to initiate the transaction for creating the blockchain subnet, so as to meet the networking requirements of the general user, and the general user can still quickly create the blockchain subnet under the condition that an administrator is not convenient to initiate the transaction.
Taking fig. 4 as an example, the blockchain main network is main web 0, and the blockchain link points included in main web 0 are nodeA, nodeB, nodeC, nodeD, and nodeE, etc. Assume nodeA, nodeB, nodeC, and nodeD wish to create a blockchain subnet: if nodeA is an administrator and only allows the administrator to initiate the transaction to create the blockchain subnet, the transaction to create the blockchain subnet may be initiated by nodeA to mainnet 0; alternatively, nodeB-nodeE may make a request to nodeA, causing nodeA to initiate the aforementioned transaction to create blockchain subnets to mainnet 0. If nodeA is an administrator but allows a normal user to initiate a transaction to create a blockchain subnet, nodeA-nodeE may each initiate the above transaction to mainnet 0. Of course, the blockchain link point initiating the transaction to create the blockchain subnet does not necessarily participate in the created blockchain subnet, whether by an administrator or by a general user, for example, although the blockchain subnet is ultimately created by nodeA, nodeB, nodeC, and nodeD, the transaction to create the blockchain subnet may be initiated by nodeE to main 0, and the transaction is not necessarily initiated by nodeA to nodeD.
When creating the blockchain subnet based on the blockchain main network, it is easy to understand that there is a logical hierarchical relationship between the blockchain subnet and the blockchain main network. For example, when creating a block chain subnet1 on main 0 shown in fig. 4, it can be considered that main 0 is at the first layer and subnet1 is at the second layer, i.e., main 0 is the parent network of subnet1 and subnet1 is the subnet of main 0. For example, another blockchain subnet1.1 may be further created on the basis of subnet1 in fig. 4, at this time, it may be considered that the subnet is at the third layer, subnet1 is a parent network corresponding to subnet1.1, subnet1.1 is a subnet1, and subnet1.1 is a subnet of mainnet 0. Likewise, subnet1.1 can still create a new blockchain subnet on its basis, so that such a multi-level tree structure is formed between blockchain networks.
In this specification, any blockchain network may be managed by its corresponding parent network, i.e., the blockchain network that created the any blockchain network. For example, in a multi-level tree structure such as fig. 4 in which a block chain master network is a root node (the lowest level of the root node), and each block chain sub-network is another node, a block chain sub-network represented by any node is managed by a block chain network corresponding to its parent node, and as a specific example, when the block chain master network is a bottom layer block chain network, the block chain master network is managed by the block chain master network itself. The blockchain main network in this specification may be a bottom-layer blockchain network, where the bottom-layer blockchain network refers to a blockchain sub-network that is not created on the basis of other blockchain networks, and therefore there is no other blockchain network other than the blockchain main network to manage the blockchain main network, for example, as shown in fig. 4, main network 0 may be regarded as a blockchain main network belonging to a type of bottom-layer blockchain network, and main 0 manages main network 0 itself. Of course, the blockchain main network may also be a subnet of other blockchain networks, which is not limited in this specification. Above-mentioned multilayer tree structure has realized successive layer management through the mode of father node management corresponding child node, has reduced the management pressure of block chain major network, avoids exposing the subnet information of upper network to the lower network simultaneously to realize the secret management of network at all levels.
In this specification, a node device may implement deployment of blockchain nodes by creating an instance of a running blockchain platform code in a process. For example, the node device may first create a first instance in a process to form a blockchain node in a blockchain master network; when the node member corresponding to the node device wishes to participate in creating the blockchain subnet, a second instance can be created in the process, the second instance is different from the first instance, and the blockchain node in the blockchain subnet is formed by the second instance. When the first instance and the second instance are located in the same process, the cross-process interaction is not involved, so that the deployment difficulty of the first subnet node can be reduced, and the deployment efficiency can be improved. Of course, the second instance may be in a different process on the node device than the first instance, and this specification does not limit this.
In fact, each block link point deployed on any node device related to the embodiments of the present specification is a different block chain instance running on any node device, blocks generated by each block link point deployed on any node device and account data of a created target account are respectively stored in different independent databases on any node device, and the independent databases used by each block link point deployed on any node device are isolated from each other. For example, the node device may create a first instance in a first process to form a first blockchain node in a blockchain master network; when the node member corresponding to the node device wishes to participate in creating the blockchain subnet, a second process different from the first process may be started, and a second instance different from the first instance may be created in the second process, so that the second blockchain node in the blockchain subnet is formed by the second instance.
Through the method, the block chain sub-network managed by the block chain main network can be created on the block chain main network. Taking fig. 4 as an example, regarding main net0 including nodeA-nodeE, subnet1 may be created on the basis of main net0, where subnet1 includes nodeA 1-nodeD 1, and any subnet node in subnet1 is deployed in the same node device as its corresponding main network node in main 0, for example, nodeA and nodeA1 are deployed in node device A, nodeB, nodeB1 is deployed in node device B, nodeC, and nodeC1 is deployed in node device C, nodeD, and nodeD1 is deployed in node device D. Similarly, a subnet2 or more blockchain subnets may also be created on mainnet0, where subnet2 contains nodeA2, nodeB2, nodeC2, and nodeE2, and nodeA1, nodeA2, nodeB and nodeB1, nodeB2, nodeC and nodeC1, nodeD and nodeD1, and nodeE2 are deployed on the same node device, respectively. And, subnet1, subnet2, etc. may be used as a blockchain main network, and a blockchain subnet is further created based on this, for example, a blockchain subnet1.1 is created based on subnet1, the process is similar to the creation of subnet1 or subnet2, only the blockchain main network is replaced by blockchain subnet1, which is not described herein, and finally, subnet1.1 includes nodeA3, nodeB3 and nodeC3, so that nodeA and nodeA1, nodeA2, nodeA3, nodeB and nodeB1, nodeB2, nodeB3, nodeC and nodeC1, nodeC2 and nodeC3 are respectively deployed on the same node device. It can be seen that the node device a is deployed with the master node nodeB and the subnet nodes nodeB1, nodeB2, and nodeB1.1, and the node device B is deployed with the master node nodeB and the subnet nodes nodeB1, nodeB2, and nodeB1.1, and the node device B and the node device C are similar to the node device a and will not be described again. The node device D has a master node nodeb and a subnet node nodeb deployed therein, and the node device E has a master node nodeb and a subnet node nodeb2 deployed therein.
In addition, for the node device with a plurality of blockchain nodes, a common database corresponding to the plurality of blockchain nodes is also maintained, and the common database is used for recording account data of common accounts among the plurality of blockchain networks. At least one common database may be maintained in the node device, and any common database may correspond to a plurality of networks in all of the blockchain networks in which the node device participates. Taking the node device a where the four blockchain nodes nodeA, nodeA1, nodeA1.1, and nodeA2 shown in fig. 4 are located as an example, as shown in fig. 5, a common database corresponding to a plurality of blockchain networks is deployed in the blockchain node, and the database may be used to record account data of common accounts among the plurality of blockchain networks. For example, if the common database corresponds to two blockchain networks, mainnet0 and subletea, the account may record account data for a common account between the two; if the common database corresponds to three blockchain networks of subnet a, subnet a1, and subnet a2, the account may record account data for a common account among the three.
In addition, in some embodiments, an independent database corresponding to each block link point may be maintained in the node device: such as independent database 0 corresponding to nodeA, independent database 1 corresponding to nodeA, independent database 1.1 corresponding to nodeA1.1 and independent database 2 corresponding to nodeA 2. Any one of the independent databases may be configured to record account data of a target account created in a corresponding blockchain node. For example, the independent database 0 is used to record account data of a target account created in nodeA, such as account on main 0 in the figure, where the independent account may be an external account or a contract account; the account data of any target account can be an account address, an account public and private key pair, an account historical operation record and the like of the account. In addition, an intelligent Contract created in the Block chain network where the account is located, such as a Contract in the figure, and a history Block generated in the Block chain network where the account is located, such as a Block in the figure, may also be recorded in the independent database corresponding to any Block link point. As can be seen, the common database corresponding to the plurality of block link points may be only used for recording account data of a common account between the block chain networks to which the plurality of block link points belong. Considering that data such as blocks, intelligent contracts and the like maintained by blockchain nodes in different blockchain networks are often different, such information in any blockchain network can be recorded in an independent database corresponding to the network, rather than in a common database with other blockchain networks, so as to implement isolation of the data.
It is to be understood that the multi-level tree structure shown in fig. 4, which includes the blockchain main network and the blockchain sub-networks, is merely an example, and is one possible structure form between the first blockchain network and the other blockchain networks in the present solution. In practical applications, the blockchain network to which the plurality of blockchain nodes belong in the node device may not follow the multi-level structure. In other words, in addition to the blockchain main network and the blockchain sub-network managed by the blockchain main network, the blockchain network to which any blockchain node deployed in the node device belongs may also be an independent blockchain network, and the aforementioned management/managed relationship does not exist between such an independent blockchain network and other blockchain networks. As shown in fig. 1, the independent blockchain network mainnet1 is independent from the main blockchain network 0 and the sub-networks subnet1, subnet2, subnet1.1, etc., so that the main blockchain network 1 and the other blockchains do not have a management/managed relationship between the blockchain main network and the blockchain sub-network. However, cross-chain interaction may also be implemented between any of the independent blockchain networks and each of the other blockchain networks, for example, in a case where nodeF, nodeG, and nodeH in main 1 are respectively deployed in the foregoing node apparatus a, node apparatus B, and node apparatus C, the foregoing network connection links are respectively established between the above-mentioned nodes of main 1 and nodes nodeA1, nodeB1, and nodeC1 in subnet1, and therefore, cross-chain interaction may be implemented between the independent blockchain network main 1 and the blockchain subnet1 based on the above-mentioned network connection links. Similarly, the cross-chain interaction between the independent blockchain network main 1 and the blockchain sub-network subnet2 and the blockchain main network main 0 can also be realized based on the corresponding network connection links. It should be noted that even if the node devices of the nodes of any two blockchain networks are not completely the same or even completely different, the inter-device network connection between the node device of each node and other node devices can still implement the inter-chain interaction between the two blockchain networks, and the detailed process is not repeated.
As described above, a plurality of blockchain nodes respectively belonging to different blockchain networks may be deployed in the same node device, where any blockchain network may create and maintain corresponding accounts in the process of implementing functions such as message consensus, contract execution, and the like, and account data of the accounts may be usually recorded in a database by the node device, in other words, an account system of the blockchain network to which each blockchain node belongs may be maintained in the node device.
In the above scenario, in order to manage and utilize the relevant accounts and their account data in the blockchain network, the node device and the blockchain link points deployed therein need to record the account data of the blockchain accounts in each blockchain network through the database and how to perform read/write operations on the account data. How to reduce the account data required to be maintained by the node device in the process of recording the account data and performing read-write operation is an urgent problem to be solved.
The inventors have discovered that there may be the same blockchain accounts between multiple blockchain networks. In contrast, if the account data of the part of the blockchain accounts can be managed and read and written uniformly, the node device only needs to maintain one account data, and thus the account data required to be maintained by the node device is expected to be reduced.
For a plurality of block chain nodes which are deployed in node equipment and respectively belong to different block chain networks, the node equipment maintains a common database corresponding to a plurality of block chain link points, the database is used for recording account data of common accounts among the plurality of block chain networks, and then a read-write request aiming at a target account is responded based on the data recording mode, and read-write operation is carried out on the corresponding account data. The following describes a creation scheme of a block chain subnet in the present specification with reference to the drawings.
Fig. 6 is a flowchart of a method for reading and writing account data according to an exemplary embodiment. As shown in fig. 6, in the method, a first blockchain node in a first blockchain network, a node device where the first blockchain node is located is also deployed with blockchain nodes of other blockchain networks, and the node device maintains a common database corresponding to a plurality of blockchain nodes, where the common database is used to record account data of common accounts between the plurality of blockchain networks, and the method includes the following steps:
As described above, a plurality of block chain nodes are deployed in the node device described in this specification, and each block chain node belongs to a different block chain network. In addition, the node equipment maintains a common database corresponding to a plurality of block link points, and the database is used for recording account data of common accounts among block chain networks to which the plurality of nodes belong. The first block link point may be any one of the plurality of block link nodes deployed in the node device, and obviously, the first block link network to which the node belongs is any one of the plurality of block link networks. In addition, the block chain network to which each block chain link point deployed in the node device described in this specification belongs may follow the aforementioned multi-level tree structure. For example, the first blockchain network may be any blockchain network therein, that is, the first blockchain network may be any blockchain sub-network or blockchain main network in the multi-level tree structure.
A plurality of public databases can be maintained in the same node device, and any public database can be used for recording account data of a public account between at least two block chains; or, only one public database may be maintained in the same node device, where the public database may record account data of public accounts among any multiple blockchain networks, and in order to avoid confusion between any public account and a blockchain network corresponding to the public account, corresponding network identifiers may be added to the account data of each public account, so as to characterize which blockchain networks each account may share. The public database described in the embodiments of the present specification may be any public database maintained by the node device, and any public account recorded in the public database may be managed by each blockchain network corresponding to the account, and accordingly, the read/write operation may be performed by each blockchain link point of each blockchain network corresponding to the account, which is deployed in the node device.
As shown in fig. 4, public databases D1 and D2 may be disposed in node device a, where public database D1 may be configured to record account data of a public account between sublet 1 and sublet 2, public database D2 may be configured to record account data of a public account between main 0, sublet 1, and sublet 2, and of course, other public databases may also be disposed to record account data of a public account between sublet 1 and sublet 2, account data of a public account between sublet 2 and sublet 1.1, and so on, or, in a case where any node (e.g., nodeF) in main 1 is disposed in node device a, other public databases may also be disposed to record account data of a public account between main 0 and main 1, account data between main 1 sublet 1 and sublet 2, and so on a one-by-one basis. Or, a common database D may also be deployed in the node device a, where the common database D may be used to record account data of a common account between any multiple networks shown in fig. 1, for example, may record account data of a common account between subnet1 and subnet2, and may add network identifiers of the two networks to the part of account data, so as to characterize the part of account data as being managed by both subnet1 and subnet 2; the public database D may also record account data of a public account among main 0, subnet1, and subnet2, and may add network identifiers of the three networks to the part of account data, so as to represent that the part of account data is managed by main 0, subnet1, and subnet2, which is not described again.
It should be noted that, for account data of a common account between multiple blockchain networks recorded in any common database, a blockchain link point of any blockchain network in the multiple blockchain networks may perform read and write operations on the account data. In the case of performing the write operation, the written new data may be read by the blockchain node of any blockchain network in the multiple blockchain networks, or may be changed after rewriting other data by the blockchain node of any blockchain network in the multiple blockchain networks, which is not described again.
In an embodiment, the first blockchain network may include an independent account in addition to the common account, that is, the blockchain accounts in the first blockchain network may include two types: a public account and an independent account; accordingly, any blockchain account in the first blockchain network may be a common account or an independent account. The independent account in any blockchain network is a blockchain account only belonging to the network, and the account data of the blockchain account is only recorded in the independent database corresponding to the blockchain network, but not recorded in other databases. For the independent account and the independent database, reference may be made to the following detailed description of the embodiments, which is not repeated herein.
In this embodiment, the read-write request for the target account is used to trigger a read-write operation on account data of the target account, specifically, the read-write operation may be a data read operation, and may also be a data write operation. The read-write request may include a network identifier of a blockchain network to which the target account belongs (hereinafter referred to as a target blockchain network), so that the first blockchain link point determines which blockchain network the request needs to be responded to according to the network identifier; the read-write request may also include the account address and/or public key and other identity information of the target account, so that the first block link point determines which account the target account is; the read-write request may further include operation information of the read-write operation for the target account, such as a data identifier of the data to be read, the data to be written, and the like, so that the first block link point executes the corresponding read-write operation accordingly. It is worth noting that, from the perspective of the underlying operations of the database, the data read operation may correspond to a read action for data, and the data write operation may correspond to an add, delete, and modify action for data.
In addition, the first block link point may obtain the read/write request in various ways. For example, a first block link point may receive a read-write request acquired and sent by a node device; for another example, the first blockchain link point may also receive a read-write request sent by another blockchain node (such as a blockchain node in the first blockchain network or another blockchain network) deployed in the node device; in both of these two acquisition modes, the read/write request may be a blockchain transaction or a non-transaction blockchain message. For another example, the first blockchain link point may also generate the read/write request during the course of performing blockchain transaction, and in this case, the request may be a non-transaction blockchain message, which is not limited in this embodiment of the present disclosure.
Typically, accounts in a blockchain network may include external accounts that may be controlled by a corresponding public-private key pair and contract accounts that may be created by an intelligent contract and controlled by corresponding contract code. Any individual account in the first blockchain network may be an external account or a contract account, and thus the target account described herein may be either an external account or a contract account. Of course, when the number of the target accounts is multiple, the multiple target accounts may be multiple external accounts, multiple contract accounts, or at least one external account and at least one contract account, and the embodiments of the present specification are only described with respect to any one of the accounts.
In response to the acquired read-write request, the first blockchain link point may determine whether the account data of the target account is recorded in a public database corresponding to the first blockchain network to which the first blockchain point belongs. For example, when the first blockchain link point maintains the account address of each blockchain account in the first blockchain network, the first blockchain link point may determine, according to the account address of the target account carried in the read/write request, whether the target account is a blockchain account maintained by itself: under the condition that the account address of any block chain account maintained by the block chain system is the same as the account address of the target account, determining the block chain account as the target account; on the contrary, if the account address of each block chain account maintained by the system is different from the account address of the target account, it may be determined that the target account does not belong to the first block chain network, so that the response process for the read-write request may be terminated.
In a case where it is determined that the target account is maintained by itself, the first blockchain link point may determine the public database corresponding to the first blockchain network according to a correspondence between the network identifier of the first blockchain network and the public database. Further, the first block link point may look up the target account from the common database and perform read and write operations on its account data.
Under the condition that a plurality of block chain nodes respectively belonging to different block chain networks are deployed in the node equipment, the node equipment also maintains a public database corresponding to the plurality of block chain nodes, and the public database is used for recording account data of public accounts among the plurality of block chain networks. Based on the recording mode of the account data, for the obtained read-write request for the target account, the first block link point or the node device may search the target account from the public database and perform read-write operation on the account data of the target account when the account data of the target account is recorded in the public database.
Through the above manner, the node device can store the account data of the common account between different blockchain networks in the common database, and perform read-write operation on the account data of the account recorded in the common database in response to the read-write request for the common account. Therefore, the multiple blockchain networks can maintain the common account together, a shared management scheme for the common account is realized, the multiple independent blockchain networks can have the shared common account, the account system under the scene of the multiple blockchain networks is simplified to a certain extent, and the workload of maintaining the account by the node equipment is reduced. Moreover, due to the sharing characteristic of the common account, the operation result of the read-write operation performed by the first block chain network on the account data of the target account can also be used (for example, read) by other block chain networks, so that the unified operation of different block chain nodes on the same account is realized, and the management and utilization efficiency of the common account is improved.
In an embodiment, the read/write request may be a blockchain transaction including an account address of the target account, and the first blockchain link point may determine the independent database and perform the read/write operation in a corresponding manner according to a recording manner of the account address in the blockchain transaction. As an exemplary embodiment, the account address of the target account may be included in a from field of the blockchain transaction, and the record indicates that the blockchain transaction is initiated by the target account, so that the first blockchain link point may search the target account in the public database corresponding to the first blockchain network according to the account address, and read the recorded account public key from the searched target account. It can be seen that the read-write operation performed by the link point of the first block is to read the account public key of the target account from the target account, that is, the read-write operation is to read data. The account public key of the target account read in the above manner may be used to verify a transaction signature of the blockchain transaction (i.e., verify that the target account is a transaction signature added to the transaction), and if the verification passes, the first blockchain link node may submit the transaction to the first blockchain network to participate in consensus or directly execute the transaction; in the case of failed verification, the first block link point may terminate the response process for the transaction, and may perform recording, warning, etc. processing on the illegal transaction. In this way, the first blockchain link point can read the account public key of the target account from the public database recording account data of the public account in response to the read-write request, and check and sign the blockchain transaction initiated by the target account based on the public key, thereby being beneficial to ensuring the validity and reliability of the blockchain transaction responded by the J1.
As another example embodiment, the account address of the target account may be included in the to field of the blockchain transaction, and the data field of the transaction may also include the participation information. The above-mentioned recording mode of the account address of the target account indicates that the blockchain transaction is initiated from other accounts to the target account, so that the first blockchain link point can search the target account in the public database corresponding to the first blockchain network according to the account address, and perform read-write operation on the account data of the searched target account according to the access information. The reading and writing operation executed by the first block link point may be a data reading operation, and the access parameter information may be a data reading method or information such as a data identifier and an account balance of data to be read; alternatively, the read/write operation performed by the first block link point may also be a data write operation, and the entry parameter information may be data to be written. By the method, the first block chain link point can respond to the read-write request and execute read-write operation on account data of the target account according to the access information in the read-write request, so that the execution process of the block chain transaction is completed.
In an embodiment, the common database corresponding to the plurality of block link points may be further configured to record account data of independent accounts in the block chain network to which the block link points respectively belong, and the common database further records account types of each common account and the target account. In this scenario, the first tile link point may look up a target account from the common accounts according to the account type. For example, in the case that the account type of the target account is a common account, the first block link point may search the target account from the common accounts recorded in the common database; and in the case that the account type of the target account is an independent account, the first block link point can search the target account from the independent accounts recorded in the common database. By the method, when the first blockchain node searches the target account in the plurality of blockchain accounts maintained in the public database, each blockchain account to be searched can be divided according to the account type, and then the target account is searched only from the blockchain account of the type of the target account, so that the number of accounts to be searched is reduced, and the searching efficiency of the target account is improved.
In another embodiment, in addition to the aforementioned common database, the node device may also maintain an independent database corresponding to each block link point, where the independent databases are used to record account data of target accounts in the block link network to which the corresponding block link node belongs. In this scenario, for the read-write request acquired by the first blockchain link point, the account data of the target account corresponding to the read-write request may be recorded in a public database corresponding to the first blockchain network, or may be recorded in an independent database corresponding to another blockchain network. In other words, the target account may be a common account or an independent account. Based on this, the first block link point may, in a case where the account type of the target account is determined to be a common account, search the common database for the target account and perform a read-write operation on account data of the target account. In addition, when the account type of the target account is an independent account, the first block link point may first determine an independent database corresponding to the first block link node on the node device, and then search the target account from the independent database and perform a read-write operation on account data of the target account. By the method, the first block link point can quickly determine the database for recording the account data according to the account type of the target account, and executes read-write operation on the account data, so that the response efficiency of read-write requests is high.
In addition, when it is determined that the account data of the target account is not recorded in the common database corresponding to the first block link point, the first block link point may transmit the read-write request to the node device, so that the node device determines, from the individual databases maintained by the node device, the individual database in which the account data of the target account is recorded, and submits the request to the block chain network corresponding to the determined individual database. It is understood that the node device may access any locally deployed database, and thus the node device may access the independent database corresponding to the first blockchain network and the independent databases corresponding to the other blockchain networks, respectively. The blockchain network to which the target account belongs is not marked as the target blockchain network. Based on the above manner, the first blockchain node may transmit the request to the node device when determining that the account data of the target account is not recorded in the public database corresponding to the first blockchain node, so that the node device determines the target blockchain network in each blockchain network according to whether the target account is recorded in the database corresponding to each blockchain network, and further submits the read-write request to the determined network. Of course, after the node device submits the read-write request to the target blockchain network, the blockchain link point deployed in the node device and belonging to the network may also respond to the request to perform read-write operation on account data of the target account recorded in the independent database corresponding to the network, and the specific process is similar to the execution process of the first blockchain node and is not described again.
By the method, by utilizing the characteristic that the node equipment can access any locally deployed database, under the condition that the account data of the target account is not recorded in the public database corresponding to the first block chain network, the independent database in which the account data of the target account is recorded can still be determined from the independent databases corresponding to the networks, so that the read-write operation is performed on the account data in the database, and the effective response to the read-write request is realized.
When the read-write request is a blockchain transaction, the transaction may include an account type field for characterizing an account type of the target account. For example, the account type field may be part of a data field of a blockchain transaction, i.e., the account type of the target account is recorded in the data field of the blockchain transaction. Thus, the first block link point may determine the account type of the target account according to the field value of the account type field. By the method, the initiator of the blockchain transaction can directly designate the account type of the target account to be operated, so that the first blockchain link point can quickly execute read-write operation on account data according to the account type, the data maintenance amount of the first blockchain node is reduced, and the response efficiency of the read-write request is improved.
As described above, in a case that account data of a target account is not recorded in a common database corresponding to the first blockchain network, the node device may determine, from independent databases respectively corresponding to locally deployed blockchain nodes, an independent database in which account data of the target account is recorded, where the independent database may be determined by the node device in various ways. For example, based on the fact that the node device can access any database maintained by itself, the node device may determine an independent database recording account data of the target account from all independent databases maintained by itself. For another example, considering that it is the first blockchain node in the first blockchain network that performs the read-write operation in response to the read-write request, the node device may determine, when the account data of the target account is not recorded in the independent database corresponding to the first blockchain network and the first blockchain network has an access right to the independent database corresponding to the other blockchain network, the independent data in which the account data of the target account is recorded from the independent databases corresponding to the other blockchain networks. The independent database determined by the method records the account data of the target account, the first block chain network has access authority for the database, and the first block chain link point in the first block chain network naturally also has access authority, so that the first block chain link point can execute read-write operation for the account data in the database based on the access authority. For the independent database, the first block chain link point for performing the read-write operation on the account data recorded in the independent database has legal access authority, so that the legality of the performed read-write operation is ensured. In addition, the first blockchain network may only have access rights to a part of independent databases deployed in the node device, and therefore to improve efficiency of determining the independent database for recording the account data of the target account, the node device may first determine the part of the independent databases having access rights in the first blockchain network, and then determine the independent database for recording the account data of the target account from the part of databases.
Specifically, the node device may maintain a network identifier of a blockchain network to which each locally deployed blockchain point belongs, so that which network of the blockchain networks to which each locally deployed blockchain point belongs is the target blockchain network may be determined according to the network identifier of the target blockchain network included in the read-write request, and a database corresponding to the target blockchain network may be an independent database for recording account data of the target account.
Further, a multi-level blockchain system may be formed between blockchain networks to which a plurality of blockchain nodes deployed on the node device respectively belong, and any blockchain network may be managed by a parent blockchain network in the multi-level blockchain system. The independent database corresponding to the first block link point can inherit and maintain a copy of account data of a target account in a parent block link network. The multi-level blockchain system may have a multi-level tree structure as shown in fig. 4, and is described below with reference to the node device a shown in fig. 5: if it is not assumed that the first blockchain network is subnet1 and the parent blockchain network is main 0, when node device a participates in creating subnet1 on the basis of main 0, it may first determine an account to be inherited from all blockchain accounts of main 0, then read the account data of the account to be inherited from independent database 0, and write the data into independent database 1 corresponding to newly created subnet1, thereby forming a copy of the account data of the account to be inherited in the database.
It is understood that the copy of the account data stored in the independent database 1 is only the account data recorded in main 0 at the creation time of subnet1 (i.e. the time of reading the account data of the account to be inherited from the independent database 0), i.e. the data copy can be regarded as a "snapshot" of the account data stored in the independent database 1 at the creation time. After completion of creation of subnet1, the account data recorded in independent database 0 may be updated as main 0 runs, the copy of the account data recorded in independent database 1 may be updated as subnet1 runs, and the updating processes of the two are independent of each other. Of course, the node device may also create each account to be inherited only in the independent database 1 corresponding to the newly created subnet1, and not copy the copy of the corresponding account data, so as to save only the account data generated by the operation node of the subnet1 in the independent database 1. Through the manner, the first blockchain network can inherit the original target account from the parent blockchain network, or inherit the original target account and the account data thereof, so that a user does not need to repeatedly create an existing account in main 0 in newly created subnet1, and each node in subnet1 does not need to acquire the account data from other blockchain networks, thereby simplifying the creation process of a new network and being beneficial to improving the creation efficiency.
Alternatively, the first block link point may have an access right to an independent database corresponding to its parent block link network. Still taking fig. 4 and fig. 5 as an example, it is not assumed that the first blockchain network is subnet1, the parent blockchain network is mainnet0, and nodeA1 in subnet1 is a first blockchain node, and then the first blockchain node may have an access right to independent database 0 corresponding to mainnet 0. In order to ensure the security of the account data recorded in the independent database of the parent blockchain network as much as possible, only some nodes may have access rights to the independent database 0, for example, the main node of subnet1 has the access rights, and other nodes do not have the access rights. The first blockchain node is a node having an access right to the independent database corresponding to the parent blockchain network. Of course, any node in main 0 may also have access right to the independent database 1 corresponding to subnet1, and details are not described again.
Based on the description of the foregoing embodiments, the present specification also provides another method for reading and writing account data. As shown in fig. 7, the method is applied to a node device, where a plurality of blockchain nodes respectively belonging to different blockchain networks are deployed in the node device, and the node device maintains a common database corresponding to the plurality of blockchain nodes, where the common database is used to record account data of a common account between the plurality of blockchain networks, and the method includes the following steps:
In an embodiment, the node device further maintains an independent database corresponding to each blockchain node, where the independent database is used to record account data of a target account in a blockchain network to which the corresponding blockchain node belongs;
the searching the target account from the public database and executing the read-write operation on the account data of the target account comprises: under the condition that the account type of the target account is a common account, searching the target account from the common database and executing read-write operation on account data of the target account;
the method further comprises the following steps: and under the condition that the account type of the target account is an independent account, determining an independent database corresponding to the first block chain node on the node equipment, searching the target account from the determined independent database, and executing read-write operation on account data of the target account.
In one embodiment, the method further comprises:
receiving an assistance request of transparent transmission of a first block link point in a first block chain network, wherein the assistance request is transmitted by a first block chain node under the condition that account data of the target account is not recorded in the public database;
and determining an independent database for recording the account data of the target account from each independent database maintained by the user, and submitting the assistance request to a block chain network corresponding to the determined independent database.
In an embodiment, the determining, from the independent databases maintained by the independent databases, an independent database recording account data of the target account includes:
determining an independent database for recording account data of the target account from all independent databases maintained by the node equipment; alternatively, the first and second electrodes may be,
and under the condition that the account data of the target account is not recorded in the independent database corresponding to the first blockchain network and the first blockchain network has access right to other independent databases corresponding to other blockchain networks, determining the independent database for recording the account data of the target account from other independent databases.
In an embodiment, a multi-level blockchain system is formed between blockchain networks to which a plurality of blockchain nodes deployed on the node device respectively belong, and any blockchain network is managed by a parent-level blockchain network in the multi-level blockchain system; wherein:
the independent database corresponding to the first block chain point inherits and maintains a copy of account data of a target account in a parent block chain network; alternatively, the first and second electrodes may be,
the first block link point has access to an independent database corresponding to its parent block link network.
In an embodiment, the public database is further configured to record account data of target accounts in a plurality of blockchain networks, and the public database further records account types of each public account and each target account; the searching the target account from the public database comprises:
searching the target account from the public accounts recorded in the public database under the condition that the account type of the target account is a public account;
and searching the target account from the independent accounts recorded in the public database under the condition that the account type of the target account is an independent account.
In one embodiment, the target account includes: an external account and/or a contract account.
The node device may store account data of a common account between different blockchain networks in a common database, and perform a read-write operation on the account data of the account recorded in the common database in response to a read-write request for the common account. Therefore, the multiple blockchain networks can maintain the common account together, a shared management scheme for the common account is realized, the multiple independent blockchain networks can have the shared common account, the account system under the scene of the multiple blockchain networks is simplified to a certain extent, and the workload of maintaining the account by the node equipment is reduced. Moreover, due to the sharing characteristic of the common account, the operation result of the read-write operation performed by the first block chain network on the account data of the target account can also be used (for example, read) by other block chain networks, so that the unified operation of different block chain nodes on the same account is realized, and the management and utilization efficiency of the common account is improved.
Fig. 8 is a schematic structural diagram of an apparatus according to an exemplary embodiment. Referring to fig. 8, at the hardware level, the apparatus includes a processor 802, an internal bus 804, a network interface 806, a memory 808, and a non-volatile memory 810, but may also include hardware required for other services. One or more embodiments of the present description may be implemented in software, such as by the processor 802 reading a corresponding computer program from the non-volatile storage 810 into the memory 808 and then executing the computer program. Of course, besides software implementation, the one or more embodiments in this specification do not exclude other implementations, such as logic devices or combinations of software and hardware, and so on, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.
Fig. 9 is a block diagram of a device for reading and writing account data according to an exemplary embodiment. Referring to fig. 9, the apparatus may be applied to the device shown in fig. 8 to implement the technical solution of the present specification. The device for reading and writing account data is applied to a first block chain node in a first block chain network, block chain link points of other block chain networks are also deployed in node equipment where the first block chain link point is located, and the node equipment maintains a common database corresponding to a plurality of block chain nodes, wherein the common database is used for recording account data of common accounts among the plurality of block chain networks, and the device comprises:
a request obtaining module 901, configured to obtain a read-write request for a target account;
a first reading and writing module 902, configured to, when the account data of the target account is recorded in the public database, search the target account from the public database and perform a reading and writing operation on the account data of the target account.
Optionally, the read-write request is a blockchain transaction, and a from field of the blockchain transaction includes an account address of the target account; the first read-write module 902 is further configured to:
and searching the target account in the public database according to the account address, and reading a recorded account public key from the searched target account, wherein the account public key is used for verifying and signing the transaction signature of the block chain transaction.
Optionally, the data read-write request is a blockchain transaction, the to field of the blockchain transaction includes an account address of the target account, and the data field of the blockchain transaction includes access information; the first read-write module 902 is further configured to:
searching the target account in the public database according to the account address;
and executing read-write operation on the found account data of the target account according to the access information.
Optionally, the node device further maintains an independent database corresponding to each blockchain node, where the independent database is used to record account data of a target account in a blockchain network to which the corresponding blockchain node belongs;
the first read-write module 902 is further configured to: under the condition that the account type of the target account is a common account, searching the target account from the common database and executing read-write operation on account data of the target account;
the apparatus further comprises a second read-write module 903 for: and under the condition that the account type of the target account is an independent account, determining an independent database corresponding to the first block chain node on the node equipment, searching the target account from the determined independent database, and executing read-write operation on account data of the target account.
Optionally, the method further includes:
and a transparent transmission module 904, configured to transmit the read-write request to the node device in a transparent manner when the account data of the target account is not recorded in the public database, so that the node device determines, from each independent database maintained by the node device, an independent database in which the account data of the target account is recorded, and then submits the read-write request to the block link network corresponding to the determined independent database.
Optionally, the transparent transmission module 904 is further configured to:
determining an independent database for recording account data of the target account from all independent databases maintained by the node equipment; alternatively, the first and second electrodes may be,
and under the condition that the account data of the target account is not recorded in the independent database corresponding to the first blockchain network and the first blockchain network has access right to the independent databases corresponding to other blockchain networks, determining the independent database for recording the account data of the target account from the independent databases corresponding to other blockchain networks.
Optionally, a multi-level blockchain system is formed between blockchain networks to which a plurality of blockchain nodes deployed on the node device respectively belong, and any blockchain network is managed by a parent-level blockchain network in the multi-level blockchain system; wherein:
the independent database corresponding to the first block chain point inherits and maintains a copy of account data of a target account in a parent block chain network; alternatively, the first and second electrodes may be,
the first block link point has access to an independent database corresponding to its parent block link network.
Optionally, the public database is further configured to record account data of target accounts in a plurality of blockchain networks, and the public database further records account types of each public account and the target account; the first read-write module 902 is further configured to:
searching the target account from the public accounts recorded in the public database under the condition that the account type of the target account is a public account;
and searching the target account from the independent accounts recorded in the public database under the condition that the account type of the target account is an independent account.
Optionally, the data read-write request is a blockchain transaction, where the blockchain transaction includes an account type field, and the apparatus further includes:
a type determining module 905, configured to determine an account type of the target account according to a field value of the account type field.
Optionally, the target account includes: an external account and/or a contract account.
Optionally, the target account includes: an external account and/or a contract account.
Fig. 10 is a block diagram of a device for reading and writing account data according to an exemplary embodiment. Referring to fig. 10, the apparatus may be applied to the device shown in fig. 8 to implement the technical solution of the present specification. The apparatus for reading and writing account data is applied to a node device, where the node device is deployed with multiple blockchain nodes respectively belonging to different blockchain networks, and maintains a common database corresponding to the multiple blockchain nodes, where the common database is used to record account data of a common account among the multiple blockchain networks, and the apparatus includes:
a request obtaining module 1001, configured to obtain a read-write request for a target account;
the first reading and writing module 1002 is configured to, when the account data of the target account is recorded in the public database, search the target account from the public database and perform a reading and writing operation on the account data of the target account.
Optionally, the node device further maintains an independent database corresponding to each blockchain node, where the independent database is used to record account data of a target account in a blockchain network to which the corresponding blockchain node belongs;
the first read-write module 1002 is further configured to: under the condition that the account type of the target account is a common account, searching the target account from the common database and executing read-write operation on account data of the target account;
the apparatus further comprises a second read-write module 1003 for: and under the condition that the account type of the target account is an independent account, determining an independent database corresponding to the first block chain node on the node equipment, searching the target account from the independent database and executing read-write operation on account data of the target account.
Optionally, the method further includes:
an assistance request receiving module 1004, configured to receive an assistance request transmitted through a first blockchain link point in a first blockchain network, where the assistance request is transmitted through the first blockchain node when account data of the target account is not recorded in the public database;
an assistance request submitting module 1005, configured to determine, from each independent database maintained by itself, an independent database in which account data of the target account is recorded, and submit the assistance request to a blockchain network corresponding to the determined independent database.
Optionally, the assistance request submitting module 1004 is further configured to:
determining an independent database for recording account data of the target account from all independent databases maintained by the node equipment; alternatively, the first and second electrodes may be,
and under the condition that the account data of the target account is not recorded in the independent database corresponding to the first blockchain network and the first blockchain network has access right to other independent databases corresponding to other blockchain networks, determining the independent database for recording the account data of the target account from other independent databases.
Optionally, a multi-level blockchain system is formed between blockchain networks to which a plurality of blockchain nodes deployed on the node device respectively belong, and any blockchain network is managed by a parent-level blockchain network in the multi-level blockchain system; wherein:
the independent database corresponding to the first block chain point inherits and maintains a copy of account data of a target account in a parent block chain network; alternatively, the first and second electrodes may be,
the first block link point has access to an independent database corresponding to its parent block link network.
Optionally, the public database is further configured to record account data of target accounts in a plurality of blockchain networks, and the public database further records account types of each public account and the target account; the first read-write module 1002 is further configured to:
searching the target account from the public accounts recorded in the public database under the condition that the account type of the target account is a public account;
and searching the target account from the independent accounts recorded in the public database under the condition that the account type of the target account is an independent account.
Optionally, the target account includes: an external account and/or a contract account.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the various elements may be implemented in the same one or more software and/or hardware implementations of the present description.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks. In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments herein. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The above description is only for the purpose of illustrating the preferred embodiments of the one or more embodiments of the present disclosure, and is not intended to limit the scope of the one or more embodiments of the present disclosure, and any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the one or more embodiments of the present disclosure should be included in the scope of the one or more embodiments of the present disclosure.
Claims (21)
1. A method for reading and writing account data is applied to a first block chain node in a first block chain network, block chain link points of other block chain networks are also deployed in node equipment where the first block chain link point is located, and the node equipment maintains a common database corresponding to a plurality of block chain nodes, wherein the common database is used for recording account data of common accounts among the plurality of block chain networks, and the method comprises the following steps:
acquiring a read-write request aiming at a target account;
and under the condition that the account data of the target account is recorded in the public database, searching the target account from the public database and executing read-write operation on the account data of the target account.
2. The method of claim 1, the read and write request being a blockchain transaction, a from field of the blockchain transaction including an account address of the target account; the searching the target account from the public database and executing the read-write operation on the account data of the target account comprises:
and searching the target account in the public database according to the account address, and reading a recorded account public key from the searched target account, wherein the account public key is used for verifying and signing the transaction signature of the block chain transaction.
3. The method of claim 1, the data read and write request being a blockchain transaction, a to field of the blockchain transaction including an account address of the target account, and a data field of the blockchain transaction including participation information; the searching the target account from the public database and executing the read-write operation on the account data of the target account comprises:
searching the target account in the public database according to the account address;
and executing read-write operation on the found account data of the target account according to the access information.
4. The method according to claim 1, wherein the node device further maintains an independent database corresponding to each blockchain node, and the independent database is used for recording account data of target accounts in the blockchain network to which the corresponding blockchain node belongs;
the searching the target account from the public database and executing the read-write operation on the account data of the target account comprises: under the condition that the account type of the target account is a common account, searching the target account from the common database and executing read-write operation on account data of the target account;
the method further comprises the following steps: and under the condition that the account type of the target account is an independent account, determining an independent database corresponding to the first block chain node on the node equipment, searching the target account from the independent database and executing read-write operation on account data of the target account.
5. The method of claim 4, further comprising:
and under the condition that the account data of the target account is not recorded in the public database, the read-write request is transmitted to the node equipment in a transparent mode, so that the node equipment determines the independent database for recording the account data of the target account from each independent database maintained by the node equipment, and then submits the read-write request to the block chain network corresponding to the determined independent database.
6. The method of claim 5, wherein the node device determines an independent database recording account data of the target account from an independent database maintained by the node device, and the method comprises the following steps:
determining an independent database for recording account data of the target account from all independent databases maintained by the node equipment; alternatively, the first and second electrodes may be,
and under the condition that the account data of the target account is not recorded in the independent database corresponding to the first blockchain network and the first blockchain network has access right to the independent databases corresponding to other blockchain networks, determining the independent database for recording the account data of the target account from the independent databases corresponding to other blockchain networks.
7. The method according to claim 6, wherein a multi-level blockchain system is formed between blockchain networks to which a plurality of blockchain nodes deployed on the node device respectively belong, and any blockchain network is managed by a parent blockchain network in the multi-level blockchain system; wherein:
the independent database corresponding to the first block chain point inherits and maintains a copy of account data of a target account in a parent block chain network; alternatively, the first and second electrodes may be,
the first block link point has access to an independent database corresponding to its parent block link network.
8. The method of claim 1, wherein the common database is further configured to record account data of target accounts in a plurality of blockchain networks, and the common database further records account types of the respective common accounts and the target accounts; the searching the target account from the public database comprises:
searching the target account from the public accounts recorded in the public database under the condition that the account type of the target account is a public account;
and searching the target account from the independent accounts recorded in the public database under the condition that the account type of the target account is an independent account.
9. The method of claim 4 or 8, wherein the data read and write request is a blockchain transaction, the blockchain transaction including an account type field, the method further comprising:
and determining the account type of the target account according to the field value of the account type field.
10. The method of claim 1, the target account comprising: an external account and/or a contract account.
11. A method for reading and writing account data is applied to node equipment, wherein the node equipment is provided with a plurality of block chain nodes respectively belonging to different block chain networks, and maintains a public database corresponding to the plurality of block chain nodes, wherein the public database is used for recording the account data of a public account among the plurality of block chain networks, and the method comprises the following steps:
acquiring a read-write request aiming at a target account;
and under the condition that the account data of the target account is recorded in the public database, searching the target account from the public database and executing read-write operation on the account data of the target account.
12. The method according to claim 11, wherein the node device further maintains an independent database corresponding to each blockchain node, and the independent database is used for recording account data of target accounts in the blockchain network to which the corresponding blockchain node belongs;
the searching the target account from the public database and executing the read-write operation on the account data of the target account comprises: under the condition that the account type of the target account is a common account, searching the target account from the common database and executing read-write operation on account data of the target account;
the method further comprises the following steps: and under the condition that the account type of the target account is an independent account, determining an independent database corresponding to the first block chain node on the node equipment, searching the target account from the determined independent database, and executing read-write operation on account data of the target account.
13. The method of claim 12, further comprising:
receiving an assistance request of transparent transmission of a first block link point in a first block chain network, wherein the assistance request is transmitted by a first block chain node under the condition that account data of the target account is not recorded in the public database;
and determining an independent database for recording the account data of the target account from each independent database maintained by the user, and submitting the assistance request to a block chain network corresponding to the determined independent database.
14. The method of claim 13, wherein the determining the independent database recording the account data of the target account from the independent databases maintained by the independent databases comprises:
determining an independent database for recording account data of the target account from all independent databases maintained by the node equipment; alternatively, the first and second electrodes may be,
and under the condition that the account data of the target account is not recorded in the independent database corresponding to the first blockchain network and the first blockchain network has access right to other independent databases corresponding to other blockchain networks, determining the independent database for recording the account data of the target account from other independent databases.
15. The method according to claim 14, wherein a multi-level blockchain system is formed between blockchain networks to which a plurality of blockchain nodes deployed on the node device respectively belong, and any blockchain network is managed by a parent blockchain network in the multi-level blockchain system; wherein:
the independent database corresponding to the first block chain point inherits and maintains a copy of account data of a target account in a parent block chain network; alternatively, the first and second electrodes may be,
the first block link point has access to an independent database corresponding to its parent block link network.
16. The method of claim 11, wherein the common database is further configured to record account data of target accounts in a plurality of blockchain networks, and the common database further records account types of the respective common accounts and the target accounts; the searching the target account from the public database comprises:
searching the target account from the public accounts recorded in the public database under the condition that the account type of the target account is a public account;
and searching the target account from the independent accounts recorded in the public database under the condition that the account type of the target account is an independent account.
17. The method of claim 11, the target account comprising: an external account and/or a contract account.
18. An account data read-write device is applied to a first block chain node in a first block chain network, block chain link points of other block chain networks are also deployed in node equipment where the first block chain link point is located, and the node equipment maintains a common database corresponding to a plurality of block chain nodes, wherein the common database is used for recording account data of common accounts among the plurality of block chain networks, and the device comprises:
the request acquisition module is used for acquiring a read-write request aiming at a target account;
the first reading and writing module is used for searching the target account from the public database and executing reading and writing operation on the account data of the target account under the condition that the account data of the target account is recorded in the public database.
19. An account data read-write device is applied to node equipment, wherein a plurality of blockchain nodes respectively belonging to different blockchain networks are deployed in the node equipment, a public database corresponding to the plurality of blockchain nodes is maintained in the node equipment, and the public database is used for recording account data of public accounts among the plurality of blockchain networks, and the device comprises:
the request acquisition module is used for acquiring a read-write request aiming at a target account;
the first reading and writing module is used for searching the target account from the public database and executing reading and writing operation on the account data of the target account under the condition that the account data of the target account is recorded in the public database.
20. An electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor implements the method of any one of claims 1-17 by executing the executable instructions.
21. A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, carry out the steps of the method according to any one of claims 1 to 17.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111669830.XA CN114297171A (en) | 2021-12-31 | 2021-12-31 | Account data reading and writing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111669830.XA CN114297171A (en) | 2021-12-31 | 2021-12-31 | Account data reading and writing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114297171A true CN114297171A (en) | 2022-04-08 |
Family
ID=80973213
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111669830.XA Pending CN114297171A (en) | 2021-12-31 | 2021-12-31 | Account data reading and writing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114297171A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180115538A1 (en) * | 2016-10-21 | 2018-04-26 | Cygnetise Limited | Methods And Apparatus For Recording A Change Of Authorisation State Of One Or More Authorisation Agents |
| CN108667632A (en) * | 2018-04-19 | 2018-10-16 | 阿里巴巴集团控股有限公司 | Based on the credit record sharing method and device of block chain, electronic equipment |
| KR20190000578A (en) * | 2017-06-23 | 2019-01-03 | 홍석현 | Method for keeping security of data in public distributed database based on blockchain, and server for managing blockchain using the same |
| US20200320529A1 (en) * | 2019-04-03 | 2020-10-08 | Bloomio Ag | Method for user management for blockchain-based operations |
| CN112887160A (en) * | 2021-04-29 | 2021-06-01 | 杭州链城数字科技有限公司 | Block chain all-in-one machine, multi-node deployment method and device thereof, and storage medium |
| CN113326290A (en) * | 2021-06-02 | 2021-08-31 | 支付宝(杭州)信息技术有限公司 | Cross-network query control method |
-
2021
- 2021-12-31 CN CN202111669830.XA patent/CN114297171A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180115538A1 (en) * | 2016-10-21 | 2018-04-26 | Cygnetise Limited | Methods And Apparatus For Recording A Change Of Authorisation State Of One Or More Authorisation Agents |
| KR20190000578A (en) * | 2017-06-23 | 2019-01-03 | 홍석현 | Method for keeping security of data in public distributed database based on blockchain, and server for managing blockchain using the same |
| CN108667632A (en) * | 2018-04-19 | 2018-10-16 | 阿里巴巴集团控股有限公司 | Based on the credit record sharing method and device of block chain, electronic equipment |
| US20200320529A1 (en) * | 2019-04-03 | 2020-10-08 | Bloomio Ag | Method for user management for blockchain-based operations |
| CN112887160A (en) * | 2021-04-29 | 2021-06-01 | 杭州链城数字科技有限公司 | Block chain all-in-one machine, multi-node deployment method and device thereof, and storage medium |
| CN113326290A (en) * | 2021-06-02 | 2021-08-31 | 支付宝(杭州)信息技术有限公司 | Cross-network query control method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113067904B (en) | Method for building block chain sub-network and block chain system | |
| CN113067894B (en) | Method for node to exit block chain sub-network | |
| CN113067897B (en) | Cross-chain interaction method and device | |
| CN113055190B (en) | Access control method for client | |
| CN113098983B (en) | Task execution method and device based on intelligent contract | |
| CN113067895A (en) | Method for building block chain sub-network and block chain system | |
| CN113067914B (en) | Method and device for distributing subnet identification, electronic equipment and storage medium | |
| CN113326290B (en) | Cross-network query control method | |
| CN113206893B (en) | Method for block synchronization and node joining block chain network | |
| CN113259458B (en) | Method and device for starting/closing block link point service | |
| CN113067896B (en) | Method for adding node in block chain sub-network and block chain system | |
| CN113259464B (en) | Method for building block chain sub-network and block chain system | |
| CN113067899B (en) | Method and device for starting/closing block link point service | |
| CN114363162A (en) | Block chain log generation method and device, electronic equipment and storage medium | |
| CN113067898A (en) | Method for scheduling computing services for business process contracts | |
| WO2023207076A1 (en) | Method and apparatus for establishing blockchain subnet | |
| CN113259119B (en) | Block chain message distribution method and device | |
| CN113259237B (en) | Transaction forwarding method between block chain networks | |
| CN113259466B (en) | Block chain subnet operation state control method and block chain system | |
| CN113259459B (en) | Block chain subnet operation state control method and block chain system | |
| CN113259462B (en) | Block chain message distribution method and device | |
| CN113259465B (en) | Business execution method based on off-chain computing service | |
| CN114297171A (en) | Account data reading and writing method and device | |
| CN114357080A (en) | Account data reading and writing method and device | |
| CN113259236A (en) | Transaction forwarding method between block chain networks |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |