Skip to content

Conversation

@maflcko
Copy link
Member

@maflcko maflcko commented Jun 21, 2022

Seems odd to return other policy info, but not the incremental relay fee

Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK fafee78

Copy link
Contributor

@w0xlt w0xlt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review ACK fafee78

@DrahtBot
Copy link
Contributor

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Conflicts

Reviewers, this pull request conflicts with the following ones:

  • #25353 (Add a -mempoolfullrbf node setting by ariard)

If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.

Copy link
Contributor

@brunoerg brunoerg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Concept ACK

Copy link
Contributor

@jarolrod jarolrod left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tACK fafee78

{
  "loaded": true,
  "size": 1,
  "bytes": 141,
  "usage": 1168,
  "total_fee": 0.00000141,
  "maxmempool": 300000000,
  "mempoolminfee": 0.00001000,
  "minrelaytxfee": 0.00001000,
  "incrementalrelayfee": 0.00001000,
  "unbroadcastcount": 0
}

@maflcko maflcko merged commit f52d074 into bitcoin:master Jun 27, 2022
@maflcko maflcko deleted the 2206-rpc-policy-🥙 branch June 27, 2022 06:22
{RPCResult::Type::STR_AMOUNT, "mempoolminfee", "Minimum fee rate in " + CURRENCY_UNIT + "/kvB for tx to be accepted. Is the maximum of minrelaytxfee and minimum mempool fee"},
{RPCResult::Type::STR_AMOUNT, "minrelaytxfee", "Current minimum relay fee for transactions"},
{RPCResult::Type::NUM, "unbroadcastcount", "Current number of transactions that haven't passed initial broadcast yet"}
{RPCResult::Type::NUM, "incrementalrelayfee", "minimum fee rate increment for mempool limiting or BIP 125 replacement in " + CURRENCY_UNIT + "/kvB"},
Copy link
Member

@jonatack jonatack Jun 27, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • s/minimum/Minimum/ (like the other lines in the getmempoolinfo help)
  • could add the unit to minrelaytxfee help

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Would be possibly nice for these to be expressed in sats, though I suppose that would require a new RPC.)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/minimum/Minimum/ (like the other lines in the getmempoolinfo help)

I copied this from the getnetworkinfo RPC.

could add the unit to minrelaytxfee help

Sure, but seems unrelated.

(Would be possibly nice for these to be expressed in sats, though I suppose that would require a new RPC.)

Good point, given that the wallet is moving toward sat/vB. Not sure how to fix this, though.

sidhujag pushed a commit to syscoin/syscoin that referenced this pull request Jun 27, 2022
fafee78 rpc: Return incrementalrelayfee in getmempoolinfo (MacroFake)

Pull request description:

  Seems odd to return other policy info, but not the incremental relay fee

ACKs for top commit:
  1440000bytes:
    ACK bitcoin@fafee78
  w0xlt:
    Code Review ACK bitcoin@fafee78
  jarolrod:
    tACK fafee78

Tree-SHA512: faad0af6c039b8257acbeac913bc5dcdb2ea2db304c95e52601536c8de60eb1186e9fbb4a64a68adf476605f18022aeda16a5644a0d7912592b0977e4c029638
@bitcoin bitcoin locked and limited conversation to collaborators Jun 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants