user101040: I've seen the term sigop in many places frequently. I've tried to figure out what does it mean by searching, and found that it's abbreviation of signature operation. But it's still not clear to me the meaning. I guess every opcode of scriptSig is considered to be a sigop. Am I right?
I would appreciate any explanation.
Edit:
I think this question is completely different than this. My question is clearly about what is the sigop, while the other question is about calculation of sigops.

user208: A sigop is script opcode which performs a signature check. That includes OP_CHECKSIG, OP_CHECKSIGVERIFY, OP_CHECKMULTISIG, and OP_CHECKMULTISIGVERIFY.
This concept matters because of a consensus rule in Bitcoin which limits the number of sigops per block. How they are counted depends on the context:

In the scriptPubKey of outputs, and in scriptSig of inputs (the latter happens ~never, but if it did, it would be counted):

OP_CHECKSIG and OP_CHECKSIGVERIFY count as 4
OP_CHECKMULTISIG and OP_CHECKMULTISIGVERIFY count as 80


In P2SH redeemscripts:

OP_CHECKSIG and OP_CHECKSIGVERIFY count as 4
OP_CHECKMULTISIG and OP_CHECKMULTISIGVERIFY count as 4n when preceded by OP_n, and as 80 otherwise.


In P2WSH witness scripts:

OP_CHECKSIG and OP_CHECKSIGVERIFY count as 1
OP_CHECKMULTISIG and OP_CHECKMULTISIGVERIFY count as n when preceded by OP_n, and as 20 otherwise.


In P2TR taproot scripts:

Sigops are not counted.



A valid block cannot have more than 80000 sigops (so roughly 1 per 50 bytes of block data), as counted by the rules above. Note that this is checked before actually executing any scripts. So it doesn't require these opcode to actually be executed (e.g. they also count sigops that are surrounded by OP_IF ... OP_ENDIF in unexecuted branches, or in coinbase scriptSigs which are never executed).
In taproot, a different mechanism is used. Instead of having a global per-block limit, there is a per-transaction-input limit, proportional to the size of that input. Also only actually executed checks for claimed-to-be-valid signatures are counted.

101040: <p>I've seen the term sigop in many places frequently. I've tried to figure out what does it mean by searching, and found that it's abbreviation of signature operation. But it's still not clear to me the meaning. I guess every opcode of scriptSig is considered to be a sigop. Am I right?</p>
<p>I would appreciate any explanation.</p>
<h2>Edit:</h2>
<p>I think this question is completely different than <a href="https://bitcoin.stackexchange.com/questions/67760/how-are-sigops-calculated">this</a>. My question is clearly about what is the sigop, while the other question is about calculation of sigops.</p>
 208: <p>A sigop is script opcode which performs a signature check. That includes <code>OP_CHECKSIG</code>, <code>OP_CHECKSIGVERIFY</code>, <code>OP_CHECKMULTISIG</code>, and <code>OP_CHECKMULTISIGVERIFY</code>.</p>
<p>This concept matters because of a consensus rule in Bitcoin which limits the number of sigops per block. How they are counted depends on the context:</p>
<ul>
<li>In the <code>scriptPubKey</code> of outputs, and in <code>scriptSig</code> of inputs (the latter happens ~never, but if it did, it would be counted):
<ul>
<li><code>OP_CHECKSIG</code> and <code>OP_CHECKSIGVERIFY</code> count as 4</li>
<li><code>OP_CHECKMULTISIG</code> and <code>OP_CHECKMULTISIGVERIFY</code> count as 80</li>
</ul>
</li>
<li>In P2SH redeemscripts:
<ul>
<li><code>OP_CHECKSIG</code> and <code>OP_CHECKSIGVERIFY</code> count as 4</li>
<li><code>OP_CHECKMULTISIG</code> and <code>OP_CHECKMULTISIGVERIFY</code> count as <em>4n</em> when preceded by <code>OP_n</code>, and as 80 otherwise.</li>
</ul>
</li>
<li>In P2WSH witness scripts:
<ul>
<li><code>OP_CHECKSIG</code> and <code>OP_CHECKSIGVERIFY</code> count as 1</li>
<li><code>OP_CHECKMULTISIG</code> and <code>OP_CHECKMULTISIGVERIFY</code> count as <em>n</em> when preceded by <code>OP_n</code>, and as 20 otherwise.</li>
</ul>
</li>
<li>In P2TR taproot scripts:
<ul>
<li>Sigops are not counted.</li>
</ul>
</li>
</ul>
<p>A valid block cannot have more than 80000 sigops (so roughly 1 per 50 bytes of block data), as counted by the rules above. Note that this is checked <em>before</em> actually executing any scripts. So it doesn't require these opcode to actually be executed (e.g. they also count sigops that are surrounded by <code>OP_IF ... OP_ENDIF</code> in unexecuted branches, or in coinbase <code>scriptSig</code>s which are never executed).</p>
<p>In taproot, a different mechanism is used. Instead of having a global per-block limit, there is a per-transaction-input limit, proportional to the size of that input. Also only actually executed checks for claimed-to-be-valid signatures are counted.</p>
