--- Log opened Sat Apr 11 00:00:49 2015 00:06 -!- hktud0 [wq@unaffiliated/fluffybunny] has quit [Read error: Connection reset by peer] 00:06 -!- c0rw1n [~c0rw1n@210.207-241-81.adsl-dyn.isp.belgacom.be] has quit [Remote host closed the connection] 00:07 -!- c0rw1n [~c0rw1n@210.207-241-81.adsl-dyn.isp.belgacom.be] has joined #bitcoin-wizards 00:08 -!- hktud0 [ncidsk@unaffiliated/fluffybunny] has joined #bitcoin-wizards 00:36 -!- AllieSenbub1 [~AllieS@c-98-210-139-204.hsd1.ca.comcast.net] has quit [Ping timeout: 240 seconds] 00:37 -!- AllieSenbub [~AllieS@c-98-210-139-204.hsd1.ca.comcast.net] has joined #bitcoin-wizards 00:42 -!- lclc [~lucas@unaffiliated/lclc] has quit [Ping timeout: 256 seconds] 00:45 -!- Pan0ram1x [~Pan0ram1x@095-096-084-122.static.chello.nl] has quit [Ping timeout: 245 seconds] 00:52 -!- Pan0ram1x [~Pan0ram1x@095-096-084-122.static.chello.nl] has joined #bitcoin-wizards 01:03 -!- Mably [~Mably@unaffiliated/mably] has quit [Ping timeout: 272 seconds] 01:04 -!- 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:11 -!- aakselrod [~kvirc@pool-96-253-123-21.rcmdva.fios.verizon.net] has quit [Ping timeout: 240 seconds] 01:12 -!- aakselrod [~kvirc@pool-96-253-123-21.rcmdva.fios.verizon.net] has joined #bitcoin-wizards 01:13 -!- lclc [~lucas@unaffiliated/lclc] has joined #bitcoin-wizards 01:14 -!- priidu [~priidu@unaffiliated/priidu] has quit [Ping timeout: 264 seconds] 01:18 -!- hearn [~mike@84-75-198-85.dclient.hispeed.ch] has joined #bitcoin-wizards 01:21 -!- Mably [~Mably@unaffiliated/mably] has joined #bitcoin-wizards 01:22 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-wizards 01:24 -!- spinza [~spin@197.89.184.143] has quit [Excess Flood] 01:28 -!- spinza [~spin@197.89.184.143] has joined #bitcoin-wizards 01:36 -!- damethos [~damethos@unaffiliated/damethos] has joined #bitcoin-wizards 01:45 -!- DrGrid [b2c5e2d1@gateway/web/cgi-irc/kiwiirc.com/ip.178.197.226.209] has joined #bitcoin-wizards 01:49 -!- wallet42 [~wallet42@95.6.28.61] has joined #bitcoin-wizards 01:49 -!- dEBRUYNE [~dEBRUYNE@239-196-ftth.onsbrabantnet.nl] has joined #bitcoin-wizards 01:54 -!- AllieSenbub [~AllieS@c-98-210-139-204.hsd1.ca.comcast.net] has quit [Quit: Leaving.] 01:55 -!- iugfhvybu [~vfbtgn@86.127.129.247] has quit [Ping timeout: 264 seconds] 01:59 -!- RoboTedd_ [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has joined #bitcoin-wizards 02:01 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has quit [Ping timeout: 252 seconds] 02:03 -!- RoboTedd_ [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has quit [Ping timeout: 245 seconds] 02:17 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)] 02:25 -!- hearn [~mike@84-75-198-85.dclient.hispeed.ch] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…] 02:27 -!- erasmospunk [~erasmospu@gateway/vpn/privateinternetaccess/erasmospunk] has joined #bitcoin-wizards 02:36 -!- x98gvyn [~vfbtgn@86.127.129.247] has joined #bitcoin-wizards 02:42 -!- jtimon [~quassel@189.Red-83-59-238.dynamicIP.rima-tde.net] has joined #bitcoin-wizards 02:43 -!- Crowley2k [~Crowley2k@93.113.62.93] has quit [Ping timeout: 250 seconds] 02:43 -!- Crowley2k [~Crowley2k@93.113.62.93] has joined #bitcoin-wizards 02:44 -!- wallet42 [~wallet42@95.6.28.61] has quit [Ping timeout: 276 seconds] 02:48 -!- erasmospunk [~erasmospu@gateway/vpn/privateinternetaccess/erasmospunk] has quit [Ping timeout: 256 seconds] 02:49 -!- luktgf [~vfbtgn@188.27.91.213] has joined #bitcoin-wizards 02:50 -!- erasmospunk [~erasmospu@178.162.211.232] has joined #bitcoin-wizards 02:51 -!- jtimon [~quassel@189.Red-83-59-238.dynamicIP.rima-tde.net] has quit [Ping timeout: 252 seconds] 02:51 -!- x98gvyn [~vfbtgn@86.127.129.247] has quit [Ping timeout: 245 seconds] 02:58 -!- luktgf [~vfbtgn@188.27.91.213] has quit [Read error: Connection reset by peer] 03:07 -!- lclc [~lucas@unaffiliated/lclc] has quit [Ping timeout: 265 seconds] 03:14 -!- pollux-bts [uid52270@gateway/web/irccloud.com/x-mwsttptobbkobydi] has quit [Quit: Connection closed for inactivity] 03:14 -!- cbeams [~cbeams@unaffiliated/cbeams] has joined #bitcoin-wizards 03:22 -!- x98gvyn [~vfbtgn@86.121.71.250] has joined #bitcoin-wizards 03:24 -!- cbeams [~cbeams@unaffiliated/cbeams] has quit [Remote host closed the connection] 03:29 -!- dEBRUYNE [~dEBRUYNE@239-196-ftth.onsbrabantnet.nl] has quit [Ping timeout: 252 seconds] 03:30 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has joined #bitcoin-wizards 03:32 -!- jtimon [~quassel@189.Red-83-59-238.dynamicIP.rima-tde.net] has joined #bitcoin-wizards 03:34 -!- erasmospunk [~erasmospu@178.162.211.232] has quit [Remote host closed the connection] 03:34 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has quit [Ping timeout: 240 seconds] 03:36 -!- moa [~kiwigb@opentransactions/dev/moa] has quit [Quit: Leaving.] 03:42 -!- x98gvyn [~vfbtgn@86.121.71.250] has quit [Read error: Connection reset by peer] 03:44 -!- x98gvyn [~vfbtgn@5-12-204-46.residential.rdsnet.ro] has joined #bitcoin-wizards 03:50 -!- NewLiberty [~NewLibert@2602:304:cff8:1580:c047:8aeb:b953:a993] has joined #bitcoin-wizards 04:07 -!- erasmospunk [~erasmospu@178.162.211.217] has joined #bitcoin-wizards 04:15 -!- lclc [~lucas@unaffiliated/lclc] has joined #bitcoin-wizards 04:16 -!- x98gvyn [~vfbtgn@5-12-204-46.residential.rdsnet.ro] has quit [Ping timeout: 265 seconds] 04:17 -!- damethos [~damethos@unaffiliated/damethos] has quit [Quit: Bye] 04:29 -!- damethos [~damethos@unaffiliated/damethos] has joined #bitcoin-wizards 04:30 -!- damethos [~damethos@unaffiliated/damethos] has quit [Client Quit] 04:31 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has joined #bitcoin-wizards 04:31 -!- x98gvyn [~vfbtgn@5-12-204-46.residential.rdsnet.ro] has joined #bitcoin-wizards 04:33 -!- crowleyman [crowleyman@gateway/shell/bnc4free/x-rexassodomyzfrvm] has quit [Remote host closed the connection] 04:35 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has quit [Ping timeout: 245 seconds] 04:42 -!- Quanttek [~quassel@ip1f10af17.dynamic.kabel-deutschland.de] has joined #bitcoin-wizards 04:49 -!- jgarzik [~jgarzik@unaffiliated/jgarzik] has joined #bitcoin-wizards 04:54 -!- adam3us [~Adium@modemcable130.142-161-184.mc.videotron.ca] has joined #bitcoin-wizards 04:59 -!- jtimon [~quassel@189.Red-83-59-238.dynamicIP.rima-tde.net] has quit [Ping timeout: 250 seconds] 05:00 -!- lclc [~lucas@unaffiliated/lclc] has quit [Ping timeout: 272 seconds] 05:07 -!- dEBRUYNE [~dEBRUYNE@239-196-ftth.onsbrabantnet.nl] has joined #bitcoin-wizards 05:14 -!- HostFat_ [~HostFat@adsl-ull-187-93.42-151.net24.it] has quit [Ping timeout: 245 seconds] 05:15 -!- bsm117532 [~bsm117532@static-108-21-236-13.nycmny.fios.verizon.net] has joined #bitcoin-wizards 05:20 -!- skeuomor1 [~skeuomorf@unaffiliated/skeuomorf] has joined #bitcoin-wizards 05:20 -!- skeuomor1 is now known as skeuomorf 05:26 -!- jhogan42 [~jhogan42@c-67-169-168-179.hsd1.ca.comcast.net] has quit [Quit: My Mac has gone to sleep. ZZZzzz…] 05:27 -!- lclc [~lucas@unaffiliated/lclc] has joined #bitcoin-wizards 05:29 -!- jb3000 [32bed4de@gateway/web/cgi-irc/kiwiirc.com/ip.50.190.212.222] has joined #bitcoin-wizards 05:31 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has joined #bitcoin-wizards 05:32 -!- skeuomorf [~skeuomorf@unaffiliated/skeuomorf] has quit [Ping timeout: 276 seconds] 05:33 -!- skeuomorf [~skeuomorf@unaffiliated/skeuomorf] has joined #bitcoin-wizards 05:36 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has quit [Ping timeout: 250 seconds] 05:37 -!- jb3000 [32bed4de@gateway/web/cgi-irc/kiwiirc.com/ip.50.190.212.222] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client] 05:48 -!- bsm117532 [~bsm117532@static-108-21-236-13.nycmny.fios.verizon.net] has quit [Remote host closed the connection] 05:49 -!- zooko [~user@184-96-103-97.hlrn.qwest.net] has joined #bitcoin-wizards 05:51 -!- bsm117532 [~bsm117532@static-108-21-236-13.nycmny.fios.verizon.net] has joined #bitcoin-wizards 05:54 -!- recalcitrant22 [~ubuntu@static-108-45-93-93.washdc.fios.verizon.net] has joined #bitcoin-wizards 05:59 -!- bsm117532 [~bsm117532@static-108-21-236-13.nycmny.fios.verizon.net] has quit [Ping timeout: 252 seconds] 06:02 -!- bsm117532 [~bsm117532@static-108-21-236-13.nycmny.fios.verizon.net] has joined #bitcoin-wizards 06:03 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 06:11 -!- zooko [~user@184-96-103-97.hlrn.qwest.net] has quit [Remote host closed the connection] 06:15 -!- lclc [~lucas@unaffiliated/lclc] has quit [Ping timeout: 250 seconds] 06:25 -!- adam3us [~Adium@modemcable130.142-161-184.mc.videotron.ca] has quit [Quit: Leaving.] 06:32 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has joined #bitcoin-wizards 06:34 -!- fanquake [~fanquake@unaffiliated/fanquake] has left #bitcoin-wizards [] 06:37 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has quit [Ping timeout: 250 seconds] 06:39 -!- btcdrak [uid52049@gateway/web/irccloud.com/x-cazuamsllwhyeliq] has quit [Quit: Connection closed for inactivity] 06:49 -!- lclc [~lucas@unaffiliated/lclc] has joined #bitcoin-wizards 06:50 -!- skeuomorf [~skeuomorf@unaffiliated/skeuomorf] has quit [Ping timeout: 256 seconds] 06:56 -!- btcdrak [uid52049@gateway/web/irccloud.com/x-fiwshphqjvilvbbg] has joined #bitcoin-wizards 07:00 -!- damethos [~damethos@unaffiliated/damethos] has joined #bitcoin-wizards 07:00 -!- Guest68867 is now known as amiller 07:00 -!- amiller [~socrates1@li175-104.members.linode.com] has quit [Changing host] 07:00 -!- amiller [~socrates1@unaffiliated/socrates1024] has joined #bitcoin-wizards 07:06 -!- x98gvyn [~vfbtgn@5-12-204-46.residential.rdsnet.ro] has quit [Ping timeout: 240 seconds] 07:07 -!- x98gvyn [~vfbtgn@188.27.89.70] has joined #bitcoin-wizards 07:15 -!- zmachine [uid53369@gateway/web/irccloud.com/x-ijjooeomkazaaayv] has joined #bitcoin-wizards 07:24 -!- NewLiberty [~NewLibert@2602:304:cff8:1580:c047:8aeb:b953:a993] has quit [Ping timeout: 245 seconds] 07:35 -!- binaryFate [~binaryFat@94-139-57-95.dsl.billi.be] has joined #bitcoin-wizards 07:40 -!- skeuomorf [~skeuomorf@unaffiliated/skeuomorf] has joined #bitcoin-wizards 07:43 -!- p15x [~p15x@182.50.108.93] has quit [Ping timeout: 245 seconds] 07:45 -!- p15x [~p15x@60.247.108.99] has joined #bitcoin-wizards 08:05 < gmaxwell> https://plus.google.com/103188246877163594460/posts/WTrnyFsRmHv 08:07 < jcorgan> congrats 08:07 < fluffypony> go rusty! 08:09 < amiller> nice 08:26 -!- recalcitrant22 [~ubuntu@static-108-45-93-93.washdc.fios.verizon.net] has quit [Ping timeout: 245 seconds] 08:29 -!- nessence [~alexl@c-68-51-194-2.hsd1.mi.comcast.net] has joined #bitcoin-wizards 08:34 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has joined #bitcoin-wizards 08:34 -!- priidu [~priidu@unaffiliated/priidu] has joined #bitcoin-wizards 08:34 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has quit [Read error: Connection reset by peer] 08:35 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has joined #bitcoin-wizards 08:38 -!- recalcitrant22 [~ubuntu@108.61.68.145] has joined #bitcoin-wizards 08:39 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has quit [Ping timeout: 240 seconds] 08:43 < kanzure> .title 08:43 < yoleaux> Leaving IBM May 4. Joining blockstream.com May 11. In 1997 I went to Usenix's… 08:48 -!- satwo [~satwo@unaffiliated/satwo] has joined #bitcoin-wizards 08:50 -!- hearn [~mike@84-75-198-85.dclient.hispeed.ch] has joined #bitcoin-wizards 08:50 -!- arubi_ [~ese168@unaffiliated/arubi] has quit [Quit: Leaving] 08:53 -!- MoALTz__ [~no@78.11.179.104] has quit [Quit: Leaving] 08:57 -!- x98gvyn [~vfbtgn@188.27.89.70] has quit [Ping timeout: 272 seconds] 08:58 -!- DrGrid [b2c5e2d1@gateway/web/cgi-irc/kiwiirc.com/ip.178.197.226.209] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client] 08:59 -!- x98gvyn [~vfbtgn@188.27.93.162] has joined #bitcoin-wizards 09:06 -!- x98gvyn [~vfbtgn@188.27.93.162] has quit [Ping timeout: 250 seconds] 09:09 -!- user7779078 [~user77790@ool-4a5987f1.dyn.optonline.net] has joined #bitcoin-wizards 09:13 -!- user7779078 [~user77790@ool-4a5987f1.dyn.optonline.net] has quit [Ping timeout: 245 seconds] 09:13 -!- user7779078 [user777907@gateway/vpn/mullvad/x-zgxapfpzxsexbtrv] has joined #bitcoin-wizards 09:21 -!- x98gvyn [~vfbtgn@188.27.93.162] has joined #bitcoin-wizards 09:24 -!- wallet42 [~wallet42@83.66.118.141] has joined #bitcoin-wizards 09:33 -!- yorick [~yorick@oftn/member/yorick] has quit [Read error: Connection reset by peer] 09:34 -!- Burrito [~Burrito@unaffiliated/burrito] has joined #bitcoin-wizards 09:35 -!- yorick [~yorick@oftn/member/yorick] has joined #bitcoin-wizards 09:35 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has joined #bitcoin-wizards 09:35 -!- yorick [~yorick@oftn/member/yorick] has quit [Remote host closed the connection] 09:36 -!- yorick [~yorick@ip51cd0513.speed.planet.nl] has joined #bitcoin-wizards 09:36 -!- yorick [~yorick@ip51cd0513.speed.planet.nl] has quit [Changing host] 09:36 -!- yorick [~yorick@oftn/member/yorick] has joined #bitcoin-wizards 09:37 -!- yorick [~yorick@oftn/member/yorick] has quit [Remote host closed the connection] 09:37 -!- yorick [~yorick@ip51cd0513.speed.planet.nl] has joined #bitcoin-wizards 09:37 -!- yorick [~yorick@ip51cd0513.speed.planet.nl] has quit [Changing host] 09:37 -!- yorick [~yorick@oftn/member/yorick] has joined #bitcoin-wizards 09:39 -!- hearn [~mike@84-75-198-85.dclient.hispeed.ch] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…] 09:40 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has quit [Ping timeout: 265 seconds] 09:44 -!- lclc [~lucas@unaffiliated/lclc] has quit [Ping timeout: 244 seconds] 09:46 -!- zmachine [uid53369@gateway/web/irccloud.com/x-ijjooeomkazaaayv] has quit [Quit: Connection closed for inactivity] 09:52 -!- shesek [~shesek@77.127.158.156] has quit [Ping timeout: 264 seconds] 09:53 -!- satwo [~satwo@unaffiliated/satwo] has quit [] 09:55 -!- hearn [~mike@84-75-198-85.dclient.hispeed.ch] has joined #bitcoin-wizards 09:57 -!- dEBRUYNE [~dEBRUYNE@239-196-ftth.onsbrabantnet.nl] has quit [Ping timeout: 252 seconds] 09:57 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has joined #bitcoin-wizards 10:02 -!- copumpkin [~copumpkin@unaffiliated/copumpkin] has joined #bitcoin-wizards 10:08 -!- dEBRUYNE [~dEBRUYNE@239-196-ftth.onsbrabantnet.nl] has joined #bitcoin-wizards 10:13 -!- wallet42 [~wallet42@83.66.118.141] has quit [Quit: Leaving.] 10:16 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…] 10:23 -!- wallet42 [~wallet42@83.66.118.141] has joined #bitcoin-wizards 10:23 -!- satwo [~satwo@unaffiliated/satwo] has joined #bitcoin-wizards 10:24 -!- fanquake1 [~fanquake@203-59-86-189.dyn.iinet.net.au] has joined #bitcoin-wizards 10:30 -!- wallet42 [~wallet42@83.66.118.141] has quit [Quit: Leaving.] 10:36 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has joined #bitcoin-wizards 10:39 -!- btcdrak [uid52049@gateway/web/irccloud.com/x-fiwshphqjvilvbbg] has quit [Quit: Connection closed for inactivity] 10:39 -!- HostFat [~HostFat@adsl-ull-187-93.42-151.net24.it] has joined #bitcoin-wizards 10:40 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has quit [Ping timeout: 245 seconds] 10:43 -!- bsm117532 [~bsm117532@static-108-21-236-13.nycmny.fios.verizon.net] has quit [Remote host closed the connection] 10:44 -!- bsm117532 [~bsm117532@static-108-21-236-13.nycmny.fios.verizon.net] has joined #bitcoin-wizards 10:46 -!- Crowley2k [~Crowley2k@93.113.62.93] has quit [Read error: Connection reset by peer] 10:49 -!- wallet42 [~wallet42@83.66.118.141] has joined #bitcoin-wizards 10:50 -!- Crowley2k [~Crowley2k@93.113.62.93] has joined #bitcoin-wizards 10:51 -!- CodeShark [~textual@cpe-76-167-237-202.san.res.rr.com] has quit [Ping timeout: 240 seconds] 10:51 -!- bitbumper [~bitbumper@161.47.143.24.cm.sunflower.com] has joined #bitcoin-wizards 10:52 -!- pollux-bts [uid52270@gateway/web/irccloud.com/x-vbxqtpbbejohthlo] has joined #bitcoin-wizards 10:56 -!- NewLiberty [~NewLibert@2602:304:cff8:1580:c047:8aeb:b953:a993] has joined #bitcoin-wizards 11:01 -!- bosma [~bosma@S01067cb21bda6531.vc.shawcable.net] has quit [Ping timeout: 272 seconds] 11:02 -!- lclc [~lucas@unaffiliated/lclc] has joined #bitcoin-wizards 11:06 -!- btcdrak [uid52049@gateway/web/irccloud.com/x-pqwxdboxcfmvlrgu] has joined #bitcoin-wizards 11:08 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has joined #bitcoin-wizards 11:12 -!- jhogan42 [~jhogan42@c-67-169-168-179.hsd1.ca.comcast.net] has joined #bitcoin-wizards 11:16 -!- lclc [~lucas@unaffiliated/lclc] has quit [Ping timeout: 250 seconds] 11:21 -!- erasmospunk [~erasmospu@178.162.211.217] has quit [Remote host closed the connection] 11:28 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…] 11:29 -!- recalcitrant22 [~ubuntu@108.61.68.145] has quit [Quit: Leaving] 11:30 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has joined #bitcoin-wizards 11:31 < Taek> rusty congrats 11:31 -!- nivah [~linker@183.91.30.143] has joined #bitcoin-wizards 11:32 < Taek> also congrats to blockstream 11:41 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has joined #bitcoin-wizards 11:48 -!- Crowley2k [~Crowley2k@93.113.62.93] has quit [Ping timeout: 265 seconds] 11:53 -!- koshii [~0@cm-171-100-165-124.revip10.asianet.co.th] has quit [Ping timeout: 250 seconds] 11:58 -!- SubCreative [~SubCreati@unaffiliated/cannacoin] has quit [Ping timeout: 264 seconds] 12:07 -!- damethos [~damethos@unaffiliated/damethos] has quit [Quit: Bye] 12:13 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…] 12:20 < jgarzik> Taek, great addition to the _bitcoin_ dev team :) 12:20 < jgarzik> (meaning the wider bitcoin community) 12:20 < jgarzik> The BTC community needs more smart, capable people like Rusty. 12:20 < bsm117532> What happened? 12:21 < andytoshi> +1 jgarzik , and congrats rusty 12:22 < jgarzik> 12:22 < jgarzik> I am vaguely tempted to see if I could find funding just to hire a "bitcoin intern" -- take a motivated C/C++'er and teach them bitcoin, to grow the community. Cheap payroll for me, intern learns bitcoin core, and the bitcoin community grows. 12:25 -!- bosma [~bosma@S01067cb21bda6531.vc.shawcable.net] has joined #bitcoin-wizards 12:26 -!- p15x [~p15x@60.247.108.99] has quit [Max SendQ exceeded] 12:30 -!- p15x [~p15x@60.247.108.99] has joined #bitcoin-wizards 12:31 -!- bosma [~bosma@S01067cb21bda6531.vc.shawcable.net] has quit [Ping timeout: 245 seconds] 12:32 < morcos> you should definitely do that! get a Ga Tech CS student for the summer 12:32 -!- p15x [~p15x@60.247.108.99] has quit [Max SendQ exceeded] 12:34 -!- Cornholio [Cornholi0@ip72-193-168-218.lv.lv.cox.net] has joined #bitcoin-wizards 12:34 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has quit [Ping timeout: 256 seconds] 12:34 -!- Cornholi0 [Cornholi0@unaffiliated/cornholi0] has quit [Ping timeout: 272 seconds] 12:35 < jgarzik> morcos, yup 12:38 -!- bosma [~bosma@S01067cb21bda6531.vc.shawcable.net] has joined #bitcoin-wizards 12:41 -!- Guest65932 [~guest@5ED11658.cm-7-2a.dynamic.ziggo.nl] has joined #bitcoin-wizards 12:44 -!- Starduster_ [~guest@unaffiliated/starduster] has quit [Ping timeout: 240 seconds] 12:44 -!- satwo [~satwo@unaffiliated/satwo] has quit [] 12:48 -!- Guest65932 [~guest@5ED11658.cm-7-2a.dynamic.ziggo.nl] has quit [Ping timeout: 240 seconds] 12:49 -!- arubi_ [~ese168@unaffiliated/arubi] has joined #bitcoin-wizards 12:52 -!- afk11 [~thomas@86.46.16.201] has joined #bitcoin-wizards 12:52 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-wizards 12:56 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has joined #bitcoin-wizards 12:56 -!- nuke_ [~nuke@176.92.19.38] has joined #bitcoin-wizards 12:58 -!- arubi_ [~ese168@unaffiliated/arubi] has quit [Quit: Leaving] 13:00 -!- nuke1989 [~nuke@46-149-36.adsl.cyta.gr] has quit [Ping timeout: 244 seconds] 13:00 -!- hearn [~mike@84-75-198-85.dclient.hispeed.ch] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…] 13:18 -!- Crowley2k [~Crowley2k@93.113.62.93] has joined #bitcoin-wizards 13:21 -!- IRCFrEAK [~jircii@dhcp-108-168-3-60.cable.user.start.ca] has joined #bitcoin-wizards 13:21 -!- IRCFrEAK is now known as thufir 13:23 -!- Starduster [~guest@unaffiliated/starduster] has joined #bitcoin-wizards 13:23 -!- AnoAnon [~AnoAnon@197.37.12.56] has joined #bitcoin-wizards 13:24 -!- AnoAnon [~AnoAnon@197.37.12.56] has quit [Max SendQ exceeded] 13:24 < thufir> So, my NSA killing project is about to have the first public PREVIEW release. It is cloud 2.0, decentralized. Next step is incentivized. It will use bitcoin. The hash power cannot be split. I grok this. This is a purpose other than enabling cloud 2.0. It gives bitcoin intrinsic value that exists only on the internet (ie, no exchange needed, my project is an exchange for btc->bandwidth,storage,and more). Anyways, I come to ask. 13:24 < thufir> Is bitcoin ready yet!?! IE: I NEED NLOCKTIMEDLAY!!! (or something like that to do probabilitc payments, channels, etc.. i need massive transaction amount) 13:25 < thufir> please say yes and how... 13:26 -!- adam3us [~Adium@207.253.217.242] has joined #bitcoin-wizards 13:26 < sipa> if by nlocktimedelay you mean checklocktimeverify (bip 65), feel free to help test the implenentation and contribute 13:27 < thufir> so that is enabled on test net at least? 13:27 < sipa> if you need massive transaction amount, the bitcoin blockchain won't help you (it is directly in conflict with the ability for the world to validate it) 13:27 < thufir> and thank you! for that information (i will read bip65) 13:28 < sipa> no, it is not even implemented entirely 13:28 < thufir> sipa: probabibilistic payments 13:28 < sipa> wrt killing the NSA: take it elsewhere 13:28 < thufir> 1/1bill lotto ticket = 1 billion x transaction count 13:28 < thufir> sure, if you are afraid of satan i understand 13:28 -!- damethos [~damethos@unaffiliated/damethos] has joined #bitcoin-wizards 13:29 < andytoshi> thufir: keep it civil 13:29 < thufir> andytoshi: i won't mention it again while sipa is around, i am civil. 13:29 < thufir> so is that nlock thing enabled on the test net? 13:30 < sipa> i just told you it is not even implemented entirely 13:31 < sipa> let alone an actual deployment plan 13:31 < sipa> let alone being in production 13:31 < andytoshi> thufir: it's not just sipa. this channel is about research and technology; while these sort of stuff is hard to separate from the political context there's no need for name-calling or manifesto-type comments 13:31 < thufir> don't be mad, i wasn't attacking you, i am just done with being afraid of them. we must be open, it is the antidote to their system. if we are open, we find each other. if we are closed, we find allies much slower. 13:31 < sipa> feel free to contribute to its development, however 13:32 < thufir> yes, sorry 13:32 < kanzure> inflammatory comments are obvious and they are very boring 13:33 < sipa> thufir: if i was afraid of them i wouldn't be asking you to stop talking about it in a publicly logged channel. this channel is about technical research. anything else is off topic, whether you agree with the statements or not 13:33 < thufir> i said none. only objective pragmatic fact. you are the ones who keep talking about that. i am here to yes, contribute to development 13:33 < thufir> asking me to stop is doing their job, so i would now guess yes, afriad 13:33 < thufir> lets stop talking about it then and talk about development, no? 13:33 < sipa> good 13:34 < kanzure> sipa: if he is this bad at thinking about that topic, why would you expect him to be capable of contributing on other topics 13:34 < thufir> so then, bip 65 is the state of the art in what I seek? (enabling probabilistic payments?) and it isn't implemented even in test net yet? i thought some nlocktimedelay was done and in testnet? 13:35 < sipa> i do not know what nlocktimedelay is, nor do i know the state of the art for probabilistic payments 13:35 < thufir> kanzure: not asking him then, but i don't judge, i hope he learns. i am open to all who want to join, regardless of their past. 13:35 < thufir> ok, i might have it wrong, sec... 13:35 -!- RoboTeddy [~roboteddy@c-67-180-192-179.hsd1.ca.comcast.net] has joined #bitcoin-wizards 13:36 < thufir> I guess it is just nLockTime (no delay) 13:36 < sipa> do you have some reference for s probabilistic payment scheme that uses nlocktimedelay (and do you have something describing what nlocktinedelay is, if not checklocktimeverify)? 13:36 < andytoshi> thufir: i think bip62 (non-malleability) is sufficient for probabilistic payments 13:37 < thufir> well, bip-65 is referenced as "revisiting nLockTime" by qntra.net 13:37 < thufir> i found now in search, thanks to you guys so thanks, and no hard feelings, i am just forward 13:37 < thufir> oh awesome andy! 13:37 < thufir> is that implemented in at least test net? :( :) 13:38 < thufir> because yes, only flaw of probabilistic payments is the darn malliability 13:38 < sipa> bip62 is not fully implemented 13:39 < thufir> because fixing malliability would save on tracactions.. nLockTime would require transactions still and might not really work for probabilisitc payments at the scale i know that fixing malliability would 13:39 < andytoshi> thufir: you can build and test systems which depend on bip62 since transactions which violate its restrictions are nonstandard to most nodes 13:40 < andytoshi> actual deployment would need to wait for it to be fully implemented 13:40 < sipa> andytoshi: the low-s rule is not enforced however 13:40 -!- damethos [~damethos@unaffiliated/damethos] has quit [Quit: Bye] 13:40 < andytoshi> oh, oops, i thought it was 13:40 < thufir> is it implemented enough that i could use testnet as the backing for my system? when you guys are ready i switch it over? testnet would be enough as my system is not gold if you loose it, just bandwidth 13:41 < sipa> no, it is not implemented enough 13:41 < sipa> nowhere 13:41 < thufir> ah ok, thank you! 13:42 < sipa> and implementation is not sufficient: you need the actual network to adopt it 13:42 < thufir> well, i might be joining your dev team to help because the free world needs cloud 2.0, and cloud 2.0 needs bitcoin (i refuse to use an alternative like creating a filecoin, i already know it must be bitcoin) 13:43 < thufir> but that sucks cause it will slow me down 13:43 < sipa> wth is cloud 2.0? 13:43 < sipa> stop using buzzwords 13:43 < thufir> my project. my purpose in life. 13:43 < fluffypony> sipa: it's just before cloud 3.0 13:43 < fluffypony> and inbetween IAAS 1.5 and SAAS 2.8 13:44 < thufir> ok, then you heard it here first. only the "unnamable" knows its name, and one friend. now you all do: morphis 13:44 < thufir> it deprecates bittorrent to start 13:45 < sipa> whitepaper? research? code? design documents? 13:45 < thufir> 3 months in the coding, years and years of thinking and planning. 13:45 < fluffypony> guitar lessons: http://www.morphis.com 13:45 < fluffypony> .title 13:45 < yoleaux> Beginner Guitar Lessons :: morphis.com 13:46 < thufir> i say maybe a month until preview release that will sufficiently deprecate bittorrent 13:46 < thufir> yes, i don't care 13:46 < thufir> morph.is 13:46 < thufir> :) 13:46 < thufir> eat your heart out guitar guy 13:46 < thufir> oh btw, i taught myself classical guitar, will check out your site :) 13:46 < kanzure> what is your opinion of mkultra 13:46 < fluffypony> where's bramc when you need him... 13:46 < thufir> might be what created me, 13:46 < fluffypony> thufir: it's not my site 13:47 < thufir> ah :( i could use more guitar expert friends 13:47 < thufir> kanzure: why do you ask? 13:48 < thufir> well, i also know it to be a failure. unless you wanted your control of the interenet to be lost 13:54 < thufir> I see. we'll i guess I'll wait for Todd. Thanks for the info so far though guys. 13:56 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…] 13:57 -!- SubCreative [~SubCreati@2601:8:a380:e29:81cc:502:a98b:d6f0] has joined #bitcoin-wizards 13:57 -!- SubCreative [~SubCreati@2601:8:a380:e29:81cc:502:a98b:d6f0] has quit [Changing host] 13:57 -!- SubCreative [~SubCreati@unaffiliated/cannacoin] has joined #bitcoin-wizards 14:07 -!- Sub|afk [~SubCreati@2601:8:a380:e29:c555:5318:daf2:c953] has joined #bitcoin-wizards 14:09 -!- SubCreative [~SubCreati@unaffiliated/cannacoin] has quit [Ping timeout: 245 seconds] 14:11 -!- Sub|afk is now known as SubCreative 14:11 -!- SubCreative [~SubCreati@2601:8:a380:e29:c555:5318:daf2:c953] has quit [Changing host] 14:11 -!- SubCreative [~SubCreati@unaffiliated/cannacoin] has joined #bitcoin-wizards 14:14 -!- dardasaba [~cinch@ec2-52-10-119-235.us-west-2.compute.amazonaws.com] has joined #bitcoin-wizards 14:15 -!- PRab [~chatzilla@2601:4:400:2105:91f6:b3f4:6f79:f8e6] has quit [Quit: ChatZilla 0.9.91.1 [Firefox 36.0.4/20150320202338]] 14:15 -!- dardasaba [~cinch@ec2-52-10-119-235.us-west-2.compute.amazonaws.com] has quit [Remote host closed the connection] 14:16 < thufir> so what is the low-s rule? 14:16 -!- dardasaba [~cinch@ec2-52-10-119-235.us-west-2.compute.amazonaws.com] has joined #bitcoin-wizards 14:16 -!- PRab [~chatzilla@2601:4:400:2105:91f6:b3f4:6f79:f8e6] has joined #bitcoin-wizards 14:16 -!- nullbyte [~WW@unaffiliated/loteriety] has quit [Quit: leaving] 14:17 -!- hhogan420 [~WW@unaffiliated/loteriety] has joined #bitcoin-wizards 14:18 < andytoshi> thufir: ECDSA sigs consist of a pair of numbers (s, r) which each live in a field of order roughly 2^256; turns out for each (s, r) that ($field_order - s, r) is also a valid sig, creating a degree of freedom that an attacker can use to change data on the wire (which doesn't affect any functionality but can confuse things); the low-s rule says that only one of these is actually valid, removing that 14:18 < andytoshi> degree of freedom 14:20 < thufir> so low-s means the sig is only valid if it is the lowest possible sig? so it is not implemented yet because? i guess it is impossible to know the lowest possible s (ie, someone might know math that would calculate a valid lower one) ? 14:21 < andytoshi> that's not what it means; it means exactly what i said. it's not implemented because it was overlooked that this degree of freedom could be problematic, it's still not problematic for systems in use today, and changes in a consensus system are slow to happen 14:21 < thufir> yes, i understand. i mean the low-s rule, it means only accept lowest s? 14:22 -!- b_lumenkraft [~b_lumenkr@unaffiliated/b-lumenkraft/x-4457406] has quit [Quit: b_lumenkraft] 14:22 < gmaxwell> What do you mean not implemented? all Bitcoin Core nodes produce low-s signatures, but it cannot be enforced in the network currently because it would break existing wallets. 14:22 < thufir> I don't know what you mean by "rule says that only one of these is actually valid". one of what? 14:23 < thufir> oh, is that all? 14:23 < thufir> like you guys know you know the math to know the lowest s? so you could implement such a rule? if only it didn't break existing wallets with higher s's? 14:23 < gmaxwell> It's implemented in bitcoin core, but not enforced for other people's transactions. 14:24 < thufir> wow. damn. i understand the problem that we can't force old wallets to have to move their coins. damn 14:24 < gmaxwell> not move their coins, but not create incompatible transactions. 14:25 -!- afk11 [~thomas@86.46.16.201] has quit [Remote host closed the connection] 14:25 < thufir> so can't it be simple like: if coins come from < block (351720) then don't apply low-s rule, otherwise, transaction must be low-s to be accepted? 14:26 < gmaxwell> Great, and now your coins are all stuck becuase you have some unupgradable hardware wallet. 14:27 < thufir> because that hardware wallet might genereate a non low-s new address? 14:27 < thufir> only generate 14:27 < gmaxwell> this has nothing to do with addresses. 14:27 < gmaxwell> It's the /SIGNATURE/. 14:28 -!- arubi_ [~ese168@unaffiliated/arubi] has joined #bitcoin-wizards 14:28 < Taek> while people are asking dumb questions: do schnorr signature schemes have curves? I confess I still don't understand them well 14:28 < thufir> hmm, ok i think i see. hardware wallet that makes high-s transaction signatures can't escape its coins 14:29 < thufir> gmaxwell: thank you immensiley. i am thinking :) 14:30 < thufir> it would be too much cpu or something for the rule i proposed to be instead of < block 351720, to instead be: if all input coins to a TX come from low-s signed transactions, then the TX must be low-s as well. 14:30 < gmaxwell> Taek: schnorr is a signature system based on groups where discrete logs are hard. 14:31 < gmaxwell> Taek: it can be used over integer rings or EC or other groups that have the right properties. 14:31 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has joined #bitcoin-wizards 14:31 < gmaxwell> thufir: what software people who send you coins runs doesn't imply anything about the software you run! 14:34 < thufir> but i mean if me and alice want to do something that requires malliability fixed, then i can transfer my coins into a valid low-s TX if they are not already. then I can do my probablistic TX to alice. she knows that since the coins in this probabilistic TX come from a low-s TX that the lotto ticket is valid? 14:36 < thufir> valid i mean safe, not winning, you knew that probably 14:36 < Taek> gmaxwell: ok, I think I understand that. You could use secp256k1 as 'g' because discrete logs are hard in that field? But more typically a Schnorr group is used? 14:37 < gmaxwell> I have never personally seen schnorr implemented over an integer ring in deployment. 14:38 < thufir> gmaxwell: does that solve it? ie, anyone else doesn't care about low/high-s. but for those who do because they are looking at a probabilistic ticket, they can know it is valid if it is low-s signed and all input coins come from low-s TXs, because that is the new low-s rule? 14:40 < thufir> your pause is getting me excited... because it means you haven't found the flaw yet? ;) 14:40 < gmaxwell> thufir: I am unable to decode your request! 14:40 < thufir> lol (crying laugh) :) 14:41 < gmaxwell> what the heck is a "probablistic ticket"? :) 14:41 < thufir> probabilistic payments 14:41 < thufir> only broken due to malleability 14:41 < andytoshi> thufir: the problem is that -in transit- somebody can change a signature from low-s to high-s; it doesn't matter if everyone involved agrees to use low-s 14:41 < thufir> a cheap way for 1 billion x tx on btc 14:41 < thufir> yes, humans won't like it. but autonomous agents won't mind 14:41 < gmaxwell> I think you need to step back and understand actually the mechenism by which things are broken. 14:42 < thufir> andytoshi: so if that high-s tx has only coins from low-s txs then it won't be accepted with my proposed low-s rule.? 14:42 < thufir> gmaxwell: i think i do understand it :) 14:42 < gmaxwell> (also, I'm not aware of probablistic payment scheme which is broken by malleability) 14:43 < gmaxwell> thufir: the transaction _you_ accept isn't your issue in any case. 14:43 < thufir> if i know the ticket i was given is low-s and matches the rule so low-s rule will be applied then i know the network won't accept any other 14:43 < andytoshi> thufir: you're confusing different parts of the system; coins don't come "from txs" (see https://download.wpsoftware.net/bitcoin/bitcoin-faq.pdf ) for an explanation of low-s vs high-s see https://download.wpsoftware.net/bitcoin/malleability-faq.pdf 14:44 < thufir> andytoshi: thx 14:44 < gmaxwell> thufir: we just explained that the network cannot currently reject violating transactions because that will break existing wallets. 14:44 < andytoshi> thufir: btw everything in there about mt gox is probably false 14:44 < andytoshi> but the technical content is correct 14:44 < thufir> gmaxwell: so are you saying one of the probabilistic payments schemes does work 100%? 14:45 < gmaxwell> I'm saying that issues they have are not malleability related. 14:45 < thufir> gmaxwell: even with my altered rule? existing wallets would make non low-s txs, but the coins would come from non... shit, i guess it is random. its coins might be in low-s TXs but its next TX it would ever generate is high-s? that is the issue? 14:45 < thufir> gmaxwell: i've heard that before that the only issue is humans 14:46 < andytoshi> thufir: you aren't making sense, please read the PDFs i linked you 14:46 < thufir> gmaxwell: is that what you mean? human acceptance of a losing lotto ticket as payment? 14:46 < thufir> gmaxwell: if that is the only problem, my system doesn't mind that, it understands that is a valid payment.. the risk 14:46 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Remote host closed the connection] 14:46 < thufir> andytoshi: i am, thank you 14:46 < gmaxwell> thufir: thats a problem with it, most people reject the idea very agressively in my expirence. Not the only one. 14:47 < thufir> gmaxwell: ok, that one for me is 100% not relivent. I do understand it, but for my system to use it in the background it doesn't mind what humans think. 14:47 < thufir> gmaxwell: what are the other problems if not malleability? 14:47 < thufir> andytoshi: i did read these back in mtgox days, still thank you 14:48 < gmaxwell> What made you think malleability was an issue at all? All the proposals I've seen have double spending problems. 14:48 < thufir> exactly. isn't that due to malleability? 14:48 < thufir> that the double spend is possible? 14:48 < gmaxwell> No. 14:49 < gmaxwell> e.g. you use the same coin to probablistically pay many people concurrently instead of sequentially. 14:49 < thufir> hmm 14:50 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…] 14:50 < thufir> from https://en.bitcoin.it/wiki/Nanopayments: "If need be, this could be solved with hub servers that nanopayment recipients would use to announce coins currently in use to other nanopayment recipients." 14:50 < thufir> so that is what you are speaking of then 14:50 < thufir> that is the problem and if i fix that then malliability is for sure not a problem? 14:51 < gmaxwell> thufir: I still have no idea why you thought malleability was an issue to begin with! 14:51 < thufir> because my system deprecates 'hub servers' so very well might be the symbiant of bitcoin that fixes nano-payments 14:51 < gmaxwell> (for that application) 14:52 < gmaxwell> thufir: that fix requires they be a semitrusted cosigner on the coins. 14:52 < thufir> i am sorry, it is not fresh in my mind. i realized it when mtgox made it an issue. so i forget the thinking. 14:52 < andytoshi> gmaxwell: iirc a payment that goes through is a pair of chained transactions that get confirmed together 14:53 < andytoshi> so there's a potential loss if the first gets marred then confirmed 14:53 -!- Cornholio is now known as Cornholi0 14:53 -!- Cornholi0 [Cornholi0@ip72-193-168-218.lv.lv.cox.net] has quit [Changing host] 14:53 -!- Cornholi0 [Cornholi0@unaffiliated/cornholi0] has joined #bitcoin-wizards 14:53 < thufir> yes, what andy is saying sounds familiar 14:53 < thufir> if i had a winning ticket they can jam it or whatever he is saying 14:53 < thufir> before i broadcast it 14:53 < gmaxwell> andytoshi: in the last protocol I remembered all it did is jam. 14:53 < thufir> i think they invalidate the tx the coins in the winning ticket came from 14:54 < thufir> i can fix the semitructed cosigner to fix the double spend. i believe it in easy due to nature of my system 14:54 < gmaxwell> I find this doubtful. 14:54 < thufir> but that thing andytoshi is talking about I do not know how to solve unless my low-s rules sounds good?? 14:54 < andytoshi> gmaxwell: the one in the wiki can't jam, the payer creates a tx and sends it to the payee, that is the entirety of the payment 14:54 < andytoshi> then if it happens to be valid, the payee broadcasts it 14:55 < gmaxwell> andytoshi: yea, indeed. 14:57 < thufir> so by your opinions, the link i sent nanopayments. if my code doesn't mind like a human (that isn't the issue), and i have a magic oracle to register the source tx with like the wiki says: "A hub server would be pretty simple, just a single lookup table. A merchant sends it a reserve message. The server checks that the signature matches the coin. If a reserve is already in effect for that coin, it returns an error, otherwise 14:57 < thufir> OK." (just assume like human problem this doesn't exist), then in your guys exper opinions, the wiki nanopayment is 100% perfect? no malleability problem? 14:57 < andytoshi> i also had some idea that double-spending wasn't a problem except with pretty low probability (if you send two payments then 0, 1 or 2 of the will go through; if you double-spend then the "2" case results in theft, but that's unlikely), but i can't remember the details 14:57 < andytoshi> and to double-spend you need your txid guess to be in-range for multiple probabilistic transactions, which if the range is small and random, is unlikely to occur 14:58 < gmaxwell> andytoshi: you _always_ concurrently spend, it's a direct division of your payment, undetectably, proportially to the parallelism you can achieve. 14:58 < andytoshi> thufir: ...but i really didn't think these things through, please don't go building systems based on these half-bakked thoughts! 14:58 < thufir> hehe 14:58 < thufir> no thank you so much 14:58 < andytoshi> gmaxwell: oh, right, derp 14:59 < thufir> andytoshi: i am sorry to say that i am already 3 months into full time development of it, 1 month until first version (0 bitcoin in it) 14:59 < thufir> andytoshi: but next step is what i've planned for years, since you first proposed nanopayments! 15:00 < gmaxwell> if you have a (semi-)trusted cosigner then you can stop the multiplication. 15:00 < andytoshi> thufir: i didn't propose them, it was mike caldwell i think, i had an old article about them that didn't cite him upfront (but it is now fixed to do this) 15:00 < thufir> i stand on the shoulder of giants. credit to you all 15:01 < thufir> thanks both of you for your time so far, i can't thank you enough. well, hopefully my contribution helps 15:04 < thufir> My name is Sam Maloney, btw. This is my usual nick on freenode. Take care for now. 15:07 -!- Sub|afk [~SubCreati@2601:8:a380:e29:143f:7a56:b480:1e1d] has joined #bitcoin-wizards 15:08 -!- thufir [~jircii@dhcp-108-168-3-60.cable.user.start.ca] has quit [Changing host] 15:08 -!- thufir [~jircii@unaffiliated/thufir] has joined #bitcoin-wizards 15:08 -!- SubCreative [~SubCreati@unaffiliated/cannacoin] has quit [Ping timeout: 245 seconds] 15:15 -!- metamarc [~snizysnaz@unaffiliated/agorist000] has joined #bitcoin-wizards 15:21 -!- metamarc [~snizysnaz@unaffiliated/agorist000] has quit [Ping timeout: 252 seconds] 15:38 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has joined #bitcoin-wizards 16:03 -!- dEBRUYNE [~dEBRUYNE@239-196-ftth.onsbrabantnet.nl] has quit [Ping timeout: 240 seconds] 16:07 -!- mengine [~mengine@14.84-234-132.customer.lyse.net] has quit [Ping timeout: 245 seconds] 16:11 -!- wallet42 [~wallet42@83.66.118.141] has quit [Quit: Leaving.] 16:11 -!- wallet42 [~wallet42@83.66.118.141] has joined #bitcoin-wizards 16:11 -!- wallet42 [~wallet42@83.66.118.141] has quit [Client Quit] 16:21 -!- Sub|afk is now known as SubCreative 16:21 -!- SubCreative [~SubCreati@2601:8:a380:e29:143f:7a56:b480:1e1d] has quit [Changing host] 16:21 -!- SubCreative [~SubCreati@unaffiliated/cannacoin] has joined #bitcoin-wizards 16:23 -!- Crowley2k [~Crowley2k@93.113.62.93] has quit [Ping timeout: 240 seconds] 16:23 -!- adam3us [~Adium@207.253.217.242] has quit [Quit: Leaving.] 16:27 < Eliel> if there's just one extra version of a tx producable through malleability, then couldn't you just produce continuation txs for both versions to effectively make malleability a non-issue? 16:28 -!- satwo [~satwo@unaffiliated/satwo] has joined #bitcoin-wizards 16:44 -!- unlord [~nathan@pool-173-79-149-156.washdc.fios.verizon.net] has joined #bitcoin-wizards 16:47 -!- unlord_ [~nathan@pool-173-79-149-156.washdc.fios.verizon.net] has quit [Ping timeout: 246 seconds] 16:52 -!- belcher [~belcher-s@unaffiliated/belcher] has joined #bitcoin-wizards 17:00 -!- skeuomorf [~skeuomorf@unaffiliated/skeuomorf] has quit [Ping timeout: 240 seconds] 17:03 -!- d1ggy [~d1ggy@dslb-092-077-241-011.092.077.pools.vodafone-ip.de] has joined #bitcoin-wizards 17:06 -!- d1ggy_ [~d1ggy@dslb-188-108-088-146.188.108.pools.vodafone-ip.de] has quit [Ping timeout: 240 seconds] 17:13 -!- bit2017 [~linker@183.91.30.143] has joined #bitcoin-wizards 17:14 -!- psgs [~psgs@CPE-58-174-37-49.mjcz1.woo.bigpond.net.au] has joined #bitcoin-wizards 17:17 -!- nivah [~linker@183.91.30.143] has quit [Ping timeout: 265 seconds] 17:17 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Ping timeout: 272 seconds] 17:18 -!- CodeShark [~textual@cpe-76-167-237-202.san.res.rr.com] has joined #bitcoin-wizards 17:22 < thufir> Eliel: i think there are essentially 2^256 different valid ones, not just one 17:26 < sipa> for ECDSA, just one 17:27 < sipa> but read BIP62, there are many ways through which a transaction can br malleated that does not rely on ECDSA malleability 17:28 -!- Mably [~Mably@unaffiliated/mably] has quit [Ping timeout: 245 seconds] 17:29 -!- metamarc [~snizysnaz@unaffiliated/agorist000] has joined #bitcoin-wizards 17:33 -!- justanotheruser [~Justan@c-24-13-158-60.hsd1.in.comcast.net] has joined #bitcoin-wizards 17:33 -!- justanotheruser [~Justan@c-24-13-158-60.hsd1.in.comcast.net] has quit [Changing host] 17:33 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-wizards 17:38 -!- metamarc [~snizysnaz@unaffiliated/agorist000] has quit [Ping timeout: 252 seconds] 17:41 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-wizards 17:42 < hhogan420> i conco 17:43 < hhogan420> concur*, if anything the bullet point summary was a really important takeaway for understanding malleability 'vectors' 17:43 -!- fanquake1 [~fanquake@203-59-86-189.dyn.iinet.net.au] has quit [Ping timeout: 250 seconds] 17:43 < hhogan420> (from BIP62) 17:56 -!- user7779078 [user777907@gateway/vpn/mullvad/x-zgxapfpzxsexbtrv] has quit [Remote host closed the connection] 17:59 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #bitcoin-wizards 18:00 -!- spinza [~spin@197.89.184.143] has quit [Excess Flood] 18:01 -!- spinza [~spin@197.89.184.143] has joined #bitcoin-wizards 18:04 -!- dabura667 [uid43070@gateway/web/irccloud.com/x-ktcmepgggbkqlalp] has joined #bitcoin-wizards 18:06 -!- RoboTeddy [~roboteddy@c-67-180-192-179.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 18:06 -!- belcher [~belcher-s@unaffiliated/belcher] has quit [Quit: Leaving] 18:06 -!- psgs [~psgs@CPE-58-174-37-49.mjcz1.woo.bigpond.net.au] has quit [Quit: Leaving] 18:16 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…] 18:24 -!- priidu [~priidu@unaffiliated/priidu] has quit [Ping timeout: 256 seconds] 18:25 -!- koshii [~0@cm-171-100-165-124.revip10.asianet.co.th] has joined #bitcoin-wizards 18:25 -!- bit2017 [~linker@183.91.30.143] has quit [Ping timeout: 264 seconds] 18:26 -!- koshii [~0@cm-171-100-165-124.revip10.asianet.co.th] has quit [Client Quit] 18:28 -!- koshii [~0@cm-171-100-165-124.revip10.asianet.co.th] has joined #bitcoin-wizards 18:32 -!- adam3us [~Adium@modemcable130.142-161-184.mc.videotron.ca] has joined #bitcoin-wizards 18:54 -!- Burrito [~Burrito@unaffiliated/burrito] has quit [Quit: Leaving] 19:01 -!- Dr-G2 [~Dr-G@xd9ba10d6.dyn.telefonica.de] has joined #bitcoin-wizards 19:01 -!- Dr-G [~Dr-G@unaffiliated/dr-g] has quit [Disconnected by services] 19:02 -!- Quanttek [~quassel@ip1f10af17.dynamic.kabel-deutschland.de] has quit [Ping timeout: 264 seconds] 19:08 -!- hhogan420 [~WW@unaffiliated/loteriety] has quit [Ping timeout: 250 seconds] 19:14 -!- zooko [~user@c-75-70-204-109.hsd1.co.comcast.net] has joined #bitcoin-wizards 19:24 -!- Starduster [~guest@unaffiliated/starduster] has quit [Read error: Connection reset by peer] 19:25 -!- Starduster [~guest@unaffiliated/starduster] has joined #bitcoin-wizards 19:34 -!- Sub|afk [~SubCreati@c-76-121-19-166.hsd1.wa.comcast.net] has joined #bitcoin-wizards 19:34 -!- dEBRUYNE [~dEBRUYNE@239-196-ftth.onsbrabantnet.nl] has joined #bitcoin-wizards 19:36 -!- SubCreative [~SubCreati@unaffiliated/cannacoin] has quit [Ping timeout: 245 seconds] 19:37 -!- airbreather [~AirBreath@d149-67-99-43.nap.wideopenwest.com] has quit [Read error: Connection reset by peer] 19:39 -!- Sub|afk is now known as SubCreative 19:39 -!- SubCreative [~SubCreati@c-76-121-19-166.hsd1.wa.comcast.net] has quit [Changing host] 19:39 -!- SubCreative [~SubCreati@unaffiliated/cannacoin] has joined #bitcoin-wizards 19:41 -!- airbreather [~AirBreath@d149-67-99-43.nap.wideopenwest.com] has joined #bitcoin-wizards 19:44 -!- adam3us [~Adium@modemcable130.142-161-184.mc.videotron.ca] has quit [Quit: Leaving.] 19:53 -!- JoiIto [~textual@c-50-137-79-91.hsd1.ma.comcast.net] has joined #bitcoin-wizards 19:57 -!- jeremyrubin [~chatzilla@2601:6:8000:4a8:4d86:873e:12b1:f83] has joined #bitcoin-wizards 20:08 -!- user7779_ [user777907@gateway/vpn/mullvad/x-penaenjutoztnixw] has joined #bitcoin-wizards 20:09 -!- hhogan420 [WW@unaffiliated/loteriety] has joined #bitcoin-wizards 20:09 -!- hhogan420 [WW@unaffiliated/loteriety] has quit [Changing host] 20:09 -!- hhogan420 [WW@gateway/vpn/mullvad/x-inymajjwxkrnvpjn] has joined #bitcoin-wizards 20:10 < rusty> Hmm, would it ease enforcement of low-s-value normalized txs if bitcoin core flipped non-conformant signatures? A bit weird, of course, to normalize other peoples transactions... 20:11 < phantomcircuit> rusty, there's nodes that add null padding 20:11 < phantomcircuit> so why not 20:11 < rusty> phantomcircuit: null padding? 20:12 < sipa> rusty: i don't think it would help 20:12 < phantomcircuit> openssl didn't correctly enforce the DER minimum encoding rules until very recently 20:12 < sipa> enforcement is about being sure that no malleated form enters the blockchain 20:12 < sipa> phantomcircuit: it also did not intend to 20:12 < phantomcircuit> so you were free to add null padding since it was BER 20:12 -!- unlord_ [~nathan@pool-173-79-149-156.washdc.fios.verizon.net] has joined #bitcoin-wizards 20:13 < phantomcircuit> sipa, the function names indicate someone at some point intended to 20:13 < phantomcircuit> d2i and such 20:13 < sipa> well they have a fully fledger ber decoder 20:13 < rusty> sipa: sure, so you start with making them non-standard (but do the normalized step first), then later at some point soft-fork to make them invalid. 20:13 < phantomcircuit> (btw they didn't fix the actual decoder, they merely do a decode/encode/compare) 20:14 < phantomcircuit> sipa, sure but that is a super set of a der decoder 20:14 < sipa> rusty: that would hurt wallets more than just making it opt-in 20:15 < sipa> phantomcircuit: if the intention was not supporting full ber, they could have used 10 times less code 20:15 < phantomcircuit> to be fair i wouldn't suggest they actually fix the DER functions since it's such a mess of macros 20:15 -!- dabura667 [uid43070@gateway/web/irccloud.com/x-ktcmepgggbkqlalp] has quit [Quit: Connection closed for inactivity] 20:15 < sipa> i am pretty sure that the intention was supporting full ber on decoding 20:15 -!- unlord [~nathan@pool-173-79-149-156.washdc.fios.verizon.net] has quit [Ping timeout: 246 seconds] 20:16 < phantomcircuit> sipa, i was under the impression that DER is simply the minimal encoding of BER 20:16 < sipa> indeed 20:16 < phantomcircuit> is that wrong? 20:16 < rusty> sipa: by making it opt-in, you're suggesting some kind of "normalized-only" sighash flag? 20:16 < sipa> rusty: i am suggesting bip 62 :) 20:17 < sipa> normalizing sighashes is not avoiding malleability... it is making malleability harmless 20:17 < sipa> bip 62 provides an opt-in way to have consensus rule enforce a single encoding of a transaction 20:17 < sipa> but bip62 does not protect against a sender re-signing 20:19 -!- NewLiberty [~NewLibert@2602:304:cff8:1580:c047:8aeb:b953:a993] has quit [Ping timeout: 245 seconds] 20:19 < rusty> sipa: Thanks, I missed that nuance when I read "but it cannot be enforced in the network currently because it would break existing wallets." from gmaxwell in earlier logs. 20:20 < phantomcircuit> sipa, so it looks like DER is strictly a subset of BER with a bunch of encoding constraints intended to maintain 1:1 value:encoding mapping 20:21 < sipa> yup 20:21 < sipa> D = distinguished 20:21 < phantomcircuit> so what 20:21 -!- [7] [~quassel@rockbox/developer/TheSeven] has quit [Disconnected by services] 20:22 < phantomcircuit> someone implemented BER because they didn't understand the purpose of DER? 20:22 -!- TheSeven [~quassel@rockbox/developer/TheSeven] has joined #bitcoin-wizards 20:22 < sipa> no 20:22 < phantomcircuit> the decoding function names seem to indicate they intended them to use DER at some point 20:22 < sipa> i am pretty sure that the intention was supporting full ber 20:22 < phantomcircuit> that's mad 20:22 < sipa> even if the standard says using der 20:23 < sipa> one would want to support more than strictly necessary on input 20:23 < sipa> that was fashionable at some point 20:23 < sipa> be strict on output, not strict on input 20:24 < rusty> sipa: a-la Postel 20:24 < phantomcircuit> sipa, ichy 20:24 * sipa scratches 20:24 < phantomcircuit> ichy not itchy... 20:25 < sipa> ah 20:25 < phantomcircuit> i can see that in non security things 20:25 < sipa> yup 20:25 < sipa> but even then 20:25 < sipa> it makes behaviour unpredictable 20:26 -!- binaryFate [~binaryFat@94-139-57-95.dsl.billi.be] has quit [Quit: Konversation terminated!] 20:26 < phantomcircuit> sipa, sure but for example a date field on some website accepting 2015-03-13 and 03/13/15 20:27 < phantomcircuit> seems reasonable (note not 03/03/15 ...) 20:27 < phantomcircuit> ok so maybe bad example... 20:28 < sipa> even for unix tools etc 20:29 < sipa> it results in differences between different platforms/implementation 20:29 < sipa> at least for DER it was well defined what the "correct" subset was supposed to be 20:30 < sipa> but how many people here have actually read the DER standard? :) 20:31 < rusty> sipa: using DER/BER was weird in the first place though. Two 32-byte integers would have been simpler and more optimal. 20:31 < thufir> why not just serialize the numbers as straight forward as possible? why use their purposely convoluted standards? 20:31 < thufir> heh, exactly! 20:32 < sipa> thufir: ask satoshi 20:32 < sipa> i don't think anyone disagrees with this 20:32 < sipa> but change is ridiculously hard 20:32 < thufir> ok, i'll get around to it ;) 20:32 < thufir> yea, true. so that is the answer then, hehe 20:33 < phantomcircuit> rusty, there is virtually zero documentation on what the openssl signature structure is 20:34 -!- moa [~kiwigb@opentransactions/dev/moa] has joined #bitcoin-wizards 20:34 < sipa> the code is self-documenting! 20:34 < phantomcircuit> (like 90% of openssl) 20:34 < thufir> my purposed DER replacement: http://pastebin.com/VvzyRTPB 20:34 < phantomcircuit> sipa, yeah like how the d2i functions are defined by macros at compile time and are roughly impossible to find 20:34 < sipa> thufir: we're not using rsa 20:35 < thufir> yes of course, adapt it. mostly a joke on how silly it is to use der/whatever. 20:35 < sipa> oh, sure, fully agree there 20:38 < thufir> you know, i looked at implementing either TLS or SSH-TRANSPORT in my project. I went with SSH because it took me a couple weeks to do it from scratch from RFCs. Looking at TLS, it would take me a year, and most of that would be implementing the crazy encoding of the certificates. that is practically a turing complete language onto itself. complication is bad, i think put there on purpose. more surface area for bugs. 20:40 < thufir> ie, the biggest surface area of attack in my opinion on TLS is the encoding of the certs. encoding. so change is hard, but, keep that in mind is all. 20:43 < thufir> not saying at all satoshi did. he was pragmatic and chose what tools were available to get 'er done. 20:45 -!- JoiIto [~textual@c-50-137-79-91.hsd1.ma.comcast.net] has quit [Quit: Textual IRC Client: www.textualapp.com] 20:51 < phantomcircuit> thufir, SSH-TRANSPORT being the ssh protocol itself or some sort of transit over ssh using the openbsd ssh-client ? 20:51 < phantomcircuit> i wouldn't suggest reimplementing ssh either... 20:52 < thufir> in the rfcs its broken up into SSH-AUTH, SSH-TRANSPORT, and SSH-CONNECT, essentially the SSH auth, encryption, integrety, and multiplexing 20:52 < thufir> basically the best damn p2p protocol now thanks to python asyncio and my python asyncio ssh implementation. 20:53 < thufir> i needed a high performance encrypted p2p library. i didn't want to 'invent it myself' and fail at security, so i followed the rfcs. its cool because i can ssh into my program with openssh :) 20:54 < thufir> i would have used paraminko, but as I said, i needed a high perf one, so async io. twisted is twisted, so yea :) 20:55 < thufir> i'll release it lgpl in a few weeks along with my gpl program 20:57 -!- bsm117532 [~bsm117532@static-108-21-236-13.nycmny.fios.verizon.net] has quit [Ping timeout: 264 seconds] 21:11 -!- sofdg2 [~sofdg2@unaffiliated/sofdg2] has joined #bitcoin-wizards 21:12 -!- nemela [~000100@unaffiliated/sheer] has joined #bitcoin-wizards 21:15 -!- nemela [~000100@unaffiliated/sheer] has quit [Max SendQ exceeded] 21:22 -!- ucerron [49cc4c7f@gateway/web/freenode/ip.73.204.76.127] has joined #bitcoin-wizards 21:24 -!- nullusr1 [~macbook@173.209.46.138] has joined #bitcoin-wizards 21:25 -!- nullusr1 [~macbook@173.209.46.138] has quit [Client Quit] 21:32 -!- zooko` [~user@c-75-70-204-109.hsd1.co.comcast.net] has joined #bitcoin-wizards 21:34 -!- zooko [~user@c-75-70-204-109.hsd1.co.comcast.net] has quit [Ping timeout: 250 seconds] 21:52 -!- zooko` [~user@c-75-70-204-109.hsd1.co.comcast.net] has quit [Remote host closed the connection] 22:04 -!- dEBRUYNE [~dEBRUYNE@239-196-ftth.onsbrabantnet.nl] has quit [Ping timeout: 252 seconds] 22:05 -!- bitbumper [~bitbumper@161.47.143.24.cm.sunflower.com] has quit [Quit: Leaving] 22:06 -!- ucerron [49cc4c7f@gateway/web/freenode/ip.73.204.76.127] has quit [Quit: Page closed] 22:15 -!- Cornholio [Cornholi0@ip72-193-168-218.lv.lv.cox.net] has joined #bitcoin-wizards 22:17 -!- Cornholi0 [Cornholi0@unaffiliated/cornholi0] has quit [Ping timeout: 264 seconds] 22:20 -!- user7779078 [~user77790@ool-4a5987f1.dyn.optonline.net] has joined #bitcoin-wizards 22:22 -!- user7779_ [user777907@gateway/vpn/mullvad/x-penaenjutoztnixw] has quit [Ping timeout: 252 seconds] 22:24 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Ping timeout: 244 seconds] 22:27 -!- Cornholi0 [Cornholi0@unaffiliated/cornholi0] has joined #bitcoin-wizards 22:28 -!- Cornholio [Cornholi0@ip72-193-168-218.lv.lv.cox.net] has quit [Ping timeout: 245 seconds] 22:34 -!- pollux-bts [uid52270@gateway/web/irccloud.com/x-vbxqtpbbejohthlo] has quit [Quit: Connection closed for inactivity] 22:36 -!- Crowley2k [~Crowley2k@93.113.62.93] has joined #bitcoin-wizards 22:43 -!- andy-logbot [~bitcoin--@wpsoftware.net] has quit [Ping timeout: 252 seconds] 22:44 -!- apoelstra [18e3de9d@gateway/web/freenode/ip.24.227.222.157] has joined #bitcoin-wizards 22:44 -!- andytoshi [~andytoshi@unaffiliated/andytoshi] has quit [Ping timeout: 272 seconds] 22:45 -!- arubi_ [~ese168@unaffiliated/arubi] has quit [Ping timeout: 264 seconds] 22:46 -!- btcdrak_ [uid52049@gateway/web/irccloud.com/x-mozngasrfdwgaald] has joined #bitcoin-wizards 22:46 -!- dasource_ [uid48409@gateway/web/irccloud.com/x-gngnpmatdmivuwlb] has joined #bitcoin-wizards 22:46 -!- andytoshi [~andytoshi@unaffiliated/andytoshi] has joined #bitcoin-wizards 22:47 -!- apoelstra [18e3de9d@gateway/web/freenode/ip.24.227.222.157] has quit [Client Quit] 22:47 -!- NeatBasisW [quasselcor@irc.bittiraha.fi] has joined #bitcoin-wizards 22:47 -!- jbenet_ [sid17552@gateway/web/irccloud.com/x-ctnmvcqsuwmfteyi] has joined #bitcoin-wizards 22:48 -!- btc____ [sid40798@gateway/web/irccloud.com/x-ffumfpwmuyeaxtxk] has joined #bitcoin-wizards 22:48 -!- richardu1 [~richardus@2605:2700:0:3::4713:9a16] has joined #bitcoin-wizards 22:49 -!- mappum_ [sid43795@gateway/web/irccloud.com/x-iemztinuprtswzid] has joined #bitcoin-wizards 22:49 -!- wump [~quassel@pdpc/supporter/professional/wumpus] has joined #bitcoin-wizards 22:50 -!- cfields_ [~quassel@unaffiliated/cfields] has joined #bitcoin-wizards 22:53 -!- Netsplit *.net <-> *.split quits: mappum, jbenet, NeatBasis, forrestv, dasource, richardus, wumpus, Krellan, btc___, cfields, (+1 more, use /NETSPLIT to show all of them) 22:54 -!- btcdrak_ is now known as btcdrak 22:55 -!- dasource_ is now known as dasource 22:55 -!- mappum_ is now known as mappum 22:56 -!- btc____ is now known as btc___ 22:57 -!- jbenet_ is now known as jbenet 22:59 -!- Netsplit over, joins: Krellan 23:01 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-wizards 23:01 -!- forrestv [forrestv@unaffiliated/forrestv] has joined #bitcoin-wizards 23:04 -!- thufir [~jircii@unaffiliated/thufir] has left #bitcoin-wizards [] 23:20 -!- sofdg2 [~sofdg2@unaffiliated/sofdg2] has quit [Quit: Saindo] 23:27 -!- wallet42 [~wallet42@83.66.118.141] has joined #bitcoin-wizards 23:30 -!- arubi_ [~ese168@unaffiliated/arubi] has joined #bitcoin-wizards 23:36 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Ping timeout: 276 seconds] 23:38 -!- priidu [~priidu@unaffiliated/priidu] has joined #bitcoin-wizards 23:51 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has joined #bitcoin-wizards 23:52 -!- blackwraith [~priidu@unaffiliated/priidu] has joined #bitcoin-wizards 23:54 -!- b_lumenkraft [~b_lumenkr@unaffiliated/b-lumenkraft/x-4457406] has joined #bitcoin-wizards 23:54 -!- priidu [~priidu@unaffiliated/priidu] has quit [Ping timeout: 252 seconds] --- Log closed Sun Apr 12 00:00:50 2015