12016-03-26T00:02:14  *** jyap has joined #bitcoin-core-dev
  22016-03-26T00:02:14  *** jyap has joined #bitcoin-core-dev
  32016-03-26T00:27:22  *** AaronvanW has joined #bitcoin-core-dev
  42016-03-26T00:53:38  *** achow101 has joined #bitcoin-core-dev
  52016-03-26T01:04:01  *** Alopex has quit IRC
  62016-03-26T01:05:07  *** Alopex has joined #bitcoin-core-dev
  72016-03-26T01:08:39  <GitHub73> [bitcoin] accraze opened pull request #7747: [docs] added depends cross compile info (master...depends-build-docs) https://github.com/bitcoin/bitcoin/pull/7747
  82016-03-26T01:24:57  *** zooko has quit IRC
  92016-03-26T01:32:31  *** p15x has quit IRC
 102016-03-26T01:33:02  *** Alopex has quit IRC
 112016-03-26T01:34:07  *** Alopex has joined #bitcoin-core-dev
 122016-03-26T01:35:52  *** xabbix__ has quit IRC
 132016-03-26T01:36:26  *** xabbix__ has joined #bitcoin-core-dev
 142016-03-26T01:40:02  *** frankenmint has quit IRC
 152016-03-26T01:43:04  *** JeromeLegoupil has quit IRC
 162016-03-26T02:59:12  *** p15 has joined #bitcoin-core-dev
 172016-03-26T03:02:01  *** Alopex has quit IRC
 182016-03-26T03:03:06  *** Alopex has joined #bitcoin-core-dev
 192016-03-26T03:13:09  *** belcher has quit IRC
 202016-03-26T03:19:07  *** supasonic has quit IRC
 212016-03-26T03:19:35  *** supasonic has joined #bitcoin-core-dev
 222016-03-26T03:24:38  *** zooko has joined #bitcoin-core-dev
 232016-03-26T03:30:10  *** achow101 has quit IRC
 242016-03-26T03:59:49  *** molz has joined #bitcoin-core-dev
 252016-03-26T04:01:01  *** Alopex has quit IRC
 262016-03-26T04:02:06  *** Alopex has joined #bitcoin-core-dev
 272016-03-26T04:02:42  *** moli has quit IRC
 282016-03-26T04:17:44  *** zooko has quit IRC
 292016-03-26T04:24:01  *** Alopex has quit IRC
 302016-03-26T04:25:06  *** Alopex has joined #bitcoin-core-dev
 312016-03-26T04:30:02  *** supasonic has quit IRC
 322016-03-26T04:50:01  *** Alopex has quit IRC
 332016-03-26T04:51:07  *** Alopex has joined #bitcoin-core-dev
 342016-03-26T05:06:01  *** Alopex has quit IRC
 352016-03-26T05:07:06  *** Alopex has joined #bitcoin-core-dev
 362016-03-26T05:43:00  *** PaulCape_ has joined #bitcoin-core-dev
 372016-03-26T05:45:12  *** PaulCapestany has quit IRC
 382016-03-26T05:51:02  *** Alopex has quit IRC
 392016-03-26T05:52:07  *** Alopex has joined #bitcoin-core-dev
 402016-03-26T06:00:07  *** JeromeLegoupil has joined #bitcoin-core-dev
 412016-03-26T06:00:08  *** dermoth has quit IRC
 422016-03-26T06:00:46  *** dermoth has joined #bitcoin-core-dev
 432016-03-26T06:13:25  *** PaulCape_ has quit IRC
 442016-03-26T06:13:52  *** PaulCapestany has joined #bitcoin-core-dev
 452016-03-26T06:15:01  *** Alopex has quit IRC
 462016-03-26T06:15:07  *** d_t has quit IRC
 472016-03-26T06:16:06  *** Alopex has joined #bitcoin-core-dev
 482016-03-26T06:16:28  *** frankenmint has joined #bitcoin-core-dev
 492016-03-26T06:17:22  *** JeromeLegoupil has quit IRC
 502016-03-26T06:26:09  *** BCBot has quit IRC
 512016-03-26T06:26:09  *** BCBot_ has quit IRC
 522016-03-26T06:28:33  *** BCBot has joined #bitcoin-core-dev
 532016-03-26T06:31:01  *** Alopex has quit IRC
 542016-03-26T06:32:06  *** Alopex has joined #bitcoin-core-dev
 552016-03-26T06:35:02  *** JeromeLegoupil has joined #bitcoin-core-dev
 562016-03-26T06:51:01  *** Alopex has quit IRC
 572016-03-26T06:52:07  *** Alopex has joined #bitcoin-core-dev
 582016-03-26T06:54:12  *** gevs has quit IRC
 592016-03-26T07:04:50  *** p15 has quit IRC
 602016-03-26T07:06:24  *** p15 has joined #bitcoin-core-dev
 612016-03-26T07:06:53  *** gevs has joined #bitcoin-core-dev
 622016-03-26T07:08:01  *** Alopex has quit IRC
 632016-03-26T07:09:06  *** Alopex has joined #bitcoin-core-dev
 642016-03-26T07:16:30  *** JeromeLegoupil has quit IRC
 652016-03-26T07:24:01  *** Alopex has quit IRC
 662016-03-26T07:25:06  *** Alopex has joined #bitcoin-core-dev
 672016-03-26T07:34:16  *** Don_John has quit IRC
 682016-03-26T07:43:07  *** moli has joined #bitcoin-core-dev
 692016-03-26T07:45:59  *** molz has quit IRC
 702016-03-26T08:00:13  <jonasschnelli> gmaxwell: good point with including the ciphersuite into the KDF to avoid a weak-ciphersuite-attack. Haven't thought about that!
 712016-03-26T08:00:57  <jonasschnelli> gmaxwell: you said "Personally I'd just suggest dropping the negoation;". I guess you mean only the ciphersuite-negotiation? Not the whole ECDH?
 722016-03-26T08:01:02  <gmaxwell> nor did the authors of dozens of other protocols that didn't. I am not so smart, lots of people have failed here before, and I'm only repeating their mistakes.
 732016-03-26T08:01:07  <gmaxwell> jonasschnelli: right.
 742016-03-26T08:02:37  <jonasschnelli> gmaxwell: you said: " (also, you're going to need a 256 bit session ID for later auth, and two 512 bit keys for the authenticated encryption);" I don't understand that. I'm only aware of two 256bit keys for both directions ECDH.
 752016-03-26T08:02:47  <jonasschnelli> I don't see a need for a auth session id.
 762016-03-26T08:03:26  <jonasschnelli> Because I assume the encryption negotiation followed by a auth identity pubkey check will keep the authentication withing the encryption session?
 772016-03-26T08:03:53  <sipa> jonasschnelli: you'll need a session id to sign when doing identity checking
 782016-03-26T08:04:26  <gmaxwell> the authentication must bind the session or varrious kinds of MITM identity proxying attacks turn up.
 792016-03-26T08:04:33  <sipa> sure, you could sign one of the encryption keys or the ECDH output directly, but it's generally better to separate them
 802016-03-26T08:04:52  <jonasschnelli> sipa: Ah. So during the encryption negotiation both side produce a 256bit session id and the other party needs to sign that (together with the pubkey) to ensure a link between the auth and the enc?
 812016-03-26T08:05:40  <sipa> jonasschnelli: auth is an overloaded term; do you mean MAC or identity verification?
 822016-03-26T08:05:53  <jonasschnelli> identity verification. sry.
 832016-03-26T08:06:10  <gmaxwell> jonasschnelli: right thats what the session ID is for.
 842016-03-26T08:06:36  <jonasschnelli> So the session ID can be transported unencrypted during ECDH nego.?
 852016-03-26T08:06:42  <jonasschnelli> no... wait.
 862016-03-26T08:06:52  <gmaxwell> the session ID is just a result of the ECDH.
 872016-03-26T08:06:52  <sipa> jonasschnelli: the session ID never ever transported
 882016-03-26T08:07:04  <sipa> not encrypted, not unencrypted
 892016-03-26T08:07:12  <jonasschnelli> hmm...
 902016-03-26T08:07:20  <gmaxwell> The ECDH runs, and the result is a session ID and a set of keys for the encryption/mac.
 912016-03-26T08:07:37  <gmaxwell> And the session ID can (optionally) be authenticated.
 922016-03-26T08:07:52  <jonasschnelli> so the ECDH calculated point could be the session ID, then run a KDF, get the sym. cipher key?
 932016-03-26T08:08:25  *** ChillazZ has quit IRC
 942016-03-26T08:08:32  <sipa> jonasschnelli: ECDH output is used as seed for a PRNG; from that PRNG you read session id, IV, encryption keys, ... whatever you need
 952016-03-26T08:08:41  *** ChillazZ has joined #bitcoin-core-dev
 962016-03-26T08:09:14  <jonasschnelli> And to verify identity (identity auth) the requesting peer needs to sign the ECDH calculated point (or a PRNG result from that seed) with his pre-shared idendity pubkey?
 972016-03-26T08:09:36  <sipa> yes
 982016-03-26T08:09:40  <gmaxwell> you never use the ECDH value directly. They'd sign the session ID. (a PRNG result)
 992016-03-26T08:09:53  <jonasschnelli> Okay. Got it!
