merge-script b18aa6f9d4 Merge rust-bitcoin/rust-bitcoin#4229: feature: introduce MAX_BLOCK_SERIALIZED_SIZE to check limit ... e4513bf925 feat: add MAX_BLOCK_SERIALIZED_SIZE existing in core (ChrisCho-H) Pull request description: fad0d9ea2d1e807806fa141238e279fddea6ae99: add `MAX_BLOCK_SERIALIZED_SIZE` as constant, which also exists in [bitcoin-core](59ff17e5af/src/consensus/consensus.h (L13)). I originally thought it would be better to use this value for checking limit of push_bytes [here](0870cd1660/bitcoin/src/blockdata/script/push_bytes.rs (L31)), as it's the actual limit(`OP_PUSHDATA4` semantic says it could allow up to 4GB though). However, I'm not sure whether there might be need to push_bytes larger than `MAX_BLOCK_SERIALIZED_SIZE`, so just let developer use this constant to check the actual limit rather than enforcing it. ACKs for top commit: tcharding: ACK e4513bf925 apoelstra: ACK e4513bf9250799bc18a10728af184d6c86a561a4; successfully ran local tests Tree-SHA512: 44c5a4882666ad286c1e1c40b9738929e2a8ad4bb44aaf48865fc395291185ae5aae351d26ac9334671e47a11e844bd037bd251a921b6b028a116d1b442b9183		2025-03-12 14:21:32 +00:00
..
contrib	Remove rust-ordered dependency	2025-02-18 13:36:07 +11:00
embedded	Move opcodes to primitives	2024-07-09 15:26:33 +10:00
examples	Merge rust-bitcoin/rust-bitcoin#4186: Clean up Witness API	2025-03-06 18:43:27 +00:00
src	Merge rust-bitcoin/rust-bitcoin#4229: feature: introduce MAX_BLOCK_SERIALIZED_SIZE to check limit	2025-03-12 14:21:32 +00:00
tests	Pick one - MAX or MAX_MONEY	2025-03-11 05:37:39 +11:00
CHANGELOG.md	Grab missing changelog	2025-02-25 19:35:43 +11:00
Cargo.toml	Remove references to cfg(mutate) from lint allow - no longer allowed	2025-03-10 12:45:57 +08:00