--- Log opened Tue Aug 09 00:00:20 2016
00:05 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 264 seconds]
00:06 -!- AusteritySucks [~Austerity@unaffiliated/austeritysucks] has joined #bitcoin-wizards
00:08 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-wizards
00:17 -!- Sleepnbum [~Sleepnbum@173.55.57.163] has quit [Ping timeout: 250 seconds]
00:18 -!- mryandao [~renlord@14-203-125-246.static.tpgi.com.au] has quit [Quit: leaving]
00:19 -!- BashCo_ [~BashCo@unaffiliated/bashco] has joined #bitcoin-wizards
00:22 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 240 seconds]
00:29 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 252 seconds]
00:36 -!- AusteritySucks [~Austerity@unaffiliated/austeritysucks] has quit [Ping timeout: 252 seconds]
00:50 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
00:52 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-wizards
01:06 -!- pro [~pro@unaffiliated/pro] has joined #bitcoin-wizards
01:08 -!- rubensayshi [~ruben@82.201.93.169] has joined #bitcoin-wizards
01:13 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards
01:26 -!- yoleaux [~yoleaux@xn--ht-1ia18f.nonceword.org] has joined #bitcoin-wizards
01:32 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has quit [Read error: Connection reset by peer]
01:37 -!- AaronvanW [~ewout@198pc231.sshunet.nl] has joined #bitcoin-wizards
01:37 -!- AaronvanW [~ewout@198pc231.sshunet.nl] has quit [Changing host]
01:37 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #bitcoin-wizards
01:41 -!- jtimon [~quassel@55.31.134.37.dynamic.jazztel.es] has joined #bitcoin-wizards
01:51 -!- AusteritySucks [~Austerity@unaffiliated/austeritysucks] has joined #bitcoin-wizards
01:57 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-wizards
01:59 -!- BashCo_ [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 260 seconds]
02:00 -!- TheSeven [~quassel@rockbox/developer/TheSeven] has quit [Ping timeout: 250 seconds]
02:01 -!- TheSeven [~quassel@rockbox/developer/TheSeven] has joined #bitcoin-wizards
02:08 -!- tunafizz [tunafizz@c-71-207-55-31.hsd1.pa.comcast.net] has quit [Read error: Connection reset by peer]
02:08 -!- Giszmo [~leo@ip5f5ac08d.dynamic.kabel-deutschland.de] has joined #bitcoin-wizards
02:32 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-dlmusiulhjcmbuoq] has joined #bitcoin-wizards
02:38 -!- AusteritySucks [~Austerity@unaffiliated/austeritysucks] has quit [Ping timeout: 265 seconds]
02:39 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Remote host closed the connection]
02:46 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Read error: Connection reset by peer]
02:46 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards
02:46 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-wizards
02:51 -!- jaekwon [~jaekwon@75-101-96-71.dsl.static.fusionbroadband.com] has quit [Remote host closed the connection]
02:55 -!- laurentmt [~Thunderbi@80.215.234.247] has joined #bitcoin-wizards
02:58 -!- laurentmt [~Thunderbi@80.215.234.247] has quit [Client Quit]
03:06 -!- freekevin [freekevin@gateway/shell/xshellz/x-dxzarrzyvrydvyqf] has quit [Ping timeout: 276 seconds]
03:11 -!- freekevin [freekevin@gateway/shell/xshellz/x-cldncftnfsehoyra] has joined #bitcoin-wizards
03:44 -!- blockzombie [~blockzomb@eth59-167-133-100.static.internode.on.net] has quit [Remote host closed the connection]
03:44 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 258 seconds]
03:47 -!- laurentmt [~Thunderbi@80.215.234.247] has joined #bitcoin-wizards
03:48 -!- laurentmt [~Thunderbi@80.215.234.247] has quit [Client Quit]
04:02 -!- proslogion [~proslogio@2.217.2.220] has joined #bitcoin-wizards
04:04 < proslogion> the NTRU keysize makes it not so interesting for Bitcoin
04:04 < proslogion> besides, it's patented, freely licensed for open source projects, but still patented
04:07 < proslogion> sill it deserves to be singled out because almost anything else PQC is much worse
04:13 -!- laurentmt [~Thunderbi@80.215.234.247] has joined #bitcoin-wizards
04:14 -!- laurentmt [~Thunderbi@80.215.234.247] has quit [Client Quit]
04:15 < nsh> ;seen bramc
04:24 -!- dEBRUYNE [~dEBRUYNE@unaffiliated/debruyne] has joined #bitcoin-wizards
04:25 -!- thesnark [~mike@unaffiliated/thesnark] has joined #bitcoin-wizards
04:26 < fluffypony> holy backlog
04:26 < fluffypony> andytoshi should hang around more often
04:30 -!- thesnark [~mike@unaffiliated/thesnark] has quit [Remote host closed the connection]
04:38 -!- thesnark [~mike@unaffiliated/thesnark] has joined #bitcoin-wizards
04:57 -!- jaekwon [~jaekwon@75-101-96-71.dsl.static.fusionbroadband.com] has joined #bitcoin-wizards
05:00 -!- jaekwon_ [~jaekwon@75-101-96-71.dsl.static.fusionbroadband.com] has joined #bitcoin-wizards
05:01 -!- jaekwon [~jaekwon@75-101-96-71.dsl.static.fusionbroadband.com] has quit [Ping timeout: 250 seconds]
05:01 -!- jaekwon_ [~jaekwon@75-101-96-71.dsl.static.fusionbroadband.com] has quit [Read error: Connection reset by peer]
05:02 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards
05:37 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-wizards
06:04 -!- edvorg [~edvorg@14.169.57.10] has joined #bitcoin-wizards
06:09 -!- jaekwon [~jaekwon@75-101-96-71.dsl.static.fusionbroadband.com] has joined #bitcoin-wizards
06:13 -!- jaekwon [~jaekwon@75-101-96-71.dsl.static.fusionbroadband.com] has quit [Ping timeout: 252 seconds]
06:21 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 244 seconds]
06:37 -!- laurentmt [~Thunderbi@80.215.178.68] has joined #bitcoin-wizards
06:38 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 240 seconds]
06:38 -!- dEBRUYNE [~dEBRUYNE@unaffiliated/debruyne] has quit [Quit: Leaving]
06:39 -!- laurentmt [~Thunderbi@80.215.178.68] has quit [Client Quit]
06:45 -!- jaekwon [~jaekwon@75-101-96-71.dsl.static.fusionbroadband.com] has joined #bitcoin-wizards
06:50 -!- jaekwon [~jaekwon@75-101-96-71.dsl.static.fusionbroadband.com] has quit [Ping timeout: 252 seconds]
07:00 -!- contrapumpkin is now known as copumpkin
07:08 -!- Sosumi [~Leon@bl10-113-190.dsl.telepac.pt] has joined #bitcoin-wizards
07:15 -!- xissburg_ [~xissburg@unaffiliated/xissburg] has joined #bitcoin-wizards
07:16 -!- xissburg_ [~xissburg@unaffiliated/xissburg] has quit [Read error: Connection reset by peer]
07:16 -!- xissburg [~xissburg@unaffiliated/xissburg] has quit [Read error: No route to host]
07:20 -!- xissburg [~xissburg@unaffiliated/xissburg] has joined #bitcoin-wizards
07:20 -!- tromp [~tromp@ool-944bc34f.dyn.optonline.net] has joined #bitcoin-wizards
07:24 -!- tromp [~tromp@ool-944bc34f.dyn.optonline.net] has quit [Ping timeout: 240 seconds]
07:24 -!- dEBRUYNE [~dEBRUYNE@unaffiliated/debruyne] has joined #bitcoin-wizards
07:35 -!- proslogion [~proslogio@2.217.2.220] has quit [Ping timeout: 260 seconds]
07:36 -!- nonaTure [~nonaTure@p4FEB907D.dip0.t-ipconnect.de] has joined #bitcoin-wizards
07:39 -!- cyphase [~cyphase@unaffiliated/cyphase] has quit [Ping timeout: 258 seconds]
07:42 -!- nonaTure [~nonaTure@p4FEB907D.dip0.t-ipconnect.de] has quit [Quit: Leaving]
07:42 -!- nonaTure [~nonaTure@p4FEB907D.dip0.t-ipconnect.de] has joined #bitcoin-wizards
07:44 -!- cyphase [~cyphase@unaffiliated/cyphase] has joined #bitcoin-wizards
07:56 -!- zooko [~user@73.95.137.99] has joined #bitcoin-wizards
08:10 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards
08:25 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-dlmusiulhjcmbuoq] has quit [Quit: Connection closed for inactivity]
08:31 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 244 seconds]
08:47 -!- rubensayshi [~ruben@82.201.93.169] has quit [Remote host closed the connection]
08:48 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-wizards
08:55 -!- jaekwon [~jaekwon@75-101-96-71.dsl.static.fusionbroadband.com] has joined #bitcoin-wizards
08:58 -!- proslogion [~proslogio@130.159.65.131] has joined #bitcoin-wizards
09:30 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-wizards
09:30 -!- mdavid613 [~Adium@cpe-104-172-191-85.socal.res.rr.com] has joined #bitcoin-wizards
09:36 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 258 seconds]
09:38 -!- bildramer [~bildramer@ppp-94-67-125-5.home.otenet.gr] has quit [Ping timeout: 244 seconds]
09:41 -!- Sleepnbum [~Sleepnbum@72.67.47.196] has joined #bitcoin-wizards
09:43 -!- bildramer [~bildramer@ppp-94-69-93-203.home.otenet.gr] has joined #bitcoin-wizards
09:52 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Remote host closed the connection]
09:54 -!- iwilcox [~iwilcox@unaffiliated/iwilcox] has joined #bitcoin-wizards
09:56 -!- mdavid613 [~Adium@cpe-104-172-191-85.socal.res.rr.com] has quit [Quit: Leaving.]
10:00 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-wizards
10:01 -!- mdavid613 [~Adium@cpe-104-172-191-85.socal.res.rr.com] has joined #bitcoin-wizards
10:08 -!- edvorg [~edvorg@14.169.57.10] has quit [Remote host closed the connection]
10:26 -!- edvorg [~edvorg@14.169.57.10] has joined #bitcoin-wizards
10:40 -!- MoALTz [~no@78-11-183-124.static.ip.netia.com.pl] has joined #bitcoin-wizards
10:41 -!- byteflame [~byteflame@70-89-65-45-little-rock-ar.hfc.comcastbusiness.net] has joined #bitcoin-wizards
10:43 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has quit [Ping timeout: 250 seconds]
10:43 -!- edvorg [~edvorg@14.169.57.10] has quit [Ping timeout: 244 seconds]
10:43 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-wizards
10:46 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-wizards
10:47 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-wizards
10:48 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Client Quit]
10:57 -!- zooko [~user@73.95.137.99] has quit [Ping timeout: 276 seconds]
11:07 -!- bildramer [~bildramer@ppp-94-69-93-203.home.otenet.gr] has quit [Ping timeout: 265 seconds]
11:15 -!- bildramer [~bildramer@ppp-94-67-123-74.home.otenet.gr] has joined #bitcoin-wizards
11:16 -!- proslogion [~proslogio@130.159.65.131] has quit [Ping timeout: 258 seconds]
11:17 < waxwing> https://www.usenix.org/system/files/conference/woot16/woot16-paper-wustrow.pdf
11:17 < waxwing> TLDR prove you DDoSed a server by using returned server sigs as proof of work, heh
11:21 -!- mdavid613 [~Adium@cpe-104-172-191-85.socal.res.rr.com] has quit [Quit: Leaving.]
11:22 -!- tromp [~tromp@ool-944bc34f.dyn.optonline.net] has joined #bitcoin-wizards
11:22 < katu_> cute :)
11:24 -!- mdavid613 [~Adium@cpe-104-172-191-85.socal.res.rr.com] has joined #bitcoin-wizards
11:24 < cjd> andytoshi: I am thinking that the problem you raised of the transaction payers robbing the miner later on is possibly acceptable in practice, if the miner creates his own transaction (e.g. paying money to himself) then he should be safe...
11:26 < cjd> and the benefit of such a scheme is you can "sync the chain" by asking a peer for the most recent block and then asking for the txout set, then validating it and asking for (say) 1000 block headers or whatever it takes to make yourself happy that you are not being fed bullshit
11:26 -!- tromp [~tromp@ool-944bc34f.dyn.optonline.net] has quit [Ping timeout: 250 seconds]
11:27 < cjd> you just take the block header number and calculate the amount of created money at that point, point multipliy that value and add it to all of the UTXOs
11:30 < andytoshi> cjd: by "asking for the txout set" you mean also all the kG values
11:30 < cjd> yes
11:30 < cjd> and I guess the header contains [ HASH(utxoSet), HASH(prevHeader), number, difficulty, time, nonce ]
11:30 < cjd> *blockNumber
11:31 < cjd> oh crap you can fiddle with the difficulty, that's annoying
11:32 < andytoshi> well the utxoSet needs to have proofs that the utxos have been committed to by the blockchain
11:32 < andytoshi> i think
11:32 < andytoshi> maybe not, maybe the header commitment is sufficient
11:33 < cjd> the reason for the hash over the utxoSet is just so that somebody else cannot steal your mining fee
11:34 < cjd> oh yeah also double-spend
11:36 < cjd> there might be still another way to compress the header chain, if the header with the highest "work" each day points at the header with the highest work from the previous day, I think you can just skip blocks
11:38 < cjd> so since you don't know if you're going to be the winner of a "checkpoint" block, just every block points at the checkpoint from the previous 144 blocks or such
11:40 < andytoshi> cjd: are you familiar with compact SPV proofs?
11:40 < cjd> uhhh I have heard this before but my memory is not working
11:40 < andytoshi> http://blockstream.com/sidechains.pdf appendix B
11:40 < andytoshi> i'm still unsure if it's OK that utxo inclusion proofs point to blocks other than the one they were included in
11:41 < andytoshi> i guess so
11:41 < Taek> [14:25:21] <cjd> andytoshi: I am thinking that the problem you raised of the transaction payers robbing the miner later on is possibly acceptable in practice, if the miner creates his own transaction (e.g. paying money to himself) then he should be safe...
11:41 < Taek> would the transactors have to do something similar to make sure the miners couldn't steal from them?
11:41 < Taek> supposing you ended up as the only transactor in a block
11:41 <@gmaxwell> andytoshi: I don't see why a tip commitment isn't fine (other than perhaps performance reasons)
11:42 < andytoshi> Taek: presumably you, the transactor, would put a kG value in here
11:42 < cjd> > the presence of lower-than-necessary hashes is in fact statistical evidence of more work done in the chain[Mil12].  <-- ok we're on the same page here
11:42 < andytoshi> gmaxwell: yeah, i think it's fine
11:42 < instagibbs> can someone reiterate the problem being discussed? I don't see in backlog
11:43 < cjd> instagibbs: optimizations to mimblewimble
11:43 < instagibbs> cjd, a little more than that :)
11:43 < cjd> crap maybe we need to start a pad to keep track of the backstory here :|
11:43 < instagibbs> > I am thinking that the problem you raised of the transaction payers robbing the miner later
11:44 < Taek> (andytoshi is going to write a paper never fear)
11:45 < andytoshi> lol. yeah, i'll write something, once things stop being in such flux
11:45 < cjd> basically I'm proposing an optimization wherein each transaction is broadcast with the sum-of-secrets and the leftover money (fee) and the miner is the one who makes the signed emptystring rather than the transactors
11:45 < cjd> instagibbs: ^^
11:45 < instagibbs> oh i see, a problem with an optimization
11:45 < instagibbs> I was confuzzled
11:46 < cjd> yes, we're going over optimizations to try to make it require O(n) storage (n being unspend outputs) :)
11:46 < andytoshi> cjd: if you make a transaction and broadcast the "sum-of-secrets" which is just your secret you can be robbed
11:46 < instagibbs> cjd, I think you will lose a lot if you drop the chain stuff
11:47 <@gmaxwell> It's useful to take a step back and consider what MW actually does.
11:48 <@gmaxwell> It's constructs a proof interactively that (under relevant assumptions) no theft except double spending could have happened.
11:48 < instagibbs> and inflation, at least in a particular history
11:48 <@gmaxwell> I don't think that property can be maintained if coin creation doesn't introduce new randomness.
11:49 < andytoshi> instagibbs: no inflation can happen within a single tx
11:49 < cjd> Can you elaborate? "new randomness" ?
11:49 < instagibbs> andytoshi, no current inflation ;P
11:50 < cjd> oh I think I get it, you're arguing that block rewards could be ripped off unless we check each block
11:51 < instagibbs> yep
11:52 < cjd> I need to showerthink about that one, I really want to not sync block headers :|
11:53 < instagibbs> the newly generated coins also probably need to be blinded, otherwise they can just be extracted
11:53 < andytoshi> cjd: i think you can decrease the block header length to log(n) as long as you commit to everything in each block
11:53 < andytoshi> using the compact SPV stuff in the sidechains paper
11:56 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 250 seconds]
12:03 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-eaiaeaobfdtlryxx] has joined #bitcoin-wizards
12:06 -!- byteflame [~byteflame@70-89-65-45-little-rock-ar.hfc.comcastbusiness.net] has quit [Ping timeout: 264 seconds]
12:11 < cjd> I'm thinking you might get away with just downloading headers until the sum of difficulty goes over K (some comfort factor)
12:12 < cjd> because in order for any money to be stolen as gmax suggests, the mining fees would have to have been stolen which is equivilant to mining a fake chain and you have reached your comfort factor of difficulty which is warranting that this did not happen
12:13 -!- dEBRUYNE_ [~dEBRUYNE@unaffiliated/debruyne] has joined #bitcoin-wizards
12:13 -!- dEBRUYNE_ [~dEBRUYNE@unaffiliated/debruyne] has quit [Read error: Connection reset by peer]
12:15 -!- dEBRUYNE [~dEBRUYNE@unaffiliated/debruyne] has quit [Ping timeout: 265 seconds]
12:15 < cjd> I have to think about it more, in simplistic contexts I feel like I understand it but when I take it to bigger contexts I'm completely lost about it's security properties
12:16 < nsh> what's the fee-stealing attack against miners?
12:18 < cjd> so this is an attack against an imagined optimization of mimblewimble only
12:19 -!- dEBRUYNE [~dEBRUYNE@unaffiliated/debruyne] has joined #bitcoin-wizards
12:19 < cjd> my optimization is when you create a transaction and you calculate  ( (secretKeyInput + valueInput) - (secretKeyOutput + valueOutput + secretKeyChange + valueChange) )
12:20 < cjd> instead of signing the emptystring with that result (as a secret key) you instead bcast the result along with the value of any leftover money
12:21 < cjd> then the miner needs constructs a block knowing sum-of-secrets from each transaction and thus can create only 1 signature for the whole block
12:21 < cjd> you following ?
12:21 < nsh> roughly
12:21 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-wizards
12:22 < nsh> how many signatures would be required otherwise for mining a block?
12:22 < cjd> one per transaction
12:22 < cjd> did you read MW ?
12:23 < nsh> oh, you mean this obviates the need for the signing at all when authenticating receipt of transaction?
12:23 < nsh> only the miner signs?
12:23 < cjd> you read mimblewimble? I just want to make sure we're talking about the same thing here...
12:23  * nsh nods
12:23 < nsh> we were talking about it notverymany hours ago
12:24 < cjd> ok so right, you can get to 1 signature per block if we are ok to bcast the sum-of-secrets and the remaining value (fee) to the miner
12:24 < cjd> because the miner merges everything
12:25 < nsh> hmm
12:25 < cjd> now for my next trick, I want to replace the signature which the miner creates with a simple output, now andytoshi reminds me that I have created a bug because now all of the outputs by the miner sum to a value which the creator of the transaction knows
12:26 < nsh> ah, okay. took me a moment to understand this still authenticates
12:27 < cjd> basically the creator of the transaction (knowing the sum of secrets, change amount, block reward and that the final sum is zero) can just deduce a transaction which spends all of the outputs from the miner
12:27 < nsh> creator of which transaction?
12:28 < cjd> lets imagine there is only 1 transaction being created in this block
12:28 < cjd> 1 person paying 1 other person and 1 miner
12:28  * nsh nods
12:28 < cjd> the payee knows the sum of secrets and if the final sum is zero, this implys he also knows the miner's secret and cna steal the fee
12:28 -!- byteflame [~byteflame@70-89-65-45-little-rock-ar.hfc.comcastbusiness.net] has joined #bitcoin-wizards
12:29 < nsh> i think you need external-to-pederson consensus logic for blocks anyway
12:30 < nsh> (for e.g. maturing block subsidies)
12:30 < cjd> But I respond that if the miner includes an *input* for which only he knows the private key, he has masked the result and the creator of this single transaction cannot rob him
12:30 < nsh> ah, right
12:30 < nsh> (i think this problems goes away when you have lots of transactions anyway, or it's a very tight lottery)
12:31 < nsh> no transaction recipient is especially privileged in being able to infer the final excess
12:31 < cjd> having no signature per block may seem unimportant but once I have convinced you that this works, I go on to suggest that validating the chain does not require downloading even the whole chain of headers
12:31 < nsh> heh, i think we need to process moonleaps one at a time
12:32 < cjd> just download the "unspent txo set" (the commitments) and the most recent block header and as many block headers as you like, then calculate based on the block number the amount of money in circulation, point multiply that and add this to all commitments and expect zero
12:32  * nsh nods
12:33 < nsh> you can have some security comfort parameter; falsification of the past can still be made dependent on a fast-growing function of hashpower
12:33 < nsh> just not clear exactly what needs to be committed yet
12:34 < cjd> but gmax points out that I'm now violating some basic assumption of MW because I've completely dropped validation of who gets the block rewards and so I am wrestling with that as we speak
12:34 < cjd> it makes so much sense the way I go but taking a different path it sounds so broken :)
12:34 < nsh> hmm
12:35 < cjd> it is as though any ring of commitments can be valid as long as it adds up to zero and spends X money
12:35 < cjd> so you must only create 1 block to fool someone
12:35 < nsh> no party with merkle
12:35 < cjd> I think there is a very simple bypass of that issue but I need to think more
12:40 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has joined #bitcoin-wizards
12:44 < tromp_> i just commented on https://news.ycombinator.com/item?id=12256291
12:45 < cjd> anyway even if you put a signature in each block, what you need to download to reconstruct a block header is [ sig, time, nonce ], everything else can be inferred
12:46 < cjd> so you're looking at like 4.2MB per year with a 10mn block rate
12:46 < cjd> *10 minute
12:48 -!- proslogion [~proslogio@2.217.2.220] has joined #bitcoin-wizards
12:48 < cjd> actually 5.8 with the public keys which are also needed
12:51 < proslogion> in MW, can i send someone some coins, then get around to manage to receive a tx from this pubkey of him as another identity so i can get his blinding factor, then next time when i do business with him, i would use the same blinding factor and amount as i used last time, so i can replay the second tx despite him not wanting to send the other identity coins this time?
12:51 < cjd> are you assuming no change address ?
12:52 < proslogion> yes
12:53 < cjd> also consider that a pubkey is never used twice
12:54 -!- nonaTure [~nonaTure@p4FEB907D.dip0.t-ipconnect.de] has quit [Ping timeout: 250 seconds]
12:54 < proslogion> what if somebody does? anything other than client-side check?
12:54 < cjd> because you have to interact with his computer in order to make the transaction so it's the decision of the programmers, not of the user
12:55 < cjd> side-effect: you can't get paid if your computer is turned off
12:55 < cjd> but that's part of MW that we can't seem to fix
12:56 < nsh> (well, you could use pegs with another chain that allows interactionless payments for certain situations)
12:59 < cjd> oh crap I have a problem with my whole optimization, once the payee reveals the sum-of-secrets the payer can rob him :(
12:59 < proslogion> ah, no, no, you cannot reuse the same r, like bitcoin, the r you use is dependent on the tx a pubkey receives as well!
12:59 < proslogion> it's a chain
13:00 < cjd> so we're back to 5:1 chain compression which is not great
13:01 < cjd> unless the payee adds an input to the tx which is going to kill off some use cases
13:04 < andytoshi> proslogion: yes, replay attacks are possible if you reuse addresses. but you create the addresses when you receive payments, and you're the one who'll get robbed. so don't reuse keys.
13:04 < andytoshi> s/address/keys/ everywhere, MW really doesn't have addresses
13:07 < cjd> I'm really unhappy that we can't get rid of sig-per-tx, not only does that mean a large chain but it also means that anyone who downloads each block (a miner for instance) can reconstruct the transactions from that block and effectively de-anonymise the money flows
13:07 <@gmaxwell> huh?!
13:08 < instagibbs> the original MW paper allows this, but it's not necessary at all
13:08 < cjd> Maybe I'm talking shit but my approach would be to try to fit groups of cancelled inputs and created outputs with signatures
13:08 < cjd> it's computationally expensive but I don't feel like it's expensive enough
13:08 < instagibbs> <andytoshi> ah, there's a simple fix, publish k1G and k2, sign with k1G but make the transaction excess be (k1 + k2)G
13:08 < instagibbs> <andytoshi> and when combining transactions all the k2's just get added together
13:09 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 265 seconds]
13:10 < cjd> is that not a variant of publish   k1G and k2G  ?   in which case I just need to fit 2 sigs together with a handful of inputs and outputs...
13:11 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-wizards
13:11 < andytoshi> cjd: no, there is no sig with k2
13:11 < andytoshi> it's an explicit value
13:12 < cjd> ahh right, so you just add up k2 every time you merge transactions in memory
13:12 < cjd> very good :)
13:12 -!- dEBRUYNE [~dEBRUYNE@unaffiliated/debruyne] has quit [Ping timeout: 244 seconds]
13:13 < proslogion> andytoshi: i don't get it, your r is determined partially by the r of your sender, i wonder if reusing a r is at all possible
13:13 < andytoshi> heh, yeah, this was what i had before MW came out (without the k1G, so it was insecure for the same reason your optimization was). i realized my mistake when MW came out, but i feel a bit better that voldemort made the opposite mistake :P
13:14 < andytoshi> proslogion: i think you'd be able to do it, at the very least by creating two outputs, skewing one to reuse r, and skewing the other in the opposite direction
13:15 < cjd> dammit why do we need these signatures floating around everywhere :|
13:19 < proslogion> andytoshi: right you can just adjust the k value to achieve that effect, i forgot
13:21 -!- dEBRUYNE [~dEBRUYNE@unaffiliated/debruyne] has joined #bitcoin-wizards
13:22 < cjd> so what makes the signature-over-emptystring work is the fact that it's not cancellable
13:22 < cjd> you can point to a utxo (a commitment) and cancel that when you are spending another transaction but the signature is forever
13:23 < cjd> if you could cancel a signature then the spender can still rob the recipient
13:24 < andytoshi> cjd: well if you can aggregate the proof of discrete logs that's still not possible .. so it's not as morose as you make it seem
13:24 < andytoshi> we could use BLS sigs for the kG values, in a pairing-friendly group, and then you could aggregate all the sigs into one and it'd still be ok
13:25 < cjd> ok, aggregatable sigs, that would be cool
13:25 < andytoshi> hmm actually maybe there is still a risk here, unsure
13:25 < cjd> but I fear the more cool math we use, the more difficult it will be to take this to post-quantum
13:26 < andytoshi> yeah
13:27 < cjd> but 5:1 compression means a 16GB blockchain assuming every tx in bitcoin was replayed into this chain...
13:27 < andytoshi> so we need two things right now: commitments that can be shown to sum to 0 (we don't need full homorphism, just sum to 0); some overflow prevention (right now we use a rangeproof); some extra randomness and a way to prove knowledge of the randomness
13:27 < cjd> IMO overflow prevention is not needed, we just need to prove knowledge of r
13:28 < cjd> a.k.a prove that they're not making up garbage to balance the books
13:29 < andytoshi> cjd: but then the outputs themselves could overflow. i make a 10BTC output and a -10BTC output and just never spend the latter
13:29 < andytoshi> (and put zero in)
13:29 < andytoshi> this is why we have the overflow protection in "traditional C"
13:30 < andytoshi> "traditional CT"
13:30 < cjd> uhh why would you use signed integers?
13:30 < andytoshi> cjd: everything works in finite rings
13:30 < cjd> oh I see, you're protecting against overflow of the whole 256 bit number
13:30 < andytoshi> if you take the group order minus n, that's -n
13:30 < cjd> got it
13:30 < andytoshi> yep
13:30 < andytoshi> none of the quantum stuff i've seen changes this (i don't see that anything could be zero-knowledge without it actually)
13:31 < cjd> changes what?
13:32 < andytoshi> changes the fact that every number is modulo something, and can thus be "negative" in a way that's not intrinsicly definable
13:32 < cjd> ahh ok
13:35 -!- rusty2 is now known as rusty
13:36 < cjd> anything I can read about the types of range proofs used here ?
13:45 < andytoshi> cjd: https://people.xiph.org/~greg/confidential_values.txt basically .. gmaxwell might know what sources he based this on
13:45 < andytoshi> also there is an optimized ring signature construction used in that, https://www.reddit.com/r/Bitcoin/comments/386vh0/borromean_ring_signatures_new_research_by_greg/ but this is a bit of an implementation detail
13:46 < cjd> ahh I didn't read the whole thing
13:46 < cjd> yeah, I was looking really for the gritty detail of the rangeproof
13:47 <@gmaxwell> you could redesign it from the text file, and borromean paper; though you'd miss some of the optimizations.
13:55 < cjd> all right, thanks, going to get some food and then I'll take a look
13:58 < waxwing> gmaxwell: shame in MW you lose the whole data-embedding thing 'cos can't share the blinding factors, right
13:58 <@gmaxwell> waxwing: correct.
13:58 < proslogion> the data embedding sounds like a weird sales pitch though
13:58 < waxwing> proslogion: well useful for amount, too
13:58 < waxwing> altho' not necessary
13:59 < proslogion> can you give that space to counterparty people etc?
13:59 < waxwing> when you consider how loudly people complain about not being able to embed stuff in blockchain :)
13:59 < waxwing> yeah you beat me to it :)
14:00 < waxwing> although, hmm, it's private to sender/receiver by default
14:00 <@gmaxwell> it _must_ be private.
14:00 <@gmaxwell> or it blows up the ZK property of the proof.
14:00 < waxwing> i was just thinking of auditors
14:01 <@gmaxwell> the reason in works in CT is that the value being sent and blinding factor is non-private to both the sender and reciever.
14:02 <@gmaxwell> so the proof doesn't need to be ZK with respect to them. :)
14:02 <@gmaxwell> for MW it does, so no data storage in it.
14:04 < andytoshi> well you do still have free s values, you can bastardize some storage into them if you've got an out-of-band key. but you'd need to structure the data heavily so your recipient can determine which s-value is forced (and therefore has no data)
14:04 < andytoshi> doing so will reveal the value to anyone who can decrypt, though not directly
14:04 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 264 seconds]
14:06 < andytoshi> waxwing: as for auditors, if i've got a commitment C = vH + rG, i can give them v and sign with rG and that'll prove the value
14:06 <@gmaxwell> yes you could carry a tiny amount of data to people who knew the value without meaningfully disclosing the blinding factors.
14:06 < andytoshi> if people already know the value, you can use every free s value as an encryption channel, that doesn't reveal anything about the blinding factor
14:06 < proslogion> just curious, do you guys read every link drop? someone just show up on this channel and send one message is so easy to miss
14:07 -!- Giszmo [~leo@ip5f5ac08d.dynamic.kabel-deutschland.de] has quit [Quit: Leaving.]
14:08 < andytoshi> proslogion: probably every link drop gets noticed, that's pretty weird behaviour. and this one happened to be on a quiet time.. then it was forwarded around a lot outside of IRC
14:09 < proslogion> andytoshi: gotcha, tks
14:10 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 250 seconds]
14:11 -!- nonaTure [~nonaTure@p4FEB907D.dip0.t-ipconnect.de] has joined #bitcoin-wizards
14:14 < kanzure> "Blinded outsourcing of channel monitoring" https://lists.linuxfoundation.org/pipermail/lightning-dev/2016-August/000565.html
14:15 < proslogion> lol i thought it was about IRC channel monitoring
14:21 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-wizards
14:28 -!- byteflame [~byteflame@70-89-65-45-little-rock-ar.hfc.comcastbusiness.net] has quit [Ping timeout: 244 seconds]
14:44 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards
14:45 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has quit [Ping timeout: 265 seconds]
14:49 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has joined #bitcoin-wizards
14:56 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has joined #bitcoin-wizards
14:56 -!- blockzombie [~blockzomb@eth59-167-133-100.static.internode.on.net] has joined #bitcoin-wizards
15:01 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 258 seconds]
15:04 -!- mkarrer [~mkarrer@142.red-83-47-107.dynamicip.rima-tde.net] has quit []
15:08 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)]
15:12 -!- MoALTz [~no@78-11-183-124.static.ip.netia.com.pl] has quit [Read error: Connection reset by peer]
15:12 -!- murch [~murch@p4FE38D69.dip0.t-ipconnect.de] has joined #bitcoin-wizards
15:19 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has quit [Read error: No route to host]
15:21 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 244 seconds]
15:21 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has joined #bitcoin-wizards
15:38 -!- FNinTak [~jonhbit@tsarviajado.media.mit.edu] has joined #bitcoin-wizards
15:59 -!- afk11 [~afk11@109.255.154.81] has joined #bitcoin-wizards
15:59 -!- afk11 [~afk11@109.255.154.81] has quit [Changing host]
15:59 -!- afk11 [~afk11@unaffiliated/afk11] has joined #bitcoin-wizards
16:02 -!- renlord [~renlord@14-203-125-246.static.tpgi.com.au] has joined #bitcoin-wizards
16:17 -!- renlord [~renlord@14-203-125-246.static.tpgi.com.au] has quit [Quit: Lost terminal]
16:18 -!- murch [~murch@p4FE38D69.dip0.t-ipconnect.de] has quit [Quit: Leaving.]
16:19 -!- tromp [~tromp@ool-944bc34f.dyn.optonline.net] has joined #bitcoin-wizards
16:37 -!- pro [~pro@unaffiliated/pro] has quit [Quit: Leaving]
16:39 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
16:39 -!- FNinTak [~jonhbit@tsarviajado.media.mit.edu] has quit [Ping timeout: 244 seconds]
16:40 -!- tromp [~tromp@ool-944bc34f.dyn.optonline.net] has quit [Remote host closed the connection]
16:41 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-wizards
16:47 -!- jaekwon [~jaekwon@75-101-96-71.dsl.static.fusionbroadband.com] has quit [Remote host closed the connection]
16:54 -!- FNinTak [~jonhbit@dhcp-18-111-16-181.dyn.mit.edu] has joined #bitcoin-wizards
17:02 -!- bildramer [~bildramer@ppp-94-67-123-74.home.otenet.gr] has quit [Ping timeout: 240 seconds]
17:07 -!- tromp [~tromp@ool-944bc34f.dyn.optonline.net] has joined #bitcoin-wizards
17:10 -!- VMazz [~VMazz@unaffiliated/mazznilla] has joined #bitcoin-wizards
17:20 -!- VMazz [~VMazz@unaffiliated/mazznilla] has quit [Quit:  HydraIRC -> http://www.hydrairc.com <- Wibbly Wobbly IRC]
17:44 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has joined #bitcoin-wizards
17:45 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 265 seconds]
17:49 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-wizards
17:53 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
17:55 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-wizards
17:57 -!- CrazyTruthYakDDS [uid67551@gateway/web/irccloud.com/x-ejufbktegtghhnkj] has joined #bitcoin-wizards
18:15 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-eaiaeaobfdtlryxx] has quit [Quit: Connection closed for inactivity]
18:19 -!- Sleepnbum [~Sleepnbum@72.67.47.196] has quit [Ping timeout: 240 seconds]
18:23 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
18:25 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-wizards
18:28 -!- FNinTak [~jonhbit@dhcp-18-111-16-181.dyn.mit.edu] has quit [Ping timeout: 250 seconds]
18:32 -!- dEBRUYNE [~dEBRUYNE@unaffiliated/debruyne] has quit [Quit: Leaving]
18:34 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
18:36 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-wizards
18:39 -!- renlord [~renlord@14-203-125-246.static.tpgi.com.au] has joined #bitcoin-wizards
18:46 -!- Nightwolf [~Nightwolf@unaffiliated/nightwolf] has quit [Read error: Connection reset by peer]
18:46 -!- Nightwolf [~Nightwolf@unaffiliated/nightwolf] has joined #bitcoin-wizards
18:51 -!- nonaTure [~nonaTure@p4FEB907D.dip0.t-ipconnect.de] has quit [Ping timeout: 258 seconds]
18:51 -!- nonaTure [~nonaTure@p4FEB8B5B.dip0.t-ipconnect.de] has joined #bitcoin-wizards
18:51 -!- FNinTak [~jonhbit@tsarviajado.media.mit.edu] has joined #bitcoin-wizards
19:03 -!- mdavid613 [~Adium@cpe-104-172-191-85.socal.res.rr.com] has quit [Quit: Leaving.]
19:09 -!- aalex [~aalex@64.187.177.58] has quit [Ping timeout: 244 seconds]
19:13 -!- aalex [~aalex@64.187.177.58] has joined #bitcoin-wizards
19:17 -!- dstadulis [~dstadulis@c-73-189-234-152.hsd1.ca.comcast.net] has joined #bitcoin-wizards
19:26 -!- proslogion [~proslogio@2.217.2.220] has quit [Ping timeout: 264 seconds]
19:30 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 252 seconds]
19:36 -!- renlord [~renlord@14-203-125-246.static.tpgi.com.au] has quit [Ping timeout: 244 seconds]
19:47 -!- nonaTure [~nonaTure@p4FEB8B5B.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]
19:57 -!- dstadulis [~dstadulis@c-73-189-234-152.hsd1.ca.comcast.net] has quit [Quit: ZZZzzz…]
19:59 -!- dstadulis [~dstadulis@c-73-189-234-152.hsd1.ca.comcast.net] has joined #bitcoin-wizards
20:14 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
20:15 -!- jtimon [~quassel@55.31.134.37.dynamic.jazztel.es] has quit [Ping timeout: 244 seconds]
20:16 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-wizards
20:21 -!- CrazyTruthYakDDS [uid67551@gateway/web/irccloud.com/x-ejufbktegtghhnkj] has quit [Quit: Connection closed for inactivity]
20:27 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
20:29 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-wizards
20:32 -!- renlord [~renlord@14-203-125-246.static.tpgi.com.au] has joined #bitcoin-wizards
20:32 -!- afk11 [~afk11@unaffiliated/afk11] has quit [Quit: ZNC 1.6.3 - http://znc.in]
20:40 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
20:42 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-wizards
20:43 -!- Sleepnbum [~Sleepnbum@173.55.57.163] has joined #bitcoin-wizards
20:45 -!- mdavid613 [~Adium@cpe-172-251-161-231.socal.res.rr.com] has joined #bitcoin-wizards
20:50 -!- dstadulis [~dstadulis@c-73-189-234-152.hsd1.ca.comcast.net] has quit [Quit: Textual IRC Client: www.textualapp.com]
20:51 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
20:53 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-wizards
21:14 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
21:16 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-wizards
21:22 -!- bildramer [~bildramer@ppp-94-67-126-179.home.otenet.gr] has joined #bitcoin-wizards
21:29 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
21:31 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards
21:31 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-wizards
21:43 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
21:45 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-wizards
21:54 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
21:56 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-wizards
22:03 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has quit [Quit: leaving]
22:07 -!- renlord [~renlord@14-203-125-246.static.tpgi.com.au] has quit [Ping timeout: 244 seconds]
22:13 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds]
22:13 -!- renlord [~renlord@14-203-125-246.static.tpgi.com.au] has joined #bitcoin-wizards
22:14 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
22:16 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-wizards
22:18 -!- Cloudflare [~cloudflar@unaffiliated/cloudflare] has joined #bitcoin-wizards
22:18 < Cloudflare> I was told there would be free bitcoins
22:18 < Cloudflare> Hi renlord
22:20 < Cloudflare> (pls no ban, I don't want any free btc)
22:21 < sipa> why would you not want free btc?!
22:21 < Cloudflare> sipa: because I am Satoshi
22:21 < Cloudflare> 😂
22:32 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
22:32 < Cloudflare> My rigs got hacked the other day
22:33 < Cloudflare> They stole my ethereum
22:33 < Cloudflare> But only a little bit of it
22:34 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 252 seconds]
22:34 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-wizards
22:43 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
22:45 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-wizards
22:48 -!- execut3 [~shesek@bzq-84-110-32-196.cablep.bezeqint.net] has quit [Ping timeout: 250 seconds]
22:48 -!- shesek [~shesek@bzq-84-110-32-196.cablep.bezeqint.net] has quit [Ping timeout: 244 seconds]
22:49 -!- Sleepnbum [~Sleepnbum@173.55.57.163] has quit [Ping timeout: 244 seconds]
23:09 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has joined #bitcoin-wizards
23:10 -!- jannes [~jannes@178.132.211.90] has quit [Ping timeout: 276 seconds]
23:39 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has quit [Remote host closed the connection]
23:49 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards
23:50 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection]
23:50 -!- jannes [~jannes@178.132.211.90] has joined #bitcoin-wizards
23:51 -!- xeon-enouf [~xeon-enou@unaffiliated/xeon-enouf] has quit [Ping timeout: 244 seconds]
23:53 -!- xeon-enouf [~xeon-enou@unaffiliated/xeon-enouf] has joined #bitcoin-wizards
23:55 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
23:55 -!- mdavid613 [~Adium@cpe-172-251-161-231.socal.res.rr.com] has quit [Quit: Leaving.]
23:56 -!- mdavid613 [~Adium@cpe-172-251-161-231.socal.res.rr.com] has joined #bitcoin-wizards
23:56 -!- mdavid613 [~Adium@cpe-172-251-161-231.socal.res.rr.com] has quit [Client Quit]
23:57 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-wizards
23:59 -!- tucenaber [~tucenaber@unaffiliated/tucenaber] has quit [Ping timeout: 264 seconds]
--- Log closed Wed Aug 10 00:00:21 2016