--- Day changed Wed Mar 23 2016 02:18 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has quit [Read error: Connection reset by peer] 02:18 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has joined #secp256k1 04:09 -!- andytoshi [~andytoshi@wpsoftware.net] has quit [Ping timeout: 250 seconds] 04:32 -!- btcdrak is now known as intdrak 05:19 -!- andytoshi [~andytoshi@wpsoftware.net] has joined #secp256k1 06:18 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has quit [Read error: Connection reset by peer] 06:18 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has joined #secp256k1 06:31 -!- jtimon [~quassel@227.31.134.37.dynamic.jazztel.es] has joined #secp256k1 07:09 -!- sipa [~pw@unaffiliated/sipa1024] has quit [Ping timeout: 250 seconds] 07:13 -!- intdrak is now known as btcdrak 07:18 -!- sipa_ [~pw@2a02:348:86:3011::1] has joined #secp256k1 07:30 -!- sipa_ is now known as sipa 07:31 -!- sipa is now known as Guest7455 07:31 -!- Guest7455 is now known as sipax 07:31 -!- sipax [~pw@2a02:348:86:3011::1] has quit [Changing host] 07:31 -!- sipax [~pw@unaffiliated/sipa1024] has joined #secp256k1 08:21 -!- sipax is now known as sipa 10:18 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has quit [Read error: Connection reset by peer] 10:19 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has joined #secp256k1 10:38 < gmaxwell> I wonder if it would be acceptable to limit the set of mutually authenticated peers of a node to some small number like 128. 10:41 < sipa> wrong channel? 10:41 < gmaxwell> want to discuss soem crypto here first. 10:44 < gmaxwell> Consider the protocol where a host has a collection of authed parties with pubkeys P1,P2,P3,P4... Party P3 connects, host picks a random x, publishes Ps = xG, and xP1, xP2, xP3, xP4... so on. This data is indistinguishable from any other candidate set of P_n, to someone without a DDH oracle. Then the responding peer replies with a tracable ring signature with respect to Ps, he knows xP3,s discrete 10:44 < gmaxwell> log with respect to Ps (thats his private key). He provides some tracing value with respect to a nums generator that the host selects and changes once per day (or whatever). The tracing lets the host tell if the same peer connected multiple times in that interval. 10:45 < gmaxwell> assuming no reuse during the tracing interval.. I think neighter party learns anything about the other's identity beyond it being in the allowed list. nor does anyone learn anything else about the other pubkeys in that set. 10:46 < gmaxwell> An actively malicious server could dummy out most of the set to remove your anonymity set; so this is something of a semi-honest assumption. 11:22 -!- jtimon [~quassel@227.31.134.37.dynamic.jazztel.es] has quit [Remote host closed the connection] 11:39 -!- maaku [~quassel@173-228-107-141.dsl.static.fusionbroadband.com] has quit [Remote host closed the connection] 11:40 -!- maaku [~quassel@173-228-107-141.dsl.static.fusionbroadband.com] has joined #secp256k1 11:51 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has quit [Quit: Leaving.] 12:32 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has joined #secp256k1 13:40 < waxwing> does anyone know anything about generating coverage stats for github? i've just taken a look at coveralls.io but it doesn't look like it supports branches(?) 13:41 < waxwing> i say 'coverage stats for github', i guess i really mean via travis, i guess you get the idea 13:43 < waxwing> ouch, sorry, wrong channel :) 14:18 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has quit [Read error: Connection reset by peer] 14:18 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has joined #secp256k1 15:31 -!- droark [~droark@c-24-22-36-12.hsd1.or.comcast.net] has joined #secp256k1 16:05 -!- sipa [~pw@unaffiliated/sipa1024] has quit [Ping timeout: 240 seconds] 16:05 -!- sipa [~pw@2a02:348:86:3011::1] has joined #secp256k1 16:06 -!- sipa is now known as Guest93735 16:06 -!- Guest93735 [~pw@2a02:348:86:3011::1] has quit [Changing host] 16:06 -!- Guest93735 [~pw@unaffiliated/sipa1024] has joined #secp256k1 16:06 -!- Guest93735 is now known as sipax 16:37 -!- GAit [~GAit@2-230-161-158.ip202.fastwebnet.it] has quit [Quit: Leaving.] 20:31 -!- molz [~molly@unaffiliated/molly] has joined #secp256k1 20:34 -!- moli [~molly@unaffiliated/molly] has quit [Ping timeout: 244 seconds] 23:17 -!- molly [~molly@unaffiliated/molly] has joined #secp256k1 23:20 -!- molz [~molly@unaffiliated/molly] has quit [Ping timeout: 252 seconds]