are
used in this flow. The new flow includes two steps where policies are specified:
when chaincode is <strong>approved</strong> by organization members, and when it is <strong>committed</strong>
to the channel.</p>
<p>The <cite>Application</cite> section of  the <cite>configtx.yaml</cite> file includes the default
chaincode lifecycle endorsement policy. In a production environment you would
customize this definition for your own use case.</p>
</div>
<div class="section" id="id18">
<h1><a href="#id14"><span