AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 21 Bitcoin

[miner] lower default -blockmintxfee to 1sat/kvB

Public commit record

What the developer wrote

Authored by glozow

68/100 · Adequate
[miner] lower default -blockmintxfee to 1sat/kvB

Back when we implemented coin age priority as a miner policy, miners
mempools might admit transactions paying very low fees, but then want to
set a higher fee for block inclusion. However, since coin age priority
was removed in v0.15, the block assembly policy is solely based on fees,
so we do not need to apply minimum feerate rules in multiple places. In
fact, the block assembly policy ignoring transactions that are added to
the mempool is likely undesirable as we waste resources accepting and
storing this transaction.

Instead, rely on mempool policy to enforce a minimum entry feerate to
the mempool (minrelaytxfee). Set the minimum block feerate to the
minimum non-zero amount (1sat/kvB) so it collects everything it finds in
mempool into the block.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This change lowers the default minimum fee a Bitcoin miner requires to include a transaction in a block from 1000 satoshis per kilovbyte to 1 satoshi per kilovbyte. The intent is to let miners include any transaction already accepted by their mempool, rather than having a separate, stricter block-inclusion rule. It is a policy/configuration change, not a cryptographic or consensus bug, and it does not bypass mempool rules.

Recommended action

No security action required. Operators and miners should review whether the new default matches their economic policy; those wanting a higher block minimum can still set -blockmintxfee explicitly.

Security signals we found

01

Default mining policy parameter changed

02

No consensus or validation logic modified

03

Mempool admission policy (minrelaytxfee) remains the gatekeeper

04

No bounds checking, memory safety, or cryptographic code touched

Risk score

Why this scored 21/100

Our methodology →
Potential impact 2/30
Exploitability 1/25
Stealth signal 1/15
Affected reach 3/15
Confidence 9/10
Evidence quality 5/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.