--- Log opened Mon Dec 28 00:00:49 2015
00:01 -!- tachys [~alex@c-73-227-77-34.hsd1.nh.comcast.net] has joined #bitcoin-wizards
00:06 -!- tachys [~alex@c-73-227-77-34.hsd1.nh.comcast.net] has quit [Ping timeout: 240 seconds]
00:10 -!- b_lumenkraft [~b_lumenkr@unaffiliated/b-lumenkraft/x-4457406] has quit [Read error: Connection reset by peer]
00:16 -!- cheetah2 [~cheetah2@172.242.102.144] has quit [Read error: Connection reset by peer]
00:17 -!- cheetah2 [~cheetah2@172.242.102.144] has joined #bitcoin-wizards
00:23 -!- Dizzle [~Dizzle@pool-108-15-195-22.ronkva.east.verizon.net] has quit [Quit: Leaving...]
00:26 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards
00:26 -!- monkey [4532b36a@gateway/web/freenode/ip.69.50.179.106] has quit [Ping timeout: 252 seconds]
00:28 -!- bramc [~bram@99-75-88-206.lightspeed.sntcca.sbcglobal.net] has quit [Quit: This computer has gone to sleep]
00:32 -!- c-cex-finch [uid120855@gateway/web/irccloud.com/x-shhvpisfszicvfni] has joined #bitcoin-wizards
00:38 -!- b_lumenkraft [~b_lumenkr@unaffiliated/b-lumenkraft/x-4457406] has joined #bitcoin-wizards
00:40 -!- b_lumenkraft [~b_lumenkr@unaffiliated/b-lumenkraft/x-4457406] has quit [Client Quit]
00:46 -!- Emcy [~MC@cpc3-swan1-0-0-cust996.7-3.cable.virginm.net] has joined #bitcoin-wizards
00:46 -!- Emcy [~MC@cpc3-swan1-0-0-cust996.7-3.cable.virginm.net] has quit [Changing host]
00:46 -!- Emcy [~MC@unaffiliated/mc1984] has joined #bitcoin-wizards
00:48 -!- Emcy_ [~MC@unaffiliated/mc1984] has quit [Ping timeout: 240 seconds]
00:58 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 246 seconds]
01:04 -!- wallet42 [~wallet42@unaffiliated/wallet42] has quit [Quit: Leaving.]
01:05 < bsm1175321> bramc: Do you have an algorithm to compactly prove that an item is NOT a member of a (Merkle) set? The best I can come up with is O(N) in the size of the set.
01:05 -!- wallet42 [~wallet42@nz112l10.bb11352.ctm.net] has joined #bitcoin-wizards
01:06 < bsm1175321> Oh he's not on.  Hope he sees that...
01:06 < adlai> ;;later tell bramc you've got mail! https://botbot.me/freenode/bitcoin-wizards/2015-12-28/?msg=56874226&page=2
01:06 < gribble> The operation succeeded.
01:07 < bsm1175321> ooh neat, thanks adlai!
01:08 < adlai> when the AI asleeps, funemployed drunkards must drive the bot slaves... yw
01:08 < bsm1175321> hahaaaaa
01:20 -!- LeMiner [LeMiner@unaffiliated/leminer] has joined #bitcoin-wizards
01:21 -!- keus [~jussi@84.250.114.176] has quit [Ping timeout: 245 seconds]
01:22 -!- Myagui [Myagui@shell.xshellz.com] has quit [Remote host closed the connection]
01:28 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds]
01:31 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-ixhmdkwzlfrtqnnt] has joined #bitcoin-wizards
01:33 -!- Myagui-afk [Myagui@shell.xshellz.com] has joined #bitcoin-wizards
01:33 -!- Myagui-afk is now known as Myagui
01:38 -!- cheetah2 [~cheetah2@172.242.102.144] has quit []
01:55 -!- JackH [~Jack@host-80-43-143-141.as13285.net] has joined #bitcoin-wizards
02:03 -!- tachys [~alex@c-73-227-77-34.hsd1.nh.comcast.net] has joined #bitcoin-wizards
02:03 -!- sparetire_ [~sparetire@unaffiliated/sparetire] has quit [Quit: sparetire_]
02:08 -!- tachys [~alex@c-73-227-77-34.hsd1.nh.comcast.net] has quit [Ping timeout: 260 seconds]
02:12 -!- jannes [~jannes@178.132.211.90] has joined #bitcoin-wizards
02:18 -!- seg [~seg@fsf/member/seg] has quit [Quit: kuwabara kuwabara]
02:20 -!- seg [~seg@fsf/member/seg] has joined #bitcoin-wizards
02:28 -!- tulip [~tulip@unaffiliated/tulip] has joined #bitcoin-wizards
02:30 < tulip> adlai: nobody signed any alerts recently. the message people saw about block frequency in their Bitcoin Core nodes was locally and independently triggered. the node will set local panic messages on all sorts of weird conditions it doesn't think are safe to be operating in.
02:31 < adlai> do you really want to troll me back on this one? bitcoin.org's shadow-cabal TLS server signed the code.
02:31 < adlai> maybe alerts should be randomly endisableable as well?
02:31 < adlai> so people actually configure their own software, god forbit read it.
02:32 < fluffypony> I'm confused
02:32 < tulip> you made a comment which made believe you thought the "too many blocks" message came from the Satoshi centralised alert system, perhaps I misunderstood you.
02:32 < fluffypony> the Gitian-signed binaries aren't signed by bitcoin.org ?
02:32  * adlai misunderstood the alert.
02:33 < adlai> and the mysterious workings of machines signing code for other machines to run
02:33 < fluffypony> Gitian is an entirely human-driven system
02:33 < adlai> but hey, satoshi didn't solve key management...
02:34 < fluffypony> a bunch of people build the binaries independently using a system that fixes differences that could occur between builds (eg. file timestamps)
02:34 < adlai> but anyway, sorry for all the drunken noise lately. the one amazing thing about bitcoin is that it stirs up an awful lot of emotion for a bunch of bits.
02:34 < tulip> you're talking about Gitian there, which is unrelated to any alert systems. Gitian allows people to reproduce builds of software down to the byte and confirm that they were created using a set piece of source code. Gitian signatures are people asserting that their real world identify saw this piece of software made in that way.
02:34 < fluffypony> and then they compare the hash of the resulting binary, and if they all agree on it then they sign off on that hash
02:34 -!- adlai [~adlai@unaffiliated/adlai] has left #bitcoin-wizards ["WeeChat 1.3"]
02:34 < fluffypony> sigh.
02:34 < tulip> never mind.
02:36 < tulip> I've seen lots of misunderstanding with the centralised alert system and what it can do and thought I could correct it a little. it can't, for example, shut down nodes. that was a wxBitcoin thing which lasted only a major version or two.
02:37 < fluffypony> tulip: have you seen how Darkcoin / Dash cannibalised it?
02:37 < tulip> for "checkpointing" blocks?
02:37 < fluffypony> no even worse
02:38 -!- wangchun [~wangchun@li414-193.members.linode.com] has quit [Quit: leaving]
02:38 < fluffypony> they've made it so that the alert system can be used to turn bits of code on and off as a way of reversing a fork caused by bad code
02:38 < fluffypony> they call it "sporks"
02:39 -!- wangchun [~wangchun@li414-193.members.linode.com] has joined #bitcoin-wizards
02:40 -!- JackH [~Jack@host-80-43-143-141.as13285.net] has quit [Ping timeout: 276 seconds]
02:43 -!- pozitron [~nu@104.238.169.66] has quit [Ping timeout: 260 seconds]
02:46 < tulip> fluffypony: that's unfortunate.
02:49 -!- laurentmt [~Thunderbi@213-245-86-6.rev.numericable.fr] has joined #bitcoin-wizards
02:50 -!- laurentmt [~Thunderbi@213-245-86-6.rev.numericable.fr] has quit [Client Quit]
02:51 -!- JackH [~Jack@host-80-43-143-141.as13285.net] has joined #bitcoin-wizards
02:52 < fluffypony> quite
02:56 -!- dEBRUYNE__ [~dEBRUYNE@56-197-ftth.onsbrabantnet.nl] has joined #bitcoin-wizards
03:00 -!- JackH [~Jack@host-80-43-143-141.as13285.net] has quit [Ping timeout: 245 seconds]
03:05 -!- dEBRUYNE__ [~dEBRUYNE@56-197-ftth.onsbrabantnet.nl] has quit [Quit: Leaving]
03:07 -!- nabu [~nabu@179.43.176.162] has joined #bitcoin-wizards
03:11 -!- seg [~seg@fsf/member/seg] has quit [Quit: kuwabara kuwabara]
03:15 -!- melvster [~melvster@ip-86-49-18-198.net.upcbroadband.cz] has quit [Ping timeout: 246 seconds]
03:16 -!- seg [~seg@fsf/member/seg] has joined #bitcoin-wizards
03:19 -!- Guyver2 [~Guyver2@a80-100-156-239.adsl.xs4all.nl] has joined #bitcoin-wizards
03:23 -!- phy1729 [~phy1729@unaffiliated/phy1729] has quit [Ping timeout: 260 seconds]
03:27 -!- melvster [~melvster@ip-86-49-18-198.net.upcbroadband.cz] has joined #bitcoin-wizards
03:29 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards
03:34 -!- JackH [~Jack@host-80-43-143-141.as13285.net] has joined #bitcoin-wizards
03:34 -!- Quanttek [~quassel@ip1f11db5b.dynamic.kabel-deutschland.de] has joined #bitcoin-wizards
03:40 -!- tachys [~alex@c-73-227-77-34.hsd1.nh.comcast.net] has joined #bitcoin-wizards
03:44 -!- phy1729 [~phy1729@unaffiliated/phy1729] has joined #bitcoin-wizards
03:45 -!- tachys [~alex@c-73-227-77-34.hsd1.nh.comcast.net] has quit [Ping timeout: 276 seconds]
03:46 -!- seg [~seg@fsf/member/seg] has quit [Quit: kuwabara kuwabara]
03:47 -!- seg [~seg@fsf/member/seg] has joined #bitcoin-wizards
03:49 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Quit: Quitte]
04:11 -!- wallet421 [~wallet42@n182z59l6.static.ctm.net] has joined #bitcoin-wizards
04:11 -!- wallet421 [~wallet42@n182z59l6.static.ctm.net] has quit [Changing host]
04:11 -!- wallet421 [~wallet42@unaffiliated/wallet42] has joined #bitcoin-wizards
04:11 -!- wallet42 [~wallet42@nz112l10.bb11352.ctm.net] has quit [Killed (weber.freenode.net (Nickname regained by services))]
04:11 -!- wallet421 is now known as wallet42
04:21 -!- Starduster [~guest@unaffiliated/starduster] has quit [Ping timeout: 260 seconds]
04:25 -!- tulip [~tulip@unaffiliated/tulip] has quit [Quit: Textual IRC Client: www.textualapp.com]
04:45 -!- AaronvanW [~ewout@meinhotspot1.websecuritas.com] has joined #bitcoin-wizards
04:45 -!- AaronvanW [~ewout@meinhotspot1.websecuritas.com] has quit [Changing host]
04:45 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #bitcoin-wizards
04:47 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has joined #bitcoin-wizards
04:50 -!- melvster1 [~melvster@86.49.18.198] has joined #bitcoin-wizards
04:50 -!- melvster [~melvster@ip-86-49-18-198.net.upcbroadband.cz] has quit [Read error: Connection reset by peer]
05:05 -!- chmod755 [~chmod755@unaffiliated/chmod755] has joined #bitcoin-wizards
05:21 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has quit [Quit: GGuyZ]
05:24 -!- c-cex-finch [uid120855@gateway/web/irccloud.com/x-shhvpisfszicvfni] has quit [Quit: Connection closed for inactivity]
05:26 -!- melvster1 [~melvster@86.49.18.198] has quit [Ping timeout: 272 seconds]
05:29 -!- eudoxia [~eudoxia@r167-57-73-74.dialup.adsl.anteldata.net.uy] has joined #bitcoin-wizards
05:39 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards
05:40 -!- melvster1 [~melvster@ip-86-49-18-198.net.upcbroadband.cz] has joined #bitcoin-wizards
05:42 -!- tachys [~alex@c-73-227-77-34.hsd1.nh.comcast.net] has joined #bitcoin-wizards
05:42 -!- p15 [~p15@24.91.145.64.client.static.strong-tk2.bringover.net] has quit [Ping timeout: 256 seconds]
05:43 -!- Giszmo [~leo@pc-139-55-215-201.cm.vtr.net] has joined #bitcoin-wizards
05:47 -!- tachys [~alex@c-73-227-77-34.hsd1.nh.comcast.net] has quit [Ping timeout: 272 seconds]
05:52 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has joined #bitcoin-wizards
05:53 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Ping timeout: 272 seconds]
06:02 -!- gielbier [~giel____@a149043.upc-a.chello.nl] has joined #bitcoin-wizards
06:02 -!- gielbier [~giel____@a149043.upc-a.chello.nl] has quit [Changing host]
06:02 -!- gielbier [~giel____@unaffiliated/gielbier] has joined #bitcoin-wizards
06:17 -!- brg444 [18257df2@gateway/web/freenode/ip.24.37.125.242] has joined #bitcoin-wizards
06:29 -!- tachys [~alex@c-73-227-77-34.hsd1.nh.comcast.net] has joined #bitcoin-wizards
06:30 -!- tachys [~alex@c-73-227-77-34.hsd1.nh.comcast.net] has quit [Client Quit]
06:35 < kanzure> http://diyhpl.us/~bryan/papers2/bitcoin/Hash%20tube%20signature%20scheme.pdf
06:39 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has quit [Ping timeout: 260 seconds]
06:43 -!- eudoxia [~eudoxia@r167-57-73-74.dialup.adsl.anteldata.net.uy] has quit [Quit: Leaving]
06:46 -!- belcher [~user@unaffiliated/belcher] has joined #bitcoin-wizards
06:47 -!- dEBRUYNE [~dEBRUYNE@56-197-ftth.onsbrabantnet.nl] has joined #bitcoin-wizards
06:54 -!- civos [~civ0s@50.248.81.65] has quit [Quit: Leaving]
06:57 -!- dEBRUYNE [~dEBRUYNE@56-197-ftth.onsbrabantnet.nl] has quit [Quit: Leaving]
06:59 -!- Burrito [~Burrito@unaffiliated/burrito] has joined #bitcoin-wizards
07:31 -!- jannes [~jannes@178.132.211.90] has quit [Ping timeout: 256 seconds]
07:44 -!- jannes [~jannes@178.132.211.90] has joined #bitcoin-wizards
07:53 -!- wallet42 [~wallet42@unaffiliated/wallet42] has quit [Quit: Leaving.]
07:58 -!- melvster1 [~melvster@ip-86-49-18-198.net.upcbroadband.cz] has quit [Ping timeout: 265 seconds]
08:00 < kanzure> various math books from springer https://gist.github.com/bishboria/8326b17bbd652f34566a
08:05  * nsh frowns
08:08 < nsh> what is the actual provenance of the hash-tube paper?
08:09 -!- tripleslash_t [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-wizards
08:10 -!- [\\\] [~triplesla@unaffiliated/imsaguy] has quit [Ping timeout: 264 seconds]
08:11 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has joined #bitcoin-wizards
08:12 -!- melvster1 [~melvster@ip-86-49-18-198.net.upcbroadband.cz] has joined #bitcoin-wizards
08:13 < phantomcircuit> nsh, im just waiting for the altcoin that wrote it to be released claiming to be "from satoshi"
08:14  * nsh nods
08:15 < nsh> it is worthwhile considering PQ hash-based signature constructions for cryptocurrencies, but i'm pretty convinced falsely attributing your ideas to satoshi is not indicative of a great attitude or agenda
08:18 < kanzure> provenance is probably not important in this case; i could strip the name from the paper if that would make nsh feel better about how terrible the world is
08:19 < Taek> It's a cool construction at least, but it still results in 8kib signatures, which is not an improvement over the lamport signature
08:19 < nsh> you'd have to elide the memory or recall faculty in my brain too :)
08:19 < kanzure> well that's trivial
08:19  * kanzure readies the kinetic memory disruptor
08:20 < nsh> sure, i accept whisky, rum, most dissociatives, &c.
08:22 < nsh> more seriously, i'm not sure there is really much in the way of research findings for the second hash property (preimage resistances given 2/3 of the preimage)
08:24 -!- JackH [~Jack@host-80-43-143-141.as13285.net] has quit [Ping timeout: 245 seconds]
08:35 -!- zookolaptop [~user@68.233.157.2] has joined #bitcoin-wizards
08:45 -!- dEBRUYNE [~dEBRUYNE@56-197-ftth.onsbrabantnet.nl] has joined #bitcoin-wizards
08:49 -!- dEBRUYNE [~dEBRUYNE@56-197-ftth.onsbrabantnet.nl] has quit [Client Quit]
08:50 -!- jannes [~jannes@178.132.211.90] has quit [Ping timeout: 256 seconds]
08:51 -!- jannes [~jannes@178.132.211.90] has joined #bitcoin-wizards
08:56 -!- laurentmt [~Thunderbi@213-245-86-6.rev.numericable.fr] has joined #bitcoin-wizards
08:56 -!- laurentmt [~Thunderbi@213-245-86-6.rev.numericable.fr] has quit [Client Quit]
08:59 -!- dEBRUYNE [~dEBRUYNE@56-197-ftth.onsbrabantnet.nl] has joined #bitcoin-wizards
09:02 -!- nuke1989 [~nuke@178-157-152.dynamic.cyta.gr] has joined #bitcoin-wizards
09:05 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-wizards
09:09 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #bitcoin-wizards
09:14 -!- c-cex-finch [uid120855@gateway/web/irccloud.com/x-lhcjulyppgiogdzz] has joined #bitcoin-wizards
09:24 -!- sparetire_ [~sparetire@unaffiliated/sparetire] has joined #bitcoin-wizards
09:29 -!- mkarrer [~mkarrer@110.Red-88-1-124.dynamicIP.rima-tde.net] has quit []
09:31 -!- mkarrer [~mkarrer@110.Red-88-1-124.dynamicIP.rima-tde.net] has joined #bitcoin-wizards
09:33 -!- fuc [~fuc@ool-43571e2c.dyn.optonline.net] has joined #bitcoin-wizards
09:33 -!- fuc [~fuc@ool-43571e2c.dyn.optonline.net] has quit [Client Quit]
09:36 -!- MrHodl [~fuc@95.211.224.48] has quit [Ping timeout: 255 seconds]
09:36 -!- Quanttek [~quassel@ip1f11db5b.dynamic.kabel-deutschland.de] has quit [Ping timeout: 250 seconds]
09:39 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 260 seconds]
09:43 -!- yosso [~yosso@31.210.188.117] has joined #bitcoin-wizards
09:44 -!- yossso [~yosso@31.210.188.117] has joined #bitcoin-wizards
09:46 -!- JackH [~Jack@host-80-43-143-141.as13285.net] has joined #bitcoin-wizards
09:47 < yosso> http://bitcoil.co.il/files/Bitcoin_meetup_Chainless.pptx - Secure "chainless" protocols for Bitcoin by Aviv Zohar
09:50 -!- eudoxia [~eudoxia@r167-56-34-212.dialup.adsl.anteldata.net.uy] has joined #bitcoin-wizards
09:52 -!- Starduster [~SD@unaffiliated/starduster] has joined #bitcoin-wizards
09:53 -!- pozitron [nu@gateway/vpn/mullvad/x-hksklgjsebfpktti] has joined #bitcoin-wizards
09:59 < Taek> yosso: can you convert that to something other than .pptx? I can't open it
09:59 < Taek> pdf would be best
10:00 < yosso> not out yet afaik
10:01 < yosso> oh you mean the format
10:02 -!- Luke-Jr [~luke-jr@unaffiliated/luke-jr] has quit [Quit: Konversation terminated!]
10:03 -!- Luke-Jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-wizards
10:09 -!- dEBRUYNE [~dEBRUYNE@56-197-ftth.onsbrabantnet.nl] has quit [Quit: Leaving]
10:14 -!- Piper-Off is now known as Monthrect
10:18 -!- keus [~jussi@dsl-espbrasgw1-54fa72-192.dhcp.inet.fi] has joined #bitcoin-wizards
10:24 -!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has quit [Ping timeout: 240 seconds]
10:34 -!- chmod755 [~chmod755@unaffiliated/chmod755] has quit [Quit: Ex-Chat]
10:44 -!- jcorgan is now known as jcorgan|away
10:49 -!- belcher [~user@unaffiliated/belcher] has quit [Quit: Leaving]
10:49 -!- eragmus [~eragmus@c-73-150-48-166.hsd1.nj.comcast.net] has joined #bitcoin-wizards
10:59 -!- yossso [~yosso@31.210.188.117] has quit [Read error: Connection reset by peer]
11:01 -!- yosso [~yosso@31.210.188.117] has quit [Ping timeout: 276 seconds]
11:10 -!- paci [~paci@host41-233-static.58-79-b.business.telecomitalia.it] has quit [Ping timeout: 264 seconds]
11:14 -!- paci [~paci@host41-233-static.58-79-b.business.telecomitalia.it] has joined #bitcoin-wizards
11:14 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Ping timeout: 264 seconds]
11:28 -!- bramc [~bram@216.216.202.69] has joined #bitcoin-wizards
11:30 < bramc> bsm1175321, Yes I have very nice proof of non-inclusion proofs, that's been a big part of my iteration
11:32 < bramc> bsm1175321, My format is that each level of the tree is a hash of something describing what's immediately below it, a metadata byte followed by one or two hashes, as applicable.
11:33 < bramc> The possible values for metadata are passthrough 0, passthrough 1, terminate 0, terminate 1, terminate both, and both branches. passthrough means only one side has any values below it, the terminates indicate that one or both of the children immediately below are leaves. A leaf gets hashed one extra time at the beginning before being included in the descriptor of the immediate parent
11:34 -!- JackH [~Jack@host-80-43-143-141.as13285.net] has quit [Ping timeout: 250 seconds]
11:34 -!- hdbuck [~hdbuck@ATuileries-153-1-57-173.w83-202.abo.wanadoo.fr] has joined #bitcoin-wizards
11:34 -!- hdbuck [~hdbuck@ATuileries-153-1-57-173.w83-202.abo.wanadoo.fr] has quit [Changing host]
11:34 -!- hdbuck [~hdbuck@unaffiliated/hdbuck] has joined #bitcoin-wizards
11:34 < bramc> This way proofs of non-inclusion are very simple: You trace down to where the thing would be if it were in there, and hit a leaf of something different or a passthrough which goes only to the other side
11:38 < bramc> This is the reason for having passthroughs, even though they seem unnecessary at first. Proofs of non-inclusion get a lot gnarlier without them.
11:38 -!- eragmus1 [~eragmus@c-73-150-48-166.hsd1.nj.comcast.net] has joined #bitcoin-wizards
11:41 -!- frankenmint [~frankenmi@75-175-72-226.ptld.qwest.net] has quit [Remote host closed the connection]
11:41 -!- eragmus [~eragmus@c-73-150-48-166.hsd1.nj.comcast.net] has quit [Ping timeout: 264 seconds]
11:42 -!- frankenmint [~frankenmi@75-175-72-226.ptld.qwest.net] has joined #bitcoin-wizards
11:43 -!- RedEmerald [~RedEmeral@216.240.130.109] has quit [Ping timeout: 246 seconds]
11:44 < bramc> There's also a special metadata value for when there's only a single thing in the entire tree, and a special root value EMPTY for when there's nothing in it and hence nothing to be hashed.
11:48 < bramc> Good grief. Just my proof verification code is 250 lines. I'm hoping that's due to it being parsing code and the rest of this winds up being less voluminous.
11:49 -!- JackH [~Jack@host-80-43-143-141.as13285.net] has joined #bitcoin-wizards
11:50 < JackH> hi kanzure, did you manage to find more than 2 pages?
11:51 -!- RedEmerald [~RedEmeral@216.240.130.109] has joined #bitcoin-wizards
11:53 < kanzure> no
11:56 < JackH> everyone seems to refer back to https://www.docdroid.net/mR3fUNS/paper.pdf.html
11:56 < JackH> but there is no indication of how this appeared to begin with
11:59 < kanzure> someone with a blog claimed to be releasing a page per day
12:00 < JackH> I am looking at history now to see where this appeared first
12:02 < JackH> this constantly seems to be referred to: http://bitcoinnewschannel.com/2015/12/27/page-2-of-the-hash-tube-signature-scheme-credited-to-satoshi-nakamoto/
12:02 < JackH> as the original source
12:03 -!- CubicEarth [~cubiceart@174-25-59-127.ptld.qwest.net] has joined #bitcoin-wizards
12:04 < bramc> It obviously isn't by the original Satoshi. For starters, that paper isn't by a native english speaker.
12:05 -!- eudoxia [~eudoxia@r167-56-34-212.dialup.adsl.anteldata.net.uy] has quit [Quit: Leaving]
12:06 < JackH> true, first weird sentence is: of a cryptographic payments
12:07 -!- jcorgan|away is now known as jcorgan
12:11 < bramc> Up to the end of the paper all it's talking about is a new secure hash based signature scheme. The hash tube idea is cute but doesn't have any obvious benefit over a regular lamport signature. It is extremely fragile though, in that if you use it more than once you'll almost certainly have made it possible for other people to sign arbitrary things later, which  can be a useful property to have for some applications
12:12 < bramc> I came up with a cruder trick to do the same thing. The two techniques can be combined effecively.
12:12 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has quit [Ping timeout: 250 seconds]
12:13 < JackH> the paper lacks the rest of the pages
12:13 < JackH> to make its point
12:13 < JackH> I get where its going, but....I dont get what its all good for
12:14 < bramc> The abstract gives no hint whatsoever of how the new primitive is supposed to be useful
12:15 < bramc> It isn't even clear in what way it's new. Practical secure hash based signatures have been around for a while. The new construction makes winternitz compression impossible.
12:16 -!- pozitrono [~nu@46.166.190.200] has joined #bitcoin-wizards
12:17 < JackH> yeah this doesnt make sense, to what extend that it is useful
12:17 < JackH> it is neat, but what is the point
12:18 -!- pozitron [nu@gateway/vpn/mullvad/x-hksklgjsebfpktti] has quit [Ping timeout: 245 seconds]
12:19 < bramc> Well, I'll give it credit that it has a construction which tells me how to improve on something I spent time on before. Whether that trick is its point or a coincidental enabler is entirely unclear though.
12:20 < JackH> its being discussed in crypto:
12:20 < JackH> https://www.reddit.com/r/crypto/comments/3yhwwv/hash_tube_signature_scheme/
12:20 < JackH> constructing what? a private key?
12:22 < bramc> A signature scheme. You can use hash tubes to make it so that if someone signs more than one thing with a signature it blows up in their face horribly.
12:23 -!- eragmus1 [~eragmus@c-73-150-48-166.hsd1.nj.comcast.net] has quit [Read error: Connection reset by peer]
12:23 -!- eragmus [~eragmus@c-73-150-48-166.hsd1.nj.comcast.net] has joined #bitcoin-wizards
12:23 < bramc> Actually, this is probably what's meant by the comment about it providing defense against double-spends. Maybe I should post an explanation of this on reddit.
12:25 -!- eragmus1 [~eragmus@c-73-150-48-166.hsd1.nj.comcast.net] has joined #bitcoin-wizards
12:27 -!- eragmus [~eragmus@c-73-150-48-166.hsd1.nj.comcast.net] has quit [Ping timeout: 255 seconds]
12:29 -!- eragmus1 [~eragmus@c-73-150-48-166.hsd1.nj.comcast.net] has quit [Ping timeout: 250 seconds]
12:31 < JackH> would like to know how you come to this understanding
12:34 -!- Newyorkadam [~Newyorkad@wikipedia/Newyorkadam] has joined #bitcoin-wizards
12:34 < bramc> JackH, When people work on the same problems they tend to come up with the same solutions
12:35 < JackH> sure
12:35 < JackH> feel free to explain it then
12:36 < bramc> I'm typing something on reddit right now.
12:36 -!- CubicEarth [~cubiceart@174-25-59-127.ptld.qwest.net] has quit [Remote host closed the connection]
12:36 < bramc> I keep getting pulled into these interesting theoretical discussions when I'm trying to do Real Work
12:36 -!- eragmus [~eragmus@c-73-150-48-166.hsd1.nj.comcast.net] has joined #bitcoin-wizards
12:36 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #bitcoin-wizards
12:43 < JackH> it is frustrating we only have 2 pages
13:00 -!- zookolaptop [~user@68.233.157.2] has quit [Ping timeout: 245 seconds]
13:05 < bramc> JackH, https://www.reddit.com/r/crypto/comments/3yhwwv/hash_tube_signature_scheme/cye6k29
13:05 < bramc> Please tell me if I start sounding like Galois
13:09 -!- Tomiii [~Tommiii@199.58.81.144] has joined #bitcoin-wizards
13:11 -!- eragmus1 [~eragmus@c-73-150-48-166.hsd1.nj.comcast.net] has joined #bitcoin-wizards
13:13 -!- eragmus [~eragmus@c-73-150-48-166.hsd1.nj.comcast.net] has quit [Ping timeout: 260 seconds]
13:14 -!- eragmus1 [~eragmus@c-73-150-48-166.hsd1.nj.comcast.net] has quit [Client Quit]
13:16 < bramc> Feedback and upvotes welcome. That took a whole bunch of brain cycles I was planning on putting into real work.
13:17 -!- coinoperated [~coinopera@cpe-static-mountainintermodal-rtr.cmts.bus.ptd.net] has joined #bitcoin-wizards
13:17 -!- CubicEarth [~cubiceart@174-25-59-127.ptld.qwest.net] has joined #bitcoin-wizards
13:18 -!- ayn1k [uid136514@gateway/web/irccloud.com/x-erbfmgonfsivhmhc] has joined #bitcoin-wizards
13:23 -!- gielbier [~giel____@unaffiliated/gielbier] has quit [Read error: Connection reset by peer]
13:23 -!- gielbier [~giel____@a149043.upc-a.chello.nl] has joined #bitcoin-wizards
13:28 < bramc> It's getting both upvotes and downvotes now. Apparently my highly technical comments are horribly controversial.
13:28 < kanzure> you shouldn't watch the karma counter, you'll rot your brain like that
13:32 < bramc> Since I never post to reddit, it's new to me. It's fascinating that even this could produce downvotes. That seems to imply that there's a movement to downvote anything which isn't ranting drivel.
13:33 -!- gielbier [~giel____@a149043.upc-a.chello.nl] has quit [Read error: Connection reset by peer]
13:33 -!- giel__ [~giel____@a149043.upc-a.chello.nl] has joined #bitcoin-wizards
13:33 < kanzure> there are also bots that randomly downvote anything, because bot farmers need to make the accounts look alive and healthy
13:33 < kanzure> it's really completely meaningless
13:34 < jojva_> if you hit refresh several times you can see your karma changing in a meaningless way. it's just bot battles.
13:35 -!- CubicEarth [~cubiceart@174-25-59-127.ptld.qwest.net] has quit [Remote host closed the connection]
13:36 < ayn1k> reddit voting should make use of pow
13:36 < kanzure> no, pow does not decide factual correctness of statements, what
13:37 < ayn1k> no, voting does that, and pow prevents a large chunk of spam votes
13:37 < jojva_> for that you need a decentralized reputation system :)
13:37 -!- laurentmt [~Thunderbi@213-245-86-6.rev.numericable.fr] has joined #bitcoin-wizards
13:37 -!- laurentmt [~Thunderbi@213-245-86-6.rev.numericable.fr] has quit [Client Quit]
13:38 -!- zookolaptop [~user@68.233.157.2] has joined #bitcoin-wizards
13:38 < kanzure> "spam votes" are doable with pow (e.g. see how trivial it is to make low-difficulty pow proofs)
13:39 < ayn1k> pow proofs is redundant but anyway, who said low-difficulty
13:41 < ayn1k> reddit as a centralized service can vary the hashing algorithm parameters quite fast and prevent optimizations
13:41 < jojva_> what the hell is that? https://github.com/kanzure/streak
13:45 < kanzure> jojva_: i think https://github.com/kanzure/nanoengineer is more interesting
13:46 < ayn1k> looks like a dead man switch
13:47 < coinoperated> bramc a certain fixed component of u/dvote probability on reddit (in anything bitcoin related) is based on whether your post could be construed (if grossly inapplicably) as being on one side or the other of the block size issue.  Just disregard.
13:47 < jojva_> kanzure: that's beautifuk
13:48 < jojva_> s/beautifuk/beautiful
13:49 < coinoperated> If you like chocolate ice cream, don't say so unless you're sure someone from the "wrong" side of that debate doesn't also like it
13:49 -!- rustyn [~rustyn@unaffiliated/rustyn] has quit [Read error: Connection reset by peer]
13:50 -!- rustyn [~rustyn@unaffiliated/rustyn] has joined #bitcoin-wizards
13:52 -!- Guest1038 [~socrates1@li175-104.members.linode.com] has quit [Changing host]
13:52 -!- Guest1038 [~socrates1@unaffiliated/socrates1024] has joined #bitcoin-wizards
13:52 -!- Guest1038 is now known as amiller
13:54 < bramc> This is very frustrating: https://medium.com/@sleevi_/a-history-of-hard-choices-c1e1cc9bb089#.ws4sf8zwp
13:55 < bramc> There's this big point which people at the standards bodies seem to just plain not understand, which is that the current attacks on sha1 put it in danger of *collision* attacks, where the relevant attack for browsers is *reversal*
13:56 < bramc> Those are from completely different galaxies in terms of difficulty. It saddens me that there's no discussion of sha3 though, apparently that standard has mostly failed?
14:02 < gwillen> bramc: well, the usual cryptographic safety rule, in my understanding, is that once your primitive is a little bit compromised, you start moving off it, even if it's probably still fine, because cryptanalysis only moves one way
14:04 -!- zookolaptop [~user@68.233.157.2] has quit [Ping timeout: 246 seconds]
14:04 < phantomcircuit> bramc, uh collision is sufficient to cause big problems
14:06 < bramc> gwillen, True, although in this case there's coherent practical reason for foot-dragging
14:06 < bramc> phantomcircuit, What are the relevant collision-based attacks? I'm not asking this sarcastically.
14:06 < gwillen> also phantomcircuit makes a good point, collision is enough to create fraudulent certificates
14:06 < gwillen> all you have to do is generate two colliding certs, one valid, one invalid
14:07 < gwillen> and then you have a signature good for the invalid one
14:08 -!- MrHodl [~fuc@91.210.105.101] has joined #bitcoin-wizards
14:08 < bramc> It boils down to whether the certificate is generated by the CA or whoever it's being given to. If CAs do the writing of certs, or at least put a bunch of random garbage at the front, then I think it's reversals which are relevant.
14:09 < phantomcircuit> bramc, sure but they dont do that in practice
14:09 < gwillen> the random garbage trick is not a general solution to collision attacks, it only works against a specific type, afaik
14:09 < gwillen> although that may be the only type currently practical, I don't know
14:09 < phantomcircuit> the ca extracts the public key from the crl and then produces an entirely predictable certificate from that
14:09 < phantomcircuit> gwillen, it's usually a reasonable way to shift from preimage to second preimage which is much much harder
14:10 < bramc> phantomcircuit, *sigh* I think that article I linked says things which amount to 'Microsoft said to put a few bytes of random garbage at the top but not all CAs are doing it'
14:10 < phantomcircuit> bramc, iirc the md5 intermediate cert was generated using a preimage attack by messing with the subdomain the cert was for
14:12 < bramc> If the certificate is entirely predictable then you can do a birthday attack on it. If it isn't then you're stuck with reversals.
14:13 -!- brg444 [18257df2@gateway/web/freenode/ip.24.37.125.242] has quit [Quit: Page closed]
14:14 -!- bramc [~bram@216.216.202.69] has quit [Quit: This computer has gone to sleep]
14:16 -!- zookolaptop [~user@68.233.157.2] has joined #bitcoin-wizards
14:20 -!- JackH [~Jack@host-80-43-143-141.as13285.net] has quit [Ping timeout: 272 seconds]
14:27  * zookolaptop looks at https://www.docdroid.net/mR3fUNS/paper.pdf.html
14:29 < zookolaptop> I wish whoever wrote that had used proper citations.
14:29 < gwillen> I feel like I should ignore this paper just to avoid encouraging people to publish further under that name :-P
14:30 < gwillen> it's a bizzare sort of self-promotion
14:30 < zookolaptop> Then it would be obvious to all readers that when they wrote "Weierstrass" they meant "Winternitz", for starters.
14:30 -!- throughnothing [~throughno@c-71-204-189-125.hsd1.ca.comcast.net] has joined #bitcoin-wizards
14:30 < zookolaptop> Now there will be a little mini-generation of people who've heard of Winternitz, but since they know it under the wrong name they won't be able to look it up in the literature...
14:32 < gwillen> heh
14:43 -!- Quanttek [~quassel@ip1f11db5b.dynamic.kabel-deutschland.de] has joined #bitcoin-wizards
14:49 -!- tulip [~tulip@unaffiliated/tulip] has joined #bitcoin-wizards
14:52 < tulip> "reddit as a centralized service can vary the hashing algorithm parameters quite fast and prevent optimizations"
14:54 < tulip> ayn1k: just in general, proof of work is broken when used in isolation. no matter the configuration there's none which has a usable end experience for real users, and actually provide any resistance to a person with a botnet.
14:54 -!- c-cex-finch [uid120855@gateway/web/irccloud.com/x-lhcjulyppgiogdzz] has quit [Quit: Connection closed for inactivity]
14:56 < tulip> you made your proof of work take 10 minutes to create a reddit post? well that's completely unacceptable for an end user, yet someone with a botnet can blast out tens of thousands of messages an hour. changing the system doesn't prevent that.
14:58 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has quit [Ping timeout: 260 seconds]
14:59 -!- Quanttek [~quassel@ip1f11db5b.dynamic.kabel-deutschland.de] has quit [Ping timeout: 246 seconds]
15:00 -!- psztorc [4575fa8d@gateway/web/freenode/ip.69.117.250.141] has joined #bitcoin-wizards
15:01 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #bitcoin-wizards
15:09 -!- tripleslash_a [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-wizards
15:11 -!- tripleslash_t [~triplesla@unaffiliated/imsaguy] has quit [Ping timeout: 260 seconds]
15:13 -!- coinoperated [~coinopera@cpe-static-mountainintermodal-rtr.cmts.bus.ptd.net] has quit [Ping timeout: 260 seconds]
15:14 -!- frankenmint [~frankenmi@75-175-72-226.ptld.qwest.net] has quit [Remote host closed the connection]
15:20 -!- bramc [~bram@216.216.202.69] has joined #bitcoin-wizards
15:27 -!- Newyorkadam [~Newyorkad@wikipedia/Newyorkadam] has quit [Quit: Newyorkadam]
15:30 < ayn1k> tulip: it should be combined with interaction speed limits, per subreddit and user, for voting and posting
15:31 < tulip> if you're using metrics like that the proof of work doesn't do anything but annoy your users.
15:31 -!- brg444 [415ce066@gateway/web/freenode/ip.65.92.224.102] has joined #bitcoin-wizards
15:31 < ayn1k> if many posts are created per minute in the same subreddit then they start with a lower score, if a user receives many votes per minute then the amount of karma he receives/loses is of lower value
15:32 < tulip> so anybody wanting to warp the score just does it slowly?
15:33 < ayn1k> if you post slowly your posts start with a higher score
15:35 -!- Newyorkadam [~Newyorkad@wikipedia/Newyorkadam] has joined #bitcoin-wizards
15:36 < ayn1k> pow sets a cost for sybil attacks while degradation on speed prevents brigading
15:42 -!- smk [2ea6bec8@gateway/web/freenode/ip.46.166.190.200] has joined #bitcoin-wizards
15:43 -!- CubicEar_ [~cubiceart@2600:100f:b123:7bc7:f846:4659:6fad:7b9d] has joined #bitcoin-wizards
15:46 < bramc> The applicable proof of 'work' to reddit is captchas
15:46 < kanzure> captchas are trivially solved by machines and also by services like deathbycaptcha (captcha solving api that uses outsourcing)
15:47 < bramc> I didn't say they're much better
15:52 < ayn1k> also captchas can't be tuned for difficulty (or at least not very smooth)
15:52 -!- Newyorkadam [~Newyorkad@wikipedia/Newyorkadam] has quit [Quit: Newyorkadam]
15:54 -!- smk [2ea6bec8@gateway/web/freenode/ip.46.166.190.200] has quit [Ping timeout: 252 seconds]
15:54 -!- Newyorkadam [~Newyorkad@wikipedia/Newyorkadam] has joined #bitcoin-wizards
15:56 -!- CubicEar_ [~cubiceart@2600:100f:b123:7bc7:f846:4659:6fad:7b9d] has quit [Remote host closed the connection]
15:57 -!- Newyorkadam [~Newyorkad@wikipedia/Newyorkadam] has quit [Client Quit]
16:10 -!- hsmiths__ [uid95325@gateway/web/irccloud.com/x-ourirjnhbataaesv] has joined #bitcoin-wizards
16:10 -!- c0rw|zZz [~c0rw1n@91.176.76.47] has quit [Read error: Connection reset by peer]
16:11 -!- c0rw|zZz_ [~c0rw1n@91.176.76.47] has joined #bitcoin-wizards
16:13 -!- Dizzle [~Dizzle@12.130.116.193] has joined #bitcoin-wizards
16:15 -!- hashtag [~hashtag@cpe-174-97-254-80.ma.res.rr.com] has quit [Read error: Connection reset by peer]
16:16 -!- Guyver2 [~Guyver2@a80-100-156-239.adsl.xs4all.nl] has quit [Read error: Connection reset by peer]
16:17 < bramc> phantomcircuit, I'm not going to get 100% code coverage of every branch where an integrity check fails in my tests. I hope you understand.
16:18 < bramc> Done rewriting get_root(). That was only 80 lines of code for today. Time to call it a day.
16:20 -!- bramc [~bram@216.216.202.69] has quit [Quit: This computer has gone to sleep]
16:28 -!- Monthrect is now known as Piper-Off
16:28 -!- pozitrono [~nu@46.166.190.200] has quit [Ping timeout: 250 seconds]
16:30 < kanzure> some commentary about fraud proofs and non-fraud proofs of correctness and segwit https://botbot.me/freenode/bitcoin-core-dev/2015-12-28/?msg=56907496&page=2
16:30 < kanzure> aww bramc already left
16:32 -!- hashtag [~hashtag@cpe-174-97-254-80.ma.res.rr.com] has joined #bitcoin-wizards
16:34 -!- belcher [~user@unaffiliated/belcher] has joined #bitcoin-wizards
16:37 -!- ghtdak [~ghtdak@unaffiliated/ghtdak] has quit [Quit: WeeChat 1.4-dev]
16:38 -!- ghtdak [~ghtdak@unaffiliated/ghtdak] has joined #bitcoin-wizards
16:38 -!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has joined #bitcoin-wizards
16:44 -!- CubicEarth [~cubiceart@c-67-168-82-178.hsd1.wa.comcast.net] has joined #bitcoin-wizards
16:48 -!- pozitron [~nu@45.32.232.26] has joined #bitcoin-wizards
17:08 -!- frankenmint [~frankenmi@75-175-72-226.ptld.qwest.net] has joined #bitcoin-wizards
17:18 -!- JackH [~Jack@host-80-43-143-141.as13285.net] has joined #bitcoin-wizards
17:19 -!- hdbuck [~hdbuck@unaffiliated/hdbuck] has quit [Quit: hdbuck]
17:24 < brg444> https://21.co/apidocs/21-lib-blockchain/
17:24 < brg444> 21 starting to release doc
17:30 -!- adam3us [~Adium@host-92-18-110-107.as13285.net] has quit [Read error: Connection reset by peer]
17:30 -!- adam3us [~Adium@host-92-18-110-107.as13285.net] has joined #bitcoin-wizards
17:36 -!- wallet42 [~wallet42@n182z59l6.static.ctm.net] has joined #bitcoin-wizards
17:44 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-ixhmdkwzlfrtqnnt] has quit [Quit: Connection closed for inactivity]
17:48 -!- coinoperated [~coinopera@70.15.164.106.res-cmts.t132.ptd.net] has joined #bitcoin-wizards
17:54 -!- NewLiberty [~NewLibert@2602:306:b8e0:8160:3d12:d5d5:eee9:519b] has joined #bitcoin-wizards
17:57 < phantomcircuit> petertodd, i hadn't seen that before, it's a strong point
17:57 < phantomcircuit> (from the logs kanzure posted)
17:58 -!- zookolaptop [~user@68.233.157.2] has quit [Remote host closed the connection]
17:58 -!- zookolaptop [~user@68.233.157.2] has joined #bitcoin-wizards
17:59 -!- raver_edm [~vegas_nig@2602:306:b8e0:8160:c1b3:84f5:2321:86b7] has joined #bitcoin-wizards
17:59 -!- bramc [~bram@99-75-88-206.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-wizards
18:01 -!- wallet421 [~wallet42@nz112l11.bb11352.ctm.net] has joined #bitcoin-wizards
18:01 -!- wallet421 [~wallet42@nz112l11.bb11352.ctm.net] has quit [Changing host]
18:01 -!- wallet421 [~wallet42@unaffiliated/wallet42] has joined #bitcoin-wizards
18:01 -!- wallet42 is now known as Guest26426
18:01 -!- Guest26426 [~wallet42@n182z59l6.static.ctm.net] has quit [Killed (tepper.freenode.net (Nickname regained by services))]
18:01 -!- wallet421 is now known as wallet42
18:02 < bramc> kanzure, A fascinating thing about ZK is that it allows for very compact and quick to check proofs of non-fraud. That's all academic for the time being though. Right now the relevant thing for what I'm working on is compact proofs of inclusion and exclusion for the set.
18:03 < bramc> And there's always the problem of invalidity that something can be technically valid but no longer because some of the data it refers to has become lost forever
18:03 < kanzure> the conversation in those logs was because of a proposal by petertodd to make a small change to make some of those proofs easier in the near future
18:03 < kanzure> you probably did not see his email about this topic, let me dig up a link
18:04 < bramc> In sipa's segwit design proofs of fraud of fees are much simpler because each node in the tree includes a fee amount
18:05 < kanzure> weird, i can't find the email.
18:06 < kanzure> ah, it's this one: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/012103.html
18:06 < kanzure> i guess skip to the end section about proofs
18:08 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-wizards
18:08 < kanzure> fraud proof stuff was also recently mentioned by jl2012 and others in http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/011935.html and http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/011961.html
18:09 -!- frankenmint [~frankenmi@75-175-72-226.ptld.qwest.net] has quit [Remote host closed the connection]
18:09 < bramc> kanzure, Oh yes I saw that. I don't like it as a solution. It adds a bunch of technical gunk which may not work so well to try and disincentivize validationless mining, when what's really needed is a bunch of work to remove the disincentives from validation, mostly around latency and validation time. Those are things we're working on already.
18:13 < bramc> In fact it may make validation time worse. Either the re-hashing is of just the witness root, which is a trivial thing to communicate without also sending the complete set of witness data, or you have to hash over all the witness data, which obviously increases latency and costs of validation, or you check a sample of witness data, which sort of works but yech.
18:18 -!- hsmiths__ [uid95325@gateway/web/irccloud.com/x-ourirjnhbataaesv] has quit [Quit: Connection closed for inactivity]
18:21 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has quit [Ping timeout: 260 seconds]
18:22 -!- brg444 [415ce066@gateway/web/freenode/ip.65.92.224.102] has quit [Ping timeout: 252 seconds]
18:27 -!- justanot1eruser [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-wizards
18:27 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Read error: Connection reset by peer]
18:33 -!- coinoperated [~coinopera@70.15.164.106.res-cmts.t132.ptd.net] has quit [Ping timeout: 276 seconds]
18:41 -!- brg444 [415ce066@gateway/web/freenode/ip.65.92.224.102] has joined #bitcoin-wizards
18:41 -!- CubicEarth [~cubiceart@c-67-168-82-178.hsd1.wa.comcast.net] has quit [Remote host closed the connection]
18:42 -!- frankenmint [~frankenmi@75-175-72-226.ptld.qwest.net] has joined #bitcoin-wizards
18:49 -!- justanot1eruser is now known as justanotheruser
18:52 -!- CubicEarth [~cubiceart@c-67-168-82-178.hsd1.wa.comcast.net] has joined #bitcoin-wizards
18:58 -!- Giszmo [~leo@pc-139-55-215-201.cm.vtr.net] has quit [Ping timeout: 240 seconds]
19:03 -!- smk [6dc99ac0@gateway/web/freenode/ip.109.201.154.192] has joined #bitcoin-wizards
19:04 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has quit [Quit: GGuyZ]
19:06 -!- Tiraspol [~Tiraspol3@unaffiliated/tiraspol] has quit []
19:09 < kanzure> psztorc: i am wondering if you could elaboate on "In a complex system, it is logically defensible to say “I don’t know what the rule is for, but we should keep it right where it is anyway.” In fact, civilization practically depends on this (namely, our laws)."
19:09 < kanzure> perhaps with something other than laws
19:14 -!- Giszmo [~leo@ip-61-226-107-190.nextelmovil.cl] has joined #bitcoin-wizards
19:17 -!- Alopex [~bitcoin@guru.dealing.ninja] has joined #bitcoin-wizards
19:18 -!- Alopex [~bitcoin@guru.dealing.ninja] has quit [Excess Flood]
19:18 -!- Dizzle [~Dizzle@12.130.116.193] has quit [Remote host closed the connection]
19:23 -!- Alopex [~bitcoin@guru.dealing.ninja] has joined #bitcoin-wizards
19:24 -!- Alopex [~bitcoin@guru.dealing.ninja] has quit [Read error: Connection reset by peer]
19:25 -!- Burrito [~Burrito@unaffiliated/burrito] has quit [Quit: Leaving]
19:25 -!- JackH [~Jack@host-80-43-143-141.as13285.net] has quit [Ping timeout: 265 seconds]
19:26 -!- Alopex [~bitcoin@guru.dealing.ninja] has joined #bitcoin-wizards
19:26 -!- Tomiii [~Tommiii@199.58.81.144] has quit [Quit: Tomiii]
19:26 -!- Alopex [~bitcoin@guru.dealing.ninja] has quit [Remote host closed the connection]
19:31 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #bitcoin-wizards
19:33 -!- Alopex [~bitcoin@guru.dealing.ninja] has joined #bitcoin-wizards
19:33 -!- Alopex [~bitcoin@guru.dealing.ninja] has quit [Remote host closed the connection]
19:33 -!- Transisto2 [~Trans@modemcable082.143-161-184.mc.videotron.ca] has joined #bitcoin-wizards
19:33 -!- Tiraspol [~Tiraspol3@c-98-212-187-224.hsd1.il.comcast.net] has joined #bitcoin-wizards
19:33 -!- Tiraspol [~Tiraspol3@c-98-212-187-224.hsd1.il.comcast.net] has quit [Changing host]
19:33 -!- Tiraspol [~Tiraspol3@unaffiliated/tiraspol] has joined #bitcoin-wizards
19:34 -!- c-cex-yuriy [uid76808@gateway/web/irccloud.com/x-fukvckzdkukjabwh] has joined #bitcoin-wizards
19:35 -!- Alopex [~bitcoin@guru.dealing.ninja] has joined #bitcoin-wizards
19:35 -!- Alopex [~bitcoin@guru.dealing.ninja] has quit [Remote host closed the connection]
19:40 -!- Alopex [~bitcoin@guru.dealing.ninja] has joined #bitcoin-wizards
19:41 -!- Alopex [~bitcoin@guru.dealing.ninja] has quit [Remote host closed the connection]
19:42 -!- tulip [~tulip@unaffiliated/tulip] has quit [Quit: Textual IRC Client: www.textualapp.com]
19:43 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #bitcoin-wizards
19:43 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has joined #bitcoin-wizards
19:44 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has left #bitcoin-wizards []
19:44 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has joined #bitcoin-wizards
19:44 -!- GGuyZ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has left #bitcoin-wizards []
19:45 -!- Alopex [~bitcoin@guru.dealing.ninja] has joined #bitcoin-wizards
19:53 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has quit [Ping timeout: 260 seconds]
20:06 -!- smk [6dc99ac0@gateway/web/freenode/ip.109.201.154.192] has quit [Ping timeout: 252 seconds]
20:14 -!- belcher [~user@unaffiliated/belcher] has quit [Quit: Leaving]
20:14 -!- funkenstein_ [~bowler@unaffiliated/funkenstein] has joined #bitcoin-wizards
20:16 -!- RedEmerald [~RedEmeral@216.240.130.109] has quit [Ping timeout: 265 seconds]
20:19 -!- raver_edm [~vegas_nig@2602:306:b8e0:8160:c1b3:84f5:2321:86b7] has quit [Quit: Leaving]
20:21 -!- justanotheruser is now known as gentoognuhurd
20:22 -!- brg444 [415ce066@gateway/web/freenode/ip.65.92.224.102] has quit [Quit: Page closed]
20:29 -!- RedEmerald [~RedEmeral@216.240.130.109] has joined #bitcoin-wizards
20:36 -!- TheSeven [~quassel@rockbox/developer/TheSeven] has quit [Ping timeout: 260 seconds]
20:36 -!- arowser [~quassel@106.120.101.38] has quit [Quit: No Ping reply in 180 seconds.]
20:37 -!- arowser [~quassel@106.120.101.38] has joined #bitcoin-wizards
20:37 -!- TheSeven [~quassel@rockbox/developer/TheSeven] has joined #bitcoin-wizards
20:40 -!- alpalp [~alp@104-54-235-28.lightspeed.austtx.sbcglobal.net] has quit [Read error: Connection reset by peer]
20:40 < petertodd> bramc: why do you think it's possible to reduce latency? no-one has ever come up with a way to reduce worst-case bandwidth driven latency with anything similar to the current design of bitcoin
20:42 -!- alpalp [~alp@104-54-235-28.lightspeed.austtx.sbcglobal.net] has joined #bitcoin-wizards
20:42 < petertodd> bramc: equally, validation driven latency is mostly a non-issue - validation is parallelizable fairly easy, and there's nothing wrong with propagating non-validated data
20:46 -!- wallet42 [~wallet42@unaffiliated/wallet42] has quit [Read error: Connection reset by peer]
20:47 -!- coinoperated [~coinopera@70.15.164.106.res-cmts.t132.ptd.net] has joined #bitcoin-wizards
20:55 -!- wallet42 [~wallet42@n182z59l6.static.ctm.net] has joined #bitcoin-wizards
20:57 -!- wallet42 [~wallet42@n182z59l6.static.ctm.net] has quit [Client Quit]
20:57 -!- wallet42 [~wallet42@n182z59l6.static.ctm.net] has joined #bitcoin-wizards
20:57 -!- wallet42 [~wallet42@n182z59l6.static.ctm.net] has quit [Client Quit]
20:58 < bramc> petertodd, The main thing necessary for reducing latency (and by this I mean making miners able to ensure that their blocks don't get orphaned) is for there to be ways to make sure that a block is only a tiny marginal amount of data on top of what's already widely propagated. Weak blocks basically fix that problem.
20:59 < petertodd> bramc: weak blocks are an average case fix, not a worst-case fix, and they probably disadvantage smaller miners too
21:02 < bramc> petertodd, Huh? In the 'aggressive' case, a weak block only has a 'hard' dependency on a previous weak block's 'weak' reference, so the amount of data needed to propagate it is less than 1k
21:02 < bramc> I mean, a successful block only has those dependencies.
21:03 < petertodd> bramc: remember that broadcasting weak blocks is optional
21:03 < petertodd> bramc: you find the most blocks relative to your competitors if less than 100% of the hashing power receives your block in time, with the threshold being at about 33%
21:03 -!- GGuyZ_ [~GGuyZ@216-15-125-203.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com] has joined #bitcoin-wizards
21:03 -!- GGuyZ_ is now known as GGuyZ
21:03 -!- p15 [~p15@42.91.145.64.client.static.strong-tk2.bringover.net] has joined #bitcoin-wizards
21:05 < bramc> petertodd, That's an unfortunate problem which I don't have any good answers to.
21:05 < petertodd> bramc: the best answer I have is keep the blocksize small enough that it's not a significant problem - that's just a hard constraint on our design until we come up with better protocols that actually fix it
21:06 < bramc> How is that a fix if weak blocks aren't?
21:08 < petertodd> bramc: weak blocks are a perfectly good average case optimization, but they can't be used to justify a blocksize increase
21:09 < bramc> petertodd, I'm not advocating a blocksize increase. Well, not past the < 2x from segwit
21:10 -!- NewLiberty [~NewLibert@2602:306:b8e0:8160:3d12:d5d5:eee9:519b] has quit [Ping timeout: 250 seconds]
21:10 < petertodd> bramc: sure - so you agree with me that weak blocks aren't a worst-case optimization?
21:11 < petertodd> bramc: er, wordedbetter, you agree with me that weak blocks don't improve worst-case, non-cooperating, block propagation?
21:11 -!- tulip [~tulip@unaffiliated/tulip] has joined #bitcoin-wizards
21:11 < bramc> Define 'non-cooperating'
21:11 < petertodd> bramc: e.g. if I decide I'll optimize for less than 100% propagation
21:13 < bramc> petertodd, If you want to optimize for less than 100% propagation you can do that just by waiting on sending out the block you found.
21:15 < petertodd> bramc: I'm better off doing it by selectively not propagating, to push out my highest latency competitors - just waiting harms them all equally, which isn't as useful
21:15 < petertodd> bramc: equally, if I'm just being lazy, and my weak block setup isn't working well for whatever reason
21:16 < bramc> petertodd, I'm hazy on the argument here. You seem to be saying that if there are weak blocks it's worthwile for one miner to make their blocks go out as slow as possible. Won't that just increase their own orphan rate and hurt them?
21:17 < petertodd> bramc: see http://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg03200.html
21:18 < petertodd> bramc: you just need to get your blocks to >29.2% of hashing power to optimize ratio of blocks you find vs. blocks they find
21:19 -!- brianhoffman [~brianhoff@pool-173-79-161-229.washdc.fios.verizon.net] has joined #bitcoin-wizards
21:19 < bramc> petertodd, I heard this argument before but haven't fully grokked it yet. If I assume what you say is true, then the problem is that each miner is under some scenarios incented to make their blocks go out slower, and the protocol's job is to make them go out fast even when whoever minted the block is trying to make it go out slow?
21:20 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 245 seconds]
21:20 < petertodd> bramc: exactly, 
21:22 < petertodd> bramc: really, we need to be in a situation where once you broadcast your block to anyone at all, it's guaranteed to get to everyone in negligable time
21:23 < bramc> The problems with quadratic hashing on single large transactions are also a big deal in that case
21:23 < petertodd> bramc: of course it is, fortunately fixing that is fairly uncontroversial - why I haven't (publicly) madea big deal about it
21:24 < petertodd> bramc: it's the bandwidth cost that is the fundemental problem
21:24 < bramc> What is the uncontroversial fix to the quadratic hashing problem?
21:24 -!- PRab [~chatzilla@c-68-34-102-231.hsd1.mi.comcast.net] has quit [Quit: ChatZilla 0.9.92 [Firefox 43.0.1/20151216175450]]
21:25 < petertodd> bramc: limiting tx size isn't such a big deal
21:25 -!- PRab [~chatzilla@c-68-34-102-231.hsd1.mi.comcast.net] has joined #bitcoin-wizards
21:25 < petertodd> bramc: equally, can change the sighash algorithm
21:26 < bramc> Allowing transactions to be included in a block in an arbitrary order is also a serious issue. There's a fair amount of meaningless information encoded in there which has to be broadcast
21:26 < petertodd> bramc: for instance, can make CHECKSIG error out if tx size >100KB, and then soft-fork in a better CHECKSIG later that doesn't havethe issue
21:27 < petertodd> bramc: why is order relevant to worstcase?
21:28 < bramc> Come to think of it, the attack here is that miner might fill their block with garbage transactions which nobody has seen before. Since transaction fees are currently de minimis they wouldn't be losing out on anything that way
21:28 < kanzure> btw i'm not sure petertodd has context about your merkle tree stuff
21:28 -!- funkenstein_ [~bowler@unaffiliated/funkenstein] has quit [Quit: Leaving]
21:28 < kanzure> (well, he has context, but probably not knowledge of your details in particular)
21:29 -!- CubicEarth [~cubiceart@c-67-168-82-178.hsd1.wa.comcast.net] has quit [Remote host closed the connection]
21:29 < bramc> kanzure, I don't think it matters for what we're discussing now
21:30 < bramc> Historically miners have been worried about the opposite problem: They freak out when their blocks get orphaned, and they've done everything in their power to avoid that, including publishing empty transactions
21:32 < petertodd> bramc: yes, that's exactly what the attack is - I've been saying that for literally years now :)
21:32 < petertodd> bramc: although,it's even worse because this *effect* can happen without actual malice
21:33 < petertodd> bramc: miners worry about the opposite because currently they're not acting entirely economically rationally
21:33 -!- CubicEarth [~cubiceart@c-67-168-82-178.hsd1.wa.comcast.net] has joined #bitcoin-wizards
21:33 < petertodd> bramc: I mean, heck, miners in china even go as far as to loan hashing power to each other w/o payment so...
21:35 < tulip> it's curious how trusty mining has become, people actually get concerned when there's blocks mined which don't have a publicly visible claim in the coinbase transaction as to who mined it.
21:36 -!- NewLiberty [~NewLibert@2602:306:b8e0:8160:b8e2:1c9c:fe32:8ba2] has joined #bitcoin-wizards
21:37 < bramc> petertodd, I think your analysis is correct but it doesn't carry over to when there are only intermittent potential orphans, it has to be a sustained thing. I'll work on it later when I'm more awake and present when I think I have a coherent argument though.
21:37 < petertodd> bramc: why does intermittancy change the analysis?
21:37 < tulip> it's probably ingrained enough that if anybody did mine blocks specifically defrauding other people, the blame would be instantly attributed to whoever was supposed to have mined it.
21:38 < petertodd> tulip: if I had hashing power, I'd put someone else's pool in my coinbase and mine RBF :)
21:39 -!- CubicEarth [~cubiceart@c-67-168-82-178.hsd1.wa.comcast.net] has quit [Read error: Connection timed out]
21:39 < coinoperated> there was a post on reddit a week ago by (someone who claimed to be) a large scale miner, to the effect that they all talk to one another these days and don't undertake any significant decisions individually without running the idea past the rest of the G-9
21:39 < bramc> petertodd, Because your potential for slowing everybody down is much when it's intermittent. I should be able to support this argument with some simple math though, so I'll hold off on making a strong claim until I work out the details. I'm a little wiped from doing too much coding at this point today so I'll sleep on it and slog through everything later.
21:39 < petertodd> coinoperated: that's probably correct, although remember that's a very situationally dependent phenomenomin...
21:39 -!- CubicEarth [~cubiceart@c-67-168-82-178.hsd1.wa.comcast.net] has joined #bitcoin-wizards
21:39 -!- brianhoffman [~brianhoff@pool-173-79-161-229.washdc.fios.verizon.net] has quit [Ping timeout: 256 seconds]
21:40 < petertodd> bramc: cool, looking forward to hearing about it
21:40 < tulip> wonder what would happen if large pools broke that cartel and started not re-using addresses.
21:40 < bramc> petertodd, I'll let you know whatever the expanded model indicates
21:42 < bramc> There's a weird thing about distribution of mining power. If you have a small number of miners they can have a gentleman's agreement not to try to re-mine bogon fees. With very distributed mining power attempts to re-mine bogon will fail in practice. Somewhere in the middle is a level of distribution where bogon fees make the system melt.
21:42 -!- CubicEarth [~cubiceart@c-67-168-82-178.hsd1.wa.comcast.net] has quit [Remote host closed the connection]
21:47 -!- Giszmo [~leo@ip-61-226-107-190.nextelmovil.cl] has quit [Quit: Leaving.]
21:47 -!- brianhoffman [~brianhoff@mobile-166-171-057-055.mycingular.net] has joined #bitcoin-wizards
21:52 -!- tulip [~tulip@unaffiliated/tulip] has quit [Quit: Textual IRC Client: www.textualapp.com]
21:52 -!- wallet42 [~wallet42@n182z59l6.static.ctm.net] has joined #bitcoin-wizards
21:54 -!- brianhoffman [~brianhoff@mobile-166-171-057-055.mycingular.net] has quit [Ping timeout: 260 seconds]
22:00 -!- frankenmint [~frankenmi@75-175-72-226.ptld.qwest.net] has quit [Remote host closed the connection]
22:01 -!- Yoghur114 [~Yoghurt11@131.224.198.111] has quit [Ping timeout: 272 seconds]
22:01 -!- Yoghur114 [~Yoghurt11@131.224.198.111] has joined #bitcoin-wizards
22:06 -!- CubicEarth [~cubiceart@c-67-168-82-178.hsd1.wa.comcast.net] has joined #bitcoin-wizards
22:06 -!- wallet421 [~wallet42@nz112l15.bb11352.ctm.net] has joined #bitcoin-wizards
22:06 -!- wallet421 [~wallet42@nz112l15.bb11352.ctm.net] has quit [Changing host]
22:06 -!- wallet421 [~wallet42@unaffiliated/wallet42] has joined #bitcoin-wizards
22:06 -!- wallet42 [~wallet42@n182z59l6.static.ctm.net] has quit [Killed (weber.freenode.net (Nickname regained by services))]
22:06 -!- wallet421 is now known as wallet42
22:13 -!- chjj [~chjj@unaffiliated/chjj] has quit [Quit: null]
22:13 -!- Transisto2 [~Trans@modemcable082.143-161-184.mc.videotron.ca] has quit []
22:15 -!- wallet42 [~wallet42@unaffiliated/wallet42] has quit [Read error: Connection reset by peer]
22:17 -!- frankenmint [~frankenmi@75-175-72-226.ptld.qwest.net] has joined #bitcoin-wizards
22:18 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-wizards
22:18 -!- rustyn [~rustyn@unaffiliated/rustyn] has quit [Read error: Connection reset by peer]
22:19 -!- rustyn [~rustyn@unaffiliated/rustyn] has joined #bitcoin-wizards
22:21 -!- Transisto2 [~Trans@modemcable082.143-161-184.mc.videotron.ca] has joined #bitcoin-wizards
22:30 -!- frankenmint [~frankenmi@75-175-72-226.ptld.qwest.net] has quit [Remote host closed the connection]
22:32 -!- frankenmint [~frankenmi@75-175-72-226.ptld.qwest.net] has joined #bitcoin-wizards
22:36 -!- CubicEarth [~cubiceart@c-67-168-82-178.hsd1.wa.comcast.net] has quit [Remote host closed the connection]
22:41 -!- c-cex-yuriy [uid76808@gateway/web/irccloud.com/x-fukvckzdkukjabwh] has quit [Quit: Connection closed for inactivity]
22:44 -!- Yoghur114 [~Yoghurt11@131.224.198.111] has quit [Ping timeout: 260 seconds]
22:44 -!- Yoghur114 [~Yoghurt11@131.224.198.111] has joined #bitcoin-wizards
22:55 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has joined #bitcoin-wizards
23:07 -!- bramc [~bram@99-75-88-206.lightspeed.sntcca.sbcglobal.net] has quit [Quit: This computer has gone to sleep]
23:07 -!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards
23:09 -!- zookolaptop [~user@68.233.157.2] has quit [Ping timeout: 256 seconds]
23:09 -!- tripleslash_b [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-wizards
23:09 -!- tripleslash_a [~triplesla@unaffiliated/imsaguy] has quit [Ping timeout: 260 seconds]
23:10 -!- hdbuck [~hdbuck@62.160.224.48] has joined #bitcoin-wizards
23:10 -!- hdbuck [~hdbuck@62.160.224.48] has quit [Changing host]
23:10 -!- hdbuck [~hdbuck@unaffiliated/hdbuck] has joined #bitcoin-wizards
23:11 -!- coinoperated [~coinopera@70.15.164.106.res-cmts.t132.ptd.net] has quit [Ping timeout: 276 seconds]
23:13 -!- waxwing [~waxwing@62.205.214.125] has quit [Read error: Connection reset by peer]
23:15 -!- waxwing [~waxwing@62.205.214.125] has joined #bitcoin-wizards
23:16 -!- giel__ [~giel____@a149043.upc-a.chello.nl] has quit [Read error: Connection reset by peer]
23:16 -!- giel__ [~giel____@a149043.upc-a.chello.nl] has joined #bitcoin-wizards
23:16 -!- CubicEarth [~cubiceart@c-67-168-82-178.hsd1.wa.comcast.net] has joined #bitcoin-wizards
23:24 -!- giel__ [~giel____@a149043.upc-a.chello.nl] has quit [Quit: Leaving]
23:28 -!- chjj [~chjj@unaffiliated/chjj] has quit [Quit: null]
23:28 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-wizards
23:34 -!- Alopex [~bitcoin@guru.dealing.ninja] has quit [Remote host closed the connection]
23:49 -!- psztorc [4575fa8d@gateway/web/freenode/ip.69.117.250.141] has quit [Quit: Page closed]
--- Log closed Tue Dec 29 00:00:34 2015