1. The client side creates a transaction proposal (chaincode function and parameters) and sends it to the Endorse Peer (endorsing node).
2. The Endorse Peer node executes the chaincode, and generates a read and write operation set based on the read and written keys.
3. The Endorse Peer node returns the proposal result (including the read and write operation set) to the client.
4. The client side submits the transaction to the Order service, and the transaction content includes the read and write operation set from the proposal result.
5. The Order service encapsulates the sorted transactions into blocks.
6. The block will be sent to the Commit Peer node.
7. The Commit Peer node performs the following operations:
(1) Run the verification logic (VSCC checks the endorsement policy, MVCC checks that the version of the read operation has not been modified in the database since the simulated transaction.
(2) Indicates which transactions are valid in the block and invalid.
(3) Add the block to the blockchain on the memory or file system, and write the valid transactions in the block into the state database.
(4) Send the Event message, so that the client can monitor which transactions through the SDK is valid or invalid.
The following figure is a schematic diagram of the complete life cycle:
The following figure is a schematic diagram of the complete transaction flow: 