< luke-jr> 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
< jojeyh> thanx
< jojeyh> still trying to get used to the whole process
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/2ae7cf8ef5be...9cf6393a4f82
< bitcoin-git> bitcoin/master a8c344b Wladimir J. van der Laan: Update chainTxData for 0.16...
< bitcoin-git> bitcoin/master 9cf6393 MarcoFalke: Merge #12270: Update chainTxData for 0.16...
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #12270: Update chainTxData for 0.16 (master...2018_01_chainstats) https://github.com/bitcoin/bitcoin/pull/12270
< ossifrage> I just noticed that ~27% of the connections to my node fail with "version handshake timeout", I wonder who all those connections are?
< luke-jr> or from?
< ossifrage> luke-jr, I only get a peerid in the log, no address, so I don't know the distribution of those connections
< bitcoin-git> [bitcoin] practicalswift opened pull request #12283: Fix typos (master...typos-20180128) https://github.com/bitcoin/bitcoin/pull/12283
< bitcoin-git> [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
< xabbix> 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?
< jnewbery> 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.
< jnewbery> Both are set by your own node
< bitcoin-git> [bitcoin] tamasblummer opened pull request #12286: Wallet: Resolve compiler warnings in ec_privkey_import_der (master...master) https://github.com/bitcoin/bitcoin/pull/12286
< gmaxwell> 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.
< BlueMatt> gmaxwell: sounds like a bug to me, it should be there always....are you looking at qt or listtransactions?
< BlueMatt> (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)
< bitcoin-git> [bitcoin] jonasschnelli opened pull request #12287: Fix missing cs_main lock for GuessVerificationProgress() (master...2018/01/rescan_lock) https://github.com/bitcoin/bitcoin/pull/12287
< bitcoin-git> [bitcoin] annanay25 opened pull request #12288: [WIP][NET] Add NATPMP support. (master...natpmp-support) https://github.com/bitcoin/bitcoin/pull/12288
< mrannanay> ^^ contributing for the first time, a little confused with the licensing on the files, etc.
< Jack> If wrong forum for such questions let me know. I downloaded bitcoin core, used bitcoin-qt.exe, can see folder of blocks in data location I created.
< Jack> 1. If I wanted to construct the actual block chain fail would I simply append blk00XXX.dat files to each other in the sequence of the number of the file name?
< Jack> 2. What is the blk00XXX.dat, rev00916.dat, and XXXXX.ldb files function?
< Jack> #bitcoin
< Jack> Join:#bitcoin