--- Day changed Wed Nov 26 2014 00:02 -!- gues_ [~gues@cpe-66-68-54-206.austin.res.rr.com] has quit [Ping timeout: 255 seconds] 00:04 -!- gues [~gues@se5x.mullvad.net] has joined #bitcoin-wizards 00:05 -!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has quit [Quit: Leaving] 00:06 -!- AaronvanW [~ewout@255pc208.sshunet.nl] has joined #bitcoin-wizards 00:06 -!- AaronvanW [~ewout@255pc208.sshunet.nl] has quit [Remote host closed the connection] 00:12 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #bitcoin-wizards 00:17 -!- heropan [835ebaa0@gateway/web/freenode/ip.131.94.186.160] has joined #bitcoin-wizards 00:21 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…] 00:26 -!- adam3us [~Adium@host-92-19-90-29.as13285.net] has joined #bitcoin-wizards 00:27 -!- fanquake [~anonymous@unaffiliated/fanquake] has quit [Quit: fanquake] 00:33 -!- damethos [~damethos@unaffiliated/damethos] has joined #bitcoin-wizards 00:43 -!- heropan [835ebaa0@gateway/web/freenode/ip.131.94.186.160] has quit [Quit: Page closed] 00:48 < gmaxwell> rusty: there are some writeups on that stuff elsewhere on this too, it's a kind of notion that is in a kind of unfortunate valley where its merely engineering work and not interesting to the academics, but big enough engineering work that it doesn't have super short term impact on bitcoin. 00:50 -!- cbeams [~cbeams@unaffiliated/cbeams] has joined #bitcoin-wizards 00:51 -!- AaronvanW [~ewout@255pc208.sshunet.nl] has joined #bitcoin-wizards 00:52 -!- cbeams [~cbeams@unaffiliated/cbeams] has quit [Read error: Connection reset by peer] 01:03 -!- cbeams [~cbeams@chello084114181075.1.15.vie.surfer.at] has joined #bitcoin-wizards 01:03 -!- cbeams [~cbeams@chello084114181075.1.15.vie.surfer.at] has quit [Changing host] 01:03 -!- cbeams [~cbeams@unaffiliated/cbeams] has joined #bitcoin-wizards 01:05 -!- andy-logbot [~bitcoin--@wpsoftware.net] has quit [Remote host closed the connection] 01:05 -!- andy-logbot [~bitcoin--@wpsoftware.net] has joined #bitcoin-wizards 01:05 * andy-logbot is logging 01:16 -!- adam3us [~Adium@host-92-19-90-29.as13285.net] has quit [Read error: Connection reset by peer] 01:18 -!- adam3us [~Adium@host-92-19-90-29.as13285.net] has joined #bitcoin-wizards 01:20 -!- hearn [~mike@84-75-198-85.dclient.hispeed.ch] has joined #bitcoin-wizards 01:28 -!- shesek [~shesek@77.125.14.5] has quit [Ping timeout: 240 seconds] 01:33 < rusty> gmaxwell: One difference between your suggestions and mine which I'd be interested in your thoughts. I hashed with each transaction an array of backrefs (ie. blocks ago, transaction number), to allow proving an unknown input. That seems simpler than trees of UTXOs + produced + consumed outputs. 01:33 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has joined #bitcoin-wizards 01:34 < gmaxwell> rusty: then you cannot spend an unconfirmed transaction? The design of bitcoin strongly decouples the transactions themselves from the chain; the chain just provides ordering, the txn themselves exist freestanding and can be validated independantly of the chain. 01:35 < rusty> gmaxwell: blocksago == 0, though my implementation didn't do that. 01:35 < gmaxwell> I mean, say you author a transaction spend ago 0 but then the unconfirmed confirms, but the spend hasn't yet. 01:36 < gmaxwell> or the chain reorgs harmlessly, have you now invalidated transactions and require signers to come back out of their valults to resign? 01:36 < rusty> gmaxwell: no, backrefs are inserted by miners, not part of transactions. 01:37 -!- cbeams [~cbeams@unaffiliated/cbeams] has quit [Ping timeout: 258 seconds] 01:37 < rusty> gmaxwell: they're simply extra metadata. 01:37 < gmaxwell> oh, if it's not part of transactions then it's probably isomorphic. 01:38 < gmaxwell> upto perhaps some efficiency differences. Commited state is something we've long wanted more of because it's useful for many other things, not just incremental validation... so that probably colors my assumptions. 01:38 < gmaxwell> hm. actually if its just backrefs how do you incrementally discover a double spend? 01:39 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-wizards 01:39 < gmaxwell> e.g. tx10 spends coin A. You can form a backref to tx1 creating it... but really in the middle tx5 already spent that coin. 01:40 < rusty> gmaxwell: it doesn't detect ds by itself, no 01:41 < gmaxwell> Oh well with state commitments you can detect the double spends without there existing any full nodes. 01:41 < rusty> gmaxwell: since the network is divided into shards, and the txs are ordered (such that same shard txs are adjacent), you'll detect ds anyway. 01:42 < rusty> gmaxwell: yes, in your scheme even miners don't need to be full nodes. That's pretty sweet. 01:44 -!- wallet42 [~wallet42@unaffiliated/wallet42] has quit [Quit: Leaving.] 01:44 < gmaxwell> Are you making an additional assumption there. E.g. that there exists some node X who isn't me, who will check all of Y or my probablity of detection of a doublespend in Y is zero. (not sure if thats materially worse that 'my probablity of detecting is at least $small, even if I am almost alone in being honest'; different in any case) 01:45 -!- adlai [~Adlai@gateway/tor-sasl/adlai] has quit [Remote host closed the connection] 01:46 -!- adlai [~Adlai@gateway/tor-sasl/adlai] has joined #bitcoin-wizards 01:48 -!- comboy_ is now known as comboy 01:51 < rusty> gmaxwell: sorry, was distracted. 01:52 < rusty> gmaxwell: assumption is that every node has full knowledge of at least 2 shards, so probability should be low. 01:53 < rusty> gmaxwell: Simplified txs only allow inputs and outputs to cross two shards, which helps. 01:54 -!- hashtag [~hashtag@69.23.213.3] has joined #bitcoin-wizards 01:54 < rusty> gmaxwell: it's trivially easy to tell if you know all txs out of your shard (due to tx ordering in block), txs in are best-effort. 01:55 < gmaxwell> okay, too tired to think about the implications of that, its a very different design. 01:56 < gmaxwell> I'm not sure what it gains over a design with a common merkelized state. May be more obvious to me in the morning. 01:56 < rusty> gmaxwell: yeah, I had to bend things pretty badly to make it work :(. That's why I'm coming around to your scheme. 01:57 < rusty> gmaxwell: oh, and in practice the tx+amount hashtree will probably have to be in addition to the normal tx hashtree, assuming sidechains have to look bitcoin-like for tx proofs. 01:58 < gmaxwell> well sidechains only should have to look bitcoin like enough for the recovery txn, the other parts could be fairly different. 01:58 < gmaxwell> Here is a fun additional thought that I hadn't had back when that text was written. Imagine you are a thin client, and there are several full nodes claiming different things about the validity of a given block. Also imagine that the bitcoin blockchain and its commitments is unchanged as it is now. 01:59 < gmaxwell> It's actually possible for our hapless litenode to figure figure out the truth if at least one of their peers is telling the truth with only O(log()) queries. 02:00 < phantomcircuit> i think you accidentally n 02:01 < gmaxwell> if I'm truncated tell me where. 02:02 < rusty> gmaxwell: well, AFAICT an honest node can disprove any spurious claim (eg. "that input never existed!", which is the hard one). 02:02 < phantomcircuit> O(log()) 02:02 < phantomcircuit> O(log(n)) 02:02 < gmaxwell> The notion is that the peers keep merkelized transcripts of their validation progress along the chain (e.g. all the data they looked up and what its results were, etc). If no one is faulty, the hashes will agree (process is determinstic). If the hashes don't agree then you can do a log() operations search against a pair of peers to find the point where they diverge. Then check to see which of them follows the rules. 02:02 < phantomcircuit> har har 02:03 < gmaxwell> rusty: at the time I'd written that text I'd assumed it was impossible to efficiently prove, e.g. "the subsidy paid out in this block is correct". with the current blockchain structure... not without giving the peer all the transactions being spent (which can be a _lot_ of data) 02:04 < gmaxwell> and thats so, in a non-interactive context, unless there are additional commitments as the proofs page talks about... but in the interactive context there don't even need to be blockchain data changes.. which is interesting at least. 02:05 < rusty> gmaxwell: I see, but this still assumes a full peer exists. If the miner is the only one who knows the entire block, you still need your enhancements as no one can call her on it. I preferred the original "no full nodes" premise: more ambitious :) 02:06 < gmaxwell> yea sure sure. Just an additional thought. The more complete vision is more interesting. 02:07 < gmaxwell> But the technique used for the interactive thing could be used to provide all kinds of interesting summaries of blockchain data, that you might not want general nodes being responsible for maintaining, and thats kind of neat too. 02:07 < gmaxwell> (just thought I'd mention it because it was the sort of thing I wish I'd realized earlier.) 02:09 -!- OX3_ [~OX3@gateway-nat.fmrib.ox.ac.uk] has joined #bitcoin-wizards 02:17 -!- shesek [~shesek@77.126.188.37] has joined #bitcoin-wizards 02:21 -!- hearn [~mike@84-75-198-85.dclient.hispeed.ch] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…] 02:25 -!- todaystomorrow [~me@d122-111-39-14.bla803.nsw.optusnet.com.au] has joined #bitcoin-wizards 02:27 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has quit [Remote host closed the connection] 02:33 -!- Shiftos [~shiftos@gateway/tor-sasl/shiftos] has quit [Remote host closed the connection] 02:33 -!- Shiftos_ [~shiftos@gateway/tor-sasl/shiftos] has joined #bitcoin-wizards 02:33 -!- Shiftos_ is now known as Shiftos 02:37 -!- prodatalab [~prodatala@c-69-254-45-177.hsd1.fl.comcast.net] has quit [Quit: Konversation terminated!] 02:42 -!- c0rw|sleep is now known as c0rw1n 02:44 -!- RoboTedd_ [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has quit [Ping timeout: 255 seconds] 02:45 -!- jb55 [~jb55@S0106f46d049a0b83.vc.shawcable.net] has quit [Remote host closed the connection] 02:47 -!- cfields is now known as cfields-away 02:47 -!- shesek [~shesek@77.126.188.37] has quit [Ping timeout: 258 seconds] 02:48 -!- coke0 [~coke0@2607:fb90:1501:fc2b:1784:1978:46e0:909c] has joined #bitcoin-wizards 02:48 -!- CoinMuncher [~jannes@178.132.211.90] has joined #bitcoin-wizards 02:51 -!- shesek [~shesek@77.127.97.249] has joined #bitcoin-wizards 02:51 -!- coke0_ [~coke0@pool-108-21-231-34.nycmny.fios.verizon.net] has quit [Ping timeout: 240 seconds] 02:55 -!- Sub|afk [~SubCreati@c-76-121-19-166.hsd1.wa.comcast.net] has joined #bitcoin-wizards 02:55 -!- prodatalab [~prodatala@c-69-254-45-177.hsd1.fl.comcast.net] has joined #bitcoin-wizards 02:58 -!- SubCreative [~SubCreati@unaffiliated/cannacoin] has quit [Ping timeout: 258 seconds] 03:01 -!- hearn [~mike@85-26.104-92.cust.bluewin.ch] has joined #bitcoin-wizards 03:02 -!- todays_tomorrow [~me@d114-78-114-23.bla803.nsw.optusnet.com.au] has joined #bitcoin-wizards 03:03 -!- cbeams [~cbeams@unaffiliated/cbeams] has joined #bitcoin-wizards 03:06 -!- todaystomorrow [~me@d122-111-39-14.bla803.nsw.optusnet.com.au] has quit [Ping timeout: 255 seconds] 03:06 -!- gavinandresen [~gavin@unaffiliated/gavinandresen] has joined #bitcoin-wizards 03:10 -!- fanquake [~anonymous@unaffiliated/fanquake] has joined #bitcoin-wizards 03:14 -!- samson_ [~samson_@180.183.83.162] has quit [Ping timeout: 255 seconds] 03:16 -!- samson_ [~samson_@183.89.175.103] has joined #bitcoin-wizards 03:19 -!- samson_ [~samson_@183.89.175.103] has quit [Client Quit] 03:19 -!- jtimon [~quassel@43.Red-176-83-168.dynamicIP.rima-tde.net] has joined #bitcoin-wizards 03:19 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has joined #bitcoin-wizards 03:24 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has quit [Ping timeout: 265 seconds] 03:28 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has joined #bitcoin-wizards 03:38 -!- jtimon [~quassel@43.Red-176-83-168.dynamicIP.rima-tde.net] has quit [Ping timeout: 255 seconds] 03:39 -!- jtimon [~quassel@195.Red-176-83-170.dynamicIP.rima-tde.net] has joined #bitcoin-wizards 03:41 -!- c0rw1n [~c0rw1n@129.66-67-87.adsl-dyn.isp.belgacom.be] has quit [Read error: Connection reset by peer] 03:41 -!- c0rw1n_ [~c0rw1n@129.66-67-87.adsl-dyn.isp.belgacom.be] has joined #bitcoin-wizards 03:43 -!- c0rw1n_ is now known as c0rw1n 03:43 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has quit [Remote host closed the connection] 03:50 -!- bifforoni [~zorin@bzq-84-108-84-113.cablep.bezeqint.net] has joined #bitcoin-wizards 03:52 -!- jtimon [~quassel@195.Red-176-83-170.dynamicIP.rima-tde.net] has quit [Ping timeout: 265 seconds] 03:53 -!- damethos [~damethos@unaffiliated/damethos] has quit [Quit: Bye] 03:56 -!- CoinMuncher [~jannes@178.132.211.90] has quit [Quit: Leaving.] 03:59 -!- fanquake [~anonymous@unaffiliated/fanquake] has quit [Quit: fanquake] 03:59 -!- samson_ [~samson_@180.183.80.164] has joined #bitcoin-wizards 04:03 -!- hearn [~mike@85-26.104-92.cust.bluewin.ch] has quit [Quit: Textual IRC Client: www.textualapp.com] 04:06 -!- atgreen [~user@CPE687f74122463-CM84948c2e0610.cpe.net.cable.rogers.com] has joined #bitcoin-wizards 04:08 -!- eristisk [~eristisk@gateway/tor-sasl/eristisk] has quit [Remote host closed the connection] 04:09 -!- op_null [~op_null@178.62.133.216] has quit [Quit: Lost terminal] 04:16 -!- coke0_ [~coke0@pool-108-21-231-34.nycmny.fios.verizon.net] has joined #bitcoin-wizards 04:18 -!- Aquent [~Aquent@gateway/tor-sasl/aquent] has quit [Remote host closed the connection] 04:19 -!- coke0 [~coke0@2607:fb90:1501:fc2b:1784:1978:46e0:909c] has quit [Ping timeout: 265 seconds] 04:21 -!- nubbins` [~leel@stjhnf0157w-047055221135.dhcp-dynamic.FibreOp.nl.bellaliant.net] has joined #bitcoin-wizards 04:21 -!- nubbins` [~leel@stjhnf0157w-047055221135.dhcp-dynamic.FibreOp.nl.bellaliant.net] has quit [Changing host] 04:21 -!- nubbins` [~leel@unaffiliated/nubbins] has joined #bitcoin-wizards 04:26 -!- coke0 [~coke0@172.56.18.120] has joined #bitcoin-wizards 04:27 -!- fanquake [~anonymous@unaffiliated/fanquake] has joined #bitcoin-wizards 04:28 -!- coke0_ [~coke0@pool-108-21-231-34.nycmny.fios.verizon.net] has quit [Ping timeout: 240 seconds] 04:35 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has joined #bitcoin-wizards 04:39 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has quit [Remote host closed the connection] 04:44 -!- coke0 [~coke0@172.56.18.120] has quit [Ping timeout: 245 seconds] 04:45 -!- fanquake [~anonymous@unaffiliated/fanquake] has quit [Quit: fanquake] 04:46 -!- coke0 [~coke0@pool-108-21-231-34.nycmny.fios.verizon.net] has joined #bitcoin-wizards 04:51 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has joined #bitcoin-wizards 04:58 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has quit [Remote host closed the connection] 04:59 -!- wallet42 [~wallet42@unaffiliated/wallet42] has joined #bitcoin-wizards 05:04 -!- OX3__ [~OX3@gateway-nat.fmrib.ox.ac.uk] has joined #bitcoin-wizards 05:07 -!- OX3_ [~OX3@gateway-nat.fmrib.ox.ac.uk] has quit [Ping timeout: 250 seconds] 05:08 -!- bifforoni [~zorin@bzq-84-108-84-113.cablep.bezeqint.net] has quit [Quit: Leaving] 05:09 -!- maraoz [~maraoz@186.137.72.181] has joined #bitcoin-wizards 05:12 -!- damethos [~damethos@unaffiliated/damethos] has joined #bitcoin-wizards 05:20 -!- eristisk [~eristisk@gateway/tor-sasl/eristisk] has joined #bitcoin-wizards 05:20 -!- Starduster_ [~Guest1@unaffiliated/starduster] has quit [Read error: Connection reset by peer] 05:22 -!- coke0_ [~coke0@172.56.18.120] has joined #bitcoin-wizards 05:23 -!- cbeams [~cbeams@unaffiliated/cbeams] has quit [Remote host closed the connection] 05:24 -!- Starduster [~Guest1@unaffiliated/starduster] has joined #bitcoin-wizards 05:24 -!- coke0 [~coke0@pool-108-21-231-34.nycmny.fios.verizon.net] has quit [Ping timeout: 245 seconds] --- Log closed Wed Nov 26 05:26:20 2014 --- Log opened Wed Nov 26 05:26:48 2014 05:26 -!- kanzure_ [~kanzure@131.252.130.248] has joined #bitcoin-wizards 05:26 -!- Irssi: #bitcoin-wizards: Total of 195 nicks [1 ops, 0 halfops, 0 voices, 194 normal] --- Log closed Wed Nov 26 05:26:53 2014 --- Log opened Wed Nov 26 05:31:50 2014 05:31 -!- kanzure [~kanzure@131.252.130.248] has joined #bitcoin-wizards 05:31 -!- Irssi: #bitcoin-wizards: Total of 189 nicks [1 ops, 0 halfops, 0 voices, 188 normal] 05:32 -!- fanquake [~anonymous@unaffiliated/fanquake] has joined #bitcoin-wizards 05:33 -!- fenn [~fenn@131.252.130.248] has joined #bitcoin-wizards 05:33 -!- heath [~ybit@131.252.130.248] has joined #bitcoin-wizards 05:36 -!- luny [~luny@unaffiliated/luny] has quit [Read error: Connection reset by peer] 05:37 -!- coke0 [~coke0@2607:fb90:1f02:7c44:db01:5756:91e2:ee58] has joined #bitcoin-wizards --- Log closed Wed Nov 26 05:42:50 2014 --- Log opened Wed Nov 26 05:43:29 2014 05:43 -!- kanzure [~kanzure@131.252.130.248] has joined #bitcoin-wizards 05:43 -!- Irssi: #bitcoin-wizards: Total of 190 nicks [1 ops, 0 halfops, 0 voices, 189 normal] 05:44 -!- gnusha [~gnusha@131.252.130.248] has joined #bitcoin-wizards 05:45 -!- OX3_ [~OX3@gateway-nat.fmrib.ox.ac.uk] has joined #bitcoin-wizards 05:45 -!- heath [~ybit@131.252.130.248] has joined #bitcoin-wizards 05:45 -!- fenn [~fenn@131.252.130.248] has joined #bitcoin-wizards 05:47 -!- cbeams [~cbeams@chello084114181075.1.15.vie.surfer.at] has joined #bitcoin-wizards 05:47 -!- cbeams [~cbeams@chello084114181075.1.15.vie.surfer.at] has quit [Changing host] 05:47 -!- cbeams [~cbeams@unaffiliated/cbeams] has joined #bitcoin-wizards 05:48 -!- OX3__ [~OX3@gateway-nat.fmrib.ox.ac.uk] has quit [Ping timeout: 264 seconds] 05:48 -!- cbeams [~cbeams@unaffiliated/cbeams] has quit [Remote host closed the connection] 05:50 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has quit [Remote host closed the connection] 05:52 -!- hguux_ [sid17919@gateway/web/irccloud.com/x-ltzxsqjetxpnnggy] has quit [Ping timeout: 258 seconds] --- Log closed Wed Nov 26 05:57:54 2014 --- Log opened Wed Nov 26 05:58:54 2014 05:58 -!- kanzure_ [~kanzure@131.252.130.248] has joined #bitcoin-wizards 05:58 -!- Irssi: #bitcoin-wizards: Total of 196 nicks [1 ops, 0 halfops, 0 voices, 195 normal] 05:58 !morgan.freenode.net [freenode-info] please register your nickname...don't forget to auto-identify! http://freenode.net/faq.shtml#nicksetup 06:00 -!- fenn [~fenn@131.252.130.248] has quit [Ping timeout: 272 seconds] 06:00 -!- kanzure [~kanzure@131.252.130.248] has quit [Ping timeout: 264 seconds] 06:00 -!- heath [~ybit@131.252.130.248] has quit [Ping timeout: 272 seconds] 06:06 -!- hashtag [~hashtag@69.23.213.3] has quit [Ping timeout: 255 seconds] 06:08 -!- You're now known as kanzure 06:09 -!- michagogo [uid14316@wikia/Michagogo] has quit [Ping timeout: 258 seconds] 06:10 -!- michagogo [uid14316@wikia/Michagogo] has joined #bitcoin-wizards 06:12 -!- Irssi: Join to #bitcoin-wizards was synced in 821 secs 06:16 -!- Quanttek [~quassel@ip1f12e8be.dynamic.kabel-deutschland.de] has joined #bitcoin-wizards 06:17 -!- Quanttek [~quassel@ip1f12e8be.dynamic.kabel-deutschland.de] has quit [Read error: Connection reset by peer] 06:21 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has joined #bitcoin-wizards 06:22 -!- hashtag [~hashtag@CPE-69-23-213-3.wi.res.rr.com] has joined #bitcoin-wizards 06:23 -!- fanquake [~anonymous@unaffiliated/fanquake] has quit [Quit: Sleeping] 06:24 -!- coiner [~linker@113.161.87.238] has quit [Ping timeout: 265 seconds] 06:25 -!- Quanttek [~quassel@2a02:8108:d00:870:fd5f:b2fa:2f28:d1b5] has joined #bitcoin-wizards 06:26 -!- hashtag [~hashtag@CPE-69-23-213-3.wi.res.rr.com] has quit [Ping timeout: 240 seconds] 06:26 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has quit [Ping timeout: 255 seconds] --- Log closed Wed Nov 26 06:33:09 2014 --- Log opened Wed Nov 26 12:12:07 2014 12:12 -!- kanzure [~kanzure@131.252.130.248] has joined #bitcoin-wizards 12:12 -!- Irssi: #bitcoin-wizards: Total of 201 nicks [1 ops, 0 halfops, 0 voices, 200 normal] 12:13 -!- Shiftos [~shiftos@gateway/tor-sasl/shiftos] has joined #bitcoin-wizards 12:14 -!- hearn [~mike@84-75-198-85.dclient.hispeed.ch] has joined #bitcoin-wizards 12:17 -!- heath [~ybit@131.252.130.248] has quit [Changing host] 12:17 -!- heath [~ybit@unaffiliated/ybit] has joined #bitcoin-wizards 12:19 -!- belcher [~belcher-s@5ec18bcf.skybroadband.com] has joined #bitcoin-wizards 12:19 -!- belcher [~belcher-s@5ec18bcf.skybroadband.com] has quit [Changing host] 12:19 -!- belcher [~belcher-s@unaffiliated/belcher] has joined #bitcoin-wizards 12:20 < bramm> The problem with finding things which require random access lookups is that there are lots of ways of leveraging sorting very effectively 12:21 -!- bitbumper [~bitbumper@c-69-254-243-205.hsd1.ks.comcast.net] has quit [Quit: Leaving] 12:21 < bramm> So you have to come up with a problem which somehow forces actual random accesses rather than repeated sorts 12:22 < tromp_> it's hard to imagine sorting being effective at finding cycles 12:22 < bramm> If you're looking for a cycle of length N you can do it with N sorts 12:23 < bramm> Which might require more memory but fewer random accesses 12:24 -!- belcher [~belcher-s@unaffiliated/belcher] has quit [Ping timeout: 250 seconds] 12:25 -!- Irssi: Join to #bitcoin-wizards was synced in 843 secs 12:25 < bramm> Really using memory and doing random accesses are two different kinds of work 12:26 -!- maaku_ [~quassel@50-0-37-37.dsl.static.fusionbroadband.com] has joined #bitcoin-wizards 12:27 -!- prepost [~rs232@184.7.34.95.customer.cdi.no] has joined #bitcoin-wizards 12:27 -!- prepost [~rs232@184.7.34.95.customer.cdi.no] has quit [Client Quit] 12:27 -!- prepost [~rs232@184.7.34.95.customer.cdi.no] has joined #bitcoin-wizards 12:27 -!- AnoAnon [~AnoAnon@197.37.73.249] has joined #bitcoin-wizards 12:27 -!- AnoAnon [~AnoAnon@197.37.73.249] has quit [Max SendQ exceeded] 12:27 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has joined #bitcoin-wizards 12:28 -!- belcher [~belcher-s@5ec18bcf.skybroadband.com] has joined #bitcoin-wizards 12:28 -!- belcher [~belcher-s@5ec18bcf.skybroadband.com] has quit [Changing host] 12:28 -!- belcher [~belcher-s@unaffiliated/belcher] has joined #bitcoin-wizards --- Log opened Wed Nov 26 19:27:23 2014 19:27 -!- kanzure [~kanzure@unaffiliated/kanzure] has joined #bitcoin-wizards 19:27 -!- Irssi: #bitcoin-wizards: Total of 188 nicks [1 ops, 0 halfops, 0 voices, 187 normal] 19:28 < tromp> the footnote explains that micro nonces generate edges and another nonce generates the key 19:28 < zooko> tromp: yes, I know. 19:28 < tromp> calling the latter the macro nonce 19:29 < tromp> it's a suggested language for ppl discussing the paper 19:29 < zooko> I'm saying, it is unnecessarily confusing to introduce the word "macro nonce" when it is used only one time, and that time is mostly just to point out that you shouldn't confuse it with the micro nonce. 19:29 < zooko> Okay. 19:29 < zooko> Also, what I really wanted was an explanation of how the macro nonce would be chosen. 19:30 < tromp> i want to save ppl the trouble from talking in terms of "that other nonce that generates the hash key" 19:30 < zooko> I suppose that's outside the scope of cuckoo per se, but I imagine it is something like sha256(previous-block-hash | macro-nonce). 19:31 < tromp> it;s sha256(header) where header has many fields including those but also merkle root and timestamp for instance 19:31 -!- samson_ [~samson_@183.89.21.106] has joined #bitcoin-wizards 19:32 -!- MoALTz__ [~no@user-46-113-21-204.play-internet.pl] has joined #bitcoin-wizards 19:35 -!- MoALTz_ [~no@user-46-113-21-204.play-internet.pl] has quit [Ping timeout: 264 seconds] 19:36 -!- Irssi: Join to #bitcoin-wizards was synced in 570 secs 19:37 -!- samson2 [~samson_@180.183.82.97] has joined #bitcoin-wizards 19:38 -!- samson_ [~samson_@183.89.21.106] has quit [Ping timeout: 255 seconds] 19:40 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has joined #bitcoin-wizards 19:41 -!- samson2 [~samson_@180.183.82.97] has quit [Ping timeout: 245 seconds] 19:41 < tromp> the macro nonce is chosen just as it is with bitcoin's pow 19:42 < tromp> in whatever way suits the miner 19:42 < tromp> that's simply outside of the pow's scope 19:42 < op_null> primes give me a warm feeling. 19:42 < op_null> go with primes. 19:43 < tromp> i mention primes in my paper, just to give you thatr warm feeling 19:43 < tromp> but found no use for them in my pow:( 19:43 < op_null> oh you 19:44 < tromp> op_null maybe you can do some gapcoin mining 19:44 < tromp> to gain more warmth 19:45 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has quit [Ping timeout: 245 seconds] 19:46 < op_null> I don't think I've mentioned it before, but I *really* like the way you handle cuckoo cycle. it's not presented as magic to save the world, you're not hounding other people to use it or like it. I'm not sure if it's right or desirable, but I certainly don't mind discussing it with you. 19:46 -!- samson_ [~samson_@180.183.167.124] has joined #bitcoin-wizards 19:46 < tromp> btw, they came up with this brilliant logo: https://bitcointalk.org/index.php?topic=822498.msg9493423#msg9493423 19:47 < op_null> what on earth is gapcoin 19:47 < tromp> thx, op_null. appreciate that 19:47 < tromp> it's the latest prime flavored PoW 19:47 < tromp> pretty neat actually 19:48 < op_null> does it have the problem primecoin does where it blows up the block header and is insane to verify? 19:49 < tromp> i'm not familiar with it 19:49 < op_null> I got sha256 PoW verification working on a $4 CPU from china, duno how I'd go with prime sieves 19:50 < tromp> gapcoin uses diffrent verification from primecoin 19:51 < tromp> they use miller rabin tests 19:51 < tromp> which give arbitrarily high confidence of primality 19:51 < op_null> I assume you have to walk the distance between the primes and check all of them for primeness though? 19:51 < tromp> primecoin uses a pseudoprimality test which cld be wrong 19:52 -!- coiner [~linker@42.119.103.23] has quit [Ping timeout: 256 seconds] 19:52 < tromp> i don't know; the proof cld enumerate some numbers in between whose compositeness is not easily established 19:53 < tromp> wld have to read up more on it 19:53 < tromp> gapcoin.org says "Verifying a prime gap is easy, you only have to check every number between the start and the end to be composite" 19:54 < tromp> so i guess they stick with the obvious 19:54 < tromp> maybe avoid miller rabin for numbers with a small divisor 19:55 < tromp> as expected, the section "But how are prime gaps useful?" is less than convincing:) 19:56 < op_null> at least what they are saying can be parsed as english. lots of altcoins dont manage that. 19:57 < op_null> my favourite one's feature was that the difficulty was locked to 1, and you had to "wait" between mining blocks for 24 hours. easiest coin to mine! 19:58 < tromp> reminds me of those bitcointalk posts that ask: cld we design a coin that limits the hashpower? 19:59 < op_null> or this one that explains how their BIP62 stuff works https://i.imgur.com/aXgRFQ8.png 20:00 < op_null> well, someone did make an altcoin with a fixed difficulty at one point and no "waiting", I think it just exploded into a world of chain forks 20:00 < tromp> was it called DDOScoin :-> 20:00 < tromp> ? 20:01 < op_null> no, but that has existed too. the idea was that if you solved a block the rest of the network launched a denial of service attack against you. 20:01 < gmaxwell> op_null: liquidcoin 20:02 < gmaxwell> yea, I think that one was mostly intended to shed hashrate from litecoin. 20:02 -!- RoboTeddy [~roboteddy@2604:5500:13:5fc:fc58:540a:4d8d:8a8e] has quit [Ping timeout: 258 seconds] 20:02 < op_null> a close contender is one that attempts to have "proof of activity", where nodes "stake" by being online. how do you prove that a node is online? you connect to them of course. so the whole network has every single node connecting to every other one, in order to watch their uptime and use it for consensus ;_; 20:04 < tromp> almost makes you want to draw up a top-100 list of most ill-conceived ideas in crypto-currencies 20:04 < op_null> gmaxwell: oh that's old. fixed difficulty 0.05, forked from tenebrix, CPU only mining with scrypt 20:06 < op_null> tromp: if you want to be DDoS fodder, go right ahead. 20:07 -!- Eliel_ [~jojkaart@jkaartinen.iki.fi] has joined #bitcoin-wizards 20:07 < op_null> gmaxwell: oh, did you hear darkcoin's coinjoin clone was vulnerable? 20:07 < gmaxwell> tromp: it was a fantstic idea, took like half of the ltc hashrate away for a month, and exploded into a zillion forks that could never converge onto a single blockchain. :P 20:08 < gmaxwell> op_null: well that was a given, but by which particular mode did it fail this time? 20:08 -!- koshii_ [~0@50.151.108.101] has joined #bitcoin-wizards 20:08 -!- Nightw0lf [~Nightwolf@v22010127607453799.yourvserver.net] has joined #bitcoin-wizards 20:09 < op_null> gmaxwell: something to do with the way they were doing fees meant the path through the coinjoin was obvious. I don't know how that works since the outputs are meant to be the same size, but I assume it's due to something with the masternodes taking out fees each time. 20:09 < gmaxwell> oh, well in that case I'm just more surprised that someone noticed. 20:09 -!- K1773R [~K1773R@unaffiliated/k1773r] has quit [Ping timeout: 264 seconds] 20:09 -!- Eliel [~jojkaart@jkaartinen.iki.fi] has quit [Ping timeout: 264 seconds] 20:09 -!- koshii [~0@50.151.108.101] has quit [Ping timeout: 264 seconds] 20:09 -!- Nightwolf [~Nightwolf@unaffiliated/nightwolf] has quit [Remote host closed the connection] 20:09 -!- SomeoneWeird [~SomeoneWe@unaffiliated/someoneweird] has quit [Ping timeout: 264 seconds] 20:10 < op_null> "We ask that everyone stop using Darksend for the time being, until we’re able to push out a fix to an issue Aswan found. This issue comes from the way fees are paid in Darksend with the combination of the way the client tries to denominate the same amount each round. The result is the possibility to trace a transaction through Darksend. 20:10 -!- SomeoneWeird_ [~SomeoneWe@ec2-122-248-235-44.ap-southeast-1.compute.amazonaws.com] has joined #bitcoin-wizards 20:10 -!- lclc_bnc [~lclc@opentransactions/monetas/lclc] has quit [Ping timeout: 264 seconds] 20:10 -!- K1773R [~K1773R@unaffiliated/k1773r] has joined #bitcoin-wizards 20:10 -!- SomeoneWeird_ is now known as SomeoneWeird 20:11 -!- SomeoneWeird is now known as Guest34913 20:11 < op_null> gmaxwell: you could also completely break their network by announcing a masternode in two places at once. 20:11 -!- lclc_bnc [~lclc@bothniafur.com] has joined #bitcoin-wizards 20:11 -!- lclc_bnc is now known as lclc 20:12 -!- Guest34913 [~SomeoneWe@ec2-122-248-235-44.ap-southeast-1.compute.amazonaws.com] has quit [Changing host] 20:12 -!- Guest34913 [~SomeoneWe@unaffiliated/someoneweird] has joined #bitcoin-wizards 20:13 -!- Guest34913 is now known as SomeoneWeird 20:15 -!- samson_ [~samson_@180.183.167.124] has quit [Ping timeout: 240 seconds] 20:20 < zooko> Ugh, I tire of reading the complaining and whining about other people's projects. 20:20 < op_null> sorry. 20:21 < zooko> Could someone set a flag when the topic in here veers onto constructive work? 20:21 < zooko> It's just social grooming. 20:21 < op_null> I take issue with people being sold disfunctional cryptosystems is all. 20:21 < zooko> We can score a few points by bonding with our buddies about how dumb and/or malicious is someone who's not present. 20:22 < zooko> Approximately the same functionality as the Facebook "like" button. 20:22 * zooko tries hard to reign in rant mode 20:22 < gmaxwell> zooko: I suppose you'd prefer to continue to divert actual productive conversation into closed membership private channels as you have in the past? 20:22 < zooko> op_null: I'm sure you personally don't deserve my ire. It's more of the "social tone" in general. 20:23 -!- samson_ [~samson_@183.89.22.186] has joined #bitcoin-wizards 20:23 < op_null> there's a difference between a social media site and cryptography that people's safety can depend on. I can't do anything to stop people doing shitty things with cryptography and selling it, ridiculing it to an audience that can understand it is about all I can do. 20:23 < kanzure> gmaxwell: there's a difference between advocating for less smearing of other terrible projects, versus advocating for a closed membership channel 20:23 < gmaxwell> zooko: there is a productive side of the conversation, understanding the failure modes is important and interesting (which was my question) though in this case it appears to have not added much to the collective understanding. (e.g. bc.i already made a very similar mistake with fee tracability) 20:24 < kanzure> in general it would probably be a good idea to not foster an environment of warantless smearing. although i can totally support thoughtful and clever smearing based on bringing up actual implementation details or concepts etc. :) 20:24 < gmaxwell> kanzure: I was "pot kettle blacking" there. I'm not pleased with the continual diversion of people into closed channels because some people are uncomfortable with the additional costs of working in public. 20:25 < kanzure> yep you and i share the same opinions there about private channels 20:25 -!- coiner [~linker@113.161.87.238] has joined #bitcoin-wizards 20:25 < gmaxwell> (in particular, because it then leaves the less interesting stuff in public) 20:26 < op_null> kanzure: in this case, it's fairly obvious that darkcoin built a flawed system where every "masternode" must have an open socket for people to connect to. the realities of a distributed system means there's a financial incentive for people to attack other nodes. which is obviously undesirable. 20:26 < kanzure> gmaxwell: right, it's quite similar to the "being ignorant in private" problem 20:26 < kanzure> op_null: you should not interpret any of my prior messages today as singling out darkcoin at all 20:26 < MRL-Relay> [tacotime] well, it's easier not to criticize other projects if they didn't have crazy instamines they've used to cash in on the public. but i guess maybe a better question is: can tx onion routing to obfuscate the sender reliably work? 20:26 < op_null> kanzure: I didn't. 20:28 < op_null> tacotime: who does that? darkcoin doesn't do that. 20:28 < kanzure> zooko was specifically saying that he thinks it is unproductive to high-five each other about smearing people who aren't around 20:28 < kanzure> that's all. this is not a complicated concept. 20:28 < kanzure> bad ideas are bad enough on their own, anyway :) 20:29 < MRL-Relay> [tacotime] op_null: isn't that the intention of darksend? to have a bunch of funds sent to a master node, mix up their dests, then send them to another node, and so on? 20:29 < zooko> op_null: I too strongly disapprove of incompetence and/or fraud harming people. ☺ 20:29 < zooko> 20:29 < zooko> Um... here's something maybe sort of relevantish, while also being constructive? 20:29 < zooko> Hold on ... 20:29 < zooko> Trying to get a web server that I can host it on. 20:29 < op_null> kanzure: I know. I was explaining why it's technically interesting and not just making fun of people for the hell of it. 20:29 < zooko> Oh well, maybe later. 20:30 < gmaxwell> As far as not around, they've been invited here. But they were only interested in paying me so they could attach my name to their project, not in actual technical discussions. In any case, I also prefer "omg guess what these idiots did" at least be directed to figuring out how to avoid the same mistakes elsewhere. :) 20:30 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has joined #bitcoin-wizards 20:30 < gmaxwell> (they'd also used my name all over their stuff intially and I had to threaten to go around bad mouthing them to get it removed.) 20:30 < op_null> tacotime: I don't know, that might be something new. it was pretty much just coinjoin with a bunch of semi untrusted peers as far as I've seen. their next hype seems to be that they "solved" instant transactions using the same masternodes. 20:31 < op_null> tacotime: they have some interesting flaws going on with masternodes. you're meant to hold a large amount of money as "stake" to prevent sybil attacks. people got tired of that because it meant you had to keep your 1000 DRK output secure. so now it's a delegation system. so people rent out their "stake" key to third parties who run nodes and collect a portion of the profit. 20:33 < MRL-Relay> [tacotime] op_null: um, hm. that's a sort of a proof of stake, i guess, but it sounds dangerous to based privacy on rented accounts. 20:33 < op_null> it's not really clear how all of this works with miners in the mix, as the masternodes now take quite a big portion of the block reward too. if you wanted your node to make the most money, your best bet is to DOS attack all of the other masternodes so you're the only viable choice. 20:33 < gmaxwell> op_null: thats pretty interesting, is it purely sybil protection now? originally they were talking about it being a bond to prevent misbehavior. I hadn't followed it because being closed source made it pointless to try. 20:34 < op_null> gmaxwell: I can't say for certain, but I don't think you can lose your output for misbehaviour. 20:35 < gmaxwell> is the profit sharing in the delegation enforced by the protocol or is it trust me? 20:36 < op_null> for a while it was up to the pool to set their percentage, but now I think it's enforced as a consensus rule. they had some trouble with the network fragmenting when they enabled that feature the first time and had to hard fork around it. 20:38 -!- LeapingL_ [~leapingle@ppp191-1.static.internode.on.net] has joined #bitcoin-wizards 20:38 < op_null> seems to be 30% of the block reward at the moment, but is set to increase over time. 20:38 < gmaxwell> thats interesting. what drove the removal of the trust there? did pools rip people off? 20:39 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has quit [Ping timeout: 264 seconds] 20:39 -!- TheSeven [~quassel@rockbox/developer/TheSeven] has quit [Ping timeout: 272 seconds] 20:40 < op_null> I think it was that pools weren't paying MN enough, I'd have to find that part of their forum thread. 20:41 -!- TheSeven [~quassel@rockbox/developer/TheSeven] has joined #bitcoin-wizards 20:41 < gmaxwell> I would be very interested in know if they were hard forking to override a market decision like that. 20:43 < op_null> "Basically if someone runs an old version of the wallet and finds a block he won't pay anything to a masternode. Enforcement means that such blocks will be rejected by the network." 20:44 < gmaxwell> oh this is enforcing the tribute to the masternodes. not the profit sharing in the delegation 20:46 < op_null> oh yes, sorry I totally misread you. 20:46 < op_null> um, I'll find out where the remote masternode stuff came from. 20:49 < op_null> still looking, but here's the masternode payment percentage table https://i.imgur.com/gglJY0q.png 20:49 < gmaxwell> yea, I knew about enforcing their diversion of the subsidy... I believe you and I may have wtf chuckled about the non-enforced version previously "no, thanks really, I'd prefer to keep all the coins." 20:50 < op_null> that is of course the rational response. 20:52 < op_null> "supports the hot/cold setupfor masternode operators (allowing your money to not be risked atall)" 20:53 < op_null> can't find much more information about it sadly. just loads and loads of guides. 20:53 < MRL-Relay> [tacotime] that's a lot of the miner subsidy going to their proof of stake system. 20:55 < MRL-Relay> [tacotime] i imagine that as you increase their share, you disincentivize mining while incentivizing hoarding, and eventually at some point things will become insecure. 20:57 < op_null> hard to say where that point is though 20:57 -!- jaekwon [~Adium@75-101-96-71.dsl.static.fusionbroadband.com] has joined #bitcoin-wizards 21:02 -!- bramm [~bram@99-75-88-206.lightspeed.sntcca.sbcglobal.net] has quit [Quit: Leaving] 21:02 -!- op_null [~op_null@178.62.133.216] has quit [Quit: gone] 21:03 < MRL-Relay> [othe] but thats all they want, increase holding so the price does not drop ;) the rest doesn´t matter. 21:21 -!- LeapingL_ [~leapingle@ppp191-1.static.internode.on.net] has quit [Remote host closed the connection] 21:24 -!- gues [~gues@gateway/vpn/mullvad/x-zyepdgmugkxedkhj] has joined #bitcoin-wizards 21:25 < smooth> that seems like kind of a fallacy although i haven't completely thought it through, but if everyone is holding and receiving stake then you are just decreasing the price 21:26 < smooth> but perhaps you are decreasing it more slowly giving the instaminers more time to get out 21:30 < MRL-Relay> [othe] but they don´t "stake"; they steal from the miner rewards 21:32 -!- gues [~gues@gateway/vpn/mullvad/x-zyepdgmugkxedkhj] has quit [Quit: Reconnecting] 21:32 -!- gues [~gues@gateway/vpn/mullvad/x-ahflcqstvmxnudhj] has joined #bitcoin-wizards 21:36 -!- arowser [~arowser@106.120.101.38] has quit [Ping timeout: 256 seconds] 21:36 < smooth> whatever you call it. if you give more coins to people who has coins all you do is make the price lower though slowly 21:38 -!- arowser [~arowser@106.120.101.38] has joined #bitcoin-wizards 21:39 -!- bitbumper [~bitbumper@c-69-254-243-205.hsd1.ks.comcast.net] has quit [Ping timeout: 264 seconds] 21:52 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has joined #bitcoin-wizards 21:54 -!- LeapingL_ [~leapingle@ppp191-1.static.internode.on.net] has joined #bitcoin-wizards 21:54 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has quit [Read error: Connection reset by peer] 21:58 -!- LeapingL_ [~leapingle@ppp191-1.static.internode.on.net] has quit [Ping timeout: 258 seconds] 22:04 -!- hashtag [~hashtag@CPE-69-23-213-3.wi.res.rr.com] has quit [Ping timeout: 258 seconds] 22:12 -!- RoboTeddy [~roboteddy@c-67-188-40-32.hsd1.ca.comcast.net] has joined #bitcoin-wizards 22:12 -!- go1111111 [~go1111111@162.244.138.37] has joined #bitcoin-wizards 22:18 -!- bitbumper [~bitbumper@c-69-254-243-205.hsd1.ks.comcast.net] has joined #bitcoin-wizards 22:20 -!- fanquake [~anonymous@unaffiliated/fanquake] has joined #bitcoin-wizards 22:33 -!- todays_tomorrow [~me@d114-78-114-23.bla803.nsw.optusnet.com.au] has quit [Ping timeout: 272 seconds] 22:41 -!- tdlfbx [~bsm117532@64.253.217.244] has quit [Read error: Connection reset by peer] 22:54 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has joined #bitcoin-wizards 22:57 -!- NewLiberty [~NewLibert@2602:304:cff8:1580:c8a2:555:25aa:17cb] has quit [Ping timeout: 258 seconds] 22:59 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has quit [Ping timeout: 265 seconds] 23:10 -!- zwischenzug [~zwischenz@33.Red-79-158-209.staticIP.rima-tde.net] has quit [Ping timeout: 256 seconds] 23:10 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has joined #bitcoin-wizards 23:11 -!- yottabit [uid36770@gateway/web/irccloud.com/x-yvzmabbtuuuqajaj] has quit [Quit: Connection closed for inactivity] 23:15 -!- MoALTz__ [~no@user-46-113-21-204.play-internet.pl] has quit [Quit: Leaving] 23:16 -!- LeapingLennie [~leapingle@ppp191-1.static.internode.on.net] has quit [] 23:23 -!- prodatalab [~prodatala@c-69-254-45-177.hsd1.fl.comcast.net] has quit [Quit: Konversation terminated!] 23:26 -!- prodatalab [~prodatala@c-69-254-45-177.hsd1.fl.comcast.net] has joined #bitcoin-wizards 23:34 -!- prodatalab [~prodatala@c-69-254-45-177.hsd1.fl.comcast.net] has quit [Quit: Konversation terminated!] 23:36 -!- prodatalab [~prodatala@c-69-254-45-177.hsd1.fl.comcast.net] has joined #bitcoin-wizards 23:37 -!- jb55 [~jb55@S0106f46d049a0b83.vc.shawcable.net] has joined #bitcoin-wizards 23:43 -!- HaltingState [~HaltingSt@unaffiliated/haltingstate] has quit [Quit: Leaving] 23:47 < gmaxwell> This bitcoin core pull req would love some more mild cryptographic review: https://github.com/bitcoin/bitcoin/pull/5227 23:50 -!- AaronvanW [~ewout@255pc208.sshunet.nl] has joined #bitcoin-wizards 23:50 -!- damethos [~damethos@unaffiliated/damethos] has joined #bitcoin-wizards 23:52 -!- fanquake [~anonymous@unaffiliated/fanquake] has quit [Quit: fanquake]