09:15 < bitcoin-git> [bitcoin] practicalswift opened pull request #16092: Don't use global (external) symbols for symbols that are used in only one translation unit (master...reduce-global-namespacing) https://github.com/bitcoin/bitcoin/pull/16092

14:15 < bitcoin-git> [bitcoin] dagrasagra opened pull request #16093: change to yamacoin (master...master) https://github.com/bitcoin/bitcoin/pull/16093

14:16 < bitcoin-git> [bitcoin] fanquake closed pull request #16093: change to yamacoin (master...master) https://github.com/bitcoin/bitcoin/pull/16093

15:40 < bitcoin-git> [bitcoin] kristapsk opened pull request #16095: Catch by reference not value in wallettool (master...catch-by-ref-wallettool) https://github.com/bitcoin/bitcoin/pull/16095

15:55 < shesek> is there a way to get the fee estimates out of a running instance, something like savemempool? I'm guessing it probably won't be safe to simply copy the fee_estimates.dat file while the instance is running?

16:24 < phantomcircuit> shesek, there's an rpc

17:11 < bitcoin-git> [bitcoin] Empact closed pull request #15253: Net: Consistently log outgoing INV messages (master...inv-log) https://github.com/bitcoin/bitcoin/pull/15253

21:09 < midnightmagic> sipa: Hey man, I think your graphs are paused again.

21:10 < midnightmagic> at least.. I think this one is? http://bitcoin.sipa.be/speed-lin.png

21:15 < bitcoin-git> [bitcoin] hebasto opened pull request #16097: Prevent meaningless negating of arguments (master...20190526-fix-negated-args) https://github.com/bitcoin/bitcoin/pull/16097

22:00 < shesek> phantomcircuit, there is? that's great! I haven't been able to find it, how's it called?

22:06 < phantomcircuit> shesek, estimatefee

22:13 < instagibbs> shesek, estimatesmartfee, estimatefee is deprecated(removed?)

22:39 < shesek> I meant get the actual fee estimates raw data out, akin to getting mempool data with "savemempool", only for fee_estimates.dat. I'm trying to do that in order to spin up a bitcoind new instance to replace the old one without losing mempool and fee estimates data and without shutting down the first instance before the new one is ready

22:39 < shesek> s/bitcoind new/new bitcoind/

22:39 < shesek> is it safe to just copy it?

22:40 < sipa> shesek: should be; it's rewritten using "write new file + move over old file"

22:41 < sipa> so copying should always give you a stable state

22:41 < shesek> thanks!

23:02 < shesek> how often does bitcoind write it to disk?

23:05 < sipa> shesek: only at shutdown i think

23:08 < sipa> d_t:

23:11 < shesek> I see, so I copying it out of a running instance won't really work, it will be quite outdated by then