What changed, and why it matters
This commit fixes a single typo in a documentation file. It changes '5satvB' to '5sat/vB' in a comment explaining Bitcoin transaction fee policy. There is no code change and no security impact.
No action required. This is a documentation-only typo fix with no security relevance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit is a one-character documentation correction in doc/policy/packages.md, adding a missing slash in the unit ‘sat/vB’ (satoshi per virtual byte). It does not modify any executable code, configuration defaults, protocol behavior, or cryptographic logic.
Changed components
doc/policy/packages.mdInspect captured patch +1 / −1
diff --git a/doc/policy/packages.md b/doc/policy/packages.md
index 4c45470e..a4d4cb07 100644
--- a/doc/policy/packages.md
+++ b/doc/policy/packages.md
@@ -115,7 +115,7 @@ rejected from the mempool when transaction volume is high and the mempool minimu
Note: Package feerate cannot be used to meet the minimum relay feerate (`-minrelaytxfee`)
requirement. For example, if the mempool minimum feerate is 5sat/vB and the minimum relay feerate is
-set to 5satvB, a 1sat/vB parent transaction with a high-feerate child will not be accepted, even if
+set to 5sat/vB, a 1sat/vB parent transaction with a high-feerate child will not be accepted, even if
submitted as a package.
*Rationale*: Avoid situations in which the mempool contains non-bumped transactions below min relay
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.