<p>The only peers to execute chaincode are the endorsing peers, rest only validates during the commit time whenever the transaction satisfies endorsement policy. And in order to be peer to be able to endorse the transaction proposal someone (admin) has to install the chaincode on it.</p>

<p>You can find more details in <a href="http://hyperledger-fabric.readthedocs.io/en/release-1.0/arch-deep-dive.html" rel="nofollow noreferrer">documentation</a> or there is a nice <a href="https://medium.com/kokster/hyperledger-fabric-endorsing-transactions-3c1b7251a709" rel="nofollow noreferrer">blog post</a> which also describes it pretty well.</p>

<p>Basically flow from high level perspective works as following:</p>

<ol>
<li>Client submits transaction proposal to endorsing peers</li>
<li>Endorsing peers invokes chaincodes</li>
<li>Endorsing peers signs over the execution results</li>
<li>Client gathers all results and check consistency</li>
<li>Client submits transaction to the ordering service</li>
<li>Ordering service cuts new block with several transactions</li>
<li>Peer gets new block via dissemination layer</li>
<li>Peer validates each transaction</li>
<li>Eventually block is committed where all valid transaction changes the sate according to the simulation results from #2.</li>
</ol>

<p>There some more int depth detail published in the <a href="https://arxiv.org/pdf/1801.10228.pdf" rel="nofollow noreferrer">official Fabric paper</a>.</p>
Did all peers execute chaincode?
<p>I have a question.
I want to know whether all nodes execute the chain code or only endorsement nodes execute the chain code?</p>