[ad_1]
I’ve been testing numerous 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 usually are not documented.
Most notable ones are “invalidateblock” and “reconsiderblock”. (What these instructions do appears fairly apparent: making a block invalid by pressure 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 perform in src/validation.cpp performs a task within the “invalidateblock” course of. It appears some previous transactions is likely to be marked as invalid if the script verification flags are completely different between the block that’s being invalidated, and the latest block. Is that this a attainable state of affairs and what occurs in such events?
[ad_2]
