What the developer wrote
Authored by Tobin C. Harding
Add tag to Block decodable
Just to make it more obvious that we only implement `Decodable` for
unchecked blocks.
The `Unchecked` tag is the default. Syntax only, no logic change.
What changed, and why it matters
This is a purely cosmetic code change. A developer added the word 'Unchecked' to an existing implementation line to make it clearer that this code path does not validate block contents. No program behavior, security checks, or logic were changed.
No action needed. This is a non-functional documentation/clarity change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit changes impl Decodable for Block to impl Decodable for Block<Unchecked> in primitives/src/block.rs. The message explicitly states this is syntax only with no logic change. Unchecked is described as the default tag, so the type meaning is unchanged. There is no security patch here.
Changed components
primitives/src/block.rsInspect captured patch +1 / −1
diff --git a/primitives/src/block.rs b/primitives/src/block.rs
index 539d1fbd..9fc9b9d7 100644
--- a/primitives/src/block.rs
+++ b/primitives/src/block.rs
@@ -392,7 +392,7 @@ impl Decoder for BlockDecoder {
}
#[cfg(feature = "alloc")]
-impl Decodable for Block {
+impl Decodable for Block<Unchecked> {
type Decoder = BlockDecoder;
fn decoder() -> Self::Decoder {
BlockDecoder(Decoder2::new(Header::decoder(), VecDecoder::<Transaction>::new()))
Why this scored 15/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.