Prioritize Transaction Simplification Wrapper #8529

issue TheBlueMatt opened this issue on August 16, 2016
  1. TheBlueMatt commented at 11:29 PM on August 16, 2016: member

    Several miners and pool operators have, at various times, requested a prioritizetransaction API, or have requested that the current one be made more accessible. Right now the flow to use it requires that you write a program which interogates mempool and finds transactions to prioritize for some use-cases.

    While I think the API is sufficient, it would be nice to have a simple python wrapper which could, for example, completely emulate the old priority mechanism (then we could remove it wholesale :p).

    We might also add a way to prioritize while submitting a transaction, but this wrapper could easily provide that as well as a demonstration (IIRC you can currently do it by prioritizing the hash and then submitting the transaction).

  2. jonasschnelli added the label Mempool on Aug 17, 2016
  3. jonasschnelli added the label Feature on Aug 17, 2016
  4. laanwj commented at 10:11 AM on August 17, 2016: member

    How is this different from the prioritisetransaction RPC call?

  5. sipa commented at 8:45 AM on August 22, 2016: member

    I'm confused about the use case.

    Prioritizetransaction maps perfectly to a model where a small number of transactions are paid for out of band - not something that requires inspecting the mempool for all transactions and recalculating things. If someone feels the need to do that, they're obviously using it in a way that's not currently being discussed here, so I'd like to know the goal.

    I also think that trying to reimplement the old prioritization mechanism would be hard and pointless. It would need to query the mempool, create a full in-memory copy of it complete with indexes, sort it by alternative criteria, then compute the effects of CPFP so it can compensated for, and continuously call prioritizetransaction.

    Providing a helper script to automate some higher-level behaviour would be useful if we know what that behaviour is, but emulating the old priority-based sorting would be a complicated and inefficient hack, and giving a bad example.

  6. MarcoFalke commented at 12:09 AM on April 27, 2020: member

    The feature request didn't seem to attract much attention in the past. Also, the issue seems not important enough right now to keep it sitting around idle in the list of open issues.

    Closing due to lack of interest. Pull requests with improvements are always welcome.

  7. MarcoFalke closed this on Apr 27, 2020

  8. DrahtBot locked this on Feb 15, 2022

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-24 15:15 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me