[execution] gate hot-state via on-chain features

The hot-state rollout switches that control write-set format, block
epilogue payload format, and `TransactionInfo` format all affect bytes
committed to the ledger, so they must agree across all validators. They
previously lived in the local `HotStateConfig`, where they could drift
per-node.

Move them to two new permanent feature flags:

- `HOTNESS_IN_EPILOGUE`: persists per-block hot-state promotions in
  `BlockEpiloguePayload::V2`, and emits V1 write sets that encode the
  hot-state changes inline.
- `TRANSACTION_INFO_V1`: assembles `TransactionInfoV1`, which carries
  the hot state root hash into the ledger accumulator.

`OnChainExecutionConfig::block_executor_onchain_config()` now takes
`&Features` and threads the booleans into `BlockExecutorConfigFromOnchain`.
Consensus reads `Features` from the reconfiguration payload and propagates
it through the epoch manager, execution client, and consensus observer.
The block executor and `do_get_execution_output` consume the on-chain
values, and the `TransactionInfoV1` flag rides along on `ExecutionOutput`
into ledger update.

The chunk-apply path still derives the transaction info format from each
chunk's actual `TransactionInfo` variants and so does not depend on the
on-chain flag.

Author: wqfish

aptos-move/aptos-release-builder/src/components/feature_flags.rs

@@ -166,6 +166,8 @@ pub enum FeatureFlag {
     VersionedTransactionValidation,
     StorageSlotNatives,
     AllowFriendEntryVisibilityDowngrade,
+    HotnessInEpilogue,
+    TransactionInfoV1,
 }
 
 fn generate_features_blob(writer: &CodeWriter, data: &[u64]) {
@@ -435,6 +437,8 @@ impl From<FeatureFlag> for AptosFeatureFlag {
             FeatureFlag::AllowFriendEntryVisibilityDowngrade => {
                 AptosFeatureFlag::ALLOW_FRIEND_ENTRY_VISIBILITY_DOWNGRADE
             },
+            FeatureFlag::HotnessInEpilogue => AptosFeatureFlag::HOTNESS_IN_EPILOGUE,
+            FeatureFlag::TransactionInfoV1 => AptosFeatureFlag::TRANSACTION_INFO_V1,
         }
     }
 }
@@ -631,6 +635,8 @@ impl From<AptosFeatureFlag> for FeatureFlag {
             AptosFeatureFlag::ALLOW_FRIEND_ENTRY_VISIBILITY_DOWNGRADE => {
                 FeatureFlag::AllowFriendEntryVisibilityDowngrade
             },
+            AptosFeatureFlag::HOTNESS_IN_EPILOGUE => FeatureFlag::HotnessInEpilogue,
+            AptosFeatureFlag::TRANSACTION_INFO_V1 => FeatureFlag::TransactionInfoV1,
         }
     }
 }

aptos-move/aptos-vm/src/aptos_vm.rs

@@ -164,7 +164,6 @@ static NUM_PROOF_READING_THREADS: OnceCell<usize> = OnceCell::new();
 static DISCARD_FAILED_BLOCKS: OnceCell<bool> = OnceCell::new();
 static PROCESSED_TRANSACTIONS_DETAILED_COUNTERS: OnceCell<bool> = OnceCell::new();
 static ENABLE_PRE_WRITE: OnceCell<bool> = OnceCell::new();
-static PERSIST_HOTNESS_IN_EPILOGUE: OnceCell<bool> = OnceCell::new();
 
 macro_rules! deprecated_module_bundle {
     () => {
@@ -514,19 +513,6 @@ impl AptosVM {
         }
     }
 
-    /// Sets persist_hotness_in_epilogue flag when invoked the first time.
-    pub fn set_persist_hotness_in_epilogue_once(persist: bool) {
-        let _ = PERSIST_HOTNESS_IN_EPILOGUE.set(persist);
-    }
-
-    /// Get the persist_hotness_in_epilogue flag if already set, otherwise return default (false)
-    pub fn get_persist_hotness_in_epilogue() -> bool {
-        match PERSIST_HOTNESS_IN_EPILOGUE.get() {
-            Some(persist) => *persist,
-            None => false,
-        }
-    }
-
     pub fn set_num_shards_once(mut num_shards: usize) {
         num_shards = max(num_shards, 1);
         // Only the first call succeeds, due to OnceCell semantics.
@@ -3425,7 +3411,6 @@ impl VMBlockExecutor for AptosVMBlockExecutor {
                 discard_failed_blocks: AptosVM::get_discard_failed_blocks(),
                 module_cache_config: BlockExecutorModuleCacheLocalConfig::default(),
                 enable_pre_write: AptosVM::get_enable_pre_write(),
-                persist_hotness_in_epilogue: AptosVM::get_persist_hotness_in_epilogue(),
             },
             onchain: onchain_config,
         };

aptos-move/aptos-vm/src/sharded_block_executor/local_executor_shard.rs

@@ -195,7 +195,7 @@ impl<S: StateView + Sync + Send + 'static> ExecutorClient<S> for LocalExecutorCl
                     state_view.clone(),
                     sub_blocks_for_shard,
                     concurrency_level_per_shard,
-                    onchain_config.clone(),
+                    onchain_config,
                 ))
                 .unwrap();
         }

