jojeyh: when we're preparing to make a new 0.n.0 release, a new 0.n branch is created and development on that branch is limited to fixes only, while new features continue on in the master branch
still trying to get used to the whole process
[bitcoin] practicalswift opened pull request #12284: tests: Remove assigned but never used local variables (master...remove-assigned-but-never-used-local-variables) https://github.com/bitcoin/bitcoin/pull/12284
When running `getmempoolentry`, I have two values, height and time. If I just started my node I am able to see mempool entries with time that is before I ever started my node (for the first time). However, the height values seem to be different in a way that I only get heights that are recent. I'm guessing the time values are taken from the node that relayed the tx to me, but the height is set by my own node?
xabbix: yes - mempool acceptance time is saved to mempool.dat on shutdown and reloaded on startup. It's required for working out when a tx should be expired from the mempool. Height is not saved so will be lost when you restart your node.
uh. I see now that with txn A, B in the wallet paying me, where B conflicts A and B eventually confirms, A just vanishes (B continues to have the conflicts record, so it hasn't forgotten it completely). Anyone know when we adopted this behavior and why? This is not good.
gmaxwell: sounds like a bug to me, it should be there always....are you looking at qt or listtransactions?
(I mean depending on context, in qt it may make sense to hide some things like rbf-replaced txn that are conflicted and the conflict is buried)