internals: Make compact_size::MAX_ENCODING_SIZE public
What changed, and why it matters
This commit simply changes the visibility of a constant named MAX_ENCODING_SIZE from internal-only to public. It does not alter any behavior, logic, or data handling. There is no security issue here.
No action needed. This is a benign visibility-only change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
A single-line visibility change: const MAX_ENCODING_SIZE: usize = 9; becomes pub const MAX_ENCODING_SIZE: usize = 9;. The value remains 9. No code behavior changes; this is an API-exporting refactor to allow reuse in consensus_encoding.
Changed components
internals/src/compact_size.rsInspect captured patch +1 / −1
diff --git a/internals/src/compact_size.rs b/internals/src/compact_size.rs
index a343f3c1..37fc775c 100644
--- a/internals/src/compact_size.rs
+++ b/internals/src/compact_size.rs
@@ -18,7 +18,7 @@ use crate::ToU64;
pub const MAX_ENCODABLE_VALUE: u64 = 0x0200_0000;
/// The maximum length of an encoding.
-const MAX_ENCODING_SIZE: usize = 9;
+pub const MAX_ENCODING_SIZE: usize = 9;
/// Returns the number of bytes used to encode this `CompactSize` value.
///
Why this scored 16/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.