Validating Transactions In the Hyperledger environment, the Validated or VLedger represents the present sum of all successfully validated transactions. Transactions which are not successfully validated or endorsed will be exempt from this list, making it a useful tool for efficiency among peer nodes.

The following graphic shows the process for validating a new transaction. Once the transaction is validated, it can be added to the Validated Ledger.

ILLUSTRATION OF THE VALIDATION PROCESS // HYPERLEDGER DOCS

A: PeerLedger; B: Validated ledger; C: Block; D: Submitting client; E: PeerLedger; F: Validated Ledger (VL); G: Genesis block; H: Peer; I: Block forming; J: Verify endorsement, readset, If OK then apply writeset, Else Invalid transaction (blob); K: Ordering service; L: Orderers.

Because Hyperledger systems exist in a closed environment, most nodes do not need to participate in the full consensus process. As a result, most nodes will simply maintain their copy of the vLedger and trust that others are ensuring its validity. This is also convenient for larger networks since it ensures that the network has a single common state at any time, rather than the possibility of local consensus emerging.