< GitHub108> [bitcoin] jonasschnelli opened pull request #8323: Add HD keypath to CKeyMetadata, report metadata in validateaddress (master...2016/07/hd_013) https://github.com/bitcoin/bitcoin/pull/8323
< jonasschnelli> I think we should consider #8323 (+37 −1) for 0.13
< GitHub29> [bitcoin] jonasschnelli closed pull request #8205: [Wallet] add HD keypath to CKeyMetadata, report over validateaddress (master...2016/06/hd_metadata) https://github.com/bitcoin/bitcoin/pull/8205
< GitHub121> [bitcoin] jonasschnelli opened pull request #8324: [Wallet] keep HD seed during salvagewallet (master...2016/07/hd_salvage) https://github.com/bitcoin/bitcoin/pull/8324
< GitHub68> [bitcoin] Pranit-Harekar opened pull request #8325: 0.12 (master...0.12) https://github.com/bitcoin/bitcoin/pull/8325
< GitHub44> [bitcoin] MarcoFalke closed pull request #8325: 0.12 (master...0.12) https://github.com/bitcoin/bitcoin/pull/8325
< btcdrak> Happy Halving Countdown https://www.youtube.com/watch?v=ovXOZjxFB00
< petertodd> sipa: what's the red represent/
< petertodd> ?
< petertodd> sipa: oh, under 1uBTC?
< sipa> yes
< petertodd> sipa: cool, thanks! mind if I link that from the blog post I'm writing?
< sipa> it is "what would the utxo set size be if we deleted all outputs below value X"
< petertodd> sipa: (as in, I'll make a copy of it today, and then link w/ a URL for the live version)
< sipa> the graph is not being automatically updated (yet)
< sipa> so feel free
< petertodd> sipa: thanks!
< sipa> i guess there is possible ambiguity: every vertical crosscut of the graph represents the entire UTXO set as it was at the date shown by the X axis
< sipa> it's not a breakdown of the current UTXO set by when the entries were created
< gmaxwell> I just suggested sipa create a breakdown one a little bit ago.