user116492: I understand what the usage is for submit block, but submit header exists in the RPC API reference.  Is that a legacy function?  Or can it still be used?
Thanks

user44760: The `submitheader RPC checks the header against the candidate chain tip to check if it is valid(i.e has sufficient PoW).

Is that a legacy function? Or can it still be used?

This can still be used today. Its primary use in quickly checking if a certain header is valid without actually checking the entire block (compared to submitblock). This is computationally much cheaper than checking the entire block which involves checking the double spends, transaction signature verification, Merkle root calculations etc.
For example, you can implement the chain sync logic using headers-first outside bitcoind using this RPC. And according to the submitheaders PR, it was required for implementation of BetterHash protocol.

116492: <p>I understand what the usage is for submit block, but submit header exists in the RPC API reference.  Is that a legacy function?  Or can it still be used?</p>
<p>Thanks</p>
 44760: <p>The `submitheader RPC checks the header against the candidate chain tip to check if it is valid(i.e has sufficient PoW).</p>
<blockquote>
<p>Is that a legacy function? Or can it still be used?</p>
</blockquote>
<p>This can still be used today. Its primary use in quickly checking if a certain header is valid without actually checking the entire block (compared to <code>submitblock</code>). This is computationally much cheaper than checking the entire block which involves checking the double spends, transaction signature verification, Merkle root calculations etc.</p>
<p>For example, you can implement the chain sync logic using headers-first outside <code>bitcoind</code> using this RPC. And according to the <a href="https://github.com/bitcoin/bitcoin/pull/13399" rel="nofollow noreferrer">submitheaders PR</a>, it was required for implementation of BetterHash protocol.</p>
