CN111951006A - Alliance chain consensus method, system and terminal - Google Patents
Alliance chain consensus method, system and terminal Download PDFInfo
- Publication number
- CN111951006A CN111951006A CN202010798928.4A CN202010798928A CN111951006A CN 111951006 A CN111951006 A CN 111951006A CN 202010798928 A CN202010798928 A CN 202010798928A CN 111951006 A CN111951006 A CN 111951006A
- Authority
- CN
- China
- Prior art keywords
- public key
- transaction
- pool
- public
- transaction application
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/389—Keeping log of transactions for guaranteeing non-repudiation of a transaction
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
-
- 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/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
- H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- General Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Strategic Management (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Development Economics (AREA)
- Technology Law (AREA)
- Marketing (AREA)
- Economics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The application discloses a federation chain consensus method, a federation chain consensus system and a federation chain consensus terminal. When a first member and a second member carry out transaction, the first member sends a transaction application to the second user according to the private key of the first member and the public key of the second member in the public key pool; and after receiving the transaction application, the second member completes the transaction according to the verification information in the transaction application and the private key of the second member. And when the member in the alliance chain conducts transaction, a transaction application is initiated according to the public key of the other party and the private key of the member. Thereby enabling the trust and security of transactions between members to be improved.
Description
Technical Field
The present application relates to the field of block chain technologies, and in particular, to a method, a system, and a terminal for alliance chain consensus.
Background
With the spread of bitcoin, the block chain technique has become the mainstream of the current research field. The blockchain system is generally divided into a public chain, a federation chain and a private chain according to different application scenarios. The block chain is born in the era of mobile internet, enterprises are generally IT and internetwork, and the block chain is very helpful for further improving the efficiency of notarization, settlement and clearing business and value exchange network in the industry chain of the circle.
But in an attempt to use existing blockchain technologies (such as bitcoin code family and etherhouses), it was found that none of the processing performance, privacy protection, compliance, etc. of existing blockchains can meet their business needs. In practical applications, enterprises often choose a part of decentralized federation chains, because the public chains cannot meet the requirements of the enterprises due to the completely decentralized nature of the public chains. The consensus mechanism is an engine and a core of a block chain, and the current mainstream consensus mechanism is mainly proposed for public chains and is difficult to be applied to alliance chains.
Disclosure of Invention
In order to solve the technical problems, the following technical scheme is provided:
in a first aspect, an embodiment of the present application provides a federation chain consensus method, where the method includes: members in a coalition chain disclose a part of each own secret key to the coalition members to form a public secret key pool, wherein the secret key identification of each member in the public secret key pool is different; when a first member and a second member carry out transaction, the first member sends a transaction application to the second user according to the private key of the first member and the public key of the second member in the public key pool; and after receiving the transaction application, the second member completes the transaction according to the verification information in the transaction application and the private key of the second member.
By adopting the implementation mode, the member in the alliance chain publishes one part of the secret key, and when the member in the alliance chain transacts, the member initiates a transaction application according to the public secret key of the other party and the secret key of the member. Thereby enabling the trust and security of transactions between members to be improved.
With reference to the first aspect, in a first possible implementation manner of the first aspect, the issuing, by the first member, a transaction application to the second user according to the own key and the public key of the second member in the public key pool includes: the first member acquires a public key of the second member in the public key pool; and encapsulating the private key of the first member, and carrying the public keys of the first member and the second member in the public key pool.
With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the obtaining, by the first member, the key of the second member in the public key pool includes: determining identification information of the second member in the public key pool; and traversing the public key pool according to the identification information to determine the public key of the second member.
With reference to the first aspect, in a third possible implementation manner of the first aspect, after receiving the transaction application, the completing a transaction according to the verification information in the transaction application and the private key of the second member includes: the second member acquires public keys of the first member and the second member in the public key pool, wherein the public keys are carried in the transaction application; matching and verifying the private key of the second member with the public key of the second member in the public key pool carried in the transaction application; if the verification is passed, further verifying public key identification information of the first member in the public key pool, wherein the public key identification information is carried in the transaction application and carries public key pool information; and if the public key pool information carried by the public key identification information of the first member in the public key pool carried in the transaction application is consistent with the public key pool information where the public key of the second member is located, allowing the transaction.
With reference to the third possible implementation manner of the first aspect, in a fourth possible implementation manner of the first aspect, if the transaction is allowed, the private key information of the first user carried in the transaction application is obtained, and the private key of the second user is encapsulated and then sent to the first user.
In a second aspect, an embodiment of the present application provides a federation chain consensus system, where the system includes: the public key pool building module is used for enabling members in a coalition chain to disclose one part of each own secret key to coalition members to form a public key pool, and the secret key identifications of each member in the public key pool are different; the system comprises a transaction application module, a first member and a second member, wherein the transaction application module is used for sending a transaction application to the second user according to a private key of the first member and a public private key of the second member in a public private key pool when the first member and the second member perform transaction; and the transaction verification module is used for completing the transaction according to verification information in the transaction application and the private key of the second member after the second member receives the transaction application.
With reference to the second aspect, in a first possible implementation manner of the second aspect, the transaction application module includes: a first obtaining unit, configured to obtain, by the first member, a public key of the second member in the public key pool; and the encapsulation unit is used for encapsulating the private key of the first member and carrying the public keys of the first member and the second member in the public key pool.
With reference to the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, the first obtaining unit includes: a first determining subunit, configured to determine identification information of the second member in the public key pool; and the second determining subunit is configured to determine the public key of the second member according to the identification information by traversing the public key pool.
With reference to the second aspect, in a third possible implementation manner of the second aspect, the transaction verification module includes: a second obtaining unit, configured to obtain, by the second member, public keys of the first member and the second member in the public key pool, where the public keys are carried in the transaction application; the first verification unit is used for matching and verifying the private key of the second member with the public key of the second member in the public key pool carried in the transaction application; the second verification unit is used for further verifying public key identification information of the first member in the public key pool, which is carried in the transaction application, if the verification is passed, wherein the identification information carries public key pool information; and the transaction unit is used for allowing the transaction if public key pool information carried by public key identification information of the first member in the public key pool carried in the transaction application is consistent with public key pool information where a public key of the second member is located.
In a third aspect, an embodiment of the present application provides a terminal, including a processor; a memory for storing computer executable instructions; when the computer-executable instructions are executed by the processor, the processor performs the federation chain consensus method of the first aspect or any possible implementation of the first aspect.
Drawings
Fig. 1 is a schematic flowchart of a federation chain consensus method according to an embodiment of the present application;
fig. 2 is a schematic diagram of a federation chain consensus system provided by an embodiment of the present application;
fig. 3 is a schematic diagram of a terminal according to an embodiment of the present application.
Detailed Description
The present embodiment is described below with reference to the accompanying drawings and the detailed description.
Fig. 1 is a schematic flow diagram of a federation chain consensus method provided in the application embodiment, and referring to fig. 1, the federation chain consensus method in the embodiment includes:
s101, members in the federation chain disclose part of the key held by each member to the members in the federation to form a public key pool, wherein the key identification of each member in the public key pool is different.
In this embodiment, each member in the federation chain may publish, as a public key, a beginning portion, an intermediate portion, or a combination of the beginning and intermediate portions of its own key to a pool of public keys. After each member of the federation chain publishes a part of the key, the rest part of the key is used as a private key for later verification of transaction use.
S102, when the first member carries out transaction with the second member, the first member sends a transaction application to the second user according to the private key of the first member and the public key of the second member in the public key pool.
The first member obtains a public key of the second member in the public key pool. Specifically, the identification information of the second member in the public key pool is determined, and the public key of the second member is determined according to the identification information by traversing the public key pool.
And encapsulating the private key of the first member, and carrying the public keys of the first member and the second member in the public key pool.
And S103, after receiving the transaction application, the second member completes the transaction according to the verification information in the transaction application and the private key of the second member.
And the second member acquires the public keys of the first member and the second member in the public key pool carried in the transaction application. And matching and verifying the private key of the second member with the public key of the second member in the public key pool carried in the transaction application. And if the verification is passed, further verifying public key identification information of the first member in the public key pool, wherein the public key identification information is carried in the transaction application and carries public key pool information. And if the public key pool information carried by the public key identification information of the first member in the public key pool carried in the transaction application is consistent with the public key pool information where the public key of the second member is located, allowing the transaction.
And if the transaction is allowed, obtaining the private key information of the first user carried in the transaction application, and packaging the private key of the second user and then sending the packaged private key to the first user.
As can be seen from the foregoing embodiments, in the present embodiment, a method for federation chain consensus is provided, in which a member of a federation chain publishes a part of a secret key, and when the member of the federation chain conducts a transaction, a transaction application is initiated according to the public secret key of the other party and the secret key of the member. Thereby enabling the trust and security of transactions between members to be improved.
Corresponding to the federation chain consensus method provided by the above embodiment, the present application also provides an embodiment of a federation chain consensus system, and referring to fig. 2, the federation chain consensus system 20 includes: a public key pool construction module 201, a transaction application module 202 and a transaction verification module 203.
The public key pool building module 201 is configured to enable members in a federation chain to disclose a part of each own secret key to members in the federation to form a public key pool, where the secret key identifier of each member in the public key pool is different.
The transaction application module 202 is configured to, when a first member performs a transaction with a second member, send a transaction application to the second user according to a private key of the first member and a public key of the second member in a public key pool.
Further, the transaction application module 201 includes: the device comprises a first acquisition unit and a packaging unit.
The first obtaining unit is configured to obtain, by the first member, a public key of the second member in the public key pool. The encapsulation unit is configured to encapsulate the private key of the first member, and carry public keys of the first member and the second member in the public key pool.
The first acquisition unit includes: a first determining subunit and a second determining subunit.
The first determining subunit is configured to determine the identification information of the second member in the public key pool. The second determining subunit is configured to determine, according to the identification information, the public key of the second member by traversing the public key pool.
The transaction verification module 203 is configured to complete a transaction according to verification information in the transaction application and a private key of the second member after the second member receives the transaction application.
The transaction verification module 203 comprises: the system comprises a second acquisition unit, a first verification unit, a second verification unit and a transaction unit.
The second obtaining unit is configured to obtain, by the second member, public keys of the first member and the second member in the public key pool, where the public keys are carried in the transaction application. The first verification unit is configured to perform matching verification on the private key of the second member and the public key of the second member in the public key pool, where the public key is carried in the transaction application. The second verification unit is configured to further verify public key identification information of the first member in the public key pool, which is carried in the transaction application, if the verification is passed, where the identification information carries public key pool information. And the transaction unit is configured to allow the transaction if public key pool information carried by public key identification information of the first member in the public key pool carried in the transaction application is consistent with public key pool information where a public key of the second member is located.
The embodiment of the present application further provides a terminal, referring to fig. 3, the terminal 30 includes: a processor 301, a memory 302, and a communication interface 303.
In fig. 3, the processor 301, the memory 302, and the communication interface 303 may be connected to each other by a bus; the bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 3, but this does not mean only one bus or one type of bus.
The processor 301 is generally an overall function of the terminal 30, for example, the terminal 30 is started, and after the terminal 30 is started, members in a federation chain disclose a part of each held key to the members in the federation to form a public key pool, wherein the key identification of each member in the public key pool is different; when a first member and a second member carry out transaction, the first member sends a transaction application to the second user according to the private key of the first member and the public key of the second member in the public key pool; and after receiving the transaction application, the second member completes the transaction according to the verification information in the transaction application and the private key of the second member.
Further, the processor 301 may be a general-purpose processor, such as a Central Processing Unit (CPU), a Network Processor (NP), or a combination of a CPU and an NP. The processor may also be a Microprocessor (MCU). The processor may also include a hardware chip. The hardware chips may be Application Specific Integrated Circuits (ASICs), Programmable Logic Devices (PLDs), or a combination thereof. The PLD may be a Complex Programmable Logic Device (CPLD), a Field Programmable Gate Array (FPGA), or the like.
The memory 302 is configured to store computer-executable instructions to support the operation of the terminal 30 data. The memory 301 may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
After the terminal 30 is started, the processor 301 and the memory 302 are powered on, and the processor 301 reads and executes the computer executable instructions stored in the memory 302 to complete all or part of the steps in the above embodiments of the federation chain consensus method.
The communication interface 303 is used for data interaction of the terminal 30, and the communication interface 303 includes a wired communication interface and may also include a wireless communication interface. The wired communication interface comprises a USB interface, a Micro USB interface and an Ethernet interface. The wireless communication interface may be a WLAN interface, a cellular network communication interface, a combination thereof, or the like.
In an exemplary embodiment, the terminal 30 provided by the embodiments of the present application further includes a power supply component that provides power to the various components of the terminal 30. The power components may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the terminal 30.
In an exemplary embodiment, the terminal 30 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), terminals, micro-terminals, processors or other electronic components.
The same and similar parts among the various embodiments in the specification of the present application may be referred to each other. Especially, for the system and terminal embodiments, since the method therein is basically similar to the method embodiments, the description is relatively simple, and the relevant points can be referred to the description in the method embodiments.
It is noted that, in this document, relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, 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. The term "comprising", without further limitation, means that the element so defined is not excluded from the group consisting of additional identical elements in the process, method, article, or apparatus that comprises the element.
Of course, the above description is not limited to the above examples, and technical features that are not described in this application may be implemented by or using the prior art, and are not described herein again; the above embodiments and drawings are only for illustrating the technical solutions of the present application and not for limiting the present application, and the present application is only described in detail with reference to the preferred embodiments instead, it should be understood by those skilled in the art that changes, modifications, additions or substitutions within the spirit and scope of the present application may be made by those skilled in the art without departing from the spirit of the present application, and the scope of the claims of the present application should also be covered.
Claims (10)
1. A federation chain consensus method, the method comprising:
members in a coalition chain disclose a part of each own secret key to the coalition members to form a public secret key pool, wherein the secret key identification of each member in the public secret key pool is different;
when a first member and a second member carry out transaction, the first member sends a transaction application to the second user according to the private key of the first member and the public key of the second member in the public key pool;
and after receiving the transaction application, the second member completes the transaction according to the verification information in the transaction application and the private key of the second member.
2. A federation chain consensus method as claimed in claim 1, wherein said first member issuing a transaction application to said second user based on its own key and the public key of said second member in a pool of public keys comprises:
the first member acquires a public key of the second member in the public key pool;
and encapsulating the private key of the first member, and carrying the public keys of the first member and the second member in the public key pool.
3. A federation chain consensus method as claimed in claim 2, wherein said obtaining by the first member the key of the second member in the pool of public keys comprises:
determining identification information of the second member in the public key pool;
and traversing the public key pool according to the identification information to determine the public key of the second member.
4. A federation chain consensus method as claimed in claim 1, wherein the second member, after receiving the transaction application, completing the transaction according to the authentication information in the transaction application and the second member's private key comprises:
the second member acquires public keys of the first member and the second member in the public key pool, wherein the public keys are carried in the transaction application;
matching and verifying the private key of the second member with the public key of the second member in the public key pool carried in the transaction application;
if the verification is passed, further verifying public key identification information of the first member in the public key pool, wherein the public key identification information is carried in the transaction application and carries public key pool information;
and if the public key pool information carried by the public key identification information of the first member in the public key pool carried in the transaction application is consistent with the public key pool information where the public key of the second member is located, allowing the transaction.
5. The alliance-chain consensus method according to claim 4, wherein if the transaction is allowed, obtaining the private key information of the first user carried in the transaction application, and sending the private key of the second user to the first user after encapsulating the private key of the second user.
6. A federation chain consensus system, the system comprising:
the public key pool building module is used for enabling members in a coalition chain to disclose one part of each own secret key to coalition members to form a public key pool, and the secret key identifications of each member in the public key pool are different;
the system comprises a transaction application module, a first member and a second member, wherein the transaction application module is used for sending a transaction application to the second user according to a private key of the first member and a public private key of the second member in a public private key pool when the first member and the second member perform transaction;
and the transaction verification module is used for completing the transaction according to verification information in the transaction application and the private key of the second member after the second member receives the transaction application.
7. A federation chain consensus system as claimed in claim 6, wherein the transaction application module comprises:
a first obtaining unit, configured to obtain, by the first member, a public key of the second member in the public key pool;
and the encapsulation unit is used for encapsulating the private key of the first member and carrying the public keys of the first member and the second member in the public key pool.
8. The federation chain consensus system of claim 7, wherein the first obtaining unit comprises:
a first determining subunit, configured to determine identification information of the second member in the public key pool;
and the second determining subunit is configured to determine the public key of the second member according to the identification information by traversing the public key pool.
9. A federation chain consensus system as claimed in claim 6, wherein the transaction verification module comprises:
a second obtaining unit, configured to obtain, by the second member, public keys of the first member and the second member in the public key pool, where the public keys are carried in the transaction application;
the first verification unit is used for matching and verifying the private key of the second member with the public key of the second member in the public key pool carried in the transaction application;
the second verification unit is used for further verifying public key identification information of the first member in the public key pool, which is carried in the transaction application, if the verification is passed, wherein the identification information carries public key pool information;
and the transaction unit is used for allowing the transaction if public key pool information carried by public key identification information of the first member in the public key pool carried in the transaction application is consistent with public key pool information where a public key of the second member is located.
10. A terminal, comprising: a processor;
a memory for storing computer executable instructions;
the computer-executable instructions, when executed by the processor, cause the processor to perform the federation chain consensus method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010798928.4A CN111951006A (en) | 2020-08-10 | 2020-08-10 | Alliance chain consensus method, system and terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010798928.4A CN111951006A (en) | 2020-08-10 | 2020-08-10 | Alliance chain consensus method, system and terminal |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111951006A true CN111951006A (en) | 2020-11-17 |
Family
ID=73332000
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010798928.4A Pending CN111951006A (en) | 2020-08-10 | 2020-08-10 | Alliance chain consensus method, system and terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111951006A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140147045A1 (en) * | 2007-10-30 | 2014-05-29 | Paceo Corp. | Method and Apparatus for Operating, Interfacing and/or Managing for at Least One Optical Characteristic System for Container Handlers in a Container Yard |
| CN109242636A (en) * | 2018-09-26 | 2019-01-18 | 盈盈（杭州）网络技术有限公司 | A kind of data transacting system and its implementation based on block chain |
| CN109687963A (en) * | 2019-01-15 | 2019-04-26 | 如般量子科技有限公司 | Anti- quantum calculation alliance chain method of commerce and system based on public key pond |
| CN110635897A (en) * | 2019-08-28 | 2019-12-31 | 如般量子科技有限公司 | Key updating or downloading method and system based on alliance chain and resisting quantum computing |
| CN110636050A (en) * | 2019-08-28 | 2019-12-31 | 如般量子科技有限公司 | Anonymous identity recognition method and system based on alliance chain and resisting quantum computation |
-
2020
- 2020-08-10 CN CN202010798928.4A patent/CN111951006A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140147045A1 (en) * | 2007-10-30 | 2014-05-29 | Paceo Corp. | Method and Apparatus for Operating, Interfacing and/or Managing for at Least One Optical Characteristic System for Container Handlers in a Container Yard |
| CN109242636A (en) * | 2018-09-26 | 2019-01-18 | 盈盈（杭州）网络技术有限公司 | A kind of data transacting system and its implementation based on block chain |
| CN109687963A (en) * | 2019-01-15 | 2019-04-26 | 如般量子科技有限公司 | Anti- quantum calculation alliance chain method of commerce and system based on public key pond |
| CN110635897A (en) * | 2019-08-28 | 2019-12-31 | 如般量子科技有限公司 | Key updating or downloading method and system based on alliance chain and resisting quantum computing |
| CN110636050A (en) * | 2019-08-28 | 2019-12-31 | 如般量子科技有限公司 | Anonymous identity recognition method and system based on alliance chain and resisting quantum computation |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109040029B (en) | Method and apparatus for executing transactions in a blockchain | |
| CN113572715B (en) | Data transmission method and system based on block chain | |
| CN111341024A (en) | Charging pile sharing method, device, equipment and storage medium based on block chain | |
| CN105637915B (en) | Method for assigning a proxy device from a first device registry to a second device registry | |
| CN110597839A (en) | Transaction data processing method, device, equipment and storage medium | |
| CN114301675B (en) | Privacy data transaction method, system, computer device and storage medium | |
| CN111814156A (en) | A data acquisition method, device and device based on trusted equipment | |
| CN110276170A (en) | Method, equipment and the medium of works protection are carried out based on block chain | |
| CN110879826A (en) | Credit blacklist sharing method and device based on block chain | |
| CN111429134A (en) | Blockchain-based data transaction method and device | |
| CN111131234A (en) | Intelligent contract data processing method and device in supply chain and computer equipment | |
| WO2019165875A1 (en) | Transaction processing method, server, client, and system | |
| Yu et al. | Blockchain technology for the 5g-enabled internet of things systems: Principle, applications and challenges | |
| US20190097806A1 (en) | System and Methods for Resolving Data Discrepancies in a Distributed System with Blockchain Controls | |
| CN113472781A (en) | Service acquisition method, server and computer readable storage medium | |
| CN111027992B (en) | Asset transaction method, device and hardware equipment based on blockchain system | |
| CN100474323C (en) | Tamper resistant device and file generation method | |
| CN111211902A (en) | Digital signature method and device based on enterprise browser | |
| CN111951006A (en) | Alliance chain consensus method, system and terminal | |
| CN115412256A (en) | Identity authentication method and device based on block chain, storage medium and terminal equipment | |
| CN113704712B (en) | Identity authentication method, device, system and electronic device | |
| CN107205080A (en) | A kind of smart mobile phone with independent finance transaction system | |
| CN111125734B (en) | Data processing method and system | |
| CN111369355A (en) | Transaction data processing method and device based on alliance chain | |
| CN110995440A (en) | Work history confirming method, device, equipment and storage medium |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201117 |
|
| RJ01 | Rejection of invention patent application after publication |