What the developer wrote
Authored by Fmt Bot
2026-04-12 automated rustfmt nightly
What changed, and why it matters
This commit is an automated code-formatting run by rustfmt. It only reorders an import statement and removes a trailing space in a test line. There is no functional change to the program.
No action required; this is a formatting-only change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff shows two purely cosmetic changes in bitcoin/src/consensus/verification.rs: (1) reordering the imported items from encode::{MAX_COMPACT_SIZE, ReadExt, WriteExt} to encode::{ReadExt, WriteExt, MAX_COMPACT_SIZE}; (2) removing a trailing space after kani::any(); in a Kani proof harness. Both changes are whitespace/import ordering only and cannot affect behavior, consensus rules, or security.
Changed components
bitcoin/src/consensus/verification.rsInspect captured patch +2 / −2
diff --git a/bitcoin/src/consensus/verification.rs b/bitcoin/src/consensus/verification.rs
index d76859ec..ffa469a2 100644
--- a/bitcoin/src/consensus/verification.rs
+++ b/bitcoin/src/consensus/verification.rs
@@ -1,6 +1,6 @@
// SPDX-License-Identifier: CC0-1.0
-use crate::consensus::encode::{MAX_COMPACT_SIZE, ReadExt, WriteExt};
+use crate::consensus::encode::{ReadExt, WriteExt, MAX_COMPACT_SIZE};
use crate::consensus::{Error, ParseError};
use crate::io::Cursor;
@@ -20,7 +20,7 @@ fn check_compact_size_roundtrip() {
#[kani::unwind(10)]
#[kani::proof]
fn check_oversized_compact_size_is_rejected() {
- let x: u64 = kani::any();
+ let x: u64 = kani::any();
kani::assume(x > MAX_COMPACT_SIZE as u64);
let mut bytes = [0u8; 9];
let mut cursor = Cursor::new(&mut bytes[..]);
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.