Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing getmempoolentry #113

Closed
FrozenPrincess opened this issue Jan 21, 2017 · 3 comments
Closed

Missing getmempoolentry #113

FrozenPrincess opened this issue Jan 21, 2017 · 3 comments

Comments

@FrozenPrincess
Copy link

Here's a sample call:

getmempoolentry abed2bc7cc77a4bc342a67e29da974b9cc69d47afa6279463d916009b1bcb6a3

{
"size": 372,
"fee": 0.00008280,
"modifiedfee": 0.00008280,
"time": 1484977137,
"height": 1085243,
"startingpriority": 541889.8421052631,
"currentpriority": 568809.6710526316,
"descendantcount": 1,
"descendantsize": 372,
"descendantfees": 8280,
"ancestorcount": 1,
"ancestorsize": 372,
"ancestorfees": 8280,
"depends": [
]
}


In my particular use-case, the fields I need are `ancestorsize` and `ancestorfees` as I'm trying to compute the feerate to guestimate if it'll confirm. I notice these fields are also missing from btcjson.GetRawMempoolVerboseResult.  So it'd be nice if they were also made complete
@dajohi
Copy link
Member

dajohi commented Jan 23, 2017

btcsuite/btcd#905

@davecgh
Copy link
Member

davecgh commented Jan 24, 2017

@dajohi: For reference, even if you add those fields to the result as 905 currently does, none of the ancestor/descendant information is available to populate the results. The mempool doesn't current keep track of that information.

EDIT: To clarify that obviously would only apply to responses from btcd. Speaking to Core which does provide it would work.

@dajohi
Copy link
Member

dajohi commented Feb 3, 2017

@FrozenPrincess Are you able to give #117 a try?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants