Reduce statement-store gossiping

prdoc/pr_9912.prdoc

@@ -0,0 +1,14 @@
+title: '[WIP] Fix statement-store gossiping'
+doc:
+- audience: Node Dev
+  description: |-
+    Fixes gossiping and scalability issues in the statement-store networking:
+    reduces traffic by propagating only recent statements, skips duplicate processing,
+    and splits large batches to stay under MAX_STATEMENT_NOTIFICATION_SIZE.
+crates:
+- name: sc-network-statement
+  bump: minor
+- name: sc-statement-store
+  bump: minor
+- name: sp-statement-store
+  bump: minor

substrate/client/network/statement/Cargo.toml

@@ -29,3 +29,6 @@ sc-network-types = { workspace = true, default-features = true }
 sp-consensus = { workspace = true, default-features = true }
 sp-runtime = { workspace = true, default-features = true }
 sp-statement-store = { workspace = true, default-features = true }
+
+[dev-dependencies]
+async-trait = { workspace = true }

substrate/client/network/statement/src/config.rs

@@ -24,10 +24,10 @@ use std::time;
 pub(crate) const PROPAGATE_TIMEOUT: time::Duration = time::Duration::from_millis(1000);
 
 /// Maximum number of known statement hashes to keep for a peer.
-pub(crate) const MAX_KNOWN_STATEMENTS: usize = 4 * 1024 * 1024;
+pub(crate) const MAX_KNOWN_STATEMENTS: usize = 4 * 1024 * 1024; // * 32 bytes for hash = 128 MB per peer
 
 /// Maximum allowed size for a statement notification.
-pub(crate) const MAX_STATEMENT_SIZE: u64 = 256 * 1024;
+pub(crate) const MAX_STATEMENT_NOTIFICATION_SIZE: u64 = 256 * 1024;
 
 /// Maximum number of statement validation request we keep at any moment.
 pub(crate) const MAX_PENDING_STATEMENTS: usize = 2 * 1024 * 1024;