1 2015-09-05 03:09:35 <phantomcircuit> ha just noticed
 2 2015-09-05 03:09:43 <phantomcircuit> getpeerinfo doesn't show which service bits the peer has set
 3 2015-09-05 03:11:28 <gmaxwell> huh?!
 4 2015-09-05 03:13:02 <gmaxwell> "services" : "0000000000000001",
 5 2015-09-05 03:13:14 <gmaxwell> ::sign:: yet another new dos attack on my node at home.
 6 2015-09-05 03:18:16 <phantomcircuit> gmaxwell, huh
 7 2015-09-05 03:18:18 <phantomcircuit> it is there
 8 2015-09-05 03:18:23 <phantomcircuit> total brain fart
 9 2015-09-05 03:18:41 <phantomcircuit> it like merged with the ip address in my mind or something
10 2015-09-05 12:05:59 <jgarzik> jonasschnelli, FYI, moved tests and lib into sub-directories, in jgarzik/univalue
11 2015-09-05 12:06:09 <jgarzik> tagged as v0.0.1
12 2015-09-05 21:08:45 <jamesob> I'm new to bitcoin-dev, but I'd like to start jumping in... can anyone recommend an approachable (if not boring/rote/arduous) issue to tackle?
13 2015-09-05 21:09:41 <Luke-Jr> jamesob: reviewing open pull requests is the best place to get started now
14 2015-09-05 21:09:56 <Luke-Jr> jamesob: another good option is writing missing unit tests
15 2015-09-05 21:10:13 <Luke-Jr> jamesob: if you really want something more interesting, obfuscating the blockchain and/or UTXO set would be useful
16 2015-09-05 21:12:47 <jamesob> Luke-Jr any recommendations for PRs to review? and are you referring to https://github.com/bitcoin/bitcoin/issues/6613 ?
17 2015-09-05 21:13:59 <Luke-Jr> yes
18 2015-09-05 21:14:21 <Luke-Jr> probably anything on https://github.com/bitcoin/bitcoin/pulls would be good to review
19 2015-09-05 21:18:07 <alpalp> luke-jr: what do you  mean obfuscating chain/utxo?
20 2015-09-05 21:18:26 <alpalp> nm saw the link
21 2015-09-05 21:21:32 <alpalp> that related to the virus signatures people put in the chain data?
22 2015-09-05 21:29:17 <Luke-Jr> alpalp: could be related to lots of things. point is to avoid false positives