This guide explains Bitcoin Core testmempoolaccept RPC in plain English. It shows what the command does, what its result means and what it cannot prove.
TL;DR
- What it is: Bitcoin Core 0.17.0 testmempoolaccept evaluated whether raw transaction hex would enter this node’s mempool under current consensus and policy. The required array had to contain exactly one item. Allowhighfees defaulted false.
- Why it matters: testmempoolaccept is a non-broadcast snapshot of one node’s decision. It helps only when exact context and fee safeguards are retained and never reserves or relays the transaction.
- Current position: Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.
Bitcoin Core testmempoolaccept RPC in simple English
Bitcoin Core testmempoolaccept RPC: Test valid, missing-input, double-spend, non-final, low-fee, excessive-fee, malformed and policy-nonstandard transactions and verify mempool remains unchanged.
Simple example
A miner is checking Bitcoin Core testmempoolaccept RPC. Record source commit, binary hash, network, chain identity, configuration and dependencies. Decode signatures, inputs, outputs, fee and replaceability and bind txid to the response.
Key terms in plain English
- Bitcoin Core:
- Widely used software that validates Bitcoin and can provide wallet, network and operator tools.
- RPC:
- A command that software sends to a node to request information or a local action.
- Consensus:
- The shared rules full nodes use to decide whether blocks and transactions are valid.
- Mempool:
- A node’s changing local collection of valid, unconfirmed transactions.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
One element
Validate that rawtxs is an array of exactly one hex string in 0.17. Do not assume newer package or batch semantics.
Exact transaction
Decode signatures, inputs, outputs, fee and replaceability and bind txid to the response. A policy test is not payment approval.
Current context
Record node version, tip, time and relevant policy. Another node or the same node later may decide differently.
High-fee guard
Keep allowhighfees false unless exceptional review proves fee and rate. The override does not make an irrational payment safe.
Reject reason
Use reject-reason as diagnostics, not a stable machine protocol. Correct underlying intent through a new review rather than blind mutation.
No broadcast
Allowed true neither reserves nor inserts the transaction. A separate broadcaster repeats final checks and handles conflicts or changed state.
Fixtures
Test valid, missing-input, double-spend, non-final, low-fee, excessive-fee, malformed and policy-nonstandard transactions and verify mempool remains unchanged. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness. Record source commit, binary hash, network, chain identity, configuration and dependencies.
Frequently asked questions
What is the main point of Bitcoin Core testmempoolaccept RPC?
Bitcoin Core testmempoolaccept RPC: Test valid, missing-input, double-spend, non-final, low-fee, excessive-fee, malformed and policy-nonstandard transactions and verify mempool remains unchanged.
For Bitcoin Core testmempoolaccept RPC, what should a beginner know about one element?
Validate that rawtxs is an array of exactly one hex string in 0.17.
For Bitcoin Core testmempoolaccept RPC, what should a beginner know about exact transaction?
Decode signatures, inputs, outputs, fee and replaceability and bind txid to the response.
For Bitcoin Core testmempoolaccept RPC, what should a beginner know about current context?
Record node version, tip, time and relevant policy. Another node or the same node later may decide differently.
Conclusion
testmempoolaccept is a non-broadcast snapshot of one node’s decision. It helps only when exact context and fee safeguards are retained and never reserves or relays the transaction.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.