TheCharlatan e80e4c6ff9 validation: Remove RECENT_CONSENSUS_CHANGE validation result ... The *_RECENT_CONSENSUS_CHANGE variants in the validation result enumerations were always unused. They seem to have been kept around speculatively for a soft fork after segwit, however they were never used for taproot either. This points at them not having a clear purpose. Based on the original pull requests' comments their usage was never entirely clear: https://github.com/bitcoin/bitcoin/pull/11639#issuecomment-370234133 https://github.com/bitcoin/bitcoin/pull/15141#discussion_r271039747 Since they are part of the validation interface and need to exposed by the kernel library keeping them around may also be confusing to future users of the library.		2024-11-11 10:24:38 +01:00
..
amount.h
consensus.h	miner: adjust clock to timewarp rule	2024-08-20 18:51:37 +02:00
merkle.cpp	Move BlockMerkleBranch back to merkle.{h,cpp}	2024-09-26 09:48:31 +02:00
merkle.h	Move BlockMerkleBranch back to merkle.{h,cpp}	2024-09-26 09:48:31 +02:00
params.h	doc: fix a few simple codespell warnings	2024-08-28 18:42:10 +02:00
tx_check.cpp	Use ParamsWrapper for witness serialization	2023-11-14 08:45:30 +10:00
tx_check.h
tx_verify.cpp	refactor: Rename CTransaction::nVersion to version	2024-06-07 13:55:23 -04:00
tx_verify.h	doc: fix: prevHeights entries are set to 0, not removed	2022-11-29 17:58:36 +00:00
validation.h	validation: Remove RECENT_CONSENSUS_CHANGE validation result	2024-11-11 10:24:38 +01:00