aptos-move/block-executor/src/executor.rs

@@ -2178,7 +2178,7 @@ where
             }
         }
         let fee_distribution = FeeDistribution::new(amount);
-        if self.config.local.persist_hotness_in_epilogue {
+        if self.config.onchain.hotness_in_epilogue() {
             let (inner, to_make_hot) = block_end_info.into_parts();
             Ok(T::block_epilogue_v2(
                 block_id,

aptos-move/e2e-tests/src/executor.rs

@@ -1009,9 +1009,8 @@ impl<O: OutputLogger> FakeExecutorImpl<O> {
                 discard_failed_blocks: false,
                 module_cache_config: BlockExecutorModuleCacheLocalConfig::default(),
                 enable_pre_write: true,
-                persist_hotness_in_epilogue: false,
             },
-            onchain: onchain_config.clone(),
+            onchain: onchain_config,
         };
 
         #[cfg(fuzzing)]

aptos-move/framework/cached-packages/src/head.mrb

@@ -876,6 +876,19 @@ module std::features {
         is_enabled(MULTISIG_TIMELOCK)
     }
 
+    /// When enabled, per-block hot-state promotions are persisted through the block
+    /// epilogue: the promotion set is embedded into the block epilogue transaction
+    /// payload (`BlockEpiloguePayload::V2`), and every transaction output in the block
+    /// uses the V1 write-set format, which encodes hot-state changes in its serialized
+    /// writes.
+    /// Lifetime: permanent
+    const HOTNESS_IN_EPILOGUE: u64 = 116;
+
+    /// When enabled, execution assembles `TransactionInfoV1`, which carries the hot
+    /// state root hash, so it is committed to the ledger accumulator.
+    /// Lifetime: permanent
+    const TRANSACTION_INFO_V1: u64 = 117;
+
     // ============================================================================================
     // Feature Flag Implementation
 

aptos-move/framework/move-stdlib/sources/configs/features.move

@@ -28,9 +28,8 @@ pub(crate) fn execute_workload(
             discard_failed_blocks: false,
             module_cache_config: BlockExecutorModuleCacheLocalConfig::default(),
             enable_pre_write: true,
-            persist_hotness_in_epilogue: false,
         },
-        // For replay, there is no block limit.
+        // For replay, there is no block limit. TODO(HotState): may need to update this.
         onchain: BlockExecutorConfigFromOnchain::on_but_large_for_test(),
     };
 

aptos-move/replay-benchmark/src/execution.rs

@@ -76,12 +76,6 @@ pub fn set_aptos_vm_configurations(node_config: &NodeConfig) {
     );
     AptosVM::set_blockstm_v2_enabled_once(node_config.execution.blockstm_v2_enabled);
     AptosVM::set_enable_pre_write_once(node_config.execution.enable_pre_write);
-    AptosVM::set_persist_hotness_in_epilogue_once(
-        node_config
-            .storage
-            .hot_state_config
-            .persist_hotness_in_epilogue,
-    );
 
     if node_config
         .execution

aptos-node/src/utils.rs

@@ -255,13 +255,6 @@ pub struct HotStateConfig {
     /// Whether we compute root hashes for hot state in executor and commit the resulting JMT to
     /// db.
     pub compute_root_hash: bool,
-    /// Whether execution should construct write sets using the V1 format and include hotness
-    /// changes in serialized format.
-    pub use_write_set_v1: bool,
-    /// Whether to embed the per-block hot-state promotions into the epilogue transactions.
-    pub persist_hotness_in_epilogue: bool,
-    /// Whether execution should assemble `TransactionInfoV1` which carries hot state root hash.
-    pub use_transaction_info_v1: bool,
 }
 
 impl Default for HotStateConfig {
@@ -271,9 +264,6 @@ impl Default for HotStateConfig {
             refresh_interval_versions: 100_000,
             delete_on_restart: true,
             compute_root_hash: true,
-            use_write_set_v1: false,
-            persist_hotness_in_epilogue: false,
-            use_transaction_info_v1: false,
         }
     }
 }