1002016-03-26T08:10:09  <jonasschnelli> Wasn't aware of the possibility to use the ECDH point as seed.
1012016-03-26T08:10:16  <gmaxwell> The PRNG input should include the ECDH along with all the 'session context' e.g. any paramter negoiation that was sent.
1022016-03-26T08:10:26  <gmaxwell> (I recommend including one of the public keys in the KDF, to avoid the gratitious loss of entropy; but this is a minor thing)
1032016-03-26T08:10:55  <jonasschnelli> And probably the ciphersuite (if we keep this).
1042016-03-26T08:11:12  <sipa> jonasschnelli: i think it makes sense to have ciphersuite versions
1052016-03-26T08:11:19  <sipa> and just have one currently
1062016-03-26T08:11:24  <jonasschnelli> Yes. I also reserved it for future changes.
1072016-03-26T08:11:37  <sipa> negotiation is hard, and general trend is moving away from it
1082016-03-26T08:12:03  <sipa> instead just have version numbers of the protocol, and each version has one fixed set of ciphers
1092016-03-26T08:12:35  <gmaxwell> sipa: I'm not sure this is better though! consider, if you merely do that, how do you guard against downgrade attacks-- I guess only by supporting just a single version?
1102016-03-26T08:12:49  <gmaxwell> otherwise, what you need to do is have the protocol commit to whatever versions were offered.
1112016-03-26T08:14:29  <jonasschnelli> Okay. I'll update the BIP and write more specification about the negotiation, session ID, KDF
1122016-03-26T08:14:47  <jonasschnelli> pbkdf2?
1132016-03-26T08:15:50  <sipa> for KDF you could use rfc6979 (slow!), just a simple SHA256 of ECDH together with a counter, chacha20, or maybe SHAKE (sha3 variant with arbitrary length output)
1142016-03-26T08:16:22  <sipa> i like sha3 because it has such large state, so you can put a lot of context in without limiting entropy
1152016-03-26T08:17:40  <sipa> the pb in pbkdf stands for password based :)
1162016-03-26T08:17:43  <gmaxwell> jonasschnelli: another thing your spec is missing is rekeying. The chacha20/poly must be rekeyed periodically.
1172016-03-26T08:17:55  <jonasschnelli> ^^
1182016-03-26T08:18:00  <gmaxwell> pbkdf2 is intentionally slow, not a requirement here.
1192016-03-26T08:18:18  <sipa> gmaxwell: my assumption was that you'd do another encinit session occasionally within the encrypted channel
1202016-03-26T08:18:24  <gmaxwell> I don't know if you noticed but I suggested that authentication could be done in a way combined with rekeying which would have some very nice properties.
1212016-03-26T08:18:32  <jonasschnelli> So... rekey = re-negotiate the whole ECDH secret every x minutes/hours?
1222016-03-26T08:18:55  <sipa> every gigabyte
1232016-03-26T08:19:07  <sipa> though having time limits is good too
1242016-03-26T08:19:42  <jonasschnelli> an right. would something speak against sipas idea of re-key within the current enc session?
1252016-03-26T08:20:11  <jonasschnelli> Would probably make the implementation simpler.
1262016-03-26T08:20:16  <jonasschnelli> (different message formats)
1272016-03-26T08:20:40  <sipa> jonasschnelli: gmaxwell's identity check idea would also automatically result in a rekey
1282016-03-26T08:20:42  <gmaxwell> I suggested that to auth, the auth requester send X H(sessionid,server_pubkey), and if the server knows the pubkey for X, she responds with a message saying that she is changing her encryption key, and changes to H(old_encryption_key, server_pubkey) as the new one.. and in the newly encrypted segment she tranmits the signature that proves she knows the secret.
1292016-03-26T08:21:18  <gmaxwell> This has a nice properity that if the server pubkey is kept secret; the confidentiality of past communications is preserved even if ECC is broken.
1302016-03-26T08:21:43  <gmaxwell> And it also proves that the servers identity key has remained online, if that procedure is used for each rekeying in the future.
1312016-03-26T08:23:46  <jonasschnelli> gmaxwell: H(old_encryption_key, server_pubkey)  <--- "old_encryption_key" would be the KDF derived  symmetric key?
1322016-03-26T08:23:56  <gmaxwell> Yes.
1332016-03-26T08:24:10  <jonasschnelli> And... right. That would be required "in both directions"...
1342016-03-26T08:25:32  <gmaxwell> My thought on that is that even when you don't have an identity you're expecting everyone could just support using the generator (private key 1).. so even without a known identity the same protocol would always be used... good for QA and for traffic analysis resistance.
1352016-03-26T08:25:42  <jonasschnelli> gmaxwell: and a re-keying without identity auth? new ECDH nego., new session id, but sym. key could be H(old_encryption_key, new_encryption_key)?
1362016-03-26T08:26:44  <gmaxwell> yes it could be there is no need to redo ECDH, just a waste of CPU time.
1372016-03-26T08:27:12  <jonasschnelli> but how would you create a new shared secret? Using a counter on both sides?
1382016-03-26T08:27:32  <gmaxwell> H(old_key) is sufficient.
1392016-03-26T08:27:52  <jonasschnelli> ah.. okay. I see. Just hash the hash, ...
1402016-03-26T08:28:13  <gmaxwell> for forward security reasons you don't want to be forced to keep the old keys around... they should be destroyed as soon as they're not in use.
1412016-03-26T08:28:31  <jonasschnelli> How would the other peer know when it is time to re-key. Probably requested by the responding peer with a new message type.
1422016-03-26T08:29:01  <jonasschnelli> s/./?
1432016-03-26T08:29:02  <gmaxwell> by sending a message in the channel, "everything that follows will be the next key"
1442016-03-26T08:29:20  <jonasschnelli> right. That makes sense.
1452016-03-26T08:30:37  <gmaxwell> and my earlier suggestion was to make the auth do this so that the pubkey could be used as a symmetric secret in the rekeying.
1462016-03-26T08:31:37  *** Ylbam has joined #bitcoin-core-dev
1472016-03-26T08:32:04  <jonasschnelli> And I suppose the identity auth also needs a timeout (probably time instead of consumed bandwith).
1482016-03-26T08:33:03  <gmaxwell> forward secrecy also wants a timeout, so something like 1 hour or 1GB whichever comes first.
1492016-03-26T08:33:23  <gmaxwell> not that our need for forward secrecy is so great, but if we're going to do something might as well do it right.
1502016-03-26T08:35:37  *** ChillazZ has quit IRC
1512016-03-26T08:36:16  <jonasschnelli> Okay... Let me update the BIP. I think this iterative improvement approach might lead to something we can use (at least use it for later improvments).
1522016-03-26T08:37:34  *** ChillazZ has joined #bitcoin-core-dev
1532016-03-26T08:38:07  *** anttea has quit IRC
1542016-03-26T08:43:55  *** Guyver2 has joined #bitcoin-core-dev
1552016-03-26T08:44:09  *** mesmer has joined #bitcoin-core-dev
1562016-03-26T08:48:25  *** ChillazZ has quit IRC
1572016-03-26T08:48:26  *** ChillazZ has joined #bitcoin-core-dev
1582016-03-26T08:48:26  *** anttea has joined #bitcoin-core-dev
1592016-03-26T08:48:26  *** ChillazZ has quit IRC
1602016-03-26T08:48:54  *** p15 has quit IRC
1612016-03-26T08:49:13  *** anttea has quit IRC
1622016-03-26T08:54:05  *** JeromeLegoupil has joined #bitcoin-core-dev
1632016-03-26T08:55:31  *** anttea has joined #bitcoin-core-dev
1642016-03-26T08:55:31  *** ChillazZ has joined #bitcoin-core-dev
1652016-03-26T08:55:32  *** anttea has quit IRC
1662016-03-26T08:56:07  *** anttea has joined #bitcoin-core-dev
1672016-03-26T08:56:48  *** Thireus has quit IRC
1682016-03-26T08:57:08  *** Thireus has joined #bitcoin-core-dev
1692016-03-26T08:59:54  *** ChillazZ has quit IRC
1702016-03-26T09:04:11  *** anttea has quit IRC
1712016-03-26T09:07:32  *** JeromeLegoupil has quit IRC
1722016-03-26T09:14:20  *** ChillazZ has joined #bitcoin-core-dev
1732016-03-26T09:18:55  *** anttea has joined #bitcoin-core-dev
1742016-03-26T09:19:35  *** ChillazZ has quit IRC
1752016-03-26T09:32:12  *** laurentmt has joined #bitcoin-core-dev
1762016-03-26T09:32:39  *** laurentmt has quit IRC
1772016-03-26T09:37:04  *** anttea has quit IRC
1782016-03-26T09:47:36  *** ChillazZ has joined #bitcoin-core-dev
1792016-03-26T09:47:37  *** anttea has joined #bitcoin-core-dev
1802016-03-26T09:51:19  *** ChillazZ has quit IRC
1812016-03-26T09:51:37  *** ChillazZ has joined #bitcoin-core-dev
1822016-03-26T09:55:16  *** anttea has joined #bitcoin-core-dev
1832016-03-26T10:03:02  *** anttea has quit IRC
1842016-03-26T10:03:02  *** anttea has joined #bitcoin-core-dev
1852016-03-26T10:10:12  *** anttea has quit IRC
1862016-03-26T10:10:13  *** ChillazZ has quit IRC
1872016-03-26T10:11:37  *** ChillazZ has joined #bitcoin-core-dev
1882016-03-26T10:11:38  *** anttea has joined #bitcoin-core-dev
1892016-03-26T10:16:36  *** anttea has quit IRC
1902016-03-26T10:16:36  *** anttea has joined #bitcoin-core-dev
1912016-03-26T10:23:02  *** Guyver2 has quit IRC
1922016-03-26T10:31:44  *** ChillazZ has quit IRC
1932016-03-26T10:31:45  *** anttea has quit IRC
1942016-03-26T10:37:15  *** anttea has joined #bitcoin-core-dev
1952016-03-26T10:38:57  *** anttea has quit IRC
1962016-03-26T10:53:44  *** anttea has joined #bitcoin-core-dev
1972016-03-26T10:58:00  *** ChillazZ has joined #bitcoin-core-dev
1982016-03-26T10:58:26  *** anttea has quit IRC
1992016-03-26T11:05:31  *** anttea has joined #bitcoin-core-dev
2002016-03-26T11:05:31  *** ChillazZ has quit IRC
2012016-03-26T11:06:11  *** anttea has quit IRC
2022016-03-26T11:07:39  *** anttea has joined #bitcoin-core-dev
2032016-03-26T11:14:54  *** anttea has quit IRC
2042016-03-26T11:14:55  *** ChillazZ has joined #bitcoin-core-dev
2052016-03-26T11:17:34  *** ChillazZ has quit IRC
2062016-03-26T11:19:28  *** anttea has joined #bitcoin-core-dev
2072016-03-26T11:24:31  *** anttea has quit IRC
2082016-03-26T11:24:42  *** anttea has joined #bitcoin-core-dev
2092016-03-26T11:33:15  *** ChillazZ has joined #bitcoin-core-dev
2102016-03-26T11:54:03  *** randy-waterhouse has quit IRC
2112016-03-26T12:32:00  *** LordByron has joined #bitcoin-core-dev
2122016-03-26T12:42:20  *** belcher has joined #bitcoin-core-dev
2132016-03-26T13:38:08  *** ChillazZ has quit IRC
2142016-03-26T13:38:24  *** ChillazZ has joined #bitcoin-core-dev
2152016-03-26T13:50:46  *** d_t has joined #bitcoin-core-dev
2162016-03-26T13:52:56  <GitHub145> [bitcoin] mruddy opened pull request #7748: test and regtest mempool: not require standard, non-mandatory, input script verification flags (master...nonstandard-sighash) https://github.com/bitcoin/bitcoin/pull/7748
2172016-03-26T13:55:10  *** d_t has quit IRC
2182016-03-26T14:08:27  *** achow101 has joined #bitcoin-core-dev
2192016-03-26T14:25:07  *** supasonic has joined #bitcoin-core-dev
2202016-03-26T14:33:56  *** achow101 has quit IRC
2212016-03-26T14:34:49  *** achow101 has joined #bitcoin-core-dev
2222016-03-26T14:50:04  *** JeromeLegoupil has joined #bitcoin-core-dev
2232016-03-26T15:56:10  *** achow101 has quit IRC
2242016-03-26T15:56:57  *** achow101 has joined #bitcoin-core-dev
2252016-03-26T15:58:10  *** achow101 has quit IRC
2262016-03-26T15:58:54  *** achow101 has joined #bitcoin-core-dev
2272016-03-26T16:00:22  *** Denker has joined #bitcoin-core-dev
2282016-03-26T16:02:40  *** achow101 has quit IRC
2292016-03-26T16:03:15  *** Chris_Stewart_5 has quit IRC
2302016-03-26T16:03:26  *** achow101 has joined #bitcoin-core-dev
2312016-03-26T16:09:13  *** laurentmt has joined #bitcoin-core-dev
2322016-03-26T16:09:48  *** laurentmt has quit IRC
2332016-03-26T16:11:02  *** Tasoshi has quit IRC
2342016-03-26T16:12:28  *** Tasoshi has joined #bitcoin-core-dev
2352016-03-26T16:58:45  *** BCBot has quit IRC
2362016-03-26T17:02:26  *** BCBot has joined #bitcoin-core-dev
2372016-03-26T17:15:03  *** AaronvanW has quit IRC
2382016-03-26T18:14:29  *** BCBot has quit IRC
2392016-03-26T18:19:55  *** BCBot has joined #bitcoin-core-dev
2402016-03-26T18:24:41  *** Chris_Stewart_5 has joined #bitcoin-core-dev
2412016-03-26T18:37:09  *** Chris_Stewart_5 has quit IRC
2422016-03-26T18:39:03  *** JeromeLegoupil has quit IRC
2432016-03-26T18:50:11  *** JeromeLegoupil has joined #bitcoin-core-dev
2442016-03-26T19:02:44  *** JeromeLegoupil has quit IRC
2452016-03-26T19:09:00  *** ChillazZ has quit IRC
2462016-03-26T19:09:00  *** ChillazZ has joined #bitcoin-core-dev
2472016-03-26T19:25:03  *** JeromeLegoupil has joined #bitcoin-core-dev
2482016-03-26T19:33:49  *** Chris_Stewart_5 has joined #bitcoin-core-dev
2492016-03-26T19:33:52  *** d_t has joined #bitcoin-core-dev
2502016-03-26T19:38:44  *** laurentmt has joined #bitcoin-core-dev
2512016-03-26T19:38:50  *** laurentmt has quit IRC
2522016-03-26T19:40:25  *** AaronvanW has joined #bitcoin-core-dev
2532016-03-26T20:03:01  *** Alopex has quit IRC
2542016-03-26T20:04:06  *** Alopex has joined #bitcoin-core-dev
2552016-03-26T20:06:36  *** Chris_Stewart_5 has quit IRC
2562016-03-26T20:19:05  <GitHub135> [bitcoin] sipa opened pull request #7749: Enforce expected outbound services (master...checkservices) https://github.com/bitcoin/bitcoin/pull/7749
2572016-03-26T20:19:34  *** JeromeLegoupil has quit IRC
2582016-03-26T20:21:41  *** hybridsole has quit IRC
2592016-03-26T20:35:39  *** JeromeLegoupil has joined #bitcoin-core-dev
2602016-03-26T20:51:34  *** Guyver2 has joined #bitcoin-core-dev
2612016-03-26T21:19:28  *** Chris_Stewart_5 has joined #bitcoin-core-dev
2622016-03-26T21:25:34  *** JeromeLegoupil has quit IRC
2632016-03-26T21:27:58  *** JeromeLegoupil has joined #bitcoin-core-dev
2642016-03-26T21:30:48  *** supasonic has quit IRC
2652016-03-26T21:31:15  *** supasonic has joined #bitcoin-core-dev
2662016-03-26T21:34:28  *** Don_John has joined #bitcoin-core-dev
2672016-03-26T21:39:57  *** JeromeLegoupil has quit IRC
2682016-03-26T21:41:51  *** JeromeLegoupil has joined #bitcoin-core-dev
2692016-03-26T21:43:04  *** Chris_Stewart_5 has quit IRC
2702016-03-26T21:44:01  *** anttea has quit IRC
2712016-03-26T21:44:07  *** anttea has joined #bitcoin-core-dev
2722016-03-26T21:54:12  *** hybridsole has joined #bitcoin-core-dev
2732016-03-26T22:01:01  *** Ylbam has quit IRC
2742016-03-26T22:08:04  *** fkhan_ has quit IRC
2752016-03-26T22:21:45  *** fkhan_ has joined #bitcoin-core-dev
2762016-03-26T22:36:02  *** frankenmint has quit IRC
2772016-03-26T22:37:04  *** Ylbam has joined #bitcoin-core-dev
2782016-03-26T23:07:08  *** Guyver2 has quit IRC
2792016-03-26T23:36:57  *** supasonic has quit IRC
2802016-03-26T23:54:51  *** kanzure has quit IRC
2812016-03-26T23:54:51  *** heath has quit IRC