From ea50ff274d69508ca95823d6fc68719e0bd25cd4 Mon Sep 17 00:00:00 2001 From: agessaman Date: Sun, 21 Jun 2026 10:52:31 -0700 Subject: [PATCH] feat(config): update public key prefix length configuration - Added a new configuration option `prefix_bytes` to specify the length of public key prefixes for repeaters, enhancing mesh graph key management. - Updated the example configuration to reflect the new default value of 3 bytes, replacing the previous default of 1 byte. - Improved documentation within the config file to clarify the purpose and usage of the `prefix_bytes` setting. --- config.ini.example | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/config.ini.example b/config.ini.example index 4ea878a..4d067b7 100644 --- a/config.ini.example +++ b/config.ini.example @@ -209,6 +209,13 @@ service_restart_backoff_seconds = 300 # Max seconds to wait for a channel message send before timing out (default: 30) send_timeout_seconds = 30 +# Set a custom prefix length for the public keys to identify repeaters +# 1 = 2 hex chars (e.g. 7E), 2 = 4 hex chars (e.g. 7E42). Also used as the mesh +# graph key length; if the mesh often uses 2-byte paths, set to 2 to avoid +# conflating distinct links (see Path Command / path-command-config.md). +# Does not control radio advert path-hash mode (firmware path.hash.mode). +prefix_bytes = 3 + [Admin] # Local admin API (binds to 127.0.0.1) enabled = false @@ -244,12 +251,6 @@ respond_to_dms = true # Default: 64 - to not change behavior on existing installations max_response_hops = 7 -# Set a custom prefix length for the public keys to identify repeaters -# 1 = 2 hex chars (e.g. 7E), 2 = 4 hex chars (e.g. 7E42). Also used as the mesh -# graph key length; if the mesh often uses 2-byte paths, set to 2 to avoid -# conflating distinct links (see Path Command / path-command-config.md). -prefix_bytes = 1 - # List of region scopes (comma-separated) that the bot will reply to when messages arrive on those scopes. # Replies mirror scope via RF correlation (TC_FLOOD / GRP_TXT); stale ADVERT/other packets are not used for scope. # Responses will be sent with the same scope hash when correlation succeeds.