Shulou(Shulou.com)06/01 Report--

This article mainly shows you "what the Fabric1.0 transaction process is like", the content is easy to understand, clear, hope to help you solve your doubts, the following let the editor lead you to study and learn "how the Fabric1.0 transaction process is like" this article.

Fabric 1.0 transaction proc

All transactions in fabric are performed through chaincode

1. The application client invokes the Certificate Services (CA) service through SDK, registers and registers, and obtains the identity certificate.

two。 The application client creates a transaction proposal (Proposal) through SDK, which sends information such as contract identification, contract method and parameter information, and client signature to the Endorser node with the contract identification, contract method and parameter information to be invoked for this transaction.

3. After receiving the transaction proposal (Proposal), the endorsement (Endorser) node starts the verification. The verification content is as follows:

The transaction plan is intact.

The plan has not been submitted before (to prevent replay attacks)

The signature carried is legal.

Whether the transaction initiator meets the block chain write policy, that is, ACL permission check

After meeting the above requirements, the endorsement node takes the "transaction plan" as the input parameter and calls the function in chaincode. Chaincode calculates a "transaction result" based on the current account status, which includes the return value, read and write set. At this point, the blockchain ledger is not updated.' The result of the transaction is returned with a yes / no endorsement after being signed, which is called a 'preplan reply'.

4. After receiving the information returned by the Endorser node, the application client determines whether the result of the proposal is consistent, and whether it receives enough results returned by the endorsement node (executed with reference to the specified endorsement policy). If there are not enough endorsements, the process is aborted and the transaction is abandoned. Otherwise, the transaction proposal, the simulated transaction result, and the endorsement information are packaged into a transaction and signed to the Orderer node (a sorting service).

The 5.Orderer node sorts the transaction information from the client (SDK) by consensus, sorts the "transaction message" by time according to the channel, packages the transaction into blocks according to the channel, and sends it to the Committer node.

6. After the Committer node receives the block, it verifies each transaction in the block, checks whether the input and output that the transaction depends on are in line with the current status of the block chain, verifies whether the endorsement policy is satisfied, and appends the block to the local block chain after verification, updates the account book, and modifies the world status. The specific process is as follows:

Run validation logic (VSCC check endorsement policy)

Indicate which transactions are valid and invalid in the block.

Add blocks to the chaining of blocks on memory or file system

Writes valid transactions within the block to the status database.

Issue an Event message so that the client knows which transactions are valid or invalid through SDK snooping.

The above is all the content of this article "what is the trading process of Fabric1.0?" thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.