json rpc – What’s the function of “Invalidateblock” RPC command and are there any doable transaction validation points with regard to this?

I’ve been testing varied RPC instructions on bitcoin.

The “RPC API Reference” web page nicely demonstrates nearly the entire instructions.

However by studying the supply code (bitcoin v27.0), I observed that a number of the instructions will not be documented.

Most notable ones are “invalidateblock” and “reconsiderblock”. (What these instructions do appears fairly apparent: making a block invalid by drive and verifying a block once more together with all of the transactions in it.)

I examined these two instructions on my bitcoin node and the habits was as I anticipated.

Q1 => Why do these instructions even exist?

Q2 => Additionally, I’ve observed that MemPoolAccept::ConsensusScriptChecks operate in src/validation.cpp performs a task within the “invalidateblock” course of. It appears some previous transactions may be marked as invalid if the script verification flags are totally different between the block that’s being invalidated, and the latest block. Is that this a doable state of affairs and what occurs in such events?

I’ve been testing varied RPC instructions on bitcoin.

The “RPC API Reference” web page nicely demonstrates nearly the entire instructions.

However by studying the supply code (bitcoin v27.0), I observed that a number of the instructions will not be documented.

Most notable ones are “invalidateblock” and “reconsiderblock”. (What these instructions do appears fairly apparent: making a block invalid by drive and verifying a block once more together with all of the transactions in it.)

I examined these two instructions on my bitcoin node and the habits was as I anticipated.

Q1 => Why do these instructions even exist?

Q2 => Additionally, I’ve observed that MemPoolAccept::ConsensusScriptChecks operate in src/validation.cpp performs a task within the “invalidateblock” course of. It appears some previous transactions may be marked as invalid if the script verification flags are totally different between the block that’s being invalidated, and the latest block. Is that this a doable state of affairs and what occurs in such events?