Mempool Policy

Overview

Meaning and scope

Mempool policy protects node resources and encourages transactions that can propagate and confirm efficiently. Rules may cover standard script forms, minimum fees, package limits, replace-by-fee, ancestor counts, data size, nonce gaps, and expiry. A block containing a transaction that violates ordinary relay policy can still be valid if the transaction meets consensus rules.

How it works

Software versions and operator configuration can therefore produce different mempool behavior across nodes. Wallet developers should test against widely deployed policy and interpret rejection codes precisely. Node operators should change defaults only with clear capacity and network-impact analysis. Payment services must not label a policy rejection as proof of an invalid payment, and should monitor upgrades that alter relay or replacement behavior. Mempool Policy should be represented as a sequence of observable states rather than one success flag. Practical implication: Mempool policy governs local unconfirmed handling beyond consensus, creating legitimate differences among nodes, versions, and relay paths.

Operational checks and limits

Policy controls which otherwise potentially valid transactions a node stores or relays, including fees, resource limits and replacement rules. It can differ across implementations and versions.

Practical example

A transaction is rejected by one node’s relay policy despite satisfying blockchain consensus validity checks.

Distinctions

Mempool policy is local pre-confirmation behavior; consensus rules determine final block validity.

How to evaluate it

A healthy payment service needs more than a single ‘network online’ indicator; for Mempool Policy, separate transaction propagation, peer connectivity, canonical-chain progress, block arrival, and the age of locally available data. When evaluating Mempool Policy, during an incident, retain observations from more than one independent endpoint; that helps distinguish a widespread protocol issue from a local network or monitoring failure without prematurely marking a customer payment as failed. Related concepts: Mempool.