Add getmempoolentry to Bitcoin API - #1601
Open
KichdiPatel wants to merge 1 commit into
Open
Conversation
Bitcoin RPC method coverage now includes getmempoolentry (enabled via chain-config PR #7178), which returns mempool metadata for a single transaction ID instead of requiring a full getrawmempool dump.
KichdiPatel
force-pushed
the
docs/bitcoin-getmempoolentry
branch
from
September 2, 2026 23:37
c1afad8 to
da1dad0
Compare
🔗 Preview Mode
|
dslovinsky
approved these changes
Sep 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
getmempoolentryto the Bitcoin compute-unit-costs pricing table (10 CU, matching the other Bitcoin mempool methods)Note
This PR originally also added the OpenRPC spec entry and overview-table row, but an automated Daikon bot PR (#1596) landed those on
mainfirst with a more detailed spec (deprecated field docs, richer descriptions). Rebased ontomainand kept the bot's version — the compute-unit-costs row is the only piece not yet covered, since the daily pricing-table sync hasn't picked up the new chain-config entry yet.Test plan
getmempoolentrypresent, no duplicate refs)