merge-script dbc8928069
Merge bitcoin/bitcoin#33993: init: point out -stopatheight may be imprecise
ff06e2468a5d3eeebeffe781904c34c9d1b44385 init: point out -stopatheight may be imprecise (brunoerg)

Pull request description:

  `-stopatheight` is used to stop running bitcoind after reaching a given height. However, this feature is imprecise since some blocks can still be processed during the shutdown.

  There are some previous discussions around it in https://github.com/bitcoin/bitcoin/pull/13713, https://github.com/bitcoin/bitcoin/pull/13490 and https://github.com/bitcoin/bitcoin/issues/13477. However, I'm not sure if it will get fixed since it's undesirable to burden the validation code further with this and we can bypass this behavior by using `invalidateblock` to wind back. Anyway, since at this moment its behavior is imprecise I think worth mentioning it in documentation.

ACKs for top commit:
  rkrux:
    re-ACK ff06e2468a5d3eeebeffe781904c34c9d1b44385
  stickies-v:
    ACK ff06e2468a5d3eeebeffe781904c34c9d1b44385
  pablomartin4btc:
    ACK ff06e2468a5d3eeebeffe781904c34c9d1b44385
  jaonoctus:
    re-ACK ff06e2468a5d3eeebeffe781904c34c9d1b44385

Tree-SHA512: 222d5e89021d5f9a7ce0edca44c4ce20b13f71832413dccea78ad40a01f2a615a061f8cf446d7290ed911023922adbc6fa22f0c88cff306dcd8b4ae14194e9b8
2025-12-09 07:39:46 -08:00
..
2025-12-06 13:06:21 +01:00
2025-12-04 19:52:49 +01:00
2025-12-06 13:06:21 +01:00
2025-10-28 15:33:57 +00:00
2025-11-27 14:33:57 +01:00
2025-05-19 16:40:33 +01:00
2025-09-03 11:23:30 +01:00
2025-05-19 16:40:33 +01:00
2025-09-30 11:06:43 -07:00
2025-12-04 19:53:06 +01:00
2025-09-30 11:06:43 -07:00
2025-11-14 01:17:38 +02:00
2025-11-14 01:17:38 +02:00
2025-11-27 14:33:57 +01:00
2025-11-27 14:33:57 +01:00
2025-11-30 10:57:48 -05:00
2025-04-09 15:59:59 +01:00