From 88f0470c91eed6d4eedc0606874114b81102d750 Mon Sep 17 00:00:00 2001 From: qwahzi Date: Sat, 31 Aug 2024 08:29:19 -0500 Subject: [PATCH] Update release-v27-0.md Added more detail to the fair queueing note, and added a note for the new prioritization bucket --- docs/releases/release-v27-0.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/releases/release-v27-0.md b/docs/releases/release-v27-0.md index 70c452903..76c8b6c52 100644 --- a/docs/releases/release-v27-0.md +++ b/docs/releases/release-v27-0.md @@ -26,7 +26,7 @@ V27 RPC changes are minor and non-breaking. ## Major updates ### Fair Queueing Enhancements -Designed by Piotr Wójcik, the fair queue has been integrated into the nano node, ensuring equal processing time for each network peer. The fair queue orders requests in a fair, round-robin fashion which is needed by several components in the node, including block, network message, bootstrap request, and vote request processing. +Designed by Piotr Wójcik, the fair queue has been integrated into the nano node, ensuring equal processing time for each network peer. The fair queue orders requests in a fair, round-robin fashion, which is needed by several components in the node, including block, network message, bootstrap request, and vote request processing. These fair queues help ensure that higher priority transactions are seen and prioritized more consistently, even during network congestion. ### Network Handling Rewrite Significant portions of the networking stack have been rewritten and simplified. Legacy code that handled half-duplex TCP channels has been removed and all TCP connections now operate full-duplex. Asynchronous callback-style code has been replaced with coroutines in several places simplifying code flow. @@ -35,7 +35,10 @@ Significant portions of the networking stack have been rewritten and simplified. This suite of features optimises transaction processing, guards against spam and denial-of-service attacks, and ensures equitable resource distribution. ### Up to 255 votes per message -V27 allows voting messages to contain up to 255 votes per message, an increase from the previous limit of 12. This enhancement reduces network congestion and voting traffic, improving consensus efficiency and robustness. Note that this change de-peers nodes older than V26.0. +V27 allows voting messages to contain up to 255 votes per message, an increase from the previous limit of 12. This enhancement reduces voting traffic and network congestion, improving consensus efficiency and robustness. Note that this change de-peers nodes older than V26.0. + +### Additional prioritization bucket +An additional prioritization bucket for amounts between Ӿ0.000001 and Ӿ0.0003 has been added, for a total of 63. More precisely, amounts above Ӿ0.0000006 (2^79 raw) and below Ӿ0.000309 (2^88 raw) will fall in this new bucket. All existing buckets remain unchanged to minimize the impact of bucket reallocation. Many Nano faucets send amounts in this range to new users trying out nano for the first time, and many wallets use Ӿ0.000001 as the minimum amount for automatic receives. More details on buckets and bucket ranges [here](../protocol-design/spam-work-and-prioritization.md). ### Configurable Logging A new, highly configurable logging system allows node operators to tailor logging levels and outputs, enhancing debugging and health monitoring without excessive disk space use.