771 | @@ -772,6 +772,9 @@ UniValue mempoolInfoToJSON()
772 | ret.push_back(Pair("size", (int64_t) mempool.size()));
773 | ret.push_back(Pair("bytes", (int64_t) mempool.GetTotalTxSize()));
774 | ret.push_back(Pair("usage", (int64_t) mempool.DynamicMemoryUsage()));
775 | + size_t maxmempool = GetArg("-maxmempool", DEFAULT_MAX_MEMPOOL_SIZE) * 1000000;
776 | + ret.push_back(Pair("maxmempool", (int64_t) maxmempool));
777 | + ret.push_back(Pair("effectiveminfee", ValueFromAmount(mempool.GetMinFee(maxmempool).GetFeePerK())));
"effectiveminfee" seems misleading if your GetMinFee() is 0.
Better suggestions?
Hm maybe just 'minfee' (context is getmempoolinfo, after all) or 'mempoolminfee'. I agree it's not really the effective number used and shouldn't be named that...
seems we have two votes for mempoolminfee - changing to that