github.com/Hnampk/fabric@v2.1.1+incompatible/docs/source/developapps/endorsementpolicies.md (about)

     1  # Endorsement policies
     2  
     3  **Audience**: Architects, Application and smart contract developers
     4  
     5  Endorsement policies define the smallest set of organizations that are required
     6  to endorse a transaction in order for it to be valid. To endorse, an organization's
     7  endorsing peer needs to run the smart contract associated with the transaction
     8  and sign its outcome. When the ordering service sends the transaction to the
     9  committing peers, they will each individually check whether the endorsements in
    10  the transaction fulfill the endorsement policy. If this is not the case, the
    11  transaction is invalidated and it will have no effect on world state.
    12  
    13  Endorsement policies work at two different granularities: they can be set for an
    14  entire namespace, as well as for individual state keys. They are formulated using
    15  basic logic expressions such as `AND` and `OR`. For example, in PaperNet this
    16  could be used as follows: the endorsement policy for a paper that has been sold
    17  from MagnetoCorp to DigiBank could be set to `AND(MagnetoCorp.peer, DigiBank.peer)`,
    18  requiring any changes to this paper to be endorsed by both MagnetoCorp and DigiBank.
    19  
    20  
    21  
    22  <!--- Licensed under Creative Commons Attribution 4.0 International License
    23  https://creativecommons.org/licenses/by/4.0/ -->