Some Important HyperLedger Fabric Terms

Some important terms are tried to be explained shortly.
Hope it helps
Feel free to communicate by bulent.yucesoy@gmail.com


- Trust model for Consensus

  Peers must agree due to a consensus.
  Trust model is the agreement threshold.
  There is no only obligation like % 51.
  You can set it to any value you will trust for that agreement.
  For example, you can say " i need % 68 agreement for this transaction to be trusted" 

- Trust model for Application

  Decentralized Application is Smart Contract itself, which contains your business logic.
  There are also Endorsement Policies related with Smart Contracts.
  Endorsement Policies can be configured as you wish.
  You may request any amount of endorsement from any amount of your business partner inside the blockchain

  For example, non-deterministic smart contract problem can be detected by endorsement
  Endorsement will occur due to your Endorsement Policy.
  When you detected non-determinism problem, your application trust will increase.
  This was just a technical sample for Application Trust concept.
  But you may have more other business concerns for your app trust, you will decide and rule it inside Endorsement Policies.

- Data model

  Ledger contains all valid and invalid transactions. (containing also invalid transactions is a unique and valuable feature of Fabric.)
  But you always need the Latest World-State Results to be able to process transactions and update the ledger correctly.
  Deriving World-State Results from all transaction data inside the ledger will occur due to your DATA MODEL.
  World-State Data is always kept updated, but it (World-State) can easily be regenerated from all transactions if lost.