CN108810137B - Alliance block chain system - Google Patents
Alliance block chain system Download PDFInfo
- Publication number
- CN108810137B CN108810137B CN201810594263.8A CN201810594263A CN108810137B CN 108810137 B CN108810137 B CN 108810137B CN 201810594263 A CN201810594263 A CN 201810594263A CN 108810137 B CN108810137 B CN 108810137B
- Authority
- CN
- China
- Prior art keywords
- account
- chain
- blockchain system
- federation
- transaction
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1059—Inter-group management mechanisms, e.g. splitting, merging or interconnection of groups
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- 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
- H04L9/3252—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 using DSA or related signature schemes, e.g. elliptic based signatures, ElGamal or Schnorr schemes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
- H04L2209/56—Financial cryptography, e.g. electronic payment or e-cash
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2463/00—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00
- H04L2463/102—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00 applying security measure for e-commerce
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates
-
- 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
Abstract
The application discloses union block chain system, which realizes the issue of user-defined permit by adding system asset chain codes in chain codes deployed by the union block chain system, maintains an account with permit and realizes the management of the permit assets by adding a permit circulation unit, and writes the state related to the permit into a field related to the system asset chain codes in an account book by the signature of the account so as to realize the permit circulation. This expands the application requirements of the federated blockchain system.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to the field of blockchain technologies, and more particularly, to an alliance blockchain system.
Background
A federated blockchain system refers to a blockchain whose consensus process is controlled by authorized trusted nodes. That is, ordinary nodes (nodes that do not obtain federation permissions) may review and trade, but may not verify the trade and may not deploy smart contracts. Only nodes that possess a certain reputation and are granted certificates by the federation can conduct authentication transactions and participate in deploying smart contracts. Compared with the traditional centralized transaction system, the multi-party mutual trust problem can be effectively solved, and the transaction record is safe and cannot be tampered.
The existing alliance blockchain system does not support circulation of the underlying certificates, namely, does not have a basis for value circulation and economic incentive. Therefore, when the node participates in the alliance blockchain network maintenance behaviors such as endorsement, endorsement and block packing of a transaction proposal, no economic incentive exists, and the issuing and circulation of the custom certificate can not be realized in the alliance blockchain system, so that the application scene of the alliance blockchain system is limited.
Disclosure of Invention
In view of the above, the present application provides an alliance blockchain system, so that certified circulation can be performed in the alliance blockchain system, thereby expanding the application requirements of the alliance blockchain system.
The application provides an alliance blockchain system, which comprises a peer-to-peer network consisting of a plurality of peer-to-peer nodes and a sequencing node;
wherein the federation blockchain system comprises:
the system comprises an account book and a transaction unit, wherein the account book and the transaction unit are configured to maintain an account book of a block of a alliance, and the account book comprises a block chain data structure and a state database;
a chain code unit configured to operate on an ledger through the ledger and transaction unit based on a call to a deployed chain code, wherein the deployed chain code comprises a system asset chain code;
a right management unit configured to perform right management based on the in-chain license certificate; and
and the certificate passing circulation unit is configured to maintain an account holding the certificate and write the state related to the certificate passing into the field related to the system asset chain code in the account book through the signature of the account so as to carry out the circulation of the certificate passing.
Further, the system asset chain code is configured to encapsulate a certification issuance interface such that the federation blockchain system supports custom certification issuance.
Further, the federation blockchain system further comprises:
and the cross-chain management unit is configured to provide an interface for cross-chain general evidence circulation.
Further, the federation blockchain system further comprises:
a plurality of relay endorsement nodes configured to endorse a cross-chain transaction proposal.
Further, the information of the account comprises a private key, a public key and an address of the account;
the signature of the account is a private key signature of the account, and the private key signature of the account is used for identifying the identity of the account.
Further, the private key is generated by the secp256k1 elliptic curve algorithm, and the public key and the address are derived by the private key.
Further, a plurality of the peer nodes in the federation blockchain are synchronized via Gossip protocol.
Further, the right management unit generates the entering-chain license certificate by adopting a PKI technology.
According to the technical scheme, the user-defined certification passing issuing is achieved by adding the system asset chain code in the chain code deployed in the block chain system of the alliance, the account with the certification passing is maintained and the certification passing asset management is achieved by adding the certification passing circulation unit, and the state related to the certification passing is written into the field related to the system asset chain code in the account book through the signature of the account so as to achieve the certification passing circulation. This expands the application requirements of the federated blockchain system.
Drawings
The above and other objects, features and advantages of the present application will become more apparent from the following description of embodiments thereof with reference to the accompanying drawings, in which:
FIG. 1 is a schematic diagram of a HyperLegger Fabric;
FIG. 2 is a schematic diagram of a network architecture of a federated blockchain system according to an embodiment of the present application;
FIG. 3 is a functional block diagram of a federation blockchain system according to an embodiment of the present application;
fig. 4 is a schematic diagram of an account data structure according to an embodiment of the present application.
Detailed Description
The present application is described below based on examples, but the present application is not limited to only these examples. In the following detailed description of the present application, certain specific details are set forth in detail. It will be apparent to one skilled in the art that the present application may be practiced without these specific details. Well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the present application.
Further, those of ordinary skill in the art will appreciate that the drawings provided herein are for illustrative purposes and are not necessarily drawn to scale.
Unless the context clearly requires otherwise, throughout the description and the claims, the words "comprise", "comprising", and the like are to be construed in an inclusive sense as opposed to an exclusive or exhaustive sense; that is, what is meant is "including, but not limited to".
In the description of the present application, it is to be understood that the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. In addition, in the description of the present application, "a plurality" means two or more unless otherwise specified.
FIG. 1 is a schematic diagram of a HyperLegger Fabric. HyperLegendr Fabric is a typical existing federation blockchain system. The Hyperridge project is a combined project which is held by a Linux fund in 12 months in 2015 and is formed by combining 30 initial enterprise members (including IBM, Accenture, Intel, Cisco and the like), provides open source reference for a transparent, open and decentralized enterprise-level distributed account book technology, and promotes the development of related protocols, specifications and standards of a block chain and a distributed account book. Fabric is the top level item that was first added to the super ledger project. The project is positioned on a distributed account book platform facing enterprises, the authority management support is innovatively introduced, and the project is pluggable and extensible in design and is the first open-source project facing a alliance chain scene. As shown in fig. 1, the hyper book Fabric is a P2P network (peer to peer) composed of a plurality of nodes, and each node is synchronized through Gossip protocol.
The P2P network, i.e. a peer-to-peer computer network, is a distributed application architecture for distributing tasks and workloads among peers, and is a networking or network form formed by the peer-to-peer computing model in the application layer.
The Gossip algorithm is a final consistency algorithm that naturally has the advantage of distributed fault tolerance. The Gossip algorithm is characterized in that each node randomly communicates with other nodes in the network, and finally the states of all the nodes are consistent after one-time chaotic communication. Therefore, the Gossip transport protocol is adopted in the embodiment, so that the ledger of the federation block continuously maintains real-time performance and synchronization.
The super book provides an API (Application Program Interface) and a corresponding SDK (Software Development Kit) for encapsulating the API for upper layer applications. The upper layer application accesses various resources in the hyper book Fabric network through the SDK, such as book, transaction, event, chain code, authority management and the like. The account book is the most core structure and is responsible for recording information generated by upper layer applications, and the upper layer applications record data in the account book through transactions. The chain code bears the logic of transaction execution, and the authority management is responsible for access control in the whole process.
The super book Fabric hierarchical structure improves the expandability and the pluggable performance of the system. However, the circulation of accounts and certificates is not supported in the hyper book Fabric, so that the identity of a caller cannot be identified when the user calls a relevant interface of a chain code through the SDK, and the hyper book Fabric is not suitable for an application scenario containing economic incentive. Meanwhile, the hyper book Fabric cannot interact with other blockchains, so that an information island exists.
Fig. 2 is a schematic network architecture of a block chain alliance system according to an embodiment of the present invention. Fig. 3 is a functional block diagram of a federation blockchain system according to an embodiment of the present application. Fig. 4 is a schematic diagram of an account data structure according to an embodiment of the present application. As shown in FIG. 2, the federation blockchain system of the present embodiment includes a plurality of peer nodes A1-An, a plurality of sorting nodes B1-Bn, and a plurality of client nodes C1-Cn. A plurality of peer nodes A1-An, a plurality of sequencing nodes B1-Bn, and a plurality of client nodes C1-Cn are coupled to and communicate through the federation blockchain network 100. Among them, peer nodes A1-An are synchronized through Gossip transmission protocol. The alliance blockchain network 100 is a P2P network (Peer-to-Peer network).
In a federated blockchain system, a peer node may be an endorsement node or an authentication node. Wherein the endorsement node endorses the transaction proposal submitted by the client node according to the endorsement rule. And the sequencing node sequences and packs the transaction after the endorsement by the sequencing node. The verification node verifies and validates the transaction in the block. Specifically, the endorsement node simulates and executes the transaction after receiving the transaction proposal, and then packages the transaction proposal and the simulation execution result together, signs the transaction proposal and the simulation execution result and sends the signed transaction proposal and the signed simulation execution result to the client node. It should be understood that the results of simulating the execution of a transaction and the state modifications are not written to the ledger. After the client node receives the response of each endorsement node, the transaction consisting of the transaction proposal and the simulation execution result is signed and then sent to the sequencing node. And the sequencing node performs consensus sequencing on the received transactions according to a consensus mechanism, packs a batch of transactions together according to a block generation strategy to generate a new block and sends the new block to the verification node. And the verification node verifies each transaction in the block after receiving the block, checks whether the input and output of the transaction conform to the state of the current block chain, and writes the block into the account book after the verification is finished. It should be understood that the endorsement node may also sometimes perform the function of the authentication node.
Preferably, the federation blockchain system supports BFT (Byzantine Fault tolerance mechanism) and Kafka consensus mechanisms. The BFT consensus mechanism means that the ledger confirmed by the 2/3 validation node can become the standard ledger. The Kafka consensus mechanism is based on the ordering implementation of Kafka (distributed message System) clusters, and supports persistence and extensibility. Consistency of multi-chain data is provided by using Kafka to provide ordering services and using fault tolerance.
In this embodiment, as shown in fig. 3, the functional units of the federation blockchain system of this embodiment include a currency circulation unit 31, an account book and transaction unit 32, a chain code unit 33, and a right management unit 34. The ledger and transaction unit 32 is configured to maintain an ledger of block of the federation according to a consensus mechanism, the ledger including a block chain data structure and a status database to record transactions and current status of block chains after transactions. The chain code unit 33 is configured to operate on the ledger of the federation blocks through the ledger and transaction unit based on a call to the deployed chain code. Wherein the chain code deployed in the federation blockchain system is used to implement logic for transaction execution, including system asset chain code. The passport circulation unit 31 is configured to maintain an account holding a passport and write a status related to the passport into a field related to a system asset chain code in the ledger through a signature of the account for circulation of the passport. The rights management unit 34 is configured to perform rights management based on the license certificate. The authority management unit generates the license by using a Public Key Infrastructure (PKI) technology.
The chain codes deployed in a federated blockchain system rely on container or state machine technology. The container technology is lightweight operating system virtualization, and can run an application program in a resource isolation process. The container technology allows the components necessary to run the application to be packaged as a mirror image and reused. When the mirror image is executed, the mirror image runs in an isolation environment, and the memory, the CPU and the disk of the host computer cannot be shared, so that the condition that the process in the container cannot monitor any process outside the container is ensured. Thus, container technology lightweight scripts improve system performance, and each container can be viewed as a distinct microservice enabling independent upgrades. The container encapsulates all relevant details necessary to run the application so that the image can be flexibly ported from one environment to another.
In this embodiment, the federation blockchain system issues a certificate based on PKI technology to nodes in the federation blockchain system through the rights management unit 34. PKI includes CA (certificate authority). Wherein the federation blockchain system issues root certificates (rootcerts) to members of the federation through the CA, registration certificates (eCert) for each authorized user, and transaction certificates (TCerts) for each registered user.
Meanwhile, the block chain system of the alliance obtains the account of the user when the user applies for the registration node so as to support the circulation of the certificate of pass. The account in the embodiment supports a configurable multi-asset system, meets the requirement of direct interaction between an anonymous user and a block chain of a alliance, and realizes the identification of the identity of a transaction initiator when a chain code is called. As shown in fig. 4, account 4 includes account balance 41 and check code Counter. The account balance 41 contains the type of each pass and the amount of each type of pass. The check code Counter is used for transaction ordering.
Wherein the generation of the account is based on a predetermined algorithm. The predetermined algorithm generates a private key and a public key of the account, and derives a corresponding account address in a single direction through the public key. Preferably, the public key is hashed to derive the address of the account. For example, the address, private key, and public key of an account are shown in the following table:
preferably, the account private and public keys are generated using the secp256k1 elliptic curve algorithm. The secp256k1 is based on an elliptic curve in a finite field, and the performance (such as calculation speed and the like) of the elliptic curve is 30% higher than that of other elliptic curves. And the constants in the secp256k1 elliptic curve algorithm tend to be generated in a predictable manner, so the private and public keys of the account generated by the secp256k1 elliptic curve algorithm are more secure. Each user's account has a private key, a public key and an address, and can be signed by the private key of the account when the associated chain code is called, so as to indicate the identity of the initiator of the current transaction.
The chain codes deployed in the federated blockchain system include system asset chain codes. The certification passing unit 31 writes the status related to the certification into the field related to the system asset chain code in the ledger through the private key signature of the account, so that the certification can pass through the federation blockchain system. The client of any user can change the relevant state in the account book through the relevant interface of the chain code to realize the transfer transaction, thereby realizing the circulation of the general evidence in the block chain system of the alliance.
Preferably, the system asset chain code is configured to encapsulate the certification issuing interface such that the federation blockchain system supports custom certification issuing. Through the support of the certification circulation unit 31, customized alliance block chain systems can be established in different industries so as to meet basic service functions and achieve customized certification circulation and customized economic incentive models.
Preferably, the federation blockchain system of the present embodiment further includes a plurality of relay endorsement nodes configured to endorse a cross-chain transaction proposal. The functional units of the federated blockchain system also include a cross-chain management unit 35 configured to provide a cross-chain interface to enable cross-chain interaction of the federated blockchain system with the public chain system. The chain codes deployed in the block chain system of the alliance also comprise cross-chain codes. Public chain cross-chain information is registered in a block chain system of the alliance through a cross-chain code so that two parties can conduct cross-chain transaction. For example, account a on the federation blockchain system side performs a cross-chain transaction for the same kind of evidence with account B on the public chain system side. The cross-chain request of account a is verified by the federation blockchain system, and then account a sends a predetermined number of pass-through locks to the cross-chain functional accounts in the federation blockchain system. And the relay endorsement node of the alliance block chain system carries out endorsement signature on the cross-chain transaction proposal and initiates a transaction proposal vote to the public chain side. The public chain system deploys a cross-chain contract in advance, and after a cross-chain transaction proposal and a cross-chain transaction request at the public chain system side are verified, a predetermined number of certificates are unlocked by a cross-chain contract account and sent to an account B. That is, cross-chain transactions between the federated blockchain system and the public chain system are achieved through certified locking and unlocking, which makes the federated blockchain system no longer have information islands.
In addition, the present embodiment provides a corresponding API (Application Program Interface) and an SDK (Software Development Kit) corresponding to the encapsulated API for the upper layer Application. The upper layer application can access the elements such as the evidence-passing circulation unit 31, the ledger and transaction unit 32, the chain code unit 33, the authority management unit 34 and the cross-chain management unit 35 in the alliance blockchain network through the SDK.
In this embodiment, by adding the certified flow unit and adding the system asset chain code to the chain code deployed in the alliance blockchain system, the alliance blockchain system can perform certified flow, which improves the performance of the alliance blockchain system and extends the application requirement of the alliance blockchain system.
The federated blockchain system of the present embodiment is suitable for deployment on multiple servers that include common computer hardware structures, such as processors and memory. The memory is adapted to store instructions or programs executable by the processor. The processor may be a stand-alone microprocessor or a collection of one or more microprocessors. Thus, the processor executes the instructions stored in the memory to perform the functions of the federation blockchain in this embodiment to implement maintenance and currency of the federation block ledger. Those skilled in the art will appreciate that the present embodiments may be implemented by computer instructions stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the functions specified in the present embodiments. These computer program instructions may also be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the embodiments.
The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (6)
1. A federated blockchain system comprising a peer-to-peer network comprised of a plurality of peer nodes and a sequencing node;
wherein the federation blockchain system comprises:
the system comprises an account book and a transaction unit, wherein the account book and the transaction unit are configured to maintain an account book of a block of a alliance, and the account book comprises a block chain data structure and a state database;
a chain code unit configured to operate on an ledger through the ledger and transaction unit based on a call to a deployed chain code, wherein the deployed chain code comprises a system asset chain code;
a right management unit configured to perform right management based on the license certificate; and
the certificate passing circulation unit is configured to maintain an account holding the certificate and write the state related to the certificate passing into a field related to the system asset chain code in the account book through the signature of the account so as to carry out the circulation of the certificate passing;
a cross-chain management unit configured to provide an interface for cross-chain passcertificate circulation;
a plurality of relay endorsement nodes configured to endorse a cross-chain transaction proposal.
2. A federation blockchain system as recited in claim 1, wherein the system asset chain code is configured to encapsulate a credential issuance interface such that the federation blockchain system supports custom credential issuance.
3. The federated blockchain system of claim 1, wherein the information of the account includes a private key, a public key, and an address of the account;
the signature of the account is a private key signature of the account, and the private key signature of the account is used for identifying the identity of the account.
4. A federation blockchain system as in claim 3 wherein the private key from which the public key and address are derived is generated by a secp256k1 elliptic curve algorithm.
5. A federation block chain system as claimed in claim 1, wherein a plurality of said peer nodes in the federation block chain are synchronized by the Gossip protocol.
6. A federation blockchain system as in claim 1 wherein the rights management unit employs PKI technology to generate the license credential.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810594263.8A CN108810137B (en) | 2018-06-11 | 2018-06-11 | Alliance block chain system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810594263.8A CN108810137B (en) | 2018-06-11 | 2018-06-11 | Alliance block chain system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108810137A CN108810137A (en) | 2018-11-13 |
| CN108810137B true CN108810137B (en) | 2021-10-01 |
Family
ID=64088998
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810594263.8A Active CN108810137B (en) | 2018-06-11 | 2018-06-11 | Alliance block chain system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108810137B (en) |
Families Citing this family (37)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109523317A (en) * | 2018-11-16 | 2019-03-26 | 上海万向区块链股份公司 | A kind of logical card system of distributed ecology |
| CN109413202B (en) * | 2018-11-29 | 2021-07-09 | 北京京东尚科信息技术有限公司 | System and method for sorting block chain transaction information |
| WO2020108289A1 (en) * | 2018-11-29 | 2020-06-04 | 华为技术有限公司 | Database system, node and method |
| CN109635165A (en) * | 2018-12-06 | 2019-04-16 | 北京磁云数字科技有限公司 | Data summarization method, device, equipment and medium based on tree-like block chain network |
| CN109710387B (en) * | 2018-12-06 | 2020-12-15 | 成都佰纳瑞信息技术有限公司 | Policy engine for block chain transaction priority ordering and use method thereof |
| CN111327565B (en) * | 2018-12-13 | 2022-09-06 | 北京果仁宝软件技术有限责任公司 | Block chaining and deblocking method and system |
| CN109685418A (en) * | 2018-12-14 | 2019-04-26 | 合肥维天运通信息科技股份有限公司 | A kind of sincere logistics alliance system and method based on block chain technology |
| CN111325552A (en) * | 2018-12-14 | 2020-06-23 | 北京海益同展信息科技有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN111355757B (en) * | 2018-12-21 | 2022-06-07 | 航天信息股份有限公司 | Cross-chain communication method and device for block chain in supply chain field |
| CN109685489B (en) * | 2018-12-28 | 2021-06-01 | 杭州云象网络技术有限公司 | Cross-chain transaction method for assets between block chains |
| CN109858908B (en) * | 2019-01-09 | 2021-07-27 | 暨南大学 | Alliance chain construction method, transaction method and distributed supply chain system |
| CN109583863B (en) * | 2019-01-21 | 2024-04-02 | 深圳市祥云万维科技有限公司 | Block chain resource transaction network and transaction method |
| CN111489256B (en) * | 2019-01-25 | 2023-06-23 | 京东科技控股股份有限公司 | Cross-chain processing method, device and system for multi-chain block chain system |
| CN109872156A (en) * | 2019-03-11 | 2019-06-11 | 赛迪(青岛)区块链研究院有限公司 | A kind of alliance's chain common recognition system and method |
| CN110020860B (en) * | 2019-04-09 | 2023-09-05 | 湖南天河国云科技有限公司 | Cross-chain asset transfer method, system and computer readable storage medium |
| CN110163751B (en) * | 2019-04-15 | 2023-07-04 | 广州致链科技有限公司 | Block chain access system oriented to alliance chain and implementation method thereof |
| CN110223170A (en) * | 2019-05-15 | 2019-09-10 | 北京瑞卓喜投科技发展有限公司 | The distributing method and system of the logical card of security type based on alliance's chain |
| CN110222532A (en) * | 2019-06-06 | 2019-09-10 | 杭州趣链科技有限公司 | A kind of subregion common recognition method for realizing the secret protection of alliance's chain based on NameSpace |
| CN110415114A (en) * | 2019-06-12 | 2019-11-05 | 阿里巴巴集团控股有限公司 | A kind of method and apparatus of the unlocking account in block chain |
| CN110430235B (en) * | 2019-06-28 | 2020-11-03 | 创新先进技术有限公司 | Method, apparatus, storage medium and computing device for cross-chain transmission of authenticatable messages |
| US11251966B2 (en) | 2019-06-28 | 2022-02-15 | Advanced New Technologies Co., Ltd. | Sending cross-chain authenticatable messages |
| CN112003703B (en) | 2019-06-28 | 2023-08-22 | 创新先进技术有限公司 | Method and device for transmitting authenticatable message across chains |
| US11356282B2 (en) | 2019-06-28 | 2022-06-07 | Advanced New Technologies Co., Ltd. | Sending cross-chain authenticatable messages |
| CN110401656B (en) * | 2019-07-24 | 2021-11-30 | 西安纸贵互联网科技有限公司 | Block chain management system |
| CN110474901B (en) * | 2019-08-13 | 2021-12-07 | 西安纸贵互联网科技有限公司 | Public block chain network system |
| CN110581887B (en) * | 2019-09-02 | 2021-03-30 | 北京海益同展信息科技有限公司 | Data processing method, device, block chain node and storage medium |
| CN110991573B (en) * | 2019-11-04 | 2023-09-01 | 京东科技信息技术有限公司 | Product management method, system, client node and storage medium |
| CN111159764A (en) * | 2019-12-26 | 2020-05-15 | 杭州趣链科技有限公司 | Voting-based method for realizing alliance chain autonomy by combining link-up and link-down |
| CN111163165A (en) * | 2019-12-28 | 2020-05-15 | 北京工业大学 | Voting consensus method based on Fabric alliance chain |
| CN111182075A (en) * | 2019-12-31 | 2020-05-19 | 杭州趣链科技有限公司 | Fabric block chain network alliance networking method |
| CN111598650A (en) * | 2020-04-28 | 2020-08-28 | 深圳壹账通智能科技有限公司 | Resource request transaction method based on block chain network and related device |
| CN111741026B (en) * | 2020-08-07 | 2020-12-01 | 百度在线网络技术（北京）有限公司 | Cross-chain transaction request processing method, device, equipment and storage medium |
| CN112398853B (en) * | 2020-11-16 | 2023-04-18 | 东软集团股份有限公司 | Method, device and system for realizing alliance chain cross-chain communication |
| CN112783877A (en) * | 2020-12-30 | 2021-05-11 | 北京百度网讯科技有限公司 | Cross-link data verification method, device, equipment and storage medium |
| CN113094398B (en) * | 2021-04-20 | 2024-04-05 | 深圳力维智联技术有限公司 | Data link tracking method based on block chain technology |
| CN114661421A (en) * | 2022-03-30 | 2022-06-24 | 蚂蚁区块链科技(上海)有限公司 | Method and system for deploying chain code in alliance chain |
| CN114979244B (en) * | 2022-04-29 | 2023-12-22 | 上海交通大学 | Hash time locking protocol-based multi-chain trusted transaction BaaS service platform architecture |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106127578A (en) * | 2016-06-20 | 2016-11-16 | 深圳市淘淘谷信息技术有限公司 | A kind of block chain shows the method for marketable securities circulation |
| EP3236403A2 (en) * | 2016-04-22 | 2017-10-25 | Sony Corporation | Client, server, method and identity verification system |
| CN107660293A (en) * | 2015-04-20 | 2018-02-02 | 欧吉达克斯公司 | Property rights electronic certificate（EDT）Distribution management method and its system |
| CN107992621A (en) * | 2017-12-22 | 2018-05-04 | 杭州云象网络技术有限公司 | A kind of intelligent cinematic industry service system based on block chain multichain technological incorporation |
-
2018
- 2018-06-11 CN CN201810594263.8A patent/CN108810137B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107660293A (en) * | 2015-04-20 | 2018-02-02 | 欧吉达克斯公司 | Property rights electronic certificate（EDT）Distribution management method and its system |
| EP3236403A2 (en) * | 2016-04-22 | 2017-10-25 | Sony Corporation | Client, server, method and identity verification system |
| CN106127578A (en) * | 2016-06-20 | 2016-11-16 | 深圳市淘淘谷信息技术有限公司 | A kind of block chain shows the method for marketable securities circulation |
| CN107992621A (en) * | 2017-12-22 | 2018-05-04 | 杭州云象网络技术有限公司 | A kind of intelligent cinematic industry service system based on block chain multichain technological incorporation |
Non-Patent Citations (1)
| Title |
|---|
| 区块链技术及其在信息安全领域的研究进展;刘敖迪等;《软件学报》;20180427;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108810137A (en) | 2018-11-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108810137B (en) | Alliance block chain system | |
| CN110915166B (en) | Block chain | |
| CN111144881B (en) | Selective access to asset transfer data | |
| CN109359957B (en) | Safe multiparty computing method and related device | |
| WO2021184963A1 (en) | Contract calling method and apparatus | |
| WO2020124317A1 (en) | Multi-access edge computing node with distributed ledger | |
| US11762842B2 (en) | Systems and methods for asynchronous delayed updates in virtual distributed ledger networks | |
| CN111164935B (en) | Systems and methods for providing privacy and security protection in blockchain-based private transactions | |
| Bozic et al. | Securing virtual machine orchestration with blockchains | |
| US11765225B2 (en) | Systems and methods for microservice execution load balancing in virtual distributed ledger networks | |
| JP2020515092A (en) | Blockchain monitoring and management | |
| KR102569409B1 (en) | Systems and methods for virtual distributed ledger networks | |
| CN110263580B (en) | Data processing method and device based on block chain and block chain link points | |
| US11838406B2 (en) | Systems and methods for control-data plane partitioning in virtual distributed ledger networks | |
| US11763298B2 (en) | Systems and methods for hybrid synchronization in virtual distributed ledger networks | |
| Mencias et al. | An optimized blockchain solution for the IBM z14 | |
| US10805294B1 (en) | Systems and methods for validating device permissions of computing devices to execute code on a decentralized database | |
| CN115705571A (en) | Protecting privacy of auditable accounts | |
| Swarnkar et al. | Security, privacy, trust management and performance optimization of blockchain technology | |
| US9361435B1 (en) | Multi-tier digital supply chain management | |
| CN116997895A (en) | Reducing transaction aborts in an execution ordering validation blockchain model | |
| CN114239043A (en) | Shared encryption storage system constructed based on block chain technology | |
| Wang et al. | ONMCA: One-Network-Multi-Chain Architecture for customizable asset-oriented blockchain systems | |
| CN116032494A (en) | Data interaction method, blockchain predictor, device and medium | |
| Novotny et al. | An optimized blockchain solution for the IBM z14 |
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 | ||
| CB03 | Change of inventor or designer information | ||
| CB03 | Change of inventor or designer information |
Inventor after: Yang Wentao Inventor after: Wang Hao Inventor after: Chen Chang Inventor after: Wang Qiang Inventor after: Tang Ling Inventor after: Xuan Songtao Inventor after: Gao Zhenfeng Inventor before: Gao Zhenfeng Inventor before: Wang Hao Inventor before: Chen Chang Inventor before: Wang Qiang Inventor before: Tang Ling Inventor before: Xuan Songtao Inventor before: Yang Wentao |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |