From cd26db8c93f887e76baae202aab150390e41983f Mon Sep 17 00:00:00 2001 From: Kamil Popielarz Date: Thu, 24 Oct 2024 11:50:59 +0000 Subject: [PATCH] feat(Consensus): Enable the `hashes-in-blocks` feature With the flag set to `true`, we will strip all ingress messages from blocks, before sending them to peers. On a receiver side, we will reconstruct the blocks by looking up the referenced ingress messages in the ingress pool or, if they are not there, by fetching missing ingress messages from peers who are advertising the blocks. --- rs/replica/setup_ic_network/src/lib.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rs/replica/setup_ic_network/src/lib.rs b/rs/replica/setup_ic_network/src/lib.rs index a93bd47366f..832bc7c5741 100644 --- a/rs/replica/setup_ic_network/src/lib.rs +++ b/rs/replica/setup_ic_network/src/lib.rs @@ -65,7 +65,7 @@ use tower_http::trace::TraceLayer; /// we will reconstruct the blocks by looking up the referenced ingress messages in the ingress /// pool or, if they are not there, by fetching missing ingress messages from peers who are /// advertising the blocks. -const HASHES_IN_BLOCKS_FEATURE_ENABLED: bool = false; +const HASHES_IN_BLOCKS_FEATURE_ENABLED: bool = true; pub const MAX_ADVERT_BUFFER: usize = 100_000; /// This limit is used to protect against a malicious peer advertising many ingress messages.