From 3f1dceaa5eb80d6977558cf1f58c4835aa7e03c0 Mon Sep 17 00:00:00 2001 From: Ricardo Date: Wed, 9 Sep 2026 14:35:33 +0800 Subject: [PATCH 1/2] Update README.md the readme does not call out the node_gossip_priority_config impacts fast block latency. --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index dd24fee..86cb8ea 100644 --- a/README.md +++ b/README.md @@ -553,6 +553,7 @@ The validator community also runs several independent root peers for non-validat Latency sensitive users can set `split_client_blocks: true` in `~/override_gossip_config.json` to stream uncommitted mempool transactions to `~/hl/data/mempool_txs/{date}`. These transactions are eagerly broadcasted by nodes before they are committed, so the file does not contain responses. To record this data, all peers between the node and the validating network must have `split_client_blocks` enabled. On a future network upgrade, this setting may be enabled for all nodes without the configuration option. By default, mempool transactions are streamed in random order to peers. Nodes can set `{"enabled": true}` in `~/hl/file_mod_time_tracker/node_gossip_priority_config.json` to respect the onchain gossip auction priority ordering. +Enabling this adds ~50ms latency. ## Troubleshooting From 844feeb4a86dae94deb520d4f190ea489199b482 Mon Sep 17 00:00:00 2001 From: Ricardo Date: Wed, 9 Sep 2026 15:11:10 +0800 Subject: [PATCH 2/2] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 86cb8ea..07fe9ef 100644 --- a/README.md +++ b/README.md @@ -553,7 +553,7 @@ The validator community also runs several independent root peers for non-validat Latency sensitive users can set `split_client_blocks: true` in `~/override_gossip_config.json` to stream uncommitted mempool transactions to `~/hl/data/mempool_txs/{date}`. These transactions are eagerly broadcasted by nodes before they are committed, so the file does not contain responses. To record this data, all peers between the node and the validating network must have `split_client_blocks` enabled. On a future network upgrade, this setting may be enabled for all nodes without the configuration option. By default, mempool transactions are streamed in random order to peers. Nodes can set `{"enabled": true}` in `~/hl/file_mod_time_tracker/node_gossip_priority_config.json` to respect the onchain gossip auction priority ordering. -Enabling this adds ~50ms latency. +Enabling this adds ~50ms latency for downstream peers. ## Troubleshooting