--- Log opened Wed Nov 25 00:00:35 2015 00:00 -!- the`doctor [~the`docto@unaffiliated/thedoctor/x-1964342] has quit [Quit: the`doctor] 00:03 -!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has quit [Quit: Leaving] 00:04 -!- damethos [~damethos@unaffiliated/damethos] has joined #bitcoin-wizards 00:06 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards 00:08 -!- moa [~kiwigb@opentransactions/dev/moa] has quit [Quit: Leaving.] 00:11 -!- Keefe [~Keefe@unaffiliated/keefe] has quit [Ping timeout: 260 seconds] 00:13 -!- Keefe [~Keefe@unaffiliated/keefe] has joined #bitcoin-wizards 00:22 -!- bedeho_ [~bedeho@195.159.234.190] has joined #bitcoin-wizards 00:25 -!- dEBRUYNE [~dEBRUYNE@56-197-ftth.onsbrabantnet.nl] has joined #bitcoin-wizards 00:28 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Ping timeout: 244 seconds] 00:29 -!- giel___ [~giel____@a149043.upc-a.chello.nl] has quit [Quit: Leaving] 00:33 -!- snthsnth [~snthsnth@c-98-207-208-241.hsd1.ca.comcast.net] has quit [Ping timeout: 272 seconds] 00:35 -!- snthsnth [~snthsnth@c-98-207-208-241.hsd1.ca.comcast.net] has joined #bitcoin-wizards 00:37 -!- dEBRUYNE [~dEBRUYNE@56-197-ftth.onsbrabantnet.nl] has quit [Ping timeout: 276 seconds] 00:39 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has joined #bitcoin-wizards 00:40 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 265 seconds] 00:41 -!- snthsnth [~snthsnth@c-98-207-208-241.hsd1.ca.comcast.net] has quit [Ping timeout: 260 seconds] 00:42 -!- bedeho_ [~bedeho@195.159.234.190] has quit [Ping timeout: 252 seconds] 00:45 -!- snthsnth [~snthsnth@c-98-207-208-241.hsd1.ca.comcast.net] has joined #bitcoin-wizards 00:51 -!- snthsnth [~snthsnth@c-98-207-208-241.hsd1.ca.comcast.net] has quit [Ping timeout: 252 seconds] 00:51 -!- jaekwon [~jaekwon@c-98-234-63-169.hsd1.ca.comcast.net] has joined #bitcoin-wizards 00:54 -!- rusty2 is now known as rusty 00:54 -!- bramc [~bram@99-75-88-206.lightspeed.sntcca.sbcglobal.net] has quit [Quit: This computer has gone to sleep] 01:00 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has joined #bitcoin-wizards 01:00 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Remote host closed the connection] 01:09 -!- jcluck [~cluckj@pool-108-16-231-242.phlapa.fios.verizon.net] has joined #bitcoin-wizards 01:12 -!- cluckj [~cluckj@pool-108-16-231-242.phlapa.fios.verizon.net] has quit [Ping timeout: 276 seconds] 01:13 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards 01:15 -!- LeMiner [LeMiner@unaffiliated/leminer] has quit [Read error: Connection reset by peer] 01:16 -!- Yoghur114 [~jorn@g227014.upc-g.chello.nl] has joined #bitcoin-wizards 01:16 -!- LeMiner [LeMiner@unaffiliated/leminer] has joined #bitcoin-wizards 01:27 -!- kinlo [~peter@unaffiliated/kinlo] has quit [Remote host closed the connection] 01:27 -!- kinlo [peter@unaffiliated/kinlo] has joined #bitcoin-wizards 01:28 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has quit [Read error: Connection reset by peer] 01:28 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has joined #bitcoin-wizards 01:31 -!- CoinMuncher [~jannes@178.132.211.90] has joined #bitcoin-wizards 01:34 -!- Yoghur114 [~jorn@g227014.upc-g.chello.nl] has quit [Remote host closed the connection] 01:52 -!- arowser [~quassel@106.120.101.38] has quit [Quit: No Ping reply in 180 seconds.] 01:53 -!- jcorgan [~jcorgan@unaffiliated/jcorgan] has quit [Ping timeout: 272 seconds] 01:53 -!- arowser [~quassel@106.120.101.38] has joined #bitcoin-wizards 01:53 -!- neha [~narula@mint-square.mit.edu] has quit [Ping timeout: 272 seconds] 01:53 -!- rasengan_ [~rasengan@eyearesee.com] has quit [Ping timeout: 272 seconds] 01:54 -!- jcorgan [~jcorgan@ec2-54-67-38-167.us-west-1.compute.amazonaws.com] has joined #bitcoin-wizards 01:54 -!- jcorgan [~jcorgan@ec2-54-67-38-167.us-west-1.compute.amazonaws.com] has quit [Changing host] 01:54 -!- jcorgan [~jcorgan@unaffiliated/jcorgan] has joined #bitcoin-wizards 01:54 -!- rasengan [~rasengan@eyearesee.com] has joined #bitcoin-wizards 01:54 -!- neha [~narula@mint-square.mit.edu] has joined #bitcoin-wizards 01:54 -!- shesek [~shesek@bzq-84-110-108-27.cablep.bezeqint.net] has quit [Ping timeout: 272 seconds] 01:54 -!- OxADADA [~OxADADA@alumni-linux.ccs.neu.edu] has quit [Ping timeout: 272 seconds] 01:54 -!- Madars [~null@unaffiliated/madars] has quit [Ping timeout: 272 seconds] 01:54 -!- OxADADA [~OxADADA@alumni-linux.ccs.neu.edu] has joined #bitcoin-wizards 01:55 -!- shesek [~shesek@bzq-84-110-108-27.cablep.bezeqint.net] has joined #bitcoin-wizards 01:56 -!- Madars [~null@unaffiliated/madars] has joined #bitcoin-wizards 01:58 -!- psztorc [4575fa8d@gateway/web/freenode/ip.69.117.250.141] has quit [Ping timeout: 246 seconds] 02:04 -!- roconnor [~roconnor@host-45-58-254-171.dyn.295.ca] has quit [Ping timeout: 272 seconds] 02:08 -!- adam3us [~Adium@2a02:200:1010:2:4cc:c3a1:4f8f:534c] has joined #bitcoin-wizards 02:09 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 246 seconds] 02:11 -!- adam3us1 [~Adium@178.197.227.255] has quit [Ping timeout: 252 seconds] 02:27 -!- jaekwon [~jaekwon@c-98-234-63-169.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 02:29 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #bitcoin-wizards 02:31 -!- andytoshi [~andytoshi@unaffiliated/andytoshi] has quit [Ping timeout: 255 seconds] 02:33 -!- TBI_ [~TBI@20.84-48-195.nextgentel.com] has quit [Ping timeout: 264 seconds] 02:34 -!- frankenmint [~frankenmi@75-175-72-226.ptld.qwest.net] has quit [] 02:35 -!- damethos [~damethos@unaffiliated/damethos] has quit [Quit: Bye] 02:36 -!- frankenmint [~frankenmi@75-175-72-226.ptld.qwest.net] has joined #bitcoin-wizards 02:39 -!- damethos [~damethos@unaffiliated/damethos] has joined #bitcoin-wizards 02:41 -!- andytoshi [~andytoshi@wpsoftware.net] has joined #bitcoin-wizards 02:45 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards 02:54 -!- simba [~simba@dhcp-18-111-121-34.dyn.MIT.EDU] has quit [Read error: Connection reset by peer] 02:54 -!- simba [~simba@dhcp-18-111-121-34.dyn.mit.edu] has joined #bitcoin-wizards 03:15 -!- K1773R [~K1773R@unaffiliated/k1773r] has quit [Quit: /dev/null] 03:16 -!- simba [~simba@dhcp-18-111-121-34.dyn.mit.edu] has quit [Read error: Connection reset by peer] 03:16 -!- simba [~simba@dhcp-18-111-121-34.dyn.MIT.EDU] has joined #bitcoin-wizards 03:22 -!- rdponticelli [~quassel@190.103.200.8] has joined #bitcoin-wizards 03:24 -!- rustyn [~rustyn@unaffiliated/rustyn] has quit [Ping timeout: 240 seconds] 03:26 -!- adam3us [~Adium@2a02:200:1010:2:4cc:c3a1:4f8f:534c] has quit [Quit: Leaving.] 03:30 -!- K1773R [~K1773R@unaffiliated/k1773r] has joined #bitcoin-wizards 03:31 -!- andytoshi [~andytoshi@wpsoftware.net] has quit [Ping timeout: 246 seconds] 03:35 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has left #bitcoin-wizards [] 03:35 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has joined #bitcoin-wizards 03:36 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has left #bitcoin-wizards [] 03:40 -!- matsjj [~matsjj@p20030089EA107E332D5ACAC7B45B8E3F.dip0.t-ipconnect.de] has joined #bitcoin-wizards 03:42 -!- matsjj_ [~matsjj@p20030089EA107E5AE57FED906E2B14D0.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds] 03:52 -!- andytoshi [~andytoshi@wpsoftware.net] has joined #bitcoin-wizards 04:01 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 260 seconds] 04:05 -!- dEBRUYNE [~dEBRUYNE@ww010749.uvt.nl] has joined #bitcoin-wizards 04:23 -!- simba [~simba@dhcp-18-111-121-34.dyn.MIT.EDU] has quit [Read error: Connection reset by peer] 04:24 -!- simba [~simba@dhcp-18-111-121-34.dyn.mit.edu] has joined #bitcoin-wizards 04:27 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards 04:30 -!- adam3us [~Adium@178.197.234.186] has joined #bitcoin-wizards 04:32 -!- bobke_ is now known as bobke 04:43 -!- flipswitchbitch [~ielo@88-105-206-36.dynamic.dsl.as9105.com] has joined #bitcoin-wizards 04:49 -!- adam3us [~Adium@178.197.234.186] has quit [Quit: Leaving.] 04:51 -!- adam3us [~Adium@178.197.234.186] has joined #bitcoin-wizards 05:03 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has joined #bitcoin-wizards 05:09 -!- adam3us [~Adium@178.197.234.186] has quit [Quit: Leaving.] 05:14 -!- Quanttek [~quassel@ip1f11db5b.dynamic.kabel-deutschland.de] has joined #bitcoin-wizards 05:19 -!- rdponticelli [~quassel@190.103.200.8] has quit [Ping timeout: 272 seconds] 05:26 -!- tulip [~tulip@unaffiliated/tulip] has quit [] 05:29 -!- adam3us [~Adium@178.197.233.90] has joined #bitcoin-wizards 05:30 -!- Yoghur114 [~Yoghurt11@131.224.198.111] has joined #bitcoin-wizards 05:31 -!- Yoghur114 [~Yoghurt11@131.224.198.111] has quit [Remote host closed the connection] 05:36 -!- simba [~simba@dhcp-18-111-121-34.dyn.mit.edu] has quit [Read error: Connection reset by peer] 05:36 -!- jgarzik [~jgarzik@unaffiliated/jgarzik] has quit [Quit: This computer has gone to sleep] 05:37 -!- simba [~simba@dhcp-18-111-121-34.dyn.mit.edu] has joined #bitcoin-wizards 05:39 -!- LeMiner [LeMiner@unaffiliated/leminer] has quit [Ping timeout: 246 seconds] 05:40 -!- adam3us [~Adium@178.197.233.90] has quit [Quit: Leaving.] 05:43 -!- Burrito [~Burrito@unaffiliated/burrito] has quit [Quit: Leaving] 05:46 -!- GGuyZ_ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has joined #bitcoin-wizards 05:46 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has quit [Read error: Connection reset by peer] 05:46 -!- GGuyZ_ is now known as GGuyZ 05:47 -!- LeMiner [LeMiner@unaffiliated/leminer] has joined #bitcoin-wizards 05:47 -!- Burrito [~Burrito@unaffiliated/burrito] has joined #bitcoin-wizards 05:51 -!- paci [~paci@host41-233-static.58-79-b.business.telecomitalia.it] has quit [Ping timeout: 272 seconds] 05:53 -!- bramc [~bram@99-75-88-206.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-wizards 05:57 -!- paci [~paci@host41-233-static.58-79-b.business.telecomitalia.it] has joined #bitcoin-wizards 05:59 -!- adam3us [~Adium@178.197.226.32] has joined #bitcoin-wizards 06:03 -!- jgarzik [~jgarzik@104-178-201-106.lightspeed.tukrga.sbcglobal.net] has joined #bitcoin-wizards 06:03 -!- jgarzik [~jgarzik@104-178-201-106.lightspeed.tukrga.sbcglobal.net] has quit [Changing host] 06:03 -!- jgarzik [~jgarzik@unaffiliated/jgarzik] has joined #bitcoin-wizards 06:13 -!- TBI [~TBI@20.84-48-195.nextgentel.com] has joined #bitcoin-wizards 06:14 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-wizards 06:15 < Taek> bramc: https://en.bitcoin.it/wiki/Protocol_documentation 06:15 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has left #bitcoin-wizards [] 06:15 < Taek> https://bitcoin.org/en/developer-reference#p2p-network 06:19 -!- simba [~simba@dhcp-18-111-121-34.dyn.mit.edu] has quit [Read error: Connection reset by peer] 06:19 -!- simba [~simba@dhcp-18-111-121-34.dyn.mit.edu] has joined #bitcoin-wizards 06:32 -!- adam3us [~Adium@178.197.226.32] has quit [Quit: Leaving.] 06:34 -!- zooko [~zooko@2601:281:8001:26aa:8561:af0b:a857:2f66] has joined #bitcoin-wizards 06:38 -!- liteIRC_ [~zooko@2607:fb90:12a:b9bc:6c8:dcd1:1a9b:42ce] has joined #bitcoin-wizards 06:41 -!- zooko [~zooko@2601:281:8001:26aa:8561:af0b:a857:2f66] has quit [Ping timeout: 246 seconds] 06:41 -!- liteIRC_ is now known as zooko 06:51 -!- gill3s [~gill3s@unaffiliated/gill3s] has quit [Ping timeout: 240 seconds] 06:52 -!- pozitrono [~nu@179.43.156.162] has joined #bitcoin-wizards 06:53 -!- sparetire_ [~sparetire@unaffiliated/sparetire] has joined #bitcoin-wizards 06:56 -!- pozitron [~nu@179.43.176.162] has joined #bitcoin-wizards 06:58 -!- justice_ [~textual@HSI-KBW-37-209-26-147.hsi15.kabel-badenwuerttemberg.de] has quit [Ping timeout: 265 seconds] 06:59 -!- pozitrono [~nu@179.43.156.162] has quit [Ping timeout: 246 seconds] 07:06 -!- adam3us [~Adium@2.227.197.178.dynamic.wless.zhbmb00p-cgnat.res.cust.swisscom.ch] has joined #bitcoin-wizards 07:17 -!- simba [~simba@dhcp-18-111-121-34.dyn.mit.edu] has quit [Read error: Connection reset by peer] 07:17 -!- simba [~simba@dhcp-18-111-121-34.dyn.MIT.EDU] has joined #bitcoin-wizards 07:29 -!- dEBRUYNE [~dEBRUYNE@ww010749.uvt.nl] has quit [Ping timeout: 276 seconds] 07:43 -!- simba [~simba@dhcp-18-111-121-34.dyn.MIT.EDU] has quit [Read error: Connection reset by peer] 07:44 -!- simba [~simba@dhcp-18-111-121-34.dyn.mit.edu] has joined #bitcoin-wizards 07:46 -!- adam3us [~Adium@2.227.197.178.dynamic.wless.zhbmb00p-cgnat.res.cust.swisscom.ch] has quit [Quit: Leaving.] 07:48 -!- Giszmo [~leo@pc-36-133-241-201.cm.vtr.net] has joined #bitcoin-wizards 07:48 -!- bramc [~bram@99-75-88-206.lightspeed.sntcca.sbcglobal.net] has quit [Quit: This computer has gone to sleep] 07:52 -!- jaekwon [~jaekwon@2601:645:c001:263a:c7b:506:7f7e:b98b] has joined #bitcoin-wizards 07:58 -!- damethos [~damethos@unaffiliated/damethos] has quit [Quit: Bye] 08:03 -!- simba [~simba@dhcp-18-111-121-34.dyn.mit.edu] has quit [Read error: Connection reset by peer] 08:03 -!- simba [~simba@dhcp-18-111-121-34.dyn.mit.edu] has joined #bitcoin-wizards 08:11 -!- zookolaptop [~user@2601:281:8001:26aa:ac94:e5d8:45fe:a98e] has quit [Ping timeout: 246 seconds] 08:12 -!- adam3us [~Adium@178.197.224.82] has joined #bitcoin-wizards 08:17 -!- adam3us [~Adium@178.197.224.82] has quit [Client Quit] 08:21 -!- kwonbie [~me@dhcp-18-189-40-118.dyn.MIT.EDU] has joined #bitcoin-wizards 08:30 -!- melvster [~melvster@ip-86-49-18-198.net.upcbroadband.cz] has quit [Read error: Connection reset by peer] 08:30 -!- melvster [~melvster@ip-86-49-18-198.net.upcbroadband.cz] has joined #bitcoin-wizards 08:38 -!- baurusdb [~baurusdb@unaffiliated/baurusdb] has joined #bitcoin-wizards 08:47 -!- damethos [~damethos@unaffiliated/damethos] has joined #bitcoin-wizards 08:50 -!- frankenmint [~frankenmi@75-175-72-226.ptld.qwest.net] has quit [Remote host closed the connection] 08:58 -!- hashtag_ [cjmedia@cpe-98-157-223-81.ma.res.rr.com] has joined #bitcoin-wizards 08:59 -!- hashtag [cjmedia@cpe-98-157-223-81.ma.res.rr.com] has quit [Ping timeout: 246 seconds] 09:08 -!- baurusdb [~baurusdb@unaffiliated/baurusdb] has quit [Quit: baurusdb] 09:14 -!- snthsnth [~snthsnth@c-98-207-208-241.hsd1.ca.comcast.net] has joined #bitcoin-wizards 09:15 -!- psztorc [~psztorc@2607:fb90:e7e:e540:672f:a7d4:ce0a:f908] has joined #bitcoin-wizards 09:19 -!- psztorc_ [~psztorc@ool-4575fa8d.dyn.optonline.net] has quit [Ping timeout: 265 seconds] 09:25 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has quit [Quit: GGuyZ] 09:31 -!- frankenmint [~frankenmi@75-175-72-226.ptld.qwest.net] has joined #bitcoin-wizards 09:38 -!- kwonbie [~me@dhcp-18-189-40-118.dyn.MIT.EDU] has quit [Ping timeout: 264 seconds] 09:38 -!- Yoghur114 [~jorn@g227014.upc-g.chello.nl] has joined #bitcoin-wizards 09:39 -!- cocoBTC [~cocoBTC__@c-233a71d5.136-1-64736c10.cust.bredbandsbolaget.se] has joined #bitcoin-wizards 09:39 -!- cocoBTC [~cocoBTC__@c-233a71d5.136-1-64736c10.cust.bredbandsbolaget.se] has quit [Client Quit] 09:45 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has quit [Ping timeout: 246 seconds] 09:47 -!- Piper-Off is now known as Monthrect 09:48 -!- kyuupichan [~Neil@ae054148.dynamic.ppp.asahi-net.or.jp] has quit [Ping timeout: 272 seconds] 09:52 -!- baurusdb [~baurusdb@unaffiliated/baurusdb] has joined #bitcoin-wizards 09:56 -!- snthsnth [~snthsnth@c-98-207-208-241.hsd1.ca.comcast.net] has quit [Ping timeout: 250 seconds] 10:01 -!- priidu [~priidu@unaffiliated/priidu] has quit [Ping timeout: 240 seconds] 10:08 -!- priidu [~priidu@unaffiliated/priidu] has joined #bitcoin-wizards 10:09 -!- the`doctor [~the`docto@unaffiliated/thedoctor/x-1964342] has joined #bitcoin-wizards 10:11 -!- cocoBTC [~cocoBTC__@c-233a71d5.136-1-64736c10.cust.bredbandsbolaget.se] has joined #bitcoin-wizards 10:11 -!- Dizzle [~Dizzle@104-6-36-162.lightspeed.austtx.sbcglobal.net] has joined #bitcoin-wizards 10:20 -!- Dizzle [~Dizzle@104-6-36-162.lightspeed.austtx.sbcglobal.net] has quit [Remote host closed the connection] 10:22 -!- Lightsword_ [~Lightswor@75.98.116.4] has joined #bitcoin-wizards 10:23 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #bitcoin-wizards 10:24 -!- Lightsword [~Lightswor@104.194.123.94] has quit [Read error: Connection reset by peer] 10:26 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-kssotdfzbjvavpmi] has quit [Ping timeout: 240 seconds] 10:26 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-qgkdjfpkbqmigkig] has joined #bitcoin-wizards 10:26 -!- bassguitarman [sid40024@gateway/web/irccloud.com/x-bunviogdhnwgthrc] has quit [Ping timeout: 240 seconds] 10:27 -!- bassguitarman [sid40024@gateway/web/irccloud.com/x-djpfegpvzlzyegsw] has joined #bitcoin-wizards 10:27 -!- Lightsword_ [~Lightswor@75.98.116.4] has quit [Ping timeout: 244 seconds] 10:29 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 244 seconds] 10:34 -!- Lightsword [~Lightswor@104.194.123.94] has joined #bitcoin-wizards 10:46 -!- MagikSquirrel [~MagikSqui@unaffiliated/magiksquirrel] has quit [Remote host closed the connection] 10:47 -!- snthsnth [~snthsnth@c-98-207-208-241.hsd1.ca.comcast.net] has joined #bitcoin-wizards 10:48 -!- MagikSquirrel [~MagikSqui@unaffiliated/magiksquirrel] has joined #bitcoin-wizards 10:49 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has joined #bitcoin-wizards 10:49 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards 10:59 -!- dEBRUYNE [~dEBRUYNE@56-197-ftth.onsbrabantnet.nl] has joined #bitcoin-wizards 10:59 -!- pozitron [~nu@179.43.176.162] has quit [Ping timeout: 246 seconds] 11:05 -!- Lightsword_ [~Lightswor@66.87.77.243] has joined #bitcoin-wizards 11:08 -!- Lightsword [~Lightswor@104.194.123.94] has quit [Ping timeout: 252 seconds] 11:08 -!- Lightsword_ is now known as Lightsword 11:11 -!- priidu [~priidu@unaffiliated/priidu] has quit [Ping timeout: 276 seconds] 11:16 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 240 seconds] 11:23 -!- koshii [~w@c-68-58-151-30.hsd1.in.comcast.net] has quit [Ping timeout: 240 seconds] 11:25 -!- adam3us [~Adium@195.138.228.8] has joined #bitcoin-wizards 11:25 -!- adam3us1 [~Adium@141.8.72.43] has joined #bitcoin-wizards 11:28 -!- snthsnth [~snthsnth@c-98-207-208-241.hsd1.ca.comcast.net] has quit [Quit: leaving] 11:30 -!- adam3us [~Adium@195.138.228.8] has quit [Ping timeout: 276 seconds] 11:32 -!- bramc [~bram@99-75-88-206.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-wizards 11:35 -!- CoinMuncher [~jannes@178.132.211.90] has quit [Quit: Leaving.] 11:37 -!- jtimon [~quassel@74.29.134.37.dynamic.jazztel.es] has quit [Ping timeout: 265 seconds] 11:38 -!- koshii [~w@c-68-58-151-30.hsd1.in.comcast.net] has joined #bitcoin-wizards 11:41 -!- Dizzle [~Dizzle@104-6-36-162.lightspeed.austtx.sbcglobal.net] has joined #bitcoin-wizards 11:44 -!- damethos [~damethos@unaffiliated/damethos] has quit [Quit: Bye] 11:49 -!- nessence [~alexl@rrcs-50-74-84-98.nyc.biz.rr.com] has joined #bitcoin-wizards 11:57 -!- psztorc_ [~psztorc@ool-4575fa8d.dyn.optonline.net] has joined #bitcoin-wizards 11:58 -!- Lightsword [~Lightswor@66.87.77.243] has quit [Ping timeout: 246 seconds] 12:00 -!- Lightsword [~Lightswor@66.87.77.243] has joined #bitcoin-wizards 12:00 -!- psztorc [~psztorc@2607:fb90:e7e:e540:672f:a7d4:ce0a:f908] has quit [Ping timeout: 240 seconds] 12:06 -!- smk [2ef67c2a@gateway/web/freenode/ip.46.246.124.42] has quit [Quit: Page closed] 12:07 -!- damethos [~damethos@unaffiliated/damethos] has joined #bitcoin-wizards 12:08 < nsh> .title https://www.youtube.com/watch?v=D0Fhg9CpbOg 12:08 < yoleaux> Bitcoin's Incentive Structure - YouTube 12:08 < nsh> (4 days ago, Aviv Zohar) 12:09 < nsh> 'Bitcoin's departure from traditional banking and money transmitting models make it one of the most disruptive and daring economic experiments of our time. Behind the scenes, the system which offers payments to nodes that support the currency, is ruled by the resulting incentives. I will overview the interaction between the protocol and different aspects of its underlying incentive scheme. In partic 12:09 < nsh> ular, I will present areas where improvements are needed, and where AGT can (hopefully) help.' 12:18 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has quit [Quit: GGuyZ] 12:30 -!- mjerr [~mjerr@p5B2093BB.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds] 12:31 -!- frankenmint [~frankenmi@75-175-72-226.ptld.qwest.net] has quit [Remote host closed the connection] 12:47 -!- damethos [~damethos@unaffiliated/damethos] has quit [Remote host closed the connection] 12:51 < gmaxwell> So-- people give up searching for the forced private key revealing trick? (aj found it with some non-trivial help). 12:52 -!- belcher [~user@unaffiliated/belcher] has joined #bitcoin-wizards 12:53 < gmaxwell> sipa: ^ 12:54 -!- baurusdb [~baurusdb@unaffiliated/baurusdb] has quit [Read error: Connection reset by peer] 12:56 -!- baurusdb [~baurusdb@unaffiliated/baurusdb] has joined #bitcoin-wizards 13:05 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has joined #bitcoin-wizards 13:09 < aj> gmaxwell: aww, come on, i came up with a vastly worse way with no help too! 13:09 < gmaxwell> oh yes! that too. 13:10 < waxwing> crypto-tease 13:10 < kanzure> i asked andytoshi the same question over dinner yesterday and i think his reply was "what's irc?" 13:20 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards 13:23 < gmaxwell> waxwing: well I wanted other people to try, with one part hope of finding a better one. 13:23 < waxwing> i jest :) 13:23 < gmaxwell> sipa: No solutions? 13:24 -!- malte [~malte@alkaid.uberspace.de] has quit [Ping timeout: 250 seconds] 13:25 -!- liteIRC_ [~zooko@2601:283:8002:c3f3:8561:af0b:a857:2f66] has joined #bitcoin-wizards 13:25 -!- JackH [~Jack@host-80-43-142-236.as13285.net] has quit [Ping timeout: 240 seconds] 13:27 -!- malte [~malte@2a00:d0c0:200:0:b9:1a:9c2c:1] has joined #bitcoin-wizards 13:27 -!- zooko [~zooko@2607:fb90:12a:b9bc:6c8:dcd1:1a9b:42ce] has quit [Ping timeout: 272 seconds] 13:27 -!- liteIRC_ is now known as zooko 13:29 -!- liteIRC_ [~zooko@2601:283:8002:c3f3:8561:af0b:a857:2f66] has joined #bitcoin-wizards 13:29 -!- zooko [~zooko@2601:283:8002:c3f3:8561:af0b:a857:2f66] has quit [Read error: Connection reset by peer] 13:29 -!- liteIRC_ is now known as zooko 13:33 -!- MoALTz [~no@78-11-179-104.static.ip.netia.com.pl] has quit [Quit: Leaving] 13:37 -!- TheSeven [~quassel@rockbox/developer/TheSeven] has quit [Ping timeout: 252 seconds] 13:38 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Quit: Quitte] 13:39 -!- TheSeven [~quassel@rockbox/developer/TheSeven] has joined #bitcoin-wizards 13:41 -!- liteIRC_ [~zooko@2601:283:8002:c3f3:8561:af0b:a857:2f66] has joined #bitcoin-wizards 13:41 -!- zooko [~zooko@2601:283:8002:c3f3:8561:af0b:a857:2f66] has quit [Read error: Connection reset by peer] 13:41 -!- liteIRC_ is now known as zooko 13:44 -!- Burrito [~Burrito@unaffiliated/burrito] has quit [Ping timeout: 240 seconds] 13:44 -!- psztorc [~psztorc@2607:fb90:e80:dbbb:60aa:7d1f:e3ac:21a8] has joined #bitcoin-wizards 13:48 -!- baurusdb [~baurusdb@unaffiliated/baurusdb] has quit [Quit: baurusdb] 13:48 -!- psztorc_ [~psztorc@ool-4575fa8d.dyn.optonline.net] has quit [Ping timeout: 276 seconds] 13:51 -!- Lightsword [~Lightswor@66.87.77.243] has quit [Read error: Connection reset by peer] 13:52 -!- zooko [~zooko@2601:283:8002:c3f3:8561:af0b:a857:2f66] has quit [Ping timeout: 246 seconds] 13:57 -!- hashtag_ [cjmedia@cpe-98-157-223-81.ma.res.rr.com] has quit [Read error: Connection reset by peer] 13:57 -!- moa [~kiwigb@opentransactions/dev/moa] has joined #bitcoin-wizards 14:01 -!- Lightsword [~Lightswor@104.194.123.94] has joined #bitcoin-wizards 14:03 -!- adam3us1 [~Adium@141.8.72.43] has quit [Quit: Leaving.] 14:04 -!- adam3us [~Adium@141.8.72.43] has joined #bitcoin-wizards 14:20 -!- psztorc_ [~psztorc@ool-4575fa8d.dyn.optonline.net] has joined #bitcoin-wizards 14:22 -!- psztorc [~psztorc@2607:fb90:e80:dbbb:60aa:7d1f:e3ac:21a8] has quit [Ping timeout: 246 seconds] 14:22 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has joined #bitcoin-wizards 14:23 -!- hsmiths_ [uid95325@gateway/web/irccloud.com/x-rjxvpovzmitwjepk] has joined #bitcoin-wizards 14:23 -!- hsmiths_ is now known as hsmiths 14:24 -!- hsmiths [uid95325@gateway/web/irccloud.com/x-rjxvpovzmitwjepk] has quit [Client Quit] 14:28 -!- midnightmagic [~midnightm@unaffiliated/midnightmagic] has quit [Ping timeout: 252 seconds] 14:28 -!- tulip [~tulip@unaffiliated/tulip] has joined #bitcoin-wizards 14:28 -!- AnoAnon [~AnoAnon@197.39.239.45] has joined #bitcoin-wizards 14:29 -!- AnoAnon [~AnoAnon@197.39.239.45] has quit [Max SendQ exceeded] 14:32 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 244 seconds] 14:34 -!- midnightmagic [~midnightm@unaffiliated/midnightmagic] has joined #bitcoin-wizards 14:40 -!- belcher [~user@unaffiliated/belcher] has quit [Read error: Connection reset by peer] 14:40 -!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has joined #bitcoin-wizards 14:40 -!- belcher [~user@unaffiliated/belcher] has joined #bitcoin-wizards 14:43 -!- jgarzik [~jgarzik@unaffiliated/jgarzik] has quit [Quit: This computer has gone to sleep] 14:44 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has joined #bitcoin-wizards 14:50 -!- the`doctor [~the`docto@unaffiliated/thedoctor/x-1964342] has quit [Quit: the`doctor] 14:52 -!- cocoBTC [~cocoBTC__@c-233a71d5.136-1-64736c10.cust.bredbandsbolaget.se] has quit [Quit: Leaving] 14:53 -!- the`doctor [~the`docto@unaffiliated/thedoctor/x-1964342] has joined #bitcoin-wizards 14:54 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 260 seconds] 14:55 -!- kyuupichan [~Neil@ae048250.dynamic.ppp.asahi-net.or.jp] has joined #bitcoin-wizards 14:57 -!- Guest66004 [~jgarzik@104-178-201-106.lightspeed.tukrga.sbcglobal.net] has joined #bitcoin-wizards 15:01 -!- dstrbd [~dstrbd@181.41.214.174] has joined #bitcoin-wizards 15:03 -!- TBI_ [~TBI@20.84-48-195.nextgentel.com] has joined #bitcoin-wizards 15:04 -!- TBI [~TBI@20.84-48-195.nextgentel.com] has quit [Ping timeout: 264 seconds] 15:11 -!- Quanttek [~quassel@ip1f11db5b.dynamic.kabel-deutschland.de] has quit [Ping timeout: 250 seconds] 15:16 -!- dEBRUYNE [~dEBRUYNE@56-197-ftth.onsbrabantnet.nl] has quit [Ping timeout: 276 seconds] 15:18 -!- Guest66004 [~jgarzik@104-178-201-106.lightspeed.tukrga.sbcglobal.net] has quit [Changing host] 15:18 -!- Guest66004 [~jgarzik@unaffiliated/jgarzik] has joined #bitcoin-wizards 15:18 -!- Guest66004 is now known as jgarzik_ 15:25 -!- bramc [~bram@99-75-88-206.lightspeed.sntcca.sbcglobal.net] has quit [Quit: This computer has gone to sleep] 15:27 -!- moa [~kiwigb@opentransactions/dev/moa] has quit [Ping timeout: 250 seconds] 15:27 < phantomcircuit> aj, lold 15:33 -!- dstrbd [~dstrbd@181.41.214.174] has left #bitcoin-wizards [] 15:36 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has joined #bitcoin-wizards 15:39 -!- moa [~kiwigb@opentransactions/dev/moa] has joined #bitcoin-wizards 15:46 < nsh> gmaxwell, can you restate the problem? 15:47 -!- Dizzle [~Dizzle@104-6-36-162.lightspeed.austtx.sbcglobal.net] has quit [Quit: Leaving...] 15:47 -!- hashtag [~hashtagg_@cpe-174-97-254-80.ma.res.rr.com] has joined #bitcoin-wizards 15:47 < nsh> something like, using current bitcoin script rules, can you create a system that reveals a hash-preimage atomically with spending a refund of a lightning channel payment sequence payment 15:48 -!- kang_ [67efe9a9@gateway/web/freenode/ip.103.239.233.169] has joined #bitcoin-wizards 15:48 < nsh> ah, it's still in my scrollback 15:53 -!- rusty2 is now known as rusty 15:54 < rusty> nsh: did he give the answer yet? I freely admit to giving up! 15:54 < nsh> not revealed yet 15:55 < nsh> but i'd like to apprehend the framing of the problem before hopelessly and instantly conceding 15:55 -!- hashtag_ [~hashtagg_@cpe-174-97-254-80.ma.res.rr.com] has joined #bitcoin-wizards 15:58 -!- hashtag [~hashtagg_@cpe-174-97-254-80.ma.res.rr.com] has quit [Ping timeout: 246 seconds] 15:59 < kanzure> win 5 15:59 < kanzure> dbflakjfoiqeq 15:59 -!- jtimon [~quassel@74.29.134.37.dynamic.jazztel.es] has joined #bitcoin-wizards 16:00 < nsh> privkey is leaked through committing to the nonce of the transaction somehow - variation of anduck's/tonych's proposals, but i don't understand the`doctor HTLC or lightning channel stuff in general 16:01 < nsh> or making the nonce derived from the privkey 16:01 < amiller_> yeah but how do you enforce anything about the nonce 16:04 -!- nanasho [~nanasha25@141.39.226.229] has joined #bitcoin-wizards 16:06 -!- damethos [~damethos@unaffiliated/damethos] has joined #bitcoin-wizards 16:10 < sipa> nsh: I have an ECDSA private key a with associated public key A. Can you construct a scriptPubKey (given A) that I can spend, but only by revealing a. 16:11 < sipa> (Is my interpretation of the problem, and I don't know the solution, so mayne I missed something in the way the question was formulated) 16:11 -!- paci [~paci@host41-233-static.58-79-b.business.telecomitalia.it] has quit [Ping timeout: 265 seconds] 16:11 < amiller_> maybe you can do something with the sighash flags, where you get a signature on an "empty" transaction, and then you provide the actual money payload with a new input, that you construct after seeing the first signature, and the script basically says "SIG has to be valid under this public key, and it has to be different than SIG' which i saw previously" 16:12 < sipa> amiller_: signing the hash 1 is possible, but the signer chooses the flags 16:12 < amiller_> oh 16:14 < amiller_> well, maybe you can just require the first signature to have the right flag before constructing the second scriptPubkey input with the actual money 16:14 < sipa> the substr opcode was disabled 16:14 < sipa> otherwise i could just require a signature whose r value was a fixed constant with known nonce 16:15 -!- paci [~paci@host41-233-static.58-79-b.business.telecomitalia.it] has joined #bitcoin-wizards 16:17 -!- tulip [~tulip@unaffiliated/tulip] has quit [Ping timeout: 272 seconds] 16:22 -!- damethos [~damethos@unaffiliated/damethos] has quit [Quit: Bye] 16:27 -!- flipswitchbitch [~ielo@88-105-206-36.dynamic.dsl.as9105.com] has quit [Ping timeout: 272 seconds] 16:37 -!- justice [~textual@HSI-KBW-37-209-26-147.hsi15.kabel-badenwuerttemberg.de] has joined #bitcoin-wizards 16:48 -!- justice [~textual@HSI-KBW-37-209-26-147.hsi15.kabel-badenwuerttemberg.de] has quit [Read error: Connection reset by peer] 16:48 -!- tulip [~tulip@unaffiliated/tulip] has joined #bitcoin-wizards 16:50 -!- psztorc [~psztorc@2607:fb90:e73:bf20:2f00:7c20:57ff:7dde] has joined #bitcoin-wizards 16:54 -!- jaekwon [~jaekwon@2601:645:c001:263a:c7b:506:7f7e:b98b] has quit [Remote host closed the connection] 16:54 -!- psztorc_ [~psztorc@ool-4575fa8d.dyn.optonline.net] has quit [Ping timeout: 260 seconds] 16:56 -!- jaekwon [~jaekwon@2601:645:c001:263a:b4f5:9c69:3c06:6680] has joined #bitcoin-wizards 17:01 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has quit [Ping timeout: 246 seconds] 17:14 -!- psztorc_ [~psztorc@ool-4575fa8d.dyn.optonline.net] has joined #bitcoin-wizards 17:14 -!- psztorc__ [~psztorc@2607:fb90:e73:bf20:8010:3553:8a0c:601f] has joined #bitcoin-wizards 17:15 -!- psztorc [~psztorc@2607:fb90:e73:bf20:2f00:7c20:57ff:7dde] has quit [Ping timeout: 240 seconds] 17:18 -!- TBI_ [~TBI@20.84-48-195.nextgentel.com] has quit [Read error: Connection reset by peer] 17:18 -!- TBI_ [~TBI@20.84-48-195.nextgentel.com] has joined #bitcoin-wizards 17:19 -!- psztorc_ [~psztorc@ool-4575fa8d.dyn.optonline.net] has quit [Ping timeout: 260 seconds] 17:21 -!- Monthrect is now known as Piper-Off 17:21 -!- Yoghur114 [~jorn@g227014.upc-g.chello.nl] has quit [Remote host closed the connection] 17:24 -!- jaekwon [~jaekwon@2601:645:c001:263a:b4f5:9c69:3c06:6680] has quit [Remote host closed the connection] 17:24 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-qgkdjfpkbqmigkig] has quit [Quit: Connection closed for inactivity] 17:34 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 260 seconds] 17:43 -!- jtimon [~quassel@74.29.134.37.dynamic.jazztel.es] has quit [Ping timeout: 252 seconds] 17:50 -!- nessence [~alexl@rrcs-50-74-84-98.nyc.biz.rr.com] has quit [Remote host closed the connection] 17:51 -!- nessence [~alexl@rrcs-50-74-84-98.nyc.biz.rr.com] has joined #bitcoin-wizards 17:55 -!- roconnor [~roconnor@host-45-58-254-127.dyn.295.ca] has joined #bitcoin-wizards 17:56 -!- nessence [~alexl@rrcs-50-74-84-98.nyc.biz.rr.com] has quit [Ping timeout: 250 seconds] 17:58 < andytoshi> i think i see how to do the signature thing 17:58 < andytoshi> pretty nasty 18:00 < andytoshi> oh, no, my idea reveals the keys. i'll shut up :) 18:01 < gmaxwell> the goal is to reveal the key! 18:02 < gmaxwell> what did you think the goal was?! 18:02 < sipa> gmaxwell: i guess he means his trick would reveal the key before spending? 18:03 < andytoshi> yes, that's what i mean sipa :P 18:03 < andytoshi> oh, wait, before even spending once? 18:04 < sipa> andytoshi: eh, perhaps you better explain what you think the goal was, and how you failed it 18:05 < andytoshi> sipa: i had thought the goal was to create a sig such that if you produce two of them with the same key, the key is revealed. but not if you only produce one. 18:05 < andytoshi> but now i see that the goal is weaker than that 18:05 < andytoshi> it's ok that if a single bitcoin signature is published, the key is exposed 18:05 < andytoshi> just that it should be possible to publish an out-of-band signature with same key, and that does not expose anything 18:06 < gmaxwell> yea, the goal is that at the end of the protocol, the final signature means the other party learns the private key. 18:06 < gmaxwell> You can have setup before that. 18:06 < gmaxwell> So, e.g. a single show signature would work; but it doesn't need to be one. 18:07 < andytoshi> ok, my thing is still broken because it reveals the key to everyone (so miners can steal). it might be salvagable tho 18:07 < gmaxwell> it's okay if it reveals it to everyone. 18:07 < gmaxwell> the last step can do normal key && leaked key (via bitcoin script.) 18:07 < andytoshi> ok, that's a good point 18:07 < andytoshi> then if my thing works at all (i'm 80% sure..) it's a win :P 18:08 < andytoshi> but how is that different than a hash preimage? 18:08 < gmaxwell> because the other party generates a new ephemeral pubkey P, and you pay to P+{pubkey whos discrete log you're gonna leak}. 18:09 < gmaxwell> and the two transactions are unlikable by the public (which doesn't know P) 18:09 < andytoshi> oh, right! 18:09 < andytoshi> sorry, i'm very tired :) 18:09 < gmaxwell> eat. 18:11 -!- the`doctor [~the`docto@unaffiliated/thedoctor/x-1964342] has quit [Ping timeout: 265 seconds] 18:11 < andytoshi> oh, shit, good call 18:20 -!- adam3us [~Adium@141.8.72.43] has quit [Quit: Leaving.] 18:27 -!- psztorc [~psztorc@ool-4575fa8d.dyn.optonline.net] has joined #bitcoin-wizards 18:30 -!- psztorc__ [~psztorc@2607:fb90:e73:bf20:8010:3553:8a0c:601f] has quit [Ping timeout: 246 seconds] 18:33 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has joined #bitcoin-wizards 18:35 -!- belcher [~user@unaffiliated/belcher] has quit [Quit: Leaving] 18:39 -!- bramc [~bram@99-75-88-206.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-wizards 18:45 -!- moa [~kiwigb@opentransactions/dev/moa] has quit [Ping timeout: 260 seconds] 18:49 -!- Newyorkadam [~Newyorkad@wikipedia/Newyorkadam] has joined #bitcoin-wizards 18:50 -!- moa [~kiwigb@opentransactions/dev/moa] has joined #bitcoin-wizards 18:51 -!- badmofo [~badmofo@unaffiliated/badmofo] has quit [Quit: Leaving] 18:52 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 18:53 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #bitcoin-wizards 19:02 -!- jaekwon [~jaekwon@2601:645:c001:263a:3cec:d85e:568d:e44b] has joined #bitcoin-wizards 19:08 -!- Lightsword [~Lightswor@104.194.123.94] has quit [Read error: Connection reset by peer] 19:08 -!- Lightsword [~Lightswor@104.194.123.94] has joined #bitcoin-wizards 19:21 -!- Giszmo [~leo@pc-36-133-241-201.cm.vtr.net] has quit [Quit: Leaving.] 19:23 -!- jcluck is now known as cluckj 19:29 -!- xeon-enouf [~xeon-enou@unaffiliated/xeon-enouf] has quit [Remote host closed the connection] 19:31 -!- xeon-enouf [~xeon-enou@unaffiliated/xeon-enouf] has joined #bitcoin-wizards 19:49 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has quit [Quit: GGuyZ] 19:54 -!- smk [2ef67c2a@gateway/web/freenode/ip.46.246.124.42] has joined #bitcoin-wizards 20:02 < bramc> Taek, Is there any technical protocol documentation which starts with the per-connection state machine? 20:05 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has joined #bitcoin-wizards 20:08 -!- jaekwon [~jaekwon@2601:645:c001:263a:3cec:d85e:568d:e44b] has quit [Remote host closed the connection] 20:10 < tulip> bramc: that's about the extent of it, beyond looking at the source. 20:10 -!- kwonbie [~me@cpe-108-183-19-42.nycap.res.rr.com] has joined #bitcoin-wizards 20:10 < bramc> tulip: What *is* the state machine of a connection? There must be one, even if it's implicit and only understood by a priestly few. 20:11 < phantomcircuit> bramc, there aren't docs about it but it's very simple really 20:11 < phantomcircuit> vesion/verack before anything else 20:11 < phantomcircuit> connecting peer sends version 20:12 < bramc> phantomcircuit, Yeah yeah let's just skip all that handshake stuff for now 20:12 < phantomcircuit> then take a look at the getheaders stuff there's a hack there to signal to the other peer that they should request more 20:12 < phantomcircuit> otherwise everything is async 20:12 -!- roconnor [~roconnor@host-45-58-254-127.dyn.295.ca] has quit [Quit: Konversation terminated!] 20:12 < phantomcircuit> currently we only respond to messages in order but well... 20:13 < bramc> When I think about a connection state machine it starts with you always having an idea of what my current longest chain is 20:13 < tulip> basically after the handshake the only thing you need to do is respond to ping messages, and not send anything invalid, everything else is optional as far as connections are concerned. 20:14 < bramc> *sigh* 20:14 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has quit [Quit: GGuyZ] 20:14 < bramc> Some day I should really write a document about how to design network protocols. 20:15 < tulip> bit late for this one. 20:15 -!- Lightsword [~Lightswor@104.194.123.94] has quit [Quit: Lightsword] 20:16 -!- TheSeven [~quassel@rockbox/developer/TheSeven] has quit [Disconnected by services] 20:16 -!- [7] [~quassel@rockbox/developer/TheSeven] has joined #bitcoin-wizards 20:16 < tulip> it's simple but lots of things are weird in ways they shouldn't be. the "alert" message type somehow manages to be more complex than all of the other ones combined, even though it is never used and all of the fields in it are irrelevant. 20:17 < bramc> If we're syncing with each other, the logic should fundamentally be that you and I announce to each other what our current greatest work factor chain is. Then whoever has a shorter one asks for stuff from the peer who has a taller one until we're back in sync 20:17 < bramc> The main subtlety should be whether we proactively send whole pieces of data to the peer or wait for them to be requested 20:18 < bramc> That's another thing which I have no idea how Bitcoin currently does it. 20:19 < kanzure> btw, have you been lurking #bitcoin-core-dev 20:19 < bramc> No I have not 20:20 -!- Newyorkadam [~Newyorkad@wikipedia/Newyorkadam] has quit [Quit: Newyorkadam] 20:20 < tulip> bramc: it works something like that at the moment. nodes can use 'getheaders' commands to build up the tree of block headers and verify the PoW before wasting time downloading the actual binaries. once it has the headers it can download them out of order. 20:20 < bramc> At the back of my mind I have this implicit assumption that everybody is familiar with BitTorrent's original wire protocol state machine and the improved one with the fast extensions and understands the philosophical implications for this for protocol design generally. This is probably a ridiculous assumption... 20:21 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has joined #bitcoin-wizards 20:22 < bramc> tulip, Right, so it's pull-based rather than push-based, at least as far as the blockchain is concerned (mempool is a different subject). That makes sense. How is a new highest block announced? 20:22 < tulip> newly received objects can be announced to peers using the 'inv' message, which contains the hash of the new transaction or block. if the node doesn't have it and is interested, it requests the binary from the peer using 'getdata'. 20:23 -!- Newyorkadam [~Newyorkad@wikipedia/Newyorkadam] has joined #bitcoin-wizards 20:23 < bramc> Does inv specific whether it's talking about a transaction or block? And if it's talking about a block, does it include work factor? 20:24 < tulip> just the type, hash of the object. there's discussion about pushing the entire header instead for blocks, which isn't a whole lot larger. 20:25 < bramc> Or I should say, work factor and height, and if it includes height is there a way to request the last n block hashes so you don't have to walk the linked list one at a time? 20:25 < tulip> the block header doesn't contain the height unfortunately. 20:26 < bramc> This protocol is... distinctly suboptimal when you're catching up. 20:26 < tulip> the coinbase transaction does however as part of BIP30, it's used as a salt to stop duplicate transaction IDs. you can include a block header and markle path to the coinbase transaction in a few hundred bytes. 20:26 < bramc> I assume peers also have a policy of not announcing that they have anything which they themselves haven't validated, and not announcing orphaned blocks? 20:27 < tulip> announcing invalid objects is a violation of the protocol and causes a disconnection and ban of that peer. 20:27 < bramc> You don't need blocks to contain heights for the peer protocol to report them 20:27 -!- jcluck [~cluckj@pool-108-16-231-242.phlapa.fios.verizon.net] has joined #bitcoin-wizards 20:28 < tulip> it's not that inefficient now for catching up with the chain, it used to be. 20:28 < bramc> An object can be valid but not validated, for example I can be in the process of downloading a block from a peer but I haven't finished validating it yet because I don't have all of the blocks below it yet. For me to announce that I have that object to my own peers would be very bad behavior. 20:30 < bramc> Well you're stuck not being able to pipeline the block headers with this protocol. That shouldn't be *too* bad as long as you can pipeline the actual transactions though. How does it handle those? Are the intermediary positions in the hash tree treated as separate objects? 20:30 -!- cluckj [~cluckj@pool-108-16-231-242.phlapa.fios.verizon.net] has quit [Ping timeout: 265 seconds] 20:31 < tulip> the merkle tree isn't stored in the block format, it's literally just a concatenation of [block header] [num of transactions] [transaction binary]. the node rebuilds it as part of the validation. 20:32 < bramc> So the transaction binary has to be transferred as a complete blob before it can be validated? 20:32 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has quit [Read error: Connection reset by peer] 20:32 -!- GGuyZ_ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has joined #bitcoin-wizards 20:33 < tulip> yes. there's an alternate protocol which in a round about way lets you build the merkle tree from transactions you've already seen on the network, the remote peer pre-emptively sending you any transaction binaries it knows you have missed. 20:35 < bramc> Also, dumb question: If I restart my node after it's been asleep for a while, what does it do with everything in its mempool? Presumably most of what's in there is now garbage, does it throw it away, waste a bunch of bandwidth trying to send it around immediately, or something else? 20:35 < tulip> the memory pool is not retained in any capacity. 20:35 < bramc> That's an unfortunate but pragmatic policy 20:35 < tulip> wait, asleep. 20:36 < tulip> if the process is just paused, the transactions in the mempool will probably have been confirmed in newly incoming blocks, once they've been confirmed they'll be removed. 20:37 < bramc> By 'asleep' I mean 'paused for long enough that the old connections all time out and new ones have to be formed' 20:37 < tulip> it'll be retained in that case. 20:37 < bramc> Presumably whenever you form a new connection, even if it's with a peer you had a connection to before, you have to rework your whole connection state 20:38 < tulip> that'll just be the new headers though. 20:39 < tulip> nodes that have been restarted are significantly slower than ones that have kept running for a while, most of the reason the network hasn't collapsed already is that Bitcoin Core uses caching of transaction validity. with the caching turned down things really start to get slow. 20:40 < bramc> By the way, in the blockchain format, does it form the merkle root by hashing the hashes of transactions, or is it really and truly the hash of the complete blob? 20:40 -!- Lightsword [~Lightswor@104.194.123.94] has joined #bitcoin-wizards 20:40 < bramc> I'm not sure what you mean by 'caching of transaction validity' 20:42 < tulip> say we see an unconfirmed transaction, we can cache the ECDSA signature verification, if we see it in a block later we can skip that slow business entirely. this is slightly problematic because the network speed relies on miners not packing blocks with unknown transactions. 20:42 -!- GGuyZ_ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has quit [Read error: Connection reset by peer] 20:43 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has joined #bitcoin-wizards 20:45 < bramc> Right signature validations should of course be cached 20:48 < tulip> it's not an ideal solution though, it opens you up to attacks where certain nodes can have a cache eviction attack performed against them to intentionally slow their accepting of new blocks. 20:48 < bramc> Maybe I should explain how I'd go about designing Bitcoin peer protocol from scratch, because we're speaking somewhat different languages here. When I design a protocol the first question is 'what is the state which peers present to each other, and how should peers respond appropriately to achieve eventual consistency?' Most network protocols are centered around 'what does the current code do in response to particular me 20:48 < bramc> ssages?' with the state being implicit and somewhat busted 20:48 -!- jaekwon [~jaekwon@2601:645:c001:263a:f829:b25c:7239:a8e1] has joined #bitcoin-wizards 20:49 < bramc> What sort of cache eviction attack are you thinking of? 20:49 -!- TBI__ [~TBI@84.48.195.20] has joined #bitcoin-wizards 20:49 -!- jaekwon [~jaekwon@2601:645:c001:263a:f829:b25c:7239:a8e1] has quit [Remote host closed the connection] 20:50 -!- jaekwon [~jaekwon@2601:645:c001:263a:f829:b25c:7239:a8e1] has joined #bitcoin-wizards 20:50 < tulip> say my node only stores 50MB of validated signatures in its cache. you flood me with 51MB of useless transactions and cause relevant ones to be evicted, when a new block comes around I've no useful pre-validation remaining and have to do all of the work again. 20:52 < bramc> Define 'useless transactions'. There's a limit of the number of transactions you can make, based on the number of utxos you have 20:52 -!- TBI_ [~TBI@20.84-48-195.nextgentel.com] has quit [Ping timeout: 264 seconds] 20:54 < tulip> that's not a meaningful limit to the number of them, there's 32642787 unspent outputs. you can also do tricks with miner participation, like making reasonable transactions and then re-signing them for their block contents causing the cache to be useless. 20:55 < bramc> To my mind there are two different and tangentially related things which connections do: transmit blocks and transmit uncommitted transactions 20:55 < tulip> one thing to remember is that when the p2p network was designed, there were more purposes than that. only 2 of the commands dealt with transactions and blocks. 20:56 < bramc> You can keep that under control by only allowing a single replacement of each input per block 20:57 < tulip> how do you mean? 20:57 < bramc> I have a working idea in my mind of a set of policies which do a decent job of deciding what in the mempool to forward, but it only works with rbf and I have little motivation to figure out how to hack things in not the right way. 20:58 < tulip> (other commands included 'review', 'product', and 'table', 'submitorder') 20:58 < bramc> If you send me a transaction which validates, then you send me another transaction for the same utxo, I ignore it until a block has passed, without even trying to validate. 20:59 < bramc> Right, there's some weird stuff about bitcoin peer protocol having plans for a marketplace, all of which has been abandoned. 20:59 < bramc> It's the borscht belt. 20:59 < tulip> and a poker game. 21:01 < tulip> I haven't followed RBF concepts so I can't really comment on that in comparison to any other. 21:01 < bramc> There are two situations to take seriously: (a) You join with nothing and are downloading since genesis, and (b) there are two different long chains which are neck and neck trying to outrace each other and swapping who's in first 21:02 -!- nessence [~alexl@cpe-67-244-121-127.nyc.res.rr.com] has joined #bitcoin-wizards 21:02 < tulip> if the latter is happening you've got other troubles. 21:03 -!- kwonbie [~me@cpe-108-183-19-42.nycap.res.rr.com] has quit [Ping timeout: 240 seconds] 21:05 < bramc> With regards to rbf and all that, the high level abstract point is that transactions go into three buckets: dead, tbd, and accepted. Which bucket they go in is based on their fees, what you already had when you received them, what else is in your mempool, and of course whether they passed validation. Sometimes after a block passes you move stuff from tbd to accepted. What accepted means is that you proactively push it on 21:05 < bramc> all your peers. The only way a transaction can get out of dead is if the block height it became dead in gets rewound. 21:06 < bramc> Yes case (b) sucks big donkey nuts. All the more reason why peers should try to handle it rather than spontaneously melting. 21:06 < bramc> Note also that (a) and (b) can happen at the same time. 21:09 < tulip> I don't think the software can handle (b), long reorganisations cause the nodes to catch fire essentially. 21:10 < tulip> all of your peers drop you due to the pings timing out, for example. 21:11 < bramc> For the purposes of (b) it's very important that peers announce what their current highest block is and be able to answer questions about its linear history as a whole 21:12 < bramc> Yes catching on fire in the event of a long reorg is what I'd expect in the case of a hacked together protocol. It isn't inherent to the blockchain though. 21:13 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has quit [Ping timeout: 252 seconds] 21:14 < tulip> the problems with the p2p protocol are a bit wider than this discussion though. the transaction flooding system is quite leaky, there's an incentive for companies to attempt to connect massively to every peer they can in order to gain timing information. what that means ultimately is that huge portion of the capacity is wasted. 21:14 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has joined #bitcoin-wizards 21:15 < bramc> The details of exactly how the current protocol catches on fire in that situation is something I'd only want to know out of morbid rather than academic curiosity 21:17 -!- nessence [~alexl@cpe-67-244-121-127.nyc.res.rr.com] has quit [] 21:17 < bramc> Well, good behavior is to either (a) spam every peer you're connected to with every transaction you accept (which like I said before isn't all of them immediately, especially with real fees and rbf) (b) spam all your peers with just the hashes of transactions you've accepted and let them request them, (c) immediately spam a subset of your peers with either of those two and wait a bit to see if you get equivalent notifica 21:17 < bramc> tions from other peers before spamming the rest 21:19 < bramc> https://imgflip.com/i/ur6ga 21:20 -!- simba [~simba@dhcp-18-111-121-34.dyn.mit.edu] has quit [Remote host closed the connection] 21:20 < bramc> Fundamentally when two peers connect to each other for each item in the mempool something will have to be sent between them for them to both know they've gotten it. The only short circuit is for the transaction to already be in an accepted block. Unless you have weak blocks. Weak blocks are a good idea. 21:22 -!- rht___ [uid86914@gateway/web/irccloud.com/x-sfokaqyszuzmliyb] has joined #bitcoin-wizards 21:23 < tulip> we do (b) today basically. 21:24 < tulip> (c) is problematic because it assumes on some level that your peers are sane. 21:24 < bramc> That is a pragmatic default. I wouldn't advocate for anything else. 21:27 -!- Newyorkadam [~Newyorkad@wikipedia/Newyorkadam] has quit [Quit: Newyorkadam] 21:30 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards 21:33 -!- Lightsword [~Lightswor@104.194.123.94] has quit [Quit: Lightsword] 21:34 -!- Newyorkadam [~Newyorkad@wikipedia/Newyorkadam] has joined #bitcoin-wizards 21:34 -!- Lightsword [~Lightswor@104.194.123.94] has joined #bitcoin-wizards 21:34 -!- Lightsword [~Lightswor@104.194.123.94] has quit [Client Quit] 21:35 -!- jaekwon [~jaekwon@2601:645:c001:263a:f829:b25c:7239:a8e1] has quit [Remote host closed the connection] 21:36 -!- simba [~simba@dhcp-18-111-93-77.dyn.mit.edu] has joined #bitcoin-wizards 21:41 -!- tulip [~tulip@unaffiliated/tulip] has quit [] 21:41 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has quit [Quit: GGuyZ] 21:49 -!- spinza [~spin@197.89.39.106] has quit [Ping timeout: 276 seconds] 21:54 -!- spinza [~spin@197.89.39.106] has joined #bitcoin-wizards 21:55 -!- sparetire_ [~sparetire@unaffiliated/sparetire] has quit [Quit: sparetire_] 21:58 < gmaxwell> No more entries in the key disclosing signature contest? 22:10 -!- dEBRUYNE [~dEBRUYNE@56-197-ftth.onsbrabantnet.nl] has joined #bitcoin-wizards 22:14 < gmaxwell> andytoshi came up with the same approach aj came up with. 22:14 -!- Newyorkadam [~Newyorkad@wikipedia/Newyorkadam] has quit [Quit: Newyorkadam] 22:14 < gmaxwell> (which I think also works, but is less efficient than mine.) 22:21 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Quit: .] 22:23 < rusty> gmaxwell: OK, spill... 22:23 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-wizards 22:27 < gmaxwell> okay lets pretend then that someone started doing it and the scriptpubkeys showed up on the network. 22:28 < gmaxwell> The scriptPubkey that forces you to reveal a private key is OP_SIZE 57 OP_LESSTHANOREQUAL OP_VERIFY

OP_CHECKSIGVERIFY 22:29 < gmaxwell> (57 could be modified slightly, as there is a signing time, security tradeoff.) 22:29 * gmaxwell stands back while all the people say "WTF?" 22:29 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Quit: .] 22:31 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-wizards 22:34 < bramc> gmaxwell, Sadly I can't read Bitcoin script. Is the challenge to make a scriptsubkey which can only be opened by revealing the private key to a specific public key which is presented as a challenge? 22:35 < gmaxwell> yes 22:35 < gmaxwell> in the existing Bitcoin network today; it's not hard to do with minor soft-fork additions. 22:36 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Ping timeout: 252 seconds] 22:37 -!- dEBRUYNE [~dEBRUYNE@56-197-ftth.onsbrabantnet.nl] has quit [Ping timeout: 265 seconds] 22:38 < petertodd> gmaxwell: oh, you're just forcing me to make a signature that allows some math to be used to recover the private key, probably using the sighash_single bug 22:38 < rusty> OK, so they have to have provided an unusually small signature. With DER encoding + sig type, that means the <= 57 bytes check here implies length of S + length of R <= 50 bytes? 22:38 < gmaxwell> petertodd: nope. :) 22:38 < gmaxwell> rusty: yes. 22:39 < gmaxwell> I'll give the rest away: There exists a point with known discrete log which begins with 90 bits of zeros. 22:40 < gmaxwell> For reasons unknown to us when G was selected for secp256k1 they took a 166 bit number of unknown origin coerced it to a point and doubled it. 22:40 < petertodd> gmaxwell: ok, so the first part of my guess was right :P 22:40 < gmaxwell> So that point has a discrete log of 1/2 F(n). 22:41 < petertodd> gmaxwell: "For reasons unknown to us" <- that sounds sketchy 22:41 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-wizards 22:42 < gmaxwell> petertodd: nah, not really-- it's pretty easy to prove that the selection of the generator is irrelevant. Thats why no specs bother to disclose how they came up with them. (I had to harass DJB to spec it for his curves.) 22:42 < gmaxwell> For lots of curves they're sha1s of random stuff or ascii text or other random stuff. 22:42 < petertodd> gmaxwell: good; irrelevant except for crazy tricks like this? 22:43 < gmaxwell> Well irrelevent for "elliptic curve security" which doesn't mean entirely irrelevant. 22:44 < rusty> gmaxwell: so, the only other (known) way to get a sig that small is brute force? 22:44 < gmaxwell> (if you have a magic generator Q that you can solve discrete logs with respect to it, solve the discrete log of G with respect to it.. Now any disrectly log problem with respect to G reduces to one with respect to Q just by multiplying the point in question by the inverse of the DL of G wrt Q.) 22:44 < gmaxwell> rusty: Yes. 22:45 < gmaxwell> The 90 bit reduction is a bit weak because you could grid R then grind S, so what my script actually requires is smaller than you'd get with that special R. 22:45 < gmaxwell> You're required to grind S some too. 22:46 < bramc> For a given modulus aren't all generators isomorphic, and you pick one which allows an efficient implementation? 22:48 < gmaxwell> bramc: assuming that there are no subgroups (there aren't for secp256k1); for EC the choice of the generator doesn't really have performance implementations, not like it does for Zp discrete-log. 22:49 < rusty> Damn, gtg. Will digest on ride home... 22:49 -!- matsjj [~matsjj@p20030089EA107E332D5ACAC7B45B8E3F.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds] 22:49 < bramc> Ah, I was thinking of GF(2^n) where they're all exactly the same and it's all about which one has the most efficient implementation 22:49 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 22:59 -!- TBI__ [~TBI@84.48.195.20] has quit [Ping timeout: 260 seconds] 23:01 -!- TBI [~TBI@84.48.195.20] has joined #bitcoin-wizards 23:10 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-vvndlqovnchvmuww] has joined #bitcoin-wizards 23:14 -!- Burrito [~Burrito@unaffiliated/burrito] has joined #bitcoin-wizards 23:15 -!- orik [~orik@50-46-140-220.evrt.wa.frontiernet.net] has joined #bitcoin-wizards 23:17 < bramc> Back on the subject of a long back and forth fork: Only a small amount of miner self-interestedness could easily result in two competing forks between miners which could take quite a while sort itself out. Eventually it inevitably would, but oh what a mess. 23:21 < bramc> One of those 'wouldn't this be fun' scenarios which works on paper. Miners could even start adding bribes to their own losing chain to pull in other miners, resulting in a Democrats vs Republicans sort of scenario 23:23 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 265 seconds] 23:24 -!- jaekwon [~jaekwon@2601:645:c001:263a:f829:b25c:7239:a8e1] has joined #bitcoin-wizards 23:27 -!- vdo [~vdo1138@unaffiliated/vdo] has quit [Ping timeout: 240 seconds] 23:27 -!- stevenroose [stevenroos@bnc1.sollidi.us] has quit [Ping timeout: 240 seconds] 23:32 -!- gnusha_ [~gnusha@unaffiliated/kanzure/bot/gnusha] has joined #bitcoin-wizards 23:32 -!- Topic for #bitcoin-wizards: This channel is for discussing theoretical ideas with regard to cryptocurrencies, not about short-term Bitcoin development | http://bitcoin.ninja/ | This channel is logged. | For logs and more information, visit http://bitcoin.ninja 23:32 -!- Topic set by sipa [~pw@unaffiliated/sipa1024] [Thu Oct 29 17:53:34 2015] 23:32 [Users #bitcoin-wizards] 23:32 [@ChanServ ] [ btcdrak ] [ gribble ] [ kinlo ] [ nickler ] [ so ] 23:32 [ [7] ] [ Burrito ] [ grubles ] [ kinlo_ ] [ nsh ] [ sparetire ] 23:32 [ [ace] ] [ c0rw1n ] [ Guest1234 ] [ Kireji ] [ null_radix ] [ spinza ] 23:32 [ [d__d] ] [ catcow ] [ Guest46756 ] [ kisspunch ] [ nwilcox|1fk ] [ Starduster ] 23:32 [ [Derek] ] [ catlasshrugged ] [ guruvan ] [ koshii ] [ OneFixt ] [ starsoccer ] 23:32 [ [Derek]_ ] [ cfields_ ] [ gwillen ] [ Krellan_ ] [ optimator ] [ stevenroose ] 23:32 [ _whitelogger ] [ ciege ] [ harding ] [ kumavis ] [ orik ] [ stonecoldpat1] 23:32 [ a5m0 ] [ cluckj ] [ harrow` ] [ kyuupichan ] [ otoburb ] [ STRML ] 23:32 [ adams__ ] [ CodeArtix ] [ hashtag_ ] [ larraboj ] [ OxADADA ] [ SwedFTP ] 23:32 [ adlai ] [ comboy ] [ hashtagg ] [ lclc ] [ paci ] [ SwedFTP_ ] 23:32 [ AdrianG ] [ coryfields ] [ heath_ ] [ lecusemble ] [ Pasha ] [ Taek ] 23:32 [ AdrianG_ ] [ crescendo ] [ helo ] [ LeMiner ] [ PaulCapestany ] [ TBI ] 23:32 [ aem ] [ d4de ] [ humd1ng3r ] [ livegnik ] [ penjenayah ] [ TD-Linux ] 23:32 [ afdudley ] [ d9b4bef9 ] [ huseby ] [ lmatteis ] [ petertodd ] [ Tenhi ] 23:32 [ aj ] [ dansmith_btc ] [ ibrightly ] [ lnovy ] [ phantomcircuit ] [ Tiraspol ] 23:32 [ aj_ ] [ dave4925_h ] [ iddo ] [ Logicwax ] [ phy1729 ] [ toomim ] 23:32 [ Alanius ] [ davec ] [ instagibbs ] [ lomax_ ] [ pigeons ] [ tripleslash ] 23:32 [ alexkuck ] [ davout ] [ ir2ivps5 ] [ Luke-Jr ] [ Piper-Off ] [ tromp_ ] 23:32 [ alpalp ] [ devrandom ] [ Iriez ] [ luke-jr_ ] [ poggy_ ] [ tromp__ ] 23:32 [ amiller_ ] [ dgenr8 ] [ isis ] [ luny ] [ PRab ] [ ttttemp ] 23:32 [ Anduck ] [ digitalmagus8 ] [ Jaamg ] [ Madars ] [ prosody ] [ tucenaber ] 23:32 [ andytoshi ] [ dignork ] [ jaekwon ] [ MagikSquirrel] [ PsychoticBoy ] [ vdo ] 23:32 [ Apocalyptic ] [ DougieBot5000 ] [ jaromil ] [ malte ] [ psztorc ] [ vdo_ ] 23:32 [ archobserver ] [ ebfull ] [ jbenet ] [ mappum ] [ publius1788 ] [ warptangent ] 23:32 [ arowser ] [ Eliel ] [ jcorgan ] [ mariorz ] [ Pugg ] [ warren ] 23:32 [ arowser_ ] [ Emcy ] [ jcorgan_ ] [ Meeh_ ] [ qawap_ ] [ waxwing ] 23:32 [ artifexd ] [ epscy ] [ jeremias ] [ melvster ] [ rasengan ] [ weex_ ] 23:32 [ arubi ] [ eric ] [ Jeremy_Rand ] [ metric ] [ rht___ ] [ wilbns ] 23:32 [ asoltys ] [ espes ] [ Jeremy_Rand_ ] [ midnightmagic] [ richardkiss ] [ wizkid057 ] 23:32 [ atgreen ] [ execute ] [ jeremyrubin ] [ mikolalysenko] [ roasbeef ] [ wpalczynski ] 23:32 [ BananaLotus ] [ face ] [ jessepollak ] [ mm_1 ] [ robmyers ] [ wump ] 23:32 [ bassguitarman ] [ Fistful_of_Coins] [ jessepollak_ ] [ moa ] [ runeks ] [ wumpus ] 23:32 [ berndj ] [ fkhan ] [ jgarzik_ ] [ morcos_ ] [ ryan-c ] [ xaptah ] 23:32 [ bildramer ] [ fluffypony ] [ jgarzik__ ] [ mountaingoat ] [ s1w ] [ xeon-enouf ] 23:32 [ binaryFateCloud] [ forrestv ] [ jlrubin ] [ mr_burdell ] [ sdaftuar ] [ Xzibit17 ] 23:32 [ bitkarma ] [ gavinandresen ] [ jlyndon ] [ mr_burdell_ ] [ seg ] [ yang ] 23:32 [ blkdb ] [ ggreer ] [ jojva ] [ MRL-Relay ] [ SgtStroopwafel ] [ Ylbam ] 23:32 [ BlueMatt ] [ ghtdak ] [ jonasschnelli] [ Myagui ] [ SgtStroopwafel_] [ yoleaux ] 23:32 [ BlueMatt_ ] [ gmaxwell ] [ jouke ] [ N0S4A2 ] [ SheffieldCrypto] [ yorick ] 23:32 [ bobke ] [ gnusha ] [ jrayhawk ] [ nanasha ] [ shesek ] [ zm4c1n3 ] 23:32 [ BrainOverfl0w ] [ gnusha_ ] [ K1773R ] [ nanasho ] [ simba ] [ zmanian_ ] 23:32 [ bramc ] [ go1111111 ] [ kang_ ] [ nanotube ] [ sipa ] [ zxzzt ] 23:32 [ brand0 ] [ Graet ] [ kanzure ] [ nba_btchip ] [ sipa_ ] 23:32 [ bsm117532 ] [ grandmaster ] [ katu ] [ neha ] [ smk ] 23:32 [ bsm1175321 ] [ grantsmith ] [ Keefe ] [ nephyrin ] [ smooth ] 23:32 [ bsm1175322 ] [ GreenIsMyPepper ] [ keus ] [ nephyrin` ] [ sneak ] 23:32 -!- Irssi: #bitcoin-wizards: Total of 272 nicks [1 ops, 0 halfops, 0 voices, 271 normal] 23:32 -!- Channel #bitcoin-wizards created Mon Feb 25 23:24:47 2013 23:32 -!- OxADADA_ [~OxADADA@alumni-linux.ccs.neu.edu] has joined #bitcoin-wizards 23:32 -!- Irssi: Join to #bitcoin-wizards was synced in 22 secs 23:32 -!- coryfields_ [~quassel@2001:4802:7800:1:6fc4:c486:ff20:1fa] has joined #bitcoin-wizards 23:32 -!- huseby_ [~huseby@unaffiliated/huseby] has joined #bitcoin-wizards 23:33 -!- jbenet_ [sid17552@gateway/web/irccloud.com/session] has joined #bitcoin-wizards 23:33 -!- phantomcircuit_ [phantomcir@2600:3c01::f03c:91ff:fe73:6892] has joined #bitcoin-wizards 23:33 -!- BurritoBazooka [~Burrito@unaffiliated/burrito] has joined #bitcoin-wizards 23:33 -!- thrasher` [~thrasher@ec2-54-66-203-250.ap-southeast-2.compute.amazonaws.com] has joined #bitcoin-wizards 23:34 -!- Taek42 [~quassel@2001:41d0:1:472e::] has joined #bitcoin-wizards 23:34 -!- dansmith_ [~dansmith@static-ip-188-138-10-193.inaddr.ip-pool.com] has joined #bitcoin-wizards 23:34 -!- crescend1 [~mozart@173.203.100.20] has joined #bitcoin-wizards 23:34 -!- kisspunch_ [~za3k@za3k.com] has joined #bitcoin-wizards 23:34 -!- catlasshrugged_ [~catlasshr@ec2-54-149-141-214.us-west-2.compute.amazonaws.com] has joined #bitcoin-wizards 23:35 -!- Netsplit *.net <-> *.split quits: nanasho, kinlo, arowser, orik, BlueMatt, tucenaber, dansmith_btc, ttttemp, metric, richardkiss, (+2 more, use /NETSPLIT to show all of them) 23:35 -!- kinlo_ is now known as kinlo 23:35 -!- pozitron [~nu@193.33.216.23] has joined #bitcoin-wizards 23:35 < bramc> A netsplit. I feel like it's 1995. 23:35 -!- warren_2 [~warren@fedora/wombat/warren] has joined #bitcoin-wizards 23:35 -!- otoburb_ [~otoburb@unaffiliated/otoburb] has joined #bitcoin-wizards 23:35 -!- bildramer [~bildramer@p5DC8A746.dip0.t-ipconnect.de] has joined #bitcoin-wizards 23:36 -!- Netsplit *.net <-> *.split quits: Piper-Off, jeremyrubin, ibrightly, keus, Pugg, catlasshrugged, morcos_, lmatteis, publius1788, N0S4A2, (+3 more, use /NETSPLIT to show all of them) 23:36 -!- berndj-blackout [~berndj@azna.co.za] has joined #bitcoin-wizards 23:36 -!- Netsplit over, joins: jeremyrubin 23:36 -!- Netsplit *.net <-> *.split quits: warren, otoburb, mm_1, berndj, Madars, Apocalyptic, Burrito, jcorgan, moa 23:36 -!- warren_2 is now known as warren 23:36 -!- keus [~jussi@84.250.114.176] has joined #bitcoin-wizards 23:36 -!- Pasha is now known as Cory 23:36 -!- earthrise [~earthrise@S01065404a6902716.cg.shawcable.net] has joined #bitcoin-wizards 23:36 -!- guruvan- [~guruvan@unaffiliated/guruvan] has joined #bitcoin-wizards 23:37 -!- Netsplit *.net <-> *.split quits: Luke-Jr, jaekwon, AdrianG, Jeremy_Rand, jonasschnelli, jgarzik_, OxADADA 23:37 -!- publius1788 [~publius17@104.200.154.10] has joined #bitcoin-wizards 23:38 < Taek42> lol @ the number of users spiking while everyone gets shifted to their alt handles 23:38 -!- smooth_ [~ubuntu@ec2-54-201-223-245.us-west-2.compute.amazonaws.com] has joined #bitcoin-wizards 23:38 < bramc> A majority of mining power could successfully conspire to reliably win forks. A significant minority could make it worth their own while to mine them. 23:39 -!- Apocalyptic [~Apocalypt@unaffiliated/apocalyptic] has joined #bitcoin-wizards 23:39 < Taek42> I've been thinking about a potential schelling point where the biggest miners only forward blocks they find to the other biggest miners and nobody else 23:39 -!- mm_1 [bnc33@bnc33.nitrado.net] has joined #bitcoin-wizards 23:39 -!- OneFixt_ [~OneFixt@unaffiliated/onefixt] has joined #bitcoin-wizards 23:40 < Taek42> as long as blocks are getting to a majority of the hashpower, the minority will experience higher orphan rates 23:40 -!- Netsplit *.net <-> *.split quits: smooth, crescendo, ebfull, Fistful_of_Coins, bsm117532, nwilcox|1fk, wilbns, nanotube, isis, hashtag_, (+7 more, use /NETSPLIT to show all of them) 23:40 -!- mr_burdell_ is now known as mr_burdell 23:40 -!- SwedFTP_ is now known as SwedFTP 23:40 -!- Netsplit over, joins: petertodd 23:40 < gmaxwell> Taek42: really you would prefer only about 33% of the hashpower gets your blocks quickly. 23:40 < gmaxwell> (same reason as the selfish mining results) 23:41 -!- Netsplit *.net <-> *.split quits: nephyrin`, fkhan, stevenroose, waxwing, shesek, adlai, kumavis, paci, nsh, go1111111, (+28 more, use /NETSPLIT to show all of them) 23:41 -!- kisspunch_ is now known as kisspunch 23:41 -!- guruvan- is now known as guruvan 23:41 -!- mr_burdell is now known as Guest79101 23:41 -!- indolering [~indolerin@104.236.55.109] has joined #bitcoin-wizards 23:41 -!- spinza [~spin@197.89.39.106] has joined #bitcoin-wizards 23:41 -!- jessepollak_ is now known as jessepollak 23:41 -!- Netsplit over, joins: humd1ng3r 23:41 -!- matsjj [~matsjj@p20030089EA0CB51E445C0B284CB18F58.dip0.t-ipconnect.de] has joined #bitcoin-wizards 23:41 -!- Netsplit over, joins: helo 23:42 -!- ibrightly [sid113387@gateway/web/irccloud.com/session] has joined #bitcoin-wizards 23:42 -!- kaptah [kaptah@hilla.kapsi.fi] has joined #bitcoin-wizards 23:42 -!- heath [~heath@unaffiliated/ybit] has joined #bitcoin-wizards 23:42 -!- fkhan [weechat@gateway/vpn/mullvad/session] has joined #bitcoin-wizards 23:42 -!- fkhan [weechat@gateway/vpn/mullvad/session] has quit [Changing host] 23:42 -!- fkhan [weechat@unaffiliated/loteriety] has joined #bitcoin-wizards 23:42 -!- Netsplit *.net <-> *.split quits: davec, starsoccer, PaulCapestany, Iriez 23:42 -!- Netsplit over, joins: PaulCapestany 23:42 -!- nsh- [~lol@wikipedia/nsh] has joined #bitcoin-wizards 23:43 -!- ttttemp [~ttttemp@pc-5305.ethz.ch] has joined #bitcoin-wizards 23:43 -!- Lightsword [~Lightswor@104.194.123.94] has joined #bitcoin-wizards 23:44 -!- joesmoe [~joesmoe@76.73.18.156] has joined #bitcoin-wizards 23:44 -!- Fistful_of_Coins [o3u@162.243.79.19] has joined #bitcoin-wizards 23:44 -!- GreenIsMyPepper [~GreenIsMy@2605:6400:20:11aa:189e:28a5:52ed:8948] has joined #bitcoin-wizards 23:45 -!- N0S4A2 [~weechat@216-243-38-141.users.condointernet.net] has joined #bitcoin-wizards 23:46 < bramc> gmaxwell, What's the reasoning behind 1/3 getting blocks quickly? 23:46 -!- rht___ [uid86914@gateway/web/irccloud.com/x-sfokaqyszuzmliyb] has quit [Quit: Connection closed for inactivity] 23:46 -!- Anduck [~anduck@unaffiliated/anduck] has joined #bitcoin-wizards 23:46 < Taek42> bramc: http://arxiv.org/pdf/1311.0243v5.pdf 23:47 < bramc> Thanks I'll read through that later 23:47 -!- catlasshrugged [~catlasshr@ec2-54-149-141-214.us-west-2.compute.amazonaws.com] has joined #bitcoin-wizards 23:48 < Taek42> when 33% of the hashpower is 1 block ahead, the remaining 66% needs to mine 2 blocks to win the fork-race 23:48 < Taek42> each side of the fork has a 50% chance of winning 23:48 -!- paci [~paci@host41-233-static.58-79-b.business.telecomitalia.it] has joined #bitcoin-wizards 23:48 -!- Pugg [Elite11832@gateway/shell/elitebnc/session] has joined #bitcoin-wizards 23:49 < bramc> Mining being heavily centralized really doesn't help 23:49 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has joined #bitcoin-wizards 23:49 < gmaxwell> bramc: no shit. 23:49 -!- go1111111 [~go1111111@104.200.154.31] has joined #bitcoin-wizards 23:49 -!- bobke_ [~bobke@94-226-145-186.access.telenet.be] has joined #bitcoin-wizards 23:49 -!- arowser [~quassel@106.120.101.38] has joined #bitcoin-wizards 23:49 < gmaxwell> Unfortunately, bitcoin users have been in excuse mode for so long, getting traction about improving that is not easy. 23:49 -!- nanotube [~nanotube@unaffiliated/nanotube] has joined #bitcoin-wizards 23:50 -!- ebfull [~sean@73.34.119.0] has joined #bitcoin-wizards 23:50 < bramc> gmaxwell, I'm not sure what can be done to improve it. Other than explaining to people that joining mining pools just because isn't such a hot idea I mean. 23:50 < bramc> Not that mining decentralization actually fixes the problem, but at least it helps. 23:51 -!- warren_2 [~warren@fedora/wombat/warren] has joined #bitcoin-wizards 23:51 -!- davout_ [~david@fr.anco.is] has joined #bitcoin-wizards 23:51 -!- zmachine [~zmachine@pool-74-100-90-30.lsanca.fios.verizon.net] has joined #bitcoin-wizards 23:51 -!- OxADADA [~OxADADA@alumni-linux.ccs.neu.edu] has joined #bitcoin-wizards 23:52 < gmaxwell> Oh there are lots of things that can be done both technical and socially. E.g. a lot would be improved to just fix the race misunderstanding; though thats harder when propagation effects make it somewhat true. 23:52 -!- seg_ [~seg@fsf/member/seg] has joined #bitcoin-wizards 23:55 -!- poggy [~poggy@ks3262860.kimsufi.com] has joined #bitcoin-wizards 23:55 -!- btcdrak_ [uid115429@gateway/web/irccloud.com/session] has joined #bitcoin-wizards 23:56 -!- Netsplit *.net <-> *.split quits: arowser_, catlasshrugged_, davout, berndj-blackout, poggy_, dansmith_, OxADADA_, neha, d4de, katu, (+8 more, use /NETSPLIT to show all of them) 23:56 -!- jonasschnelli [~jonasschn@unaffiliated/jonasschnelli] has joined #bitcoin-wizards 23:56 -!- warren_2 is now known as warren 23:56 -!- seg_ is now known as seg 23:56 -!- Netsplit over, joins: koshii 23:56 -!- kumavis [sid13576@gateway/web/irccloud.com/session] has joined #bitcoin-wizards 23:57 -!- dansmith_btc [~dansmith@static-ip-188-138-10-193.inaddr.ip-pool.com] has joined #bitcoin-wizards 23:57 -!- Netsplit over, joins: N0S4A2 23:58 -!- waxwing [~waxwing@62.205.214.125] has joined #bitcoin-wizards 23:58 -!- Netsplit over, joins: d4de 23:58 -!- Netsplit over, joins: neha, katu 23:59 -!- luke-jr_ is now known as Luke-Jr --- Log closed Thu Nov 26 00:00:23 2015