CN114039733B - Certificate storage service transfer method, device and equipment for alliance chains - Google Patents
Certificate storage service transfer method, device and equipment for alliance chains Download PDFInfo
- Publication number
- CN114039733B CN114039733B CN202111315151.2A CN202111315151A CN114039733B CN 114039733 B CN114039733 B CN 114039733B CN 202111315151 A CN202111315151 A CN 202111315151A CN 114039733 B CN114039733 B CN 114039733B
- Authority
- CN
- China
- Prior art keywords
- chain
- user
- consensus
- block
- alliance chain
- 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.)
- Active
Links
- 238000012546 transfer Methods 0.000 title claims abstract description 43
- 238000000034 method Methods 0.000 title claims abstract description 34
- 230000006399 behavior Effects 0.000 claims description 17
- 238000012544 monitoring process Methods 0.000 claims description 13
- 230000000694 effects Effects 0.000 claims description 10
- 230000000875 corresponding effect Effects 0.000 claims description 9
- 238000004590 computer program Methods 0.000 claims description 4
- 230000000977 initiatory effect Effects 0.000 claims description 4
- 230000004044 response Effects 0.000 claims description 4
- 230000002596 correlated effect Effects 0.000 claims description 2
- 238000004891 communication Methods 0.000 description 13
- 230000008520 organization Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 6
- 238000012795 verification Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 5
- 230000007246 mechanism Effects 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000000903 blocking effect Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000004422 calculation algorithm Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 101100134058 Caenorhabditis elegans nth-1 gene Proteins 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000012550 audit Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000001681 protective effect Effects 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3263—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3297—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving time stamps, e.g. generation of time stamps
Abstract
A method, device and equipment for transferring certificate storage service for alliance chains are disclosed. After users in the alliance chain agree to execute the transfer of the certificate service, the account identity information and the operation authority of each user are determined, the identity information and the operation authority are written into the initial data block of the centralized block chain type account book, and the subsequent certificate service data are written into other data blocks.
Description
Technical Field
The embodiment of the specification relates to the field of information technology, in particular to a certificate storing service transfer method, device and equipment for a alliance chain.
Background
Federated chains are a common form of blockchains that are currently subject to forensic services. Some federation chains gradually lose the "decentralization" feature of the blockchain, e.g., physically bringing nodes closer together in the federation chain, arranging them on a same cloud server, improving consensus efficiency, etc. The federation chain is becoming more and more "centric," and the effect of "decentralizing" has been lost from the business perspective.
Based on this, a scheme for performing certificate storing service transfer to a centralized database server for a federation chain is needed.
Disclosure of Invention
The embodiment of the application aims to provide a scheme for transferring a certification service to a centralized database server for a alliance chain.
In order to solve the technical problems, the embodiment of the application is realized as follows:
a certificate storing service transfer method for a alliance chain is applied to a centralized database server and comprises the following steps:
receiving feedback information of a user in the alliance chain for the certificate storing service transferring operation;
when the quantity of the feedback information agreeing to execute transfer operation accords with a preset condition, acquiring account identity information of each user in the alliance chain, and determining the operation authority of each account in a block chain account book;
and generating an initial data block of the block chain type account book containing the account identity information and the operation authority so that a user in the alliance chain writes the certification service data into other data blocks in the block chain type account book.
Correspondingly, the embodiment of the specification also provides a certificate storing service transferring device for a alliance chain, which is applied to a centralized database server and comprises the following steps:
the receiving module is used for receiving feedback information of the user in the alliance chain for the certificate storing service transferring operation;
the determining module is used for acquiring account identity information of each user in the alliance chain when the quantity of the feedback information agreeing to execute transfer operation accords with a preset condition, and determining the operation authority of each account in the block chain type account book;
and the generation module is used for generating an initial data block of the block chain type account book containing the account identity information and the operation authority so that a user in the alliance chain can write the certification service data into other data blocks in the block chain type account book.
Through the scheme in the embodiment of the specification, after users in the alliance chain agree to execute the certificate storing service transfer, account identity information and operation authority of each user are determined, the identity information and the operation authority are written into an initial data block of the centralized block chain type account book, and subsequent certificate storing service data are written into other data blocks. Through the scheme, the information and the authority of the user in the alliance chain and the follow-up certificate-storing business data are transferred to the block chain type account book of the database server, and the inquiry and the verification can be carried out at any time.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the embodiments of the disclosure.
Further, not all of the effects described above need be achieved in any of the embodiments of the present specification.
Drawings
In order to more clearly illustrate the embodiments of the present description or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments described in the embodiments of the present description, and other drawings may be obtained according to these drawings for a person having ordinary skill in the art.
FIG. 1 is a schematic flow chart of a block chain ledger generation provided in an embodiment of the present disclosure;
FIG. 2 is a schematic diagram of a system architecture of a centralized database server according to an embodiment of the present disclosure;
FIG. 3 is a schematic flow chart of a method for transferring a certificate store service for a federation chain according to an embodiment of the present disclosure;
FIG. 4 is a flowchart of a recommendation method for transferring services to a federation chain according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of a certificate store service transferring device for a federation chain according to an embodiment of the present disclosure;
fig. 6 is a schematic diagram of an apparatus for configuring the method of the embodiments of the present specification.
Detailed Description
In order for those skilled in the art to better understand the technical solutions in the embodiments of the present specification, the technical solutions in the embodiments of the present specification will be described in detail below with reference to the drawings in the embodiments of the present specification, and it is apparent that the described embodiments are only some embodiments of the present specification, not all embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present specification shall fall within the scope of protection.
Blockchains are generally divided into three types: public chains (Public Blockchain), private chains (Private Blockchain) and federated chains (Consortium Blockchain). In addition, there are many types of combinations, such as different combinations of private chain+federation chain, federation chain+public chain, and the like. Among them, the highest degree of decentralization is the public chain. Participants joining the public chain may read data records on the chain, participate in transactions, compete for billing rights for new blocks, and so forth. Moreover, each participant (i.e., node) is free to join and leave the network and perform related operations. The private chain is the opposite, the write rights of the network are controlled by an organization or organization, and the data read rights are specified by the organization. In short, the private chain may be a weakly centralized system with few and strict restrictions on participating nodes. This type of blockchain is more suitable for use within a particular organization.
The alliance chain is a block chain between public and private chains, and can realize 'partial decentralization'. Each node in the federation chain typically has an entity organization or organization corresponding thereto; the participants join the network through authorization and form a benefit related alliance, and jointly maintain the block chain operation to execute the certificate storing service. For example, judicial authorities, fair authorities, musicians 'associations, etc. collectively construct a coalition chain for music correlation, providing a coalition chain for the creation of musicians' creative works.
The decentralized blockchain is essentially a decentralized distributed ledger database. That is, the data in the blockchain is stored scattered across the nodes. The participants of the blockchain are parallel to each other, and the relationship of upper and lower levels and master and slave is not existed, so that the nodes are equal. The account book storage mode of the decentralization can play roles of fault tolerance, attack resistance and hook resistance.
If all the nodes in a blockchain are very 'honest and reliable', the blockchain has basically no collusion behavior and no attack behavior when actually carrying out service processing in the blockchain, and the meaning of 'decentralization' is not obvious. This situation is often very common in alliance chains that have a common interest base. In this case, distributed ledger storage is not necessary, and no consensus is necessary for data storage.
Fig. 2 is a schematic system architecture of a centralized database server according to an embodiment of the present disclosure. In this schematic diagram, the database server is directly oriented to multiple users (i.e., node users in the federation chain, typically organizations or enterprises), and each user may provide a certification service to other individual users or other organizations, and write certification data into a centralized block chain ledger.
In the embodiment of the present disclosure, the transfer of the certification service does not refer to transferring the certification service data existing in the federation chain to the centralized block chain account book, but refers to, for each user in the federation chain, not writing the subsequent certification service data into the federation chain, but writing the subsequent certification service data into the centralized block chain account book, where the certification service of the federation chain is terminated.
In the centralized database server, the block chain ledger is generated in the following manner, as shown in fig. 1, fig. 1 is a schematic flow chart for generating the block chain ledger, which is provided in the embodiment of the present disclosure, and includes:
s101, receiving data records to be stored, and determining hash values of the data records.
The data record to be stored can be various consumption records of individual users of the client, or can be business results, intermediate states, operation records and the like generated by the application server when executing business logic based on instructions of the users. Specific business scenarios may include consumption records, audit logs, supply chains, government regulatory records, medical records, and the like.
In one embodiment of the present description, the data records may be various forensic business data provided by federated chain users.
And S103, when a preset blocking condition is met, determining each data record in the data block to be written, and generating an N data block containing the hash value of the data block and the data record.
The preset blocking conditions include: the number of data records to be stored reaches a number threshold, for example, each time one thousand data records are received, a new data block is generated, and one thousand data records are written into the block; alternatively, the time interval from the last block forming time reaches a time threshold, e.g., every 5 minutes, a new data block is generated and the data records received within the 5 minutes are written into the block.
Here, N refers to the sequence number of the data block, in other words, in the embodiment of the present specification, the data blocks are in the form of a block chain, and are arranged in sequence based on the sequence of the block forming time, which has a strong timing characteristic. Wherein the block heights of the data blocks monotonically increase based on the order of the block times. The block height may be a sequence number, and at this time, the block height of the nth data block is N; block heights may also be generated in other ways.
When n=1, that is, the data block at this time is the initial data block. The hash value and block height of the initial data block are given based on a preset manner. For example, the initial data block does not include a data record, the hash value is any given hash value, and the block height blknum=0; for another example, the generation trigger condition of the initial data block is identical to the trigger condition of the other data blocks, but the hash value of the initial data block is determined by hashing all the contents in the initial data block.
When N >1, since the content and hash value of the previous data block have been determined, at this time, the hash value of the current data block (nth data block) may be generated based on the hash value of the previous data block (i.e., nth-1 data block), for example, in a feasible manner, determining the hash value of each data record to be written into the nth block, generating a merck tree according to the arrangement order in the block, splicing the root hash value of the merck tree and the hash value of the previous data block together, and generating the hash value of the current block again by adopting the hash algorithm. For example, the hash value of the whole data record may be obtained by splicing the sequence of the data records in the block, splicing the hash value of the previous data block and the hash value of the whole data record, and performing hash operation on the string obtained by splicing to generate the hash value of the data block.
The form of a data block may be similar to the form of a chunk in a blockchain, including a chunk header and a chunk body, metadata for the data block in the chunk header, e.g., chunk height, chunk hash, hash of a previous data block, version number, root hash of the merck tree of the data record in the chunk body, and so forth; the block body is used for writing data records.
After the user successfully uploads the data, the hash value of the corresponding data record and the hash value of the data block can be obtained and stored, and the integrity verification can be initiated based on the hash value. The specific verification method is to recalculate the hash value of the data record and the hash value of the data block in the database, and compare the hash value with the hash value stored locally.
By the foregoing generation method of the data blocks, each data block is determined by a hash value, and the hash value of the data block is determined by the content and sequence of the data records in the data block and the hash value of the previous data block. The user can initiate verification based on the hash value of the data block at any time, and the modification of any content in the data block (including modification of the content or sequence of the data record in the data block) can cause inconsistency between the hash value of the data block calculated during verification and the hash value generated during data block generation, so that verification failure is caused, and therefore, the tamper-proof effect under centralization is realized.
Compared with the operation mode in the alliance chain, the centralized database server does not need to be subjected to consensus when writing data, and the data storage does not need to be stored in each node device in a distributed mode. The centralized storage approach may free up storage space and computing resources of the node devices relative to the federation chain.
Therefore, the embodiment of the present specification provides a scheme, when users in the federation chain all agree to execute the transfer of the certification service, the certification service is transferred to the centralized database server, and the storage of the certification service data is continued by using the block chain account book.
The following describes in detail the technical solutions provided by the embodiments of the present specification with reference to the accompanying drawings. As shown in fig. 3, fig. 3 is a flow chart of a method for transferring a certificate service for a federation chain according to an embodiment of the present disclosure, where the flow specifically includes the following steps:
s301, receiving feedback information of the user in the alliance chain for the certificate storing service transferring operation.
The feedback information may be actively initiated by the user in the federation chain, e.g., the federation chain has been agreed upon at the time of creation, a vote may be periodically initiated between users, whether the federation chain needs to be terminated, and a transfer of the certification service is performed.
The feedback information may also be feedback made by the user in the federation chain on the received recommendation information. For example, when the alliance chain is built on a certain cloud platform, users in the alliance chain agree to subscribe to a recommendation service provided by the cloud platform, the recommendation service comprises evaluation of the centralization degree of the cloud platform, when the centralization degree reaches a certain degree, the cloud platform pushes corresponding recommendation information (used for describing the centralization state of the current alliance chain for each user) to each user, and each user feeds back the recommendation information to generate feedback information. The feedback information returned by a user is used for indicating whether the user agrees to execute the certificate storing service transfer.
S303, when the quantity of the feedback information agreeing to execute transfer operation accords with a preset condition, acquiring account identity information of each user in the alliance chain, and determining the operation authority of each account in the block chain type account book.
Generally, the user needs to agree to execute the forensic service transfer. Thus, the default preset condition may be that the number of feedback information that agree to be performed is equal to the number of users in the coalition chain (one user has only one piece of valid feedback information). The preset condition may be set by the user in advance, for example, the user agreeing to perform accounts for more than 90% of the entire users, and so on.
After determining that the users in the alliance chain agree to execute service transfer through the feedback information, the centralized database server side acquires account identity information of each user of the alliance group.
The account identity information of a user comprises the account number, the password, the complete identity information and the like of the user in the alliance chain, and can also comprise the login account number, the password, the identity information and the like of a third party organization and a third party person served by the user in the alliance chain.
The obtained account identity information is used for enabling the user to enter a block chained account book by using the same login account number and password.
In the block chain ledger, the operation authority of a user can be correspondingly given according to the authority of the user in the alliance chain. For example, the authority of the node user is correspondingly higher, while the authority of the third party authority and the personal user facing the node user is lower. The specific authority configuration mode can write the weight value of the user into a configuration file for storing the corresponding relation between the user identifier and the weight value of the user.
S305, generating an initial data block of the block chain type account book containing the account identity information and the operation authority so that a user in the alliance chain writes the certification service data into other data blocks in the block chain type account book.
The manner in which a blockchain ledger is generated in a centralized database server has been described above. It can be seen that the hash value of the other data blocks in a block chain ledger is dependent on the hash value of the original data block, which can be manually determined or obtained based on the content in the original data block.
In the embodiment of the present specification, the aforementioned account identity information and operation authority information should be included in the initial data block generated when the transfer service is performed. The specific writing is not limited, whether in the block header or in the block of the initial data block.
For example, account identity information and operation authority information can be regarded as one or more pieces of data records written into a block, and meanwhile, the data header contains a root hash of the merck tree corresponding to the data records; or, directly writing account identity information and operation authority information of the user with the administrator authority into the block header.
The hash value of the initial data block may be obtained by hashing a block header in the initial data block. Therefore, the hash value of the initial data block contains account identity information and operation authority information, and the subsequent other data blocks depend on the hash value of the initial data block, so that the account book generated after transfer contains information of each user in the alliance chain, and can be queried and verified at any time.
Through the scheme in the embodiment of the specification, after users in the alliance chain agree to execute the authentication service transfer, account identity information and operation authority of each user are determined, the identity information and the operation authority are written into an initial data block of the centralized block chain account book, subsequent authentication service data are written into other data blocks, the users can inquire and verify at any time, and the authentication service transfer ensures the rights and interests of the users in the original alliance chain and simultaneously releases the computing power and storage resources of node equipment in the alliance chain through the authentication service transfer.
In one embodiment, after the initial data block is generated, the user in the original alliance chain can immediately perform the certification service, and the new certification service data is directly written into the account book of the block chain, and other data blocks are generated based on the initial data block. For existing blockchain data in the original coalition chain, no transfer is made.
In another embodiment, the database server may further transfer the data in the original federation chain to the block chain ledger, where a specific transfer manner is to determine a data block included in the original federation chain and a block height M of each data block, and write the mth block as a data record to the nth data block in the block chain ledger, where m=n. For example, the 100 th chunk (containing the chunk header and chunk body) of the federation chain is written as a data record in the chunk of the 100 th data chunk in the ledger. And continuing to store the new certificate storing service data until the existing blocks in the alliance chain are transferred.
In one embodiment, in order to ensure the authenticity of the feedback information of the user, the feedback information may further include a digital signature of the user, and accordingly, when the database server receives the feedback information including the digital signature, the database server needs to use the public key of the user to decrypt and verify the digital signature.
As previously described, the feedback information of the user may be feedback of recommendation information generated based on the server-side analysis of the centralization degree of the federation chain. In the embodiment of the present disclosure, the recommendation for the certificate store service transfer of the federation chain to the database server may be performed by, as shown in fig. 4, fig. 4 is a schematic flow chart of the recommendation method for the service transfer to the federation chain provided in the embodiment of the present disclosure, and the flow chart is applied to the centralized database server that stores data in a block chain ledger book, where the flow chart specifically includes the following steps:
s401, monitoring a centralization index of the alliance chain, wherein the centralization index is used for representing centralization degree of consensus on transactions in the alliance chain.
The monitoring of the centralization index can be performed in a database server, or can be performed through nodes in a specially managed alliance chain deployed in the cloud.
It should be noted that, a transaction (transfer) described in this specification refers to a piece of data that a user creates through a client of a blockchain and needs to be finally published to a distributed database of the blockchain.
Among the transactions in the blockchain are narrow transactions and broad transactions. A narrow transaction refers to a transfer of value that a user publishes to a blockchain. And generalized transaction refers to a business data with business intention issued by a user to a blockchain; for example, the operator may build a federation chain based on actual business requirements, rely on the federation chain to deploy some other types of online business (e.g., rental business, vehicle dispatch business, insurance claim business, credit service, medical service, etc.) unrelated to value transfer, and in such federation chains, the transaction may be a business message or business request with business intent issued by the user in the federation chain.
The centering index C is an exact score that can be obtained statistically based on the device characteristics of each node in the federation chain and the traffic characteristics generated when processing the licensed traffic in the federation chain.
For business features, and in particular, federation chains as one of the blockchains, there is also a need to make consensus on transactions written to the ledger when executing the certification business. The various business features in the consensus process may reflect the degree of centralization of the federation chain, as described in several aspects below:
(1) The centering index is characterized based on the average consensus time spent by the transaction.
In the embodiment of the present disclosure, the average consensus time T of a transaction refers to the average time taken from the initiation of the transaction to the end of the consensus, or the time when a transaction is written into a new data block, or the time when a block is taken (when the block taken condition is that the transaction that the consensus passes reaches a certain value, i.e. a new block is generated). The average consensus time for a transaction may be based on consensus time statistics for the transaction over a period of time (e.g., 1 month).
In the federation chain, a transaction may be written to the ledger of the federation chain because of agreement on the transaction and the need for a plurality of nodes. Thus, in the case where nodes in a federation chain are relatively independent, communication between the nodes needs to be performed a plurality of times. It is readily understood that the more independent nodes, the more distributed, the longer the time required for the consensus process.
When the communication conditions are the same, the longer the consensus time the alliance chain needs to spend for one transaction, the more independent nodes exist in the alliance chain, and the consensus can be completed only by waiting for the consensus result of each node and comparing. In other words, the longer the consensus time of the transaction, the higher the degree of "decentralization" in the coalition chain, the smaller the centralization index; conversely, the greater the centering index.
Of course, this also has an impact on the average consensus time of the transaction, since there is a difference in the consensus mechanism adopted by each coalition chain. For example, proof of Work (POW); proof of stock (POS); practical Bayesian fault tolerance algorithms (Practical Byzantine Fault Tolerance, PBFT); proof of importance (Proof of Importance, POI); participation proof (Proof of Participation, POP), and so forth. Under different consensus mechanisms, the time required to consensus a transaction is different.
Based on this, a basic consensus time T0 of a transaction under a certain consensus mechanism may be given in advance, and then, according to determining an average consensus time T1 in a coalition chain using the consensus mechanism, a time parameter t=t1/T0 for calculating a centering index is calculated, where T and the centering index are inversely related.
(2) The centering index is characterized based on the proportion of malicious behavior in the transaction consensus process.
In consensus transactions, some nodes may behave subjectively or objectively, which may be observed frequently,
for example, a node that performs consensus stops responding to the consensus, resulting in failure of other nodes to receive the consensus result of the node. It should be noted that, in the consensus process, if there are enough nodes to stop responding, this may cause the consensus to fail. Such a stop response to consensus may be that the node device has failed, or that several nodes are in tandem, and maliciously stop the response to affect the data record in the ledger.
As another example, a node initiates a consensus of a fraudulent transaction (or may be referred to as a fraudulent transaction), and it is apparent that such a fraudulent transaction cannot be passed through the consensus. In the blockchain, there is a possibility that a node maliciously issues such spurious transactions, wasting the computational power of other nodes, or that double flowers are realized by fraudulent transactions, for own profits, etc.
Or, some nodes communicate in series, and false consensus results are made on the consensus result of a certain transaction, so as to expect to change the consensus result of the transaction.
This situation occurs when in public chains, and is less so in federated chains. It will be readily appreciated that nodes that actually have the right to perform consensus or billing will generally not initiate malicious activity because of the common underlying interests in the federation chain, unlike the public chain.
In other words, the higher the degree of centralization, the fewer the number of malicious acts that occur in the coalition chain, and thus, the centralization index of the coalition chain can be determined based on the proportion of malicious acts in the trade consensus in the coalition chain in practice. The proportion of malicious behavior is inversely related to the centering index, i.e. the lower the proportion of malicious behavior, the greater the centering index.
The proportion P of malicious activity in making a trade consensus here may refer to the proportion of transactions in which the trade fails because of the malicious activity consensus in all transactions. For example, 1000 cases are commonly recognized in the alliance chain for initiating transactions, 20 cases fail, and the proportion of malicious behavior is 20/1000=2%.
Alternatively, it may be the ratio of malicious behavior initiated by the node during the consensus transaction to normal behavior. For example, in each consensus, it needs to be performed between 10 nodes, and it is assumed that in a transaction consensus process, 3 nodes make different consensus results from other nodes, and although the transaction is still consensus successful, the proportion of malicious behaviors in the transaction can be considered to be 3/10=30%.
The proportion of malicious behaviour in the consensus for all transactions can also be added based on a single transaction, for example if there are also other transactions for which 9 consensus were successful and no malicious behaviour at the same time, the proportion of malicious behaviour at this time is 3/100=3%.
(3) The centering index is determined based on a deployment environment of a plurality of node devices in the federation chain.
Node devices refer to devices where nodes are located. In general, node devices correspond to different organizations, and thus, to maintain their independence, the environments in which the nodes are deployed are relatively independent. For example, each organization deploys its own node devices at the organization's location.
However, in practical application, when performing the certification service, the organizations in the federation chain often delegate the node devices to other professional organizations for execution, so that all nodes in the whole federation chain are on the same or a few deployment platforms, and are very close in geographic location, and even the node devices of the organizations may be some associated devices in the same deployment platform.
In this case, transaction consensus and accounting in the coalition chain is performed on several devices that are related, and the "decentralised" feature is difficult to embody. Therefore, the degree of consistency R of the deployment environment of each node may reflect the centering index, and the greater the degree of consistency R, the greater the centering index C.
As previously described, the centering index C may be embodied based on the average consensus time T (or time parameter T), the proportion P of malicious behavior in the trade consensus, and the degree of consistency R of the deployment environment of each node. In other words, c=f (T, P, R) can be characterized by the following formula. For example, a simpler calculation may be c=k (R/TP). Where k is a custom coefficient.
Of course, when calculating C, the variables in F may include both the variables T, P and R, or may be calculated using any one of the variables or calculated based on a combination of any two variables. In other words, the variable in F may include at least one of T, P and R.
S403, when the centralization index exceeds a preset value, sending recommendation information to the nodes in the alliance chain, wherein the recommendation information is used for prompting the nodes in the alliance chain to transfer the evidence storage business from each node in the alliance chain to the centralization database server.
The recommendation information may include the aforementioned centering index C, and may further include explanatory information on a block chain type centralized database server, remark information on a transfer service, and the like.
Since in practice a user may correspond to multiple nodes, sending recommendation information may be sent to each node in the federation chain, or after determining the relevant users in the federation chain, sending a recommendation to one node for each relevant user.
After receiving the recommendation information, the user can give corresponding feedback information to the recommendation information. As described above, when the amount of feedback information reaches a certain condition, the transfer of the certification service is started. By the scheme, the service transfer recommendation can be accurately initiated based on the consensus state of the alliance chain, so that a user can make an accurate decision.
Correspondingly, the embodiment of the present disclosure further provides a certificate storing service transferring device for a federation chain, which is applied to a centralized database server, as shown in fig. 5, and fig. 5 is a schematic structural diagram of the certificate storing service transferring device for the federation chain provided in the embodiment of the present disclosure, including:
the receiving module 501 receives feedback information of the user in the alliance chain for the operation of transferring the certification service;
a determining module 503, configured to obtain account identity information of each user in the coalition chain when the number of the feedback information agreeing to execute transfer operations accords with a preset condition, and determine an operation authority of each account in a block chain account book;
the generating module 505 generates an initial data block of the block chain ledger containing the account identity information and the operation authority, so that the user in the alliance chain writes the certification service data into other data blocks in the block chain ledger.
Further, the device further comprises a receiving module 507 for receiving the data records to be stored and determining hash values of the data records; the generating module 505 determines each data record in the data block to be written when a preset blocking condition is reached, and generates an nth data block including a hash value of the data block and the data record, and specifically includes: when n=1, the hash value and the block height of the initial data block are given based on a preset mode, wherein the initial data block contains the account identity information and the operation authority; when N >1, determining the hash value of the N data block according to the hash value of each data record and the N-1 data block in the data block to be written, and generating the N data block containing the hash value of the N data block and each data record, wherein the block heights of the data blocks monotonically increase based on the sequence of the block forming time.
Further, the generating module 505 obtains each block of the coalition chain and its block height, and determines each block as each data record in the data block to be written, where the block height of the block to be written is the same as the serial number N of the data block.
Further, the receiving module 507 receives feedback information including a digital signature of the user; and verifying the digital signature of the user by adopting a public key corresponding to the user in the alliance chain.
Further, the apparatus also includes a monitoring module 509 for monitoring a centralization index of the coalition chain, wherein the centralization index is used to characterize a centralization degree of consensus transactions in the coalition chain; and the sending module 511 is used for sending recommendation information to the nodes in the alliance chain when the centralization index exceeds a preset value, wherein the recommendation information is used for prompting the nodes in the alliance chain to transfer the certification service from each node in the alliance chain to the centralized database server so that each node can generate feedback information for the recommendation information.
Further, the monitoring module 509 obtains an average consensus time for a transaction in the coalition chain; and determining the centralization index of the alliance chain according to the average consensus time of the transaction, wherein the average consensus time is inversely related to the centralization index.
Further, the monitoring module 509 determines a proportion of malicious activity in the coalition chain that is subject to transaction consensus, the malicious activity including at least one of a consensus node ceasing a response to a consensus, initiating a consensus of a false transaction, or a false consensus of a transaction; and determining the centralization index of the alliance chain according to the proportion of the malicious behaviors, wherein the proportion of the malicious behaviors is inversely related to the centralization index.
Further, the monitoring module 509 obtains a deployment environment of a plurality of node devices in the federation chain, where the deployment environment includes a geographic location and/or a deployment platform; the centering index is determined according to the consistency degree of the deployment environment, wherein the consistency degree is positively correlated with the centering index.
The embodiment of the present disclosure also provides a computer device, which at least includes a memory, a processor, and a computer program stored on the memory and capable of running on the processor, where the processor implements the method for transferring a certification service for a federation chain shown in fig. 3 when executing the program.
FIG. 6 illustrates a more specific hardware architecture diagram of a computing device provided by embodiments of the present description, which may include: a processor 1010, a memory 1020, an input/output interface 1030, a communication interface 1040, and a bus 1050. Wherein processor 1010, memory 1020, input/output interface 1030, and communication interface 1040 implement communication connections therebetween within the device via a bus 1050.
The processor 1010 may be implemented by a general-purpose CPU (Central Processing Unit ), microprocessor, application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits, etc. for executing relevant programs to implement the technical solutions provided in the embodiments of the present disclosure.
The Memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory ), static storage device, dynamic storage device, or the like. Memory 1020 may store an operating system and other application programs, and when the embodiments of the present specification are implemented in software or firmware, the associated program code is stored in memory 1020 and executed by processor 1010.
The input/output interface 1030 is used to connect with an input/output module for inputting and outputting information. The input/output module may be configured as a component in a device (not shown) or may be external to the device to provide corresponding functionality. Wherein the input devices may include a keyboard, mouse, touch screen, microphone, various types of sensors, etc., and the output devices may include a display, speaker, vibrator, indicator lights, etc.
Communication interface 1040 is used to connect communication modules (not shown) to enable communication interactions of the present device with other devices. The communication module may implement communication through a wired manner (such as USB, network cable, etc.), or may implement communication through a wireless manner (such as mobile network, WIFI, bluetooth, etc.).
Bus 1050 includes a path for transferring information between components of the device (e.g., processor 1010, memory 1020, input/output interface 1030, and communication interface 1040).
It should be noted that although the above-described device only shows processor 1010, memory 1020, input/output interface 1030, communication interface 1040, and bus 1050, in an implementation, the device may include other components necessary to achieve proper operation. Furthermore, it will be understood by those skilled in the art that the above-described apparatus may include only the components necessary to implement the embodiments of the present description, and not all the components shown in the drawings.
The embodiments of the present specification also provide a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method for transferring a certification service for a federation chain shown in fig. 3.
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 storage media for a computer 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 tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
From the foregoing description of embodiments, it will be apparent to those skilled in the art that the present embodiments may be implemented in software plus a necessary general purpose hardware platform. Based on such understanding, the technical solutions of the embodiments of the present specification may be embodied in essence or what contributes to the prior art in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method described in the embodiments or some parts of the embodiments of the present specification.
The system, method, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for the method embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments for relevant points. The above-described method embodiments are merely illustrative, in that the modules illustrated as separate components may or may not be physically separate, and the functions of the modules may be implemented in the same piece or pieces of software and/or hardware when implementing the embodiments of the present disclosure. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present application without undue burden.
The foregoing is merely a specific implementation of the embodiments of this disclosure, and it should be noted that, for a person skilled in the art, several improvements and modifications may be made without departing from the principles of the embodiments of this disclosure, and these improvements and modifications should also be considered as protective scope of the embodiments of this disclosure.
Claims (8)
1. A certificate storing service transfer method for a alliance chain is applied to a centralized database server and comprises the following steps:
monitoring a centralization index of the coalition chain, wherein the centralization index is used for representing centralization degree of consensus for transactions in the coalition chain;
when the centralization index exceeds a preset value, sending recommendation information to nodes in the alliance chain, wherein the recommendation information is used for prompting the nodes in the alliance chain to transfer the certification service from each node in the alliance chain to the centralized database server so that each node can generate feedback information for the recommendation information;
receiving feedback information of one or more users of the alliance chain for the certificate storing service transferring operation;
if the number of users agreeing to execute transfer operation is determined to accord with a preset condition according to the received feedback information, acquiring account identity information of each user in the alliance chain, and determining the operation authority of each account in the block chain type account book;
creating a centralized block chain ledger so that each user of the alliance chain submits subsequent certificate-storing business data to the block chain ledger; the initial data block of the block chain type account book comprises account identity information and operation authority of each user.
2. The method of claim 1, wherein the feedback information of each user for the forensic service transfer operation includes the digital signature of the user;
the method further comprises the steps of: and verifying the digital signature included in the feedback information of the user for the certificate storing service transfer operation by adopting the public key corresponding to the user.
3. The method of claim 1, monitoring a centralization index of the coalition chain, comprising:
acquiring average consensus time for transactions in the coalition chain;
and determining the centralization index of the alliance chain according to the average consensus time of the transaction, wherein the average consensus time is inversely related to the centralization index.
4. The method of claim 1, monitoring a centralization index of the coalition chain, comprising:
determining a proportion of malicious activity in conducting transaction consensus in the coalition chain, the malicious activity including at least one of stopping a response to the consensus, initiating a consensus of a false transaction, or a false consensus of a transaction by a consensus node;
and determining the centralization index of the alliance chain according to the proportion of the malicious behaviors, wherein the proportion of the malicious behaviors is inversely related to the centralization index.
5. The method of claim 1, monitoring a centralization index of the coalition chain, comprising:
acquiring deployment environments of a plurality of node devices in the alliance chain, wherein the deployment environments comprise geographic positions and/or deployment platforms;
the centering index is determined according to the consistency degree of the deployment environment, wherein the consistency degree is positively correlated with the centering index.
6. A certification service transfer device for a federation chain, applied to a centralized database server, the device comprising:
the receiving module is used for receiving feedback information of one or more users of the alliance chain for the certificate storing service transferring operation;
the determining module is used for acquiring account identity information of each user in the alliance chain and determining the operation authority of each account in the block chain type account book if the number of the users agreeing to execute transfer operation is determined to be in accordance with a preset condition according to the received feedback information;
the creation module creates a centralized block chain type account book so that each user of the alliance chain submits and stores the subsequent certificate storing business data into the block chain type account book; the initial data block of the block chain type account book comprises account identity information and operation authority of each user;
the apparatus further comprises:
the monitoring module is used for monitoring the centralization index of the alliance chain before the receiving module executes the operation, wherein the centralization index is used for representing the centralization degree of consensus on the transaction in the alliance chain; and when the centralization index exceeds a preset value, sending recommendation information to the nodes in the alliance chain, wherein the recommendation information is used for prompting the nodes in the alliance chain to transfer the certification service from each node in the alliance chain to the centralized database server so as to generate feedback information for the recommendation information by each node.
7. A computer readable storage medium having stored thereon a computer program which when executed by a processor implements the method of any of claims 1 to 5.
8. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any one of claims 1 to 5 when the program is executed by the processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111315151.2A CN114039733B (en) | 2019-05-23 | 2019-05-23 | Certificate storage service transfer method, device and equipment for alliance chains |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910436525.2A CN110278246B (en) | 2019-05-23 | 2019-05-23 | Certificate storage service transfer method, device and equipment for alliance chain |
| CN202111315151.2A CN114039733B (en) | 2019-05-23 | 2019-05-23 | Certificate storage service transfer method, device and equipment for alliance chains |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910436525.2A Division CN110278246B (en) | 2019-05-23 | 2019-05-23 | Certificate storage service transfer method, device and equipment for alliance chain |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114039733A CN114039733A (en) | 2022-02-11 |
| CN114039733B true CN114039733B (en) | 2023-12-12 |
Family
ID=67959933
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111315151.2A Active CN114039733B (en) | 2019-05-23 | 2019-05-23 | Certificate storage service transfer method, device and equipment for alliance chains |
| CN201910436525.2A Active CN110278246B (en) | 2019-05-23 | 2019-05-23 | Certificate storage service transfer method, device and equipment for alliance chain |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910436525.2A Active CN110278246B (en) | 2019-05-23 | 2019-05-23 | Certificate storage service transfer method, device and equipment for alliance chain |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN114039733B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110928534B (en) * | 2019-10-14 | 2021-11-09 | 上海唯链信息科技有限公司 | Workflow node authentication method and device based on block chain |
| CN111625606B (en) * | 2020-06-24 | 2021-06-25 | 卓尔智联(武汉)研究院有限公司 | Alliance link data processing method and device and electronic equipment |
| CN113495926A (en) * | 2021-09-06 | 2021-10-12 | 支付宝(杭州)信息技术有限公司 | Block output method of block chain network |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20020076050A (en) * | 2001-03-27 | 2002-10-09 | 이광태 | Commercial Trading Executive Method By Using Internet And Storage Medium Thereof |
| CA2931469A1 (en) * | 2016-03-27 | 2017-09-27 | Sal Khan | Portable verifiable credentials and methods thereof |
| CN107992621A (en) * | 2017-12-22 | 2018-05-04 | 杭州云象网络技术有限公司 | A kind of intelligent cinematic industry service system based on block chain multichain technological incorporation |
| CN108052530A (en) * | 2017-11-10 | 2018-05-18 | 杭州云象网络技术有限公司 | A kind of decentralization CA construction methods and its system based on alliance's chain |
| CN108712431A (en) * | 2018-05-24 | 2018-10-26 | 广东工业大学 | A kind of traffic information deposit method and device based on alliance's chain |
| CN108829350A (en) * | 2018-05-31 | 2018-11-16 | 阿里巴巴集团控股有限公司 | Data migration method and device based on block chain |
| CN108876380A (en) * | 2018-08-07 | 2018-11-23 | 阿里巴巴集团控股有限公司 | A kind of method of commerce and system for depositing card based on centralization clearing and block chain |
| CN109189962A (en) * | 2018-08-17 | 2019-01-11 | 福建南威软件有限公司 | A kind of license service realization system based on block chain |
| CN109685489A (en) * | 2018-12-28 | 2019-04-26 | 杭州云象网络技术有限公司 | A kind of assets across chain method of commerce between block chain |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP6818034B2 (en) * | 2015-10-05 | 2021-01-20 | リップル・ルクセンブルク・エス・ア | Temporary consensus network within the resource transfer system |
| US9948467B2 (en) * | 2015-12-21 | 2018-04-17 | Mastercard International Incorporated | Method and system for blockchain variant using digital signatures |
| WO2018119585A1 (en) * | 2016-12-26 | 2018-07-05 | 深圳前海达闼云端智能科技有限公司 | Permission control method, apparatus and system for block chain, and node device |
| CN107426157B (en) * | 2017-04-21 | 2020-04-17 | 杭州趣链科技有限公司 | Alliance chain authority control method based on digital certificate and CA authentication system |
| CN109040271B (en) * | 2018-08-15 | 2020-12-29 | 深圳市引方科技有限公司 | Network equipment integrity protection method under distributed environment |
| CN109255707A (en) * | 2018-08-30 | 2019-01-22 | 陈勤 | It is a kind of to realize that object belongs to the method and system of value foundation and distribution based on common recognition technology |
| CN109472675A (en) * | 2018-11-29 | 2019-03-15 | 阿里巴巴集团控股有限公司 | Processing method, device, system and the equipment of charter business |
-
2019
- 2019-05-23 CN CN202111315151.2A patent/CN114039733B/en active Active
- 2019-05-23 CN CN201910436525.2A patent/CN110278246B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20020076050A (en) * | 2001-03-27 | 2002-10-09 | 이광태 | Commercial Trading Executive Method By Using Internet And Storage Medium Thereof |
| CA2931469A1 (en) * | 2016-03-27 | 2017-09-27 | Sal Khan | Portable verifiable credentials and methods thereof |
| CN108052530A (en) * | 2017-11-10 | 2018-05-18 | 杭州云象网络技术有限公司 | A kind of decentralization CA construction methods and its system based on alliance's chain |
| CN107992621A (en) * | 2017-12-22 | 2018-05-04 | 杭州云象网络技术有限公司 | A kind of intelligent cinematic industry service system based on block chain multichain technological incorporation |
| CN108712431A (en) * | 2018-05-24 | 2018-10-26 | 广东工业大学 | A kind of traffic information deposit method and device based on alliance's chain |
| CN108829350A (en) * | 2018-05-31 | 2018-11-16 | 阿里巴巴集团控股有限公司 | Data migration method and device based on block chain |
| CN108876380A (en) * | 2018-08-07 | 2018-11-23 | 阿里巴巴集团控股有限公司 | A kind of method of commerce and system for depositing card based on centralization clearing and block chain |
| CN109189962A (en) * | 2018-08-17 | 2019-01-11 | 福建南威软件有限公司 | A kind of license service realization system based on block chain |
| CN109685489A (en) * | 2018-12-28 | 2019-04-26 | 杭州云象网络技术有限公司 | A kind of assets across chain method of commerce between block chain |
Non-Patent Citations (1)
| Title |
|---|
| 区块链与保险创新:机制、前景与挑战;许闲;;保险研究(05);第45-54页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110278246A (en) | 2019-09-24 |
| CN114039733A (en) | 2022-02-11 |
| CN110278246B (en) | 2021-09-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| TWI724391B (en) | Node management method and device based on blockchain | |
| CN110059494B (en) | Privacy protection method for block chain transaction data and block chain system | |
| US20190172026A1 (en) | Cross blockchain secure transactions | |
| WO2020082887A1 (en) | Block chain transaction method and apparatus | |
| CN109493204B (en) | Service accounting method based on block chain and terminal equipment | |
| TW202040408A (en) | Method, system and apparatus for verifying signature in blockchain ledger, and device | |
| CN114039733B (en) | Certificate storage service transfer method, device and equipment for alliance chains | |
| US11283622B2 (en) | Signature verification for a blockchain ledger | |
| WO2020258858A1 (en) | Authorization method, system, apparatus and device in blockchain-type account book | |
| US20230037932A1 (en) | Data processing method and apparatus based on blockchain network, and computer device | |
| WO2020199710A1 (en) | Account book verification method, apparatus, and device | |
| CN113726751B (en) | Weight management method, device and equipment in block chain type account book | |
| WO2020199708A1 (en) | Monitoring method, apparatus, and device for time service certificate generation request | |
| US10790968B2 (en) | Ledger verification method and apparatus, and device | |
| WO2020233149A1 (en) | Method, apparatus and device for timing authentication in blockchain account book | |
| CN110020945B (en) | Data reading method and system based on multiple block chain networks | |
| CN112487492B (en) | Data verification method, system and equipment | |
| CN111985007A (en) | Contract signing and executing method and device based on block chain | |
| CN111339551B (en) | Data verification method and related device and equipment | |
| CN110990790B (en) | Data processing method and equipment | |
| CN109586949A (en) | Block generation method and computer storage medium | |
| CN110225103B (en) | Service recommendation method, device and equipment | |
| US10979233B2 (en) | Monitoring time certificate generation requests | |
| CN109818965B (en) | Personal identity verification device and method | |
| CN111447216B (en) | Method and apparatus for changing consensus node |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |