Notary Protocols

Notary functionality is provided in the form of plugin CorDapps. A notary protocol requires two CPBs Corda Package Bundle. A signed ZIP/JAR collection of CPKs that forms a complete application suite and contains all the code that a virtual node must operate, minus the specific network details. :

• A client, or application CPB, which is used to generate a CPI Corda Package Installer. A signed ZIP/JAR combination of a CPB and a Group Policy File that defines not only the application code that a virtual node will run, but also the details of the MGM with which to register, and the details of network PKI requirements. associated with application virtual nodes. At a minimum, this contains a CPK Corda Package. A signed ZIP/JAR library of Java code packaged to be portable with all of its dependencies and version information contained within it. that has an initiating flow Communication between participants in an application network is peer-to-peer using flows. that is automatically invoked by the Corda 5 flow framework to initiate a notarization request.
• A notary server CPB, which is used to generate a CPI associated with notary virtual nodes. At a minimum, this contains a CPK that has a responder flow to what is packaged in the client CPB.

Two notary protocols are currently available:

• Non-validating notary protocol - each virtual node checks the whole chain of transactions back to issuance.
• Contract-verifying notary protocol - the notary checks the contracts applicable to transactions.

To help you select a protocol, see the Considerations section of the Transaction Privacy Enhancements page.