From e14e47a5ba70e185e534a025d3c041b524fbe721 Mon Sep 17 00:00:00 2001 From: Anatoly Piskunov Date: Fri, 20 Nov 2026 09:35:35 +0100 Subject: [PATCH 1/3] release: bump revision to 4.4.2 for the snapshot export fix Release revision moves +1 per release (owner rule 01.11.2026). The minor is the hardfork number and never changes here; hardfork_version() masks the low 16 bits, so CHAIN_HARDFORK_VERSION stays 4.4.0 and no auto-vote for a fork is triggered. --- libraries/protocol/include/graphene/protocol/config.hpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libraries/protocol/include/graphene/protocol/config.hpp b/libraries/protocol/include/graphene/protocol/config.hpp index e34c3d0704..34e33b833d 100644 --- a/libraries/protocol/include/graphene/protocol/config.hpp +++ b/libraries/protocol/include/graphene/protocol/config.hpp @@ -8,7 +8,7 @@ // not the revision; 4.3.0 here must stay byte-equal to CHAIN_HARDFORK_17_VERSION in // hardfork.d/17.hf, which database_hardfork.cpp asserts. See hardfork.d/17.hf for the rule and // the activation-time warning. (4.2.0 was HF16: BFT finality, 1 s slots, DAO cap, fee freeze.) -#define CHAIN_VERSION (version(4, 4, 1)) +#define CHAIN_VERSION (version(4, 4, 2)) #define CHAIN_HARDFORK_VERSION (hardfork_version(CHAIN_VERSION)) #define CHAIN_NAME "VIZ" From f1cfa26d156002d4d864b4356dd08755baaeb491 Mon Sep 17 00:00:00 2001 From: Anatoly Piskunov Date: Fri, 20 Nov 2026 09:36:13 +0100 Subject: [PATCH 2/3] tests: follow the 4.4.2 bump in the version mutation anchor The emergency-exit wiring suite mutates the literal CHAIN_VERSION line to prove that some test notices a node that does not advertise HF17. With the release revision bumped, the anchor no longer matched and the mutation would have reported 'not applied' instead of exercising the check. --- tests/chain/test_emergency_exit_wiring.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/chain/test_emergency_exit_wiring.py b/tests/chain/test_emergency_exit_wiring.py index d1fd7177be..e0515fb185 100644 --- a/tests/chain/test_emergency_exit_wiring.py +++ b/tests/chain/test_emergency_exit_wiring.py @@ -358,7 +358,7 @@ def _swap_exit_after_override(text): '#define CHAIN_SCHEMA_VERSION uint32_t(15)'), ], 'chain-version-does-not-advertise-hf17': [ - ('define CHAIN_VERSION (version(4, 4, 1))', + ('define CHAIN_VERSION (version(4, 4, 2))', 'define CHAIN_VERSION (version(4, 2, 0))'), ], 'num-hardforks-not-bumped': [ From d48c50586427eb085cc9ab0c6cc0477bf73bf932 Mon Sep 17 00:00:00 2001 From: Anatoly Piskunov Date: Fri, 20 Nov 2026 09:45:42 +0100 Subject: [PATCH 3/3] release: the testnet config carries the same revision Mainnet config was bumped to 4.4.2, the testnet one stayed at 4.4.1 - two configs of the same release disagreeing about the release counter. Caught by CI: the emergency-exit suite mutates the CHAIN_VERSION line in config_testnet.hpp, and with the anchor updated to 4.4.2 the mutation no longer found its target ('anchor not found -- mutation did not land') - which is exactly what that guard exists for. --- libraries/protocol/include/graphene/protocol/config_testnet.hpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libraries/protocol/include/graphene/protocol/config_testnet.hpp b/libraries/protocol/include/graphene/protocol/config_testnet.hpp index 5c153cdb40..6e1b822e41 100644 --- a/libraries/protocol/include/graphene/protocol/config_testnet.hpp +++ b/libraries/protocol/include/graphene/protocol/config_testnet.hpp @@ -9,7 +9,7 @@ // which database_hardfork.cpp asserts. config.hpp carries the same value for the production // config — the two builds differ in chain identity and fork TIMES, not in which forks are // registered. (4.2.0 was HF16.) -#define CHAIN_VERSION (version(4, 4, 1)) +#define CHAIN_VERSION (version(4, 4, 2)) #define CHAIN_HARDFORK_VERSION (hardfork_version(CHAIN_VERSION)) #define CHAIN_NAME "VIZTEST"