--- Log opened Sat Feb 28 00:00:07 2015
00:04 -!- coiner [~linker@115.79.45.104] has quit [Ping timeout: 252 seconds]
00:08 -!- vmatekole [~vmatekole@g230142110.adsl.alicedsl.de] has joined #bitcoin-wizards
00:13 -!- vmatekole [~vmatekole@g230142110.adsl.alicedsl.de] has quit [Ping timeout: 256 seconds]
00:16 -!- coiner [~linker@115.79.45.104] has joined #bitcoin-wizards
00:17 -!- coiner [~linker@115.79.45.104] has quit [Max SendQ exceeded]
00:35 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-wizards
00:49 -!- NewLiberty [~NewLibert@2602:304:cff8:1580:cdbd:393e:aeae:591] has quit [Ping timeout: 265 seconds]
01:05 -!- andy-logbot [~bitcoin--@wpsoftware.net] has joined #bitcoin-wizards
01:05  * andy-logbot is logging
01:11 -!- Mably [~Mably@unaffiliated/mably] has joined #bitcoin-wizards
01:27 -!- paveljanik [~paveljani@79-98-72-216.sys-data.com] has joined #bitcoin-wizards
01:27 -!- paveljanik [~paveljani@79-98-72-216.sys-data.com] has quit [Changing host]
01:27 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has joined #bitcoin-wizards
01:28 -!- LarsLarsen [~lars@50.161.197.33] has quit [Read error: Connection reset by peer]
01:29 -!- LarsLarsen [~lars@50.161.197.33] has joined #bitcoin-wizards
01:34 -!- Dr-G2 [~Dr-G@gtng-4d08a429.pool.mediaWays.net] has joined #bitcoin-wizards
01:37 -!- Dr-G3 [~Dr-G@gtng-4d08a429.pool.mediaWays.net] has quit [Ping timeout: 240 seconds]
01:53 -!- bramc [~bram@99-75-88-206.lightspeed.sntcca.sbcglobal.net] has quit [Quit: This computer has gone to sleep]
01:56 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Remote host closed the connection]
02:00 -!- RoboTedd_ [~roboteddy@c-67-180-192-179.hsd1.ca.comcast.net] has quit [Remote host closed the connection]
02:00 -!- RoboTeddy [~roboteddy@2601:9:3483:2400:b4a6:71a6:b802:e9be] has joined #bitcoin-wizards
02:05 -!- RoboTeddy [~roboteddy@2601:9:3483:2400:b4a6:71a6:b802:e9be] has quit [Ping timeout: 256 seconds]
02:10 -!- vmatekole [~vmatekole@g230142110.adsl.alicedsl.de] has joined #bitcoin-wizards
02:12 -!- GAit [~lnahum@2-230-161-158.ip202.fastwebnet.it] has quit [Read error: Connection reset by peer]
02:13 -!- cbeams [~cbeams@unaffiliated/cbeams] has joined #bitcoin-wizards
02:13 -!- GAit [~lnahum@2-230-161-158.ip202.fastwebnet.it] has joined #bitcoin-wizards
02:14 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has joined #bitcoin-wizards
02:15 -!- vmatekole [~vmatekole@g230142110.adsl.alicedsl.de] has quit [Ping timeout: 244 seconds]
02:22 -!- damethos [~damethos@unaffiliated/damethos] has quit [Ping timeout: 264 seconds]
02:25 -!- hashtag [~hashtag@CPE-69-23-213-3.wi.res.rr.com] has quit [Ping timeout: 272 seconds]
02:33 -!- cbeams [~cbeams@unaffiliated/cbeams] has quit [Remote host closed the connection]
02:34 -!- Dr-G2 [~Dr-G@gtng-4d08a429.pool.mediaWays.net] has quit [Read error: Connection reset by peer]
02:34 -!- Dr-G2 [~Dr-G@gtng-4d08a429.pool.mediaways.net] has joined #bitcoin-wizards
02:35 -!- fanquake [~anonymous@unaffiliated/fanquake] has quit [Quit: fanquake]
02:36 -!- Quanttek [~quassel@2a02:8108:73f:f6e4:e23f:49ff:fe47:9364] has quit [Ping timeout: 272 seconds]
02:36 -!- moa [~moa@opentransactions/dev/moa] has quit [Quit: Leaving.]
02:44 -!- Dr-G3 [~Dr-G@gtng-4d08a429.pool.mediaWays.net] has joined #bitcoin-wizards
02:48 -!- Dr-G2 [~Dr-G@gtng-4d08a429.pool.mediaways.net] has quit [Ping timeout: 256 seconds]
02:53 -!- wallet42 [~wallet42@81.196.160.52] has joined #bitcoin-wizards
03:11 -!- Dr-G3 [~Dr-G@gtng-4d08a429.pool.mediaWays.net] has quit [Read error: Connection reset by peer]
03:11 -!- Dr-G3 [~Dr-G@gtng-4d08a429.pool.mediaWays.net] has joined #bitcoin-wizards
03:28 -!- RoboTedd_ [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has joined #bitcoin-wizards
03:30 -!- Quanttek [~quassel@2a02:8108:73f:f6e4:e23f:49ff:fe47:9364] has joined #bitcoin-wizards
03:31 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has quit [Ping timeout: 246 seconds]
03:32 -!- RoboTedd_ [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has quit [Ping timeout: 246 seconds]
03:38 -!- xenog [~xeno@86-44-192-78-dynamic.b-ras2.dbn.dublin.eircom.net] has joined #bitcoin-wizards
03:39 -!- cbeams [~cbeams@unaffiliated/cbeams] has joined #bitcoin-wizards
03:40 -!- cbeams [~cbeams@unaffiliated/cbeams] has quit [Remote host closed the connection]
03:42 -!- cbeams [~cbeams@unaffiliated/cbeams] has joined #bitcoin-wizards
03:49 -!- cbeams [~cbeams@unaffiliated/cbeams] has quit [Remote host closed the connection]
03:52 -!- cbeams [~cbeams@unaffiliated/cbeams] has joined #bitcoin-wizards
03:58 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has joined #bitcoin-wizards
03:59 -!- cbeams [~cbeams@unaffiliated/cbeams] has quit []
03:59 -!- cbeams [~cbeams@chello084114181075.1.15.vie.surfer.at] has joined #bitcoin-wizards
03:59 -!- cbeams [~cbeams@chello084114181075.1.15.vie.surfer.at] has quit [Changing host]
03:59 -!- cbeams [~cbeams@unaffiliated/cbeams] has joined #bitcoin-wizards
04:03 -!- llllllllll [~lllllllll@6d482698.ftth.concepts.nl] has joined #bitcoin-wizards
04:03 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has quit [Ping timeout: 244 seconds]
04:08 -!- xenog [~xeno@86-44-192-78-dynamic.b-ras2.dbn.dublin.eircom.net] has quit [Ping timeout: 245 seconds]
04:12 -!- vmatekole [~vmatekole@g230142110.adsl.alicedsl.de] has joined #bitcoin-wizards
04:13 -!- OneNomos [~OneNomos@pool-71-163-227-3.washdc.east.verizon.net] has joined #bitcoin-wizards
04:17 -!- vmatekole [~vmatekole@g230142110.adsl.alicedsl.de] has quit [Ping timeout: 245 seconds]
04:20 -!- wallet42 [~wallet42@81.196.160.52] has quit [Quit: Leaving.]
04:31 -!- cbeams [~cbeams@unaffiliated/cbeams] has quit [Remote host closed the connection]
04:34 -!- cbeams [~cbeams@unaffiliated/cbeams] has joined #bitcoin-wizards
04:35 -!- Quanttek [~quassel@2a02:8108:73f:f6e4:e23f:49ff:fe47:9364] has quit [Ping timeout: 252 seconds]
04:37 -!- cbeams [~cbeams@unaffiliated/cbeams] has quit [Remote host closed the connection]
04:38 -!- Quanttek [~quassel@ip1f1171b4.dynamic.kabel-deutschland.de] has joined #bitcoin-wizards
04:38 -!- cbeams [~cbeams@unaffiliated/cbeams] has joined #bitcoin-wizards
04:39 -!- shesek [~shesek@77.125.109.255] has quit [Ping timeout: 272 seconds]
04:52 -!- bsm117532 [~bsm117532@static-108-21-236-13.nycmny.fios.verizon.net] has joined #bitcoin-wizards
04:56 -!- vmatekole [~vmatekole@g230142110.adsl.alicedsl.de] has joined #bitcoin-wizards
04:59 -!- melvster [~melvster@ip-86-49-18-198.net.upcbroadband.cz] has quit [Remote host closed the connection]
04:59 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has joined #bitcoin-wizards
04:59 -!- melvster [~melvster@ip-86-49-18-198.net.upcbroadband.cz] has joined #bitcoin-wizards
05:04 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has quit [Ping timeout: 272 seconds]
05:12 -!- wallet42 [~wallet42@home-tomis2.rdsct.ro] has joined #bitcoin-wizards
05:12 -!- Burrito [~Burrito@unaffiliated/burrito] has joined #bitcoin-wizards
05:15 -!- jdvs [~John@unaffiliated/jdvs] has joined #bitcoin-wizards
05:15 < jdvs> it's difficult for me to determine if omnicoin is based on the bitcoin blockchain or another blockchain, does anyone know the answer to this?
05:17 < fluffypony> jdvs: it's forked from Bitcoin, so undoubtedly yes
05:17 -!- bsm117532 [~bsm117532@static-108-21-236-13.nycmny.fios.verizon.net] has quit [Ping timeout: 272 seconds]
05:20 -!- hashtag [~hashtag@CPE-69-23-213-3.wi.res.rr.com] has joined #bitcoin-wizards
05:20 -!- adam3us [~Adium@88-105-16-20.dynamic.dsl.as9105.com] has joined #bitcoin-wizards
05:21 < fluffypony> forked from an old version of Bitcoin too, like 0.8-ish
05:33 -!- jdvs [~John@unaffiliated/jdvs] has quit [Ping timeout: 265 seconds]
05:34 -!- hearn [~mike@84-75-198-85.dclient.hispeed.ch] has joined #bitcoin-wizards
05:38 -!- MoALTz_ [~no@78.11.179.104] has joined #bitcoin-wizards
05:41 -!- MoALTz [~no@78.11.179.104] has quit [Ping timeout: 252 seconds]
05:44 -!- NewLiberty [~NewLibert@2602:304:cff8:1580:cdbd:393e:aeae:591] has joined #bitcoin-wizards
05:49 -!- adam3us [~Adium@88-105-16-20.dynamic.dsl.as9105.com] has quit [Read error: Connection timed out]
05:50 -!- adam3us [~Adium@88-105-16-20.dynamic.dsl.as9105.com] has joined #bitcoin-wizards
05:51 -!- cbeams [~cbeams@unaffiliated/cbeams] has quit [Remote host closed the connection]
05:53 -!- Dr-G3 [~Dr-G@gtng-4d08a429.pool.mediaWays.net] has quit [Read error: Connection reset by peer]
05:53 -!- Dr-G3 [~Dr-G@gtng-4d08a429.pool.mediaWays.net] has joined #bitcoin-wizards
06:00 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has joined #bitcoin-wizards
06:00 -!- Dr-G [~Dr-G@unaffiliated/dr-g] has joined #bitcoin-wizards
06:03 -!- Dr-G3 [~Dr-G@gtng-4d08a429.pool.mediaWays.net] has quit [Ping timeout: 250 seconds]
06:04 -!- GAit [~lnahum@2-230-161-158.ip202.fastwebnet.it] has quit [Ping timeout: 264 seconds]
06:05 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has quit [Ping timeout: 250 seconds]
06:07 -!- adam3us [~Adium@88-105-16-20.dynamic.dsl.as9105.com] has quit [Read error: Connection timed out]
06:07 -!- xenog [~xeno@95.83.254.159] has joined #bitcoin-wizards
06:08 -!- adam3us [~Adium@88-105-16-20.dynamic.dsl.as9105.com] has joined #bitcoin-wizards
06:09 -!- Quanttek [~quassel@ip1f1171b4.dynamic.kabel-deutschland.de] has quit [Read error: Connection reset by peer]
06:13 -!- Quanttek [~quassel@2a02:8108:73f:f6e4:e23f:49ff:fe47:9364] has joined #bitcoin-wizards
06:14 -!- bepo [~bepo@fer68-1-78-229-8-151.fbx.proxad.net] has quit [Ping timeout: 264 seconds]
06:14 -!- bepo_ [~bepo@fer68-1-78-229-8-199.fbx.proxad.net] has joined #bitcoin-wizards
06:27 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has joined #bitcoin-wizards
06:28 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has quit [Read error: Connection reset by peer]
06:29 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has joined #bitcoin-wizards
06:29 -!- GAit [~lnahum@2-230-161-158.ip202.fastwebnet.it] has joined #bitcoin-wizards
06:30 -!- xenog [~xeno@95.83.254.159] has quit [Quit: Leaving.]
06:30 -!- Dr-G [~Dr-G@unaffiliated/dr-g] has quit [Ping timeout: 264 seconds]
06:31 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has quit [Ping timeout: 250 seconds]
06:32 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-wizards
06:34 -!- droark [~droark@209-6-53-207.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com] has joined #bitcoin-wizards
06:43 -!- adam3us [~Adium@88-105-16-20.dynamic.dsl.as9105.com] has quit [Read error: Connection timed out]
06:43 -!- adam3us [~Adium@88-105-16-20.dynamic.dsl.as9105.com] has joined #bitcoin-wizards
06:48 -!- LTD_ [3280ee9b@gateway/web/freenode/ip.50.128.238.155] has joined #bitcoin-wizards
06:55 -!- LTD_ [3280ee9b@gateway/web/freenode/ip.50.128.238.155] has left #bitcoin-wizards []
07:01 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has joined #bitcoin-wizards
07:04 -!- bepo [bepo@fer68-1-78-229-8-151.fbx.proxad.net] has joined #bitcoin-wizards
07:06 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has quit [Ping timeout: 272 seconds]
07:09 -!- bepo_ [~bepo@fer68-1-78-229-8-199.fbx.proxad.net] has quit [Ping timeout: 265 seconds]
07:22 -!- adam3us [~Adium@88-105-16-20.dynamic.dsl.as9105.com] has quit [Read error: Connection timed out]
07:23 -!- adam3us [~Adium@88-105-16-20.dynamic.dsl.as9105.com] has joined #bitcoin-wizards
07:35 -!- HaltingState [~HaltingSt@unaffiliated/haltingstate] has quit [Ping timeout: 264 seconds]
07:54 -!- adam3us1 [~Adium@88-105-16-20.dynamic.dsl.as9105.com] has joined #bitcoin-wizards
07:54 -!- adam3us [~Adium@88-105-16-20.dynamic.dsl.as9105.com] has quit [Read error: Connection reset by peer]
07:55 -!- Burrito [~Burrito@unaffiliated/burrito] has quit [Quit: Leaving]
07:58 -!- Burrito [~Burrito@unaffiliated/burrito] has joined #bitcoin-wizards
08:08 -!- xenog [~xeno@95.83.254.159] has joined #bitcoin-wizards
08:11 -!- adam3us1 [~Adium@88-105-16-20.dynamic.dsl.as9105.com] has quit [Read error: Connection timed out]
08:11 -!- adam3us [~Adium@88-105-16-20.dynamic.dsl.as9105.com] has joined #bitcoin-wizards
08:12 -!- xenog [~xeno@95.83.254.159] has quit [Client Quit]
08:13 -!- koeppelmann [~koeppelma@dyn-160-39-29-101.dyn.columbia.edu] has quit [Remote host closed the connection]
08:13 -!- koeppelmann [~koeppelma@dyn-160-39-29-101.dyn.columbia.edu] has joined #bitcoin-wizards
08:24 -!- adam3us [~Adium@88-105-16-20.dynamic.dsl.as9105.com] has quit [Ping timeout: 272 seconds]
08:28 -!- bramc [~bram@99-75-88-206.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-wizards
08:36 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has quit [Read error: Connection reset by peer]
08:36 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has joined #bitcoin-wizards
08:37 -!- OneNomos [~OneNomos@pool-71-163-227-3.washdc.east.verizon.net] has quit [Remote host closed the connection]
08:41 -!- xenog [~xeno@95.83.254.159] has joined #bitcoin-wizards
08:50 -!- flower_ [~user@202.44.238.62] has quit [Remote host closed the connection]
08:51 -!- koeppelmann [~koeppelma@dyn-160-39-29-101.dyn.columbia.edu] has quit [Remote host closed the connection]
08:53 -!- prodatalab_ [~prodatala@c-69-254-45-177.hsd1.fl.comcast.net] has joined #bitcoin-wizards
08:56 -!- prodatalab [~prodatala@c-69-254-45-177.hsd1.fl.comcast.net] has quit [Ping timeout: 250 seconds]
08:57 -!- prodatalab_ is now known as prodatalab
08:58 -!- ryanxcharles [~ryan@2601:9:4680:dd0:d48a:363e:5916:7ebb] has joined #bitcoin-wizards
09:00 -!- Rynomster [~quassel@unaffiliated/rynomster] has joined #bitcoin-wizards
09:02 -!- SDCDev [~quassel@unaffiliated/sdcdev] has quit [Ping timeout: 264 seconds]
09:02 -!- hearn [~mike@84-75-198-85.dclient.hispeed.ch] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
09:03 -!- eudoxia [~eudoxia@r167-63-59-81.su-static.adinet.com.uy] has joined #bitcoin-wizards
09:03 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has joined #bitcoin-wizards
09:06 -!- xenog [~xeno@95.83.254.159] has quit [Quit: Leaving.]
09:07 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has quit [Ping timeout: 252 seconds]
09:11 -!- hearn [~mike@84-75-198-85.dclient.hispeed.ch] has joined #bitcoin-wizards
09:27 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has quit [Read error: Connection reset by peer]
09:27 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has joined #bitcoin-wizards
09:35 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has joined #bitcoin-wizards
09:36 -!- RoboTeddy [~roboteddy@c-67-188-40-206.hsd1.ca.comcast.net] has joined #bitcoin-wizards
09:36 -!- kmels [~kmels@186.151.61.56] has joined #bitcoin-wizards
09:38 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has quit [Ping timeout: 245 seconds]
09:39 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has joined #bitcoin-wizards
09:42 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 245 seconds]
09:43 -!- melvster [~melvster@ip-86-49-18-198.net.upcbroadband.cz] has quit [Remote host closed the connection]
09:43 -!- woah [~woah@199-241-202-232.PUBLIC.monkeybrains.net] has joined #bitcoin-wizards
09:43 -!- OneNomos [~OneNomos@pool-71-163-227-3.washdc.east.verizon.net] has joined #bitcoin-wizards
09:44 -!- melvster [~melvster@ip-86-49-18-198.net.upcbroadband.cz] has joined #bitcoin-wizards
09:44 -!- bsm117532 [~bsm117532@static-108-21-236-13.nycmny.fios.verizon.net] has joined #bitcoin-wizards
09:51 -!- woah [~woah@199-241-202-232.PUBLIC.monkeybrains.net] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
09:52 -!- hearn [~mike@84-75-198-85.dclient.hispeed.ch] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
09:52 -!- zooko` [~user@97-122-248-7.hlrn.qwest.net] has joined #bitcoin-wizards
09:53 -!- NewLiberty [~NewLibert@2602:304:cff8:1580:cdbd:393e:aeae:591] has quit [Ping timeout: 256 seconds]
09:55 -!- zooko [~user@c-75-70-204-109.hsd1.co.comcast.net] has quit [Ping timeout: 245 seconds]
09:57 < maaku> GreenIsMyPepper: where does SIGHASH_NORMALIZED get the normalized transaction IDs from?
09:57 -!- tcrypt [~tylersmit@c-67-169-17-114.hsd1.ca.comcast.net] has joined #bitcoin-wizards
09:59 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has joined #bitcoin-wizards
09:59 -!- woah [~woah@199-241-202-232.PUBLIC.monkeybrains.net] has joined #bitcoin-wizards
10:00 -!- woah [~woah@199-241-202-232.PUBLIC.monkeybrains.net] has quit [Client Quit]
10:03 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has quit [Ping timeout: 265 seconds]
10:06 < bramc> A question I keep meaning to ask: If there are a bunch of utxos all of which can be unlocked with the same key, can they all be accumulated together with a single transaction which has a single signature?
10:08 -!- zooko` is now known as zooko
10:08 < sipa> no, you need a signature per input
10:09 < sipa> in theory it would be possible to allow them to be combined
10:09 < sipa> but it would require a more complex design
10:09 < sipa> and it would encourage key reuse
10:12 -!- Cory [~Cory@unaffiliated/cory] has joined #bitcoin-wizards
10:13 < Eliel> yep, not going to happen because of that last part.
10:14 -!- jps [~Jud@cpe-74-72-116-143.nyc.res.rr.com] has joined #bitcoin-wizards
10:15 -!- jps [~Jud@cpe-74-72-116-143.nyc.res.rr.com] has quit [Client Quit]
10:18 < nsh> sipa, can you sketch the more complex design?
10:22 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has quit [Read error: Connection reset by peer]
10:22 -!- xenog [~xeno@46.7.118.40] has joined #bitcoin-wizards
10:22 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has joined #bitcoin-wizards
10:23 -!- flower [~user@202.44.238.62] has joined #bitcoin-wizards
10:23 -!- Quanttek [~quassel@2a02:8108:73f:f6e4:e23f:49ff:fe47:9364] has quit [Ping timeout: 252 seconds]
10:23 < maaku> nsh: i'm not sure sipa was referencing an actual design so much as commenting that bitcoin transaction format is not expressive enough to represent 'one signature covering multiple inputs'
10:23 < nsh> right
10:24 < nsh> but you might have a sidechain that is, conceivably?
10:27 < maaku> sure, maybe, but why would you want to?
10:27 -!- flower [~user@202.44.238.62] has quit [Client Quit]
10:28 -!- flower [~user@202.44.238.62] has joined #bitcoin-wizards
10:29 < nsh> maaku, good question
10:30 < nsh> i don't presume to be able to guess bramc's thinking
10:30 < nsh> some kind of consolidation / defragmentation maybe
10:32 < bramc> nsh, It's useful for reducing transaction fees by making transactions smaller (at least in the future, when such things are correlated) and yes I'm thinking of it for cleaning up dust, or at least change-making
10:32 < nsh> right
10:33 < bramc> There's no real anonymity lost by sending a bunch of outputs to the same key if they're all going to be consolidated together anyway.
10:33 < nsh> i mooted at some point a kind of sweeper service that's funded from mining subsidies somehow
10:33 < nsh> but it was very woolly thinking
10:34 < bramc> There isn't a very good change-making service out there right now. Cryptoshuffle might be one but I haven't read that paper yet.
10:35 -!- Emcy [~MC@152.27.187.81.in-addr.arpa] has joined #bitcoin-wizards
10:35 -!- Emcy [~MC@152.27.187.81.in-addr.arpa] has quit [Changing host]
10:35 -!- Emcy [~MC@unaffiliated/mc1984] has joined #bitcoin-wizards
10:35 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has joined #bitcoin-wizards
10:35 < bramc> I mean, cryptoshuffle might be a proposal for one, I don't believe anyone claims to be running such a service.
10:36  * nsh nods
10:37 < bramc> It would be nice if there was a bitcoin wallet which had a 'make change' button which cleaned up the dust and unlinked all the utxos through a centralized service which specialized in that
10:37 < bramc> It's unclear how much demand there might be for such a beast though.
10:37 -!- Emcy_ [~MC@unaffiliated/mc1984] has quit [Ping timeout: 244 seconds]
10:39 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has quit [Read error: Connection reset by peer]
10:40 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has joined #bitcoin-wizards
10:40 < bramc> But working on the design of that centralized service would be fun
10:40 < nsh> what would the trust implications be?
10:41 < nsh> (better than using bc.i obviously, but non-zero presumably)
10:42 < bramc> nsh, Not all that much if you use simultaneous transfer properly, a little bit of threat that the centralized service could re-link your unlinked transactions, or if they screw it up could reveal information about your business with them and hence who you are
10:43 -!- hktud0 [wq@unaffiliated/fluffybunny] has quit [Read error: Connection reset by peer]
10:43 < bramc> At one point in this channel we had a discussion about the algorithms for picking which utxos to combine/split when making a payment from a wallet. The upshot was basically 'we do this, but have no coherent intellectual basis for arguing that other algorithms are better or worse'
10:43 < nsh> right
10:44 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has joined #bitcoin-wizards
10:45 < bramc> After thinking about it a bunch, my conclusion is that what you really should do is make payments by taking the smallest coin you have bigger than the target and splitting it in two, and move the extra into your dust pile, along with all received transactions, and when the amount of dust gets too much go use the change-making service
10:45 < bramc> There's a potential natural monopoly with the change-making service, because the bigger the pool the better the unlinking
10:47 < nsh> to greater the extent to which the input-choice algorithm is deterministic, the greater the ability to link transactions
10:47 < nsh> if you coupled with lossy mechanisms like coin-join that could be mitigated
10:48 < bramc> Sort of, randomization can open you up to attacks as well, where lots of small transactions are more likely to give away your identity
10:48 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has quit [Ping timeout: 245 seconds]
10:48 < nsh> right, yup
10:48 < nsh> randomness can be just as pernicious
10:48 < nsh> just less intuitively :/
10:48 < bramc> The unlinking service I'm talking about would basically be a massive better version of coin-join
10:48 < nsh> ah right. that's favorable imho
10:49 < nsh> but as i understand it, the complexity of coin-join grows as you scale it up to more users
10:49 < bramc> It seems like a potentially good business, and fun to work on, but I'm busy working on other stuff
10:49  * nsh nods
10:51 < bramc> It gets a lot easier if you have a centralized service and trust the centralized service to throw out their data eventually. The idea is that you do a coinswap with the service for all of your utxos, where they give you back somewhat better formed change by consolidating some of the dust they got from other people
10:51 -!- tcrypt [~tylersmit@c-67-169-17-114.hsd1.ca.comcast.net] has quit [Remote host closed the connection]
10:52 < nsh> right. you can certainly increase the transparency and auditability to some 'trustworthy' threshold (again, certainly compared to e.g. bc.i)
10:52 < nsh> but proving the destruction of information is basically impossible
10:52 < nsh> that's the problem with trusted set-up (common reference string) schemes too
10:52 < bramc> The service needs a certain amount of working capital, and some algorithms for deciding which utxos to consolidate together when. That's the fun part.
10:52  * nsh nods
10:52 < bramc> Dumb question: what are you referencing by bc.i?
10:53 < nsh> because lots of people just trust these guys with their wallet keys, as i understand it
10:53 < nsh> and that is really not too warranted from experience
10:53 < nsh> i'm just picking on them because i'm too lazy to think of other examples though
10:53 < nsh> oh, blockchain.info
10:53 < nsh> sorry
10:54 < bramc> Yeah trusting with wallet keys is totally cringeworthy. It calls into question whether you can get customers by doing things like change-making securely
10:54  * nsh nods
10:54 < bramc> It could be that any such change-making service would wind up mostly servicing the relatively small number of vendors who are mostly receiving payments rather than sending them
10:54 < nsh> cultivating the right degree and the right kind of paranoia in the general public is a hard problem
10:54  * nsh nods
10:55 < bramc> Although that would of course still be a very real business
10:57 < nsh> aye
10:59 -!- damethos [~damethos@unaffiliated/damethos] has joined #bitcoin-wizards
11:03 < bramc> Making it truly decentralized is an interesting academic challenge but probably vastly less secure than using a centralized service
11:03 < nsh> i'm not sure i follow
11:03 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
11:04 < nsh> centralization generally concentrates the negative consequences of insecurity
11:04 < nsh> in exchange for lower complexity or better synchronicity
11:06 < bramc> If you try to make a truly decentralized change-making service, there are a lot more potential attacks where the participants mess with whoever they happen to be interacting with
11:09 < nsh> ah, i see
11:09 < nsh> yeah i guess you have more leeway to leverage human psychology/error in a decentralized solution that involves cluefulness
11:11 < bramc> It isn't just psychology. There are potential connection flooding attacks and selective leaving and tagging when you're participating in a decentralized system
11:15 < nsh> that too, aye
11:16 < nsh> you have to be very careful delegating security properties to unexamined assumptions about network connectivity
11:16 < nsh> this is a common way to screw up
11:18 < nsh> s/delegating...to/making contingent...on/
11:22 < bramc> Given what a huge improvement the centralized system would be over what exists today, it's more compelling to make that. There's also less of a business in making the decentralized thing. But if anybody comes up with interesting designs on the decentralized thing I'd love to see them.
11:23 < sipa> bramc: i think it's a pretty bad idea to have a design that makes loss of privacy cheaper; if you don't reuse keus (which you should for privacy reasons), this optimization does not gain you anything anyway
11:25 -!- koeppelmann [~koeppelma@dyn-160-39-29-101.dyn.columbia.edu] has joined #bitcoin-wizards
11:27 < bramc> sipa, fair enough
11:28 -!- Profreid [~Profreitt@gateway/vpn/privateinternetaccess/profreid] has joined #bitcoin-wizards
11:35 -!- coinrookie [~c0inr00ki@c-68-53-21-189.hsd1.tn.comcast.net] has joined #bitcoin-wizards
11:42 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
11:42 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
11:43 < adam3us> anyone interested in cryptonote / ring sig crypto? i think you can ~halve the signature size by using section 5.1 from http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.363.3431&rep=rep1&type=pdf
11:45 < nsh> neat
11:51 < andytoshi> adam3us: cool, this is actually quite different from the van saberhagen scheme
11:51 < andytoshi> so i can't just copy the key image over. but probably i can come up with something analogous
11:52 -!- jps [~Jud@cpe-74-72-116-143.nyc.res.rr.com] has joined #bitcoin-wizards
11:53 < andytoshi> hopefully i'll have time for brainteasers later this weekend to do it, if you haven't. (anyone else who wants to give it a shot is welcome to PM me for advice -- i'm 75% sure it's just "straightforward algebra" and does not require math/crypto experience)
11:54 -!- andytoshi [~andytoshi@wpsoftware.net] has quit [Changing host]
11:54 -!- andytoshi [~andytoshi@unaffiliated/andytoshi] has joined #bitcoin-wizards
11:54 < adam3us> andytoshi: i think its close enough. if you look at the g^s*y^c that is basically L
11:54 < adam3us> so compute R also and put that also into each hash
11:55 < bramc> There tends to be a fairly firm separation between crypto primitive work and using the primitives to make protocols. The former is mostly math, the latter is mostly 'crypto'
11:55 < andytoshi> oh, yeah, i see...but if R is in there you lose the space savings right?
11:55 < adam3us> and i think you're done (add I to the signature, add R=H(y)^s*I^c to the verification step)
11:55 < adam3us> (and convert to EC basis)
11:56 < adam3us> andytoshi: no because R is computed
11:57 < adam3us> andytoshi: the sig includes I now, and you can compute the rest…. H(y)^s*I^c
11:58 < andytoshi> ok, that seems correct, i'm not confident of security because the van saberhagen scheme has a second set of challenges and i worry they are necessary (and will imply that you need bigger sigs)
11:58 < bramc> This all sounds like fun. I'm stuck in monte carlo land.
11:58 -!- koeppelmann [~koeppelma@dyn-160-39-29-101.dyn.columbia.edu] has quit [Remote host closed the connection]
11:58 < andytoshi> but i just need to write it out
11:59 -!- koeppelmann [~koeppelma@dyn-160-39-29-101.dyn.columbia.edu] has joined #bitcoin-wizards
12:00 < adam3us> andytoshi: i have the cryptonote paper here.  it includes c_i and q_i which are analogous c_i and s_i here.
12:00 < adam3us> andytoshi: i was trying to figure out how to do this trick (towards my hobby of trying to find a fixed size ring sig for all of utxo ha ha) and found this paper with the magic formula- they did what i was trying to do.
12:01 < adam3us> andytoshi: so that takes it form O(2n+c) to O(n+c) only the pesky O(n) to get rid of :)
12:02 -!- hktud0 [~ncidsk@unaffiliated/fluffybunny] has joined #bitcoin-wizards
12:03 -!- koeppelmann [~koeppelma@dyn-160-39-29-101.dyn.columbia.edu] has quit [Ping timeout: 256 seconds]
12:05 < andytoshi> adam3us: "analogous" is a stretch, they require sum{c_i} = H(...) so they can program all but one of the c_i's, whereas in this paper the c_i's are all hashes and all-but-one are programmed by chaining into each other, which is enough difference to confuse my intuition
12:05 < andytoshi> but i see what you're saying now, i think that you're right
12:08 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
12:10 < andytoshi> it's surprising to me that s doesn't even need to change, it's as though c_i = d_i in the van saberhagen scheme
12:11 -!- jps [~Jud@cpe-74-72-116-143.nyc.res.rr.com] has quit [Quit: jps]
12:12 < andytoshi> oh never mind, there is no d_i in the saberhagen scheme, i am looking at my own notes which do something else (combining signatures iirc)
12:12 < adam3us> andytoshi: i think the actual challenge requirement is that they depend on the commitments (g^s*y^c) such that you can forge at most n-1 of them and need one private key.  the c values are arbitrary and could come from a CPRNG
12:12 -!- espes__ [~espes@205.185.120.132] has quit [Ping timeout: 264 seconds]
12:14 < andytoshi> adam3us: right ... doing it by sum is the "obvious" way, this chaining thing is entirely new to me ... does the space savings come from this change somehow?
12:15 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
12:15 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
12:16 < andytoshi> ah, i think so, doing it by sum requires that you have a new equation for each new thing you wanna prove the DL of (in this case, the key image I = H(y)^x as well as y = g^x), else you have fewer equations than unknown and are not forced
12:16 < andytoshi> whereas you can put as many things as you want into a single hash challenge and it'll force them all at once
12:16 < andytoshi> very slick
12:17 -!- jps [~Jud@cpe-74-72-116-143.nyc.res.rr.com] has joined #bitcoin-wizards
12:17 < adam3us> andytoshi: yes you only need to send c1, the rest is computed by recurrence.  so then the sig becomes c1,s1,…,sn instead of c1,…,cn,s1,…,sn
12:17 -!- lclc [~lucas@unaffiliated/lclc] has joined #bitcoin-wizards
12:18 -!- Quanttek [~quassel@ip1f1171b4.dynamic.kabel-deutschland.de] has joined #bitcoin-wizards
12:22 < andytoshi> ok, i understand. the space savings is simply because the recurrence avoids the need to send every c_i. (what i was saying explained how we avoid having both L_i's and R_i's, which are not sent but computed in verification; the paper you posted has only e_i's, so there's also a 50% speedup)
12:26 -!- jps [~Jud@cpe-74-72-116-143.nyc.res.rr.com] has quit [Quit: jps]
12:31 < andytoshi> this is really cool, this "ring of hash commitments" is totally out of left field to me
12:31 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-wizards
12:33 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
12:33 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
12:34 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Ping timeout: 256 seconds]
12:37 -!- espes__ [~espes@205.185.120.132] has joined #bitcoin-wizards
12:39 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has joined #bitcoin-wizards
12:39 < andytoshi> for constant-size sigs, i wonder if you can do something like: replace the s_i's with a single sum of c_i^i*x_i, then [magic magic] this reduces to "given g^x, g^(x^2), ..., g^(x^q) determine g^(x^{q+1})" which is a standard and imo safe assumption (called q-diffie-hellman iirc)
12:41 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has quit [Client Quit]
12:51 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
12:51 -!- cbeams [~cbeams@unaffiliated/cbeams] has joined #bitcoin-wizards
12:51 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
12:52 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has quit [Read error: Connection reset by peer]
12:52 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-wizards
12:53 -!- koeppelmann [~koeppelma@dyn-160-39-29-101.dyn.columbia.edu] has joined #bitcoin-wizards
12:56 -!- weex [~weex@fsf/member/weex] has joined #bitcoin-wizards
12:57 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has quit [Ping timeout: 244 seconds]
12:57 -!- weex_ [~weex@99-6-135-18.lightspeed.snmtca.sbcglobal.net] has quit [Read error: Connection reset by peer]
12:58 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-wizards
13:00 -!- xenog [~xeno@46.7.118.40] has quit [Ping timeout: 265 seconds]
13:01 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-wizards
13:03 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has quit [Ping timeout: 244 seconds]
13:03 < adam3us> andytoshi: i know scribbles on paper here in similar directions.  the hard part is to correct it so you dont disclose which signature was the one with known private key.  if it can be made to work its practically useful for bitcoin.
13:03 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Quit: Leaving]
13:03 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-wizards
13:04 -!- damethos [~damethos@unaffiliated/damethos] has quit [Ping timeout: 252 seconds]
13:04 -!- Quanttek [~quassel@ip1f1171b4.dynamic.kabel-deutschland.de] has quit [Remote host closed the connection]
13:04 < adam3us> andytoshi: the issue is one of the s_i values is computed as \alpha-c_i*x_i (where x_i is the private key from y_i = g^x_i)
13:06 -!- Quanttek [~quassel@2a02:8108:73f:f6e4:e23f:49ff:fe47:9364] has joined #bitcoin-wizards
13:09 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has quit [Ping timeout: 244 seconds]
13:10 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-wizards
13:10 < andytoshi> the other s_i's are random, i wonder if we can deterministically generate them from each other (with an arbitrary one being programmable) with something like an "invertible permutation hash"
13:11 < andytoshi> lol, is there anything wrong with just doing s_i = s_0 + i actually?
13:15 -!- zooko [~user@97-122-248-7.hlrn.qwest.net] has quit [Ping timeout: 272 seconds]
13:21 < andytoshi> or what if all the s_i's are the same?
13:22 -!- cbeams [~cbeams@unaffiliated/cbeams] has quit [Remote host closed the connection]
13:23 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
13:23 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
13:23 -!- cbeams [~cbeams@chello084114181075.1.15.vie.surfer.at] has joined #bitcoin-wizards
13:23 -!- cbeams [~cbeams@chello084114181075.1.15.vie.surfer.at] has quit [Changing host]
13:23 -!- cbeams [~cbeams@unaffiliated/cbeams] has joined #bitcoin-wizards
13:23 -!- cbeams [~cbeams@unaffiliated/cbeams] has quit [Remote host closed the connection]
13:23 -!- cbeams [~cbeams@unaffiliated/cbeams] has joined #bitcoin-wizards
13:24 < adam3us> andytoshi: i did try s_{k+1} = E( s_k ) which implies s_{k-1} = D( s_k ) etc however you still arrive back at the problem that either you make the one you can fix coincide with the c_k you are calculating and divulge which is the real private key)
13:25 -!- koeppelmann [~koeppelma@dyn-160-39-29-101.dyn.columbia.edu] has quit [Remote host closed the connection]
13:25 -!- koeppelmann [~koeppelma@dyn-160-39-29-101.dyn.columbia.edu] has joined #bitcoin-wizards
13:27 < andytoshi> i don't see why, the one you fix is blinded by α which is not revealed
13:28 -!- wyager [~wyager@nat-128-62-76-251.public.utexas.edu] has joined #bitcoin-wizards
13:28 -!- eudoxia [~eudoxia@r167-63-59-81.su-static.adinet.com.uy] has quit [Quit: Leaving]
13:30 -!- koeppelmann [~koeppelma@dyn-160-39-29-101.dyn.columbia.edu] has quit [Ping timeout: 252 seconds]
13:32 < andytoshi> oh derp i see, you cannot actually have all the s_i's constant because you need to know c_k (which depends on s_{k-1}) before you compute s_k
13:33 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has joined #bitcoin-wizards
13:35 -!- Quanttek [~quassel@2a02:8108:73f:f6e4:e23f:49ff:fe47:9364] has quit [Remote host closed the connection]
13:36 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has quit [Ping timeout: 245 seconds]
13:36 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has joined #bitcoin-wizards
13:39 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has quit [Ping timeout: 252 seconds]
13:39 -!- Quanttek [~quassel@ip1f1171b4.dynamic.kabel-deutschland.de] has joined #bitcoin-wizards
13:39 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
13:40 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
13:45 -!- fac7or [~fac7or@90.193.157.46] has joined #bitcoin-wizards
13:47 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has quit [Read error: Connection reset by peer]
13:48 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has joined #bitcoin-wizards
13:49 -!- cbeams [~cbeams@unaffiliated/cbeams] has quit [Read error: Connection reset by peer]
13:50 -!- cbeams [~cbeams@unaffiliated/cbeams] has joined #bitcoin-wizards
13:51 -!- wyager [~wyager@nat-128-62-76-251.public.utexas.edu] has quit [Quit: wyager]
13:54 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has quit [Read error: Connection reset by peer]
13:54 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has joined #bitcoin-wizards
13:59 -!- xenog [~xeno@46.7.118.40] has joined #bitcoin-wizards
14:02 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
14:02 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
14:03 -!- Ody10 [~Odysseas@client-8-29.eduroam.oxuni.org.uk] has joined #bitcoin-wizards
14:08 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has quit [Read error: Connection reset by peer]
14:08 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has joined #bitcoin-wizards
14:08 -!- lclc [~lucas@unaffiliated/lclc] has quit [Ping timeout: 256 seconds]
14:10 -!- wyager [~wyager@nat-128-62-76-251.public.utexas.edu] has joined #bitcoin-wizards
14:13 -!- wyager [~wyager@nat-128-62-76-251.public.utexas.edu] has quit [Client Quit]
14:20 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
14:21 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
14:23 -!- fac7or [~fac7or@90.193.157.46] has quit []
14:23 -!- prodatalab_ [~prodatala@c-69-254-45-177.hsd1.fl.comcast.net] has joined #bitcoin-wizards
14:24 -!- prodatalab [~prodatala@c-69-254-45-177.hsd1.fl.comcast.net] has quit [Ping timeout: 246 seconds]
14:24 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has quit [Read error: Connection reset by peer]
14:25 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has joined #bitcoin-wizards
14:30 < Eliel> if you wanted to help people learn bitcoin better, you'd first need to create a compact but easily understandable materials and then persuade the most popular wallets to include or at least link to it.
14:34 < nsh> you mean documentation?
14:36 < nsh> it's useful to appreciate how the curve might look when you graph the amount of information required to understand something well enough to do it right against the distribution of people who would benefit by using it
14:36 < nsh> i suspect the decay is quite sharp
14:37 < nsh> you can only package things and make them accessible to a certain degree, after that it's just a case of how much a given person is willing to eat the morsels
14:37 < nsh> if you want a wide franchise, you can't expect there to be a large meal of lore to swallow
14:37 < nsh> even if you make it into a yummy fruit smoothie
14:37 < bramc> Given that journalists sometimes write laudatory 'bitcoin is the future' articles while clearly not even understanding what it does and how, I don't think lack of documentation is the problem.
14:37 < nsh> journalism is the problem :)
14:37 < nsh> no, that's glib :)
14:38 < bliljerk101> what's the bitcoin-wizards channel for?
14:39 < bramc> bliljerk101, For discussing advanced topics and potential new development outside of the day to day of bitcoin development
14:39 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
14:39 < nsh> discussion of the theory and future developments of the technology of the blockchain and its associated/peripheral things
14:40 < nsh> and sometimes, within reason, other topics that might be of interest to the demographic that would usually discuss such thing
14:40 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
14:40 -!- wallet42 [~wallet42@home-tomis2.rdsct.ro] has quit [Quit: Leaving.]
14:41 -!- xenog [~xeno@46.7.118.40] has quit [Ping timeout: 264 seconds]
14:42 -!- Profreid [~Profreitt@gateway/vpn/privateinternetaccess/profreid] has quit [Quit: Profreid]
14:43 < bliljerk101> i see. i wasn't sure since i don't see much useful discussion going on in here
14:43 < bramc> bliljerk101, You can see past discussion in the archives on bitcoin.ninja
14:44 < nsh> thank goodness you intervened, bliljerk101 :)
14:44 < bramc> It frequently gets deep into arcane and technical discussions
14:45 -!- Ody10 [~Odysseas@client-8-29.eduroam.oxuni.org.uk] has quit [Quit: Ody10]
14:45 -!- xenog [~xeno@46.7.118.40] has joined #bitcoin-wizards
14:47 -!- wyager [~wyager@nat-128-62-76-251.public.utexas.edu] has joined #bitcoin-wizards
14:48 -!- wyager [~wyager@nat-128-62-76-251.public.utexas.edu] has quit [Client Quit]
14:48 -!- prodatalab_ is now known as prodatalab
14:49 -!- wyager [~wyager@nat-128-62-76-251.public.utexas.edu] has joined #bitcoin-wizards
14:49 -!- fac7or [~fac7or@90.193.157.46] has joined #bitcoin-wizards
14:51 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Remote host closed the connection]
14:56 -!- xenog [~xeno@46.7.118.40] has quit [Ping timeout: 264 seconds]
14:56 < bliljerk101> bramc thanks. nsh thanks for adding merit to my previous statement
14:56  * nsh nods
14:58 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
14:58 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
15:00 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has quit [Read error: Connection reset by peer]
15:01 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has joined #bitcoin-wizards
15:04 -!- zooko [~user@c-75-70-204-109.hsd1.co.comcast.net] has joined #bitcoin-wizards
15:05 -!- koeppelmann [~koeppelma@dyn-160-39-29-101.dyn.columbia.edu] has joined #bitcoin-wizards
15:08 -!- koeppelmann [~koeppelma@dyn-160-39-29-101.dyn.columbia.edu] has quit [Remote host closed the connection]
15:09 -!- koeppelmann [~koeppelma@dyn-160-39-29-101.dyn.columbia.edu] has joined #bitcoin-wizards
15:09 -!- rhadamanthus [~rhadamant@unaffiliated/rhadamanthus] has joined #bitcoin-wizards
15:11 -!- mkarrer [~mkarrer@126.Red-83-32-132.dynamicIP.rima-tde.net] has joined #bitcoin-wizards
15:13 -!- koeppelmann [~koeppelma@dyn-160-39-29-101.dyn.columbia.edu] has quit [Ping timeout: 246 seconds]
15:14 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has joined #bitcoin-wizards
15:17 -!- rhadamanthus [~rhadamant@unaffiliated/rhadamanthus] has quit [Quit: rhadamanthus]
15:18 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has quit [Ping timeout: 250 seconds]
15:20 -!- droark [~droark@209-6-53-207.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com] has quit [Quit: ZZZzzz…]
15:24 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
15:25 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
15:47 -!- ebfull [~ebfull@c-76-120-40-34.hsd1.co.comcast.net] has quit [Remote host closed the connection]
15:48 -!- wyager [~wyager@nat-128-62-76-251.public.utexas.edu] has quit [Quit: wyager]
15:50 -!- wyager [~wyager@nat-128-62-76-251.public.utexas.edu] has joined #bitcoin-wizards
15:50 -!- wyager [~wyager@nat-128-62-76-251.public.utexas.edu] has quit [Client Quit]
15:53 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has quit [Read error: Connection reset by peer]
15:53 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has joined #bitcoin-wizards
15:54 < zooko> phantomcircuit, maaku: Ah! Psychology! Now that is an argument I can admit might be true, although I have a hard time judging if it is true.
15:55 < phantomcircuit> zooko, it's pretty obvious that it's different
15:56 < phantomcircuit> there's a reason the irs collects taxes through withholding and tax collectors
15:56 < maaku> zooko: the psychological argument is real
15:56 < maaku> the other argument is from sticky prices
15:57 < maaku> inflation allows those closest to the source of money to unevenly profit from the inflation
15:57 < zooko> To me sticky prices are another expression of psychology.
15:57 < zooko> Or of inaccurate or limited mental models of the players.
15:57 < maaku> well, in the sense that economics is really a social science
15:58 < zooko> bbiab
16:05 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
16:06 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
16:06 -!- xenog [~xeno@46.7.118.40] has joined #bitcoin-wizards
16:09 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has quit [Read error: Connection reset by peer]
16:10 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has joined #bitcoin-wizards
16:11 -!- NewLiberty [~NewLibert@2602:304:cff8:1580:cdbd:393e:aeae:591] has joined #bitcoin-wizards
16:26 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
16:26 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
16:31 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has joined #bitcoin-wizards
16:35 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has quit [Client Quit]
16:40 -!- bramc [~bram@99-75-88-206.lightspeed.sntcca.sbcglobal.net] has quit [Quit: This computer has gone to sleep]
16:48 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
16:48 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
16:51 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has joined #bitcoin-wizards
16:52 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has quit [Client Quit]
17:03 -!- wallet42 [~wallet42@home-tomis2.rdsct.ro] has joined #bitcoin-wizards
17:04 -!- flower_ [~user@202.44.238.62] has joined #bitcoin-wizards
17:07 -!- flower [~user@202.44.238.62] has quit [Ping timeout: 272 seconds]
17:16 -!- HaltingState [~HaltingSt@unaffiliated/haltingstate] has joined #bitcoin-wizards
17:16 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has quit [Read error: Connection reset by peer]
17:17 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has joined #bitcoin-wizards
17:17 -!- SwedFTP [~SwedFTP@unaffiliated/swedftp] has joined #bitcoin-wizards
17:17 -!- delll_ [~chatzilla@yh97.internetdsl.tpnet.pl] has quit [Ping timeout: 252 seconds]
17:19 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has joined #bitcoin-wizards
17:20 -!- xenog [~xeno@46.7.118.40] has quit [Quit: Leaving.]
17:21 -!- dabura667 [uid43070@gateway/web/irccloud.com/x-uelnblcwccxbcyqj] has joined #bitcoin-wizards
17:22 -!- skittylx [~skittylx@184.107.219.242] has joined #bitcoin-wizards
17:26 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has quit [Read error: Connection reset by peer]
17:26 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has joined #bitcoin-wizards
17:26 -!- mkarrer [~mkarrer@126.Red-83-32-132.dynamicIP.rima-tde.net] has quit [Remote host closed the connection]
17:30 -!- ceedz [~eric@187.139.146.65] has joined #bitcoin-wizards
17:33 -!- bsm117532 [~bsm117532@static-108-21-236-13.nycmny.fios.verizon.net] has quit [Ping timeout: 252 seconds]
17:37 -!- nuke1989 [~nuke@176.92.55.87] has quit [Read error: Connection reset by peer]
17:37 -!- nuke1989 [~nuke@46-163-153.adsl.cyta.gr] has joined #bitcoin-wizards
17:39 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has quit [Quit: Leaving]
17:39 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-wizards
17:47 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
17:47 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
17:50 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has quit [Read error: Connection reset by peer]
17:50 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has joined #bitcoin-wizards
17:54 -!- skittylx [~skittylx@184.107.219.242] has quit [Quit: meatworld time]
17:55 -!- Mably [~Mably@unaffiliated/mably] has quit [Read error: Connection reset by peer]
17:56 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
18:00 -!- vmatekole [~vmatekole@g230142110.adsl.alicedsl.de] has quit [Read error: Connection reset by peer]
18:01 -!- vmatekole [~vmatekole@g230142110.adsl.alicedsl.de] has joined #bitcoin-wizards
18:06 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
18:06 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
18:07 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has quit [Read error: Connection reset by peer]
18:08 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has joined #bitcoin-wizards
18:10 -!- Quanttek [~quassel@ip1f1171b4.dynamic.kabel-deutschland.de] has quit [Ping timeout: 264 seconds]
18:18 -!- d1ggy [~d1ggy@dslb-088-071-013-176.088.071.pools.vodafone-ip.de] has joined #bitcoin-wizards
18:21 -!- d1ggy_ [~d1ggy@dslb-088-071-014-097.088.071.pools.vodafone-ip.de] has quit [Ping timeout: 272 seconds]
18:24 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
18:25 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
18:34 -!- ceedz [~eric@187.139.146.65] has quit [Quit: ceedz]
18:36 -!- ceedz [~eric@187.139.146.65] has joined #bitcoin-wizards
18:40 -!- damethos [~damethos@unaffiliated/damethos] has joined #bitcoin-wizards
18:41 -!- vmatekole [~vmatekole@g230142110.adsl.alicedsl.de] has quit [Remote host closed the connection]
18:51 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
18:51 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
18:54 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has joined #bitcoin-wizards
18:57 -!- pigeons [~pigeons@172.56.5.12] has joined #bitcoin-wizards
18:57 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has quit [Ping timeout: 240 seconds]
19:01 -!- ebfull [~ebfull@c-76-120-40-34.hsd1.co.comcast.net] has joined #bitcoin-wizards
19:06 -!- damethos [~damethos@unaffiliated/damethos] has quit [Quit: Bye]
19:06 -!- zooko [~user@c-75-70-204-109.hsd1.co.comcast.net] has quit [Read error: Connection reset by peer]
19:07 -!- zooko [~user@c-75-70-204-109.hsd1.co.comcast.net] has joined #bitcoin-wizards
19:12 -!- ceedz [~eric@187.139.146.65] has quit [Quit: ceedz]
19:13 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
19:14 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
19:19 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has quit [Read error: Connection reset by peer]
19:20 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has joined #bitcoin-wizards
19:20 -!- skittylx [~skittylx@ks203868.kimsufi.com] has joined #bitcoin-wizards
19:21 -!- ceedz [~eric@187.139.146.65] has joined #bitcoin-wizards
19:22 -!- sneak [~sneak@unaffiliated/sneak] has quit [Ping timeout: 252 seconds]
19:22 -!- sneak [~sneak@unaffiliated/sneak] has joined #bitcoin-wizards
19:23 -!- llllllllll [~lllllllll@6d482698.ftth.concepts.nl] has quit []
19:27 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Ping timeout: 255 seconds]
19:34 -!- ceedz [~eric@187.139.146.65] has quit [Quit: ceedz]
19:36 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
19:36 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
19:39 -!- HaltingState [~HaltingSt@unaffiliated/haltingstate] has quit [Quit: Leaving]
19:44 -!- NewLiberty [~NewLibert@2602:304:cff8:1580:cdbd:393e:aeae:591] has quit [Ping timeout: 265 seconds]
19:51 -!- OneNomos [~OneNomos@pool-71-163-227-3.washdc.east.verizon.net] has quit [Remote host closed the connection]
19:57 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has joined #bitcoin-wizards
20:00 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
20:01 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
20:01 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has quit [Client Quit]
20:02 -!- NewLiberty [~NewLibert@2602:304:cff8:1580:cdbd:393e:aeae:591] has joined #bitcoin-wizards
20:08 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has joined #bitcoin-wizards
20:11 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has quit [Ping timeout: 245 seconds]
20:13 -!- dc17523be3 [unknown@gateway/vpn/mullvad/x-egbvscdqovjsnabf] has quit [Ping timeout: 272 seconds]
20:14 -!- dc17523be3 [~unknown@cpe-66-68-54-206.austin.res.rr.com] has joined #bitcoin-wizards
20:27 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
20:28 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
20:29 -!- dc17523be3 [~unknown@cpe-66-68-54-206.austin.res.rr.com] has quit [Ping timeout: 256 seconds]
20:31 -!- dc17523be3 [~unknown@193.138.219.233] has joined #bitcoin-wizards
20:45 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
20:45 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
20:46 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has quit [Read error: Connection reset by peer]
20:47 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has joined #bitcoin-wizards
20:51 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has joined #bitcoin-wizards
20:53 -!- TheSeven [~quassel@rockbox/developer/TheSeven] has quit [Disconnected by services]
20:53 -!- [7] [~quassel@rockbox/developer/TheSeven] has joined #bitcoin-wizards
20:56 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has joined #bitcoin-wizards
20:57 -!- fac7or [~fac7or@90.193.157.46] has quit []
20:58 -!- copumpkin [~copumpkin@unaffiliated/copumpkin] has joined #bitcoin-wizards
21:00 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has quit [Ping timeout: 256 seconds]
21:01 -!- bramc [~bram@99-75-88-206.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-wizards
21:01 -!- jaekwon [~jaekwon@75-101-96-71.dsl.static.fusionbroadband.com] has joined #bitcoin-wizards
21:02 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
21:03 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
21:04 -!- jaekwon_ [~jaekwon@75-101-96-71.dsl.static.fusionbroadband.com] has quit [Ping timeout: 246 seconds]
21:11 -!- orik [~orik@50-46-132-219.evrt.wa.frontiernet.net] has quit [Ping timeout: 252 seconds]
21:15 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has joined #bitcoin-wizards
21:18 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has quit [Ping timeout: 246 seconds]
21:18 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has joined #bitcoin-wizards
21:21 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
21:22 -!- Dr-G2 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has quit [Ping timeout: 256 seconds]
21:22 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
21:23 -!- espes__ [~espes@205.185.120.132] has quit [Ping timeout: 264 seconds]
21:25 -!- huseby [~huseby@unaffiliated/huseby] has quit [Ping timeout: 265 seconds]
21:25 -!- GreenIsMyPepper [~GreenIsMy@altcoins.are-on-my.ignorelist.com] has quit [Ping timeout: 265 seconds]
21:28 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Quit: .]
21:29 -!- GreenIsMyPepper [~GreenIsMy@altcoins.are-on-my.ignorelist.com] has joined #bitcoin-wizards
21:29 -!- espes__ [~espes@205.185.120.132] has joined #bitcoin-wizards
21:30 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-wizards
21:35 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has quit [Read error: Connection reset by peer]
21:36 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has joined #bitcoin-wizards
21:39 -!- jaekwon [~jaekwon@75-101-96-71.dsl.static.fusionbroadband.com] has quit [Ping timeout: 245 seconds]
21:39 -!- jaekwon_ [~jaekwon@75-101-96-71.dsl.static.fusionbroadband.com] has joined #bitcoin-wizards
21:52 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
21:52 -!- agorist000 [~snizysnaz@68-114-156-198.dhcp.kgpt.tn.charter.com] has joined #bitcoin-wizards
21:52 -!- agorist000 [~snizysnaz@68-114-156-198.dhcp.kgpt.tn.charter.com] has quit [Changing host]
21:52 -!- agorist000 [~snizysnaz@unaffiliated/agorist000] has joined #bitcoin-wizards
21:52 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
21:53 < agorist000> IIRC the new 0.10.0 version uses deterministic signing with libsecp256k1. Is this correct?
21:54 < phantomcircuit> agorist000, yes
21:54 < phantomcircuit> signing but not verification
21:54 < agorist000> Does that mean that the 3rd party TXID malleability problem is solved?
21:55 < phantomcircuit> no
21:56 < agorist000> I see. What else is needed for this to be solved then?
21:56 < gmaxwell> agorist000: thats a complete and total misunderstanding of what malleability and determinstic signing mean.
21:56 < gmaxwell> its unrelated.
21:56 < gmaxwell> determinstic signing does not and cannot make the signatures unique.
21:56 -!- huseby [~huseby@unaffiliated/huseby] has joined #bitcoin-wizards
21:58 < gmaxwell> agorist000: malleability is an intentional feature it cannot be solved without abandoning useful features (like lighthouses' kickstarter transaction);  perhaps you only intend to say unwelcome malleability? thats addressed by BIP 62.
22:00 < agorist000> I see. Thanks for taking the time to explain. I shall have to research further.
22:02 < Luke-Jr> do we need BIP 62 if we end up adding a new OP_CHECKSIG with Joseph's sighash changes?
22:03 -!- skittylx [~skittylx@ks203868.kimsufi.com] has quit [Quit: Bye]
22:06 -!- agorist000 [~snizysnaz@unaffiliated/agorist000] has quit [Ping timeout: 252 seconds]
22:07 -!- gmaxwell [greg@wikimedia/KatWalsh/x-0001] has left #bitcoin-wizards []
22:10 < maaku> Luke-Jr: yes they are mostly unrelated
22:11 < Luke-Jr> implementation-wise, yes; but what does BIP 62 solve that the latter does not?
22:11 < maaku> Joseph's suggestions (if they work... they at minimum require storing more informatino per UTXO than we currently are) are active opt-in
22:11 < maaku> bip 62 are opt-out
22:12 < maaku> and they cover different cases -- e.g. bip 62 doesn't protect against signer malleability, but it does work out of the box for "normal" transactions
22:13 < maaku> whereas Joseph's extensions do protect against signer malleability but are only really usable in certain constructs. they are not generally safe
22:14 -!- moa [~moa@opentransactions/dev/moa] has joined #bitcoin-wizards
22:16 < Luke-Jr> I disagree that BIP62 is any more opt-out..
22:16 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
22:17 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
22:17 < GreenIsMyPepper> Mmm I guess I see BIP 62 as a "nice to have", but it seems to get you convenience more than security? If an output is a single person/address, the receiver can just re-sign.
22:18 < maaku> Luke-Jr: what I meant is that typical use of the bitcoin protocl is protected by malleability by default with bip62. to be vulnerable you have to "opt out" by using different sighash modes for example
22:18 < GreenIsMyPepper> Whereas a normalized sighash flag lets you spend from a mutated transaction with a multisig output, which is when malleability is actively dangerous IMO
22:18 < Luke-Jr> maaku: you first have to opt-in by using v2 txs
22:19 < maaku> Luke-Jr: eh.. so? that's a trivial one line fix for any infrastructure
22:19 < maaku> GreenIsMyPepper: did you see my point about the normalized txid?
22:19 < GreenIsMyPepper> maaku: which point? sorry
22:19 < maaku> there isn't a way to calulate that from the infromation in the UTXO
22:20 < maaku> *the UTXO db
22:20 < Luke-Jr> maaku: current implementation in Bitcoin Core of the UTXO db*
22:20 < GreenIsMyPepper> no you'd need to also include the normalized txid as part of the UTXO
22:20 -!- moa [~moa@opentransactions/dev/moa] has quit [Read error: Connection reset by peer]
22:21  * Luke-Jr still prefers using "hash of the scriptPubKey", which doesn't have any requirement to change UTXO db format
22:21 < maaku> right so at minimum you'd have to upgrade the UTXO db on startup, including re-downloading blocks with unspent txns if pruning is enabled (which is likely to be deployed first...)
22:21 -!- moa [~moa@opentransactions/dev/moa] has joined #bitcoin-wizards
22:22 < GreenIsMyPepper> Luke-Jr: I can understand the argument that people do silly things like reuse addresses, so keeping them from shooting themselves in the foot might make sense, even if that means UTXO size is ~doubled
22:22 < maaku> Luke-Jr: at the cost of not being sufficient if you care about more than just the on output
22:22 < bramc> bip 62 doesn't fix the problem that you can't know a utxo output id until after the transaction has been committed
22:23 < maaku> bramc: for certain transactions it does
22:23 < maaku> if you assume that the signers don't re-sign with a different nonce, of course
22:23 < bramc> maaku, Let me rephrase, until after you know a valid signature for the transaction
22:24 -!- copumpkin [~copumpkin@unaffiliated/copumpkin] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
22:24 < GreenIsMyPepper> maaku: it's not unsolvable. for older transactions the normalized txid can only spend from tx version number above 3, etc.
22:24 < bramc> gmaxwell, How do lighthouse transactions work? The web page doesn't go into much detail.
22:25 < GreenIsMyPepper> but that entails some risk as well for some clients that don't check or download the transactions they're spending (blockchain.info?)
22:25 < maaku> gmaxwell is gone. i angered him. but the search term you might want is "assurance contract"
22:26 < maaku> hearn gave a good talk about it at the 2014 conference too, which hopefully is available online
22:26 < phantomcircuit> bramc, iirc they're basically just anyone can pay
22:27 < maaku> GreenIsMyPepper: it's probably easier and better to just upgrade the db, if this feature is wanted bad enough to be deployed
22:27 < maaku> i just wasn't sure if you had considered this issue
22:29 < GreenIsMyPepper> maaku: Didn't consider blockchain pruning, just older txes, it's a good point.
22:32 < bramc> I'm not quite following how SIGHASH_ANYONECANPAY works
22:33 < maaku> bramc: you dont sign input ids
22:34 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
22:34 < bramc> It seems like in lighthouse, somebody creates a transaction which sends the goal amount to a specific output, and then everybody else adds in bits to act as its inputs
22:34 < GreenIsMyPepper> anyonecanpay means you don't sign any input other than your own
22:34 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
22:35 < bramc> So how are signatures of the other inputs included then? And how do they specify the output?
22:35 -!- arubi [~ese168@unaffiliated/arubi] has quit [Ping timeout: 264 seconds]
22:35 < GreenIsMyPepper> they are included as part of the transaction, the other inputs are not SIGNED as part of your own input signature
22:36 < bramc> But there has to be some signature of the input utxos somewhere to make their spending valid
22:37 < phantomcircuit> bramc, each input signs the outputs
22:37 < phantomcircuit> or something to that effect
22:37 < phantomcircuit> i cant 100% remember
22:37 < GreenIsMyPepper> the signature is included as part of your own input. presume 100 inputs, one of them your own. you sign all outputs and your OWN input, all other inputs are not signed. your signature included as part of the transaction
22:38 < bramc> It seems like the big advantage is that the pledgers can go offline before everything goes through, otherwise there's a lot of round and round with getting the transaction re-signed as you find that some of the inputs have changed
22:39 < GreenIsMyPepper> bramc: this is the most accurate description out there (the stuff in the wiki has some small errors) Page 35: http://enetium.com/resources/Bitcoin.pdf
22:39 -!- NewLiberty [~NewLibert@2602:304:cff8:1580:cdbd:393e:aeae:591] has quit [Ping timeout: 265 seconds]
22:40 < bramc> Thanks GreenIsMyPepper that's a document I should read through in its own right
22:42 < GreenIsMyPepper> np, yeah, the primary value of anyonecanpay in lighthouse afaik is asynchronous transaction creation and an inability to attack by just refusing to sign after tx construction
22:43 < bramc> It seems like the initial bitcoin version was something satoshi had spent quite a bit of time on before releasing it
22:43 < maaku> maybe
22:45 < bramc> The only real hint I've seen to satoshi's identity is that john gilmore was just a liiitle too quick about giving a deep insight in response to the initial post. I suspect he knows who satoshi is.
22:46 < maaku> fyi satoshi speculation is frowned upon here. no good comes of that.
22:46 < bramc> Fair enough, that's all I have to say on the matter anyway
22:48 < bramc> Not sure how I feel about sigtypes. My mental model has mostly had transactions including all inputs and outputs in a single signed entity.
22:49 < bramc> sigtypes feels both overkill for what's actually used right now and underpowered for possible future extension
22:51 < bramc> Anyway, I definitely need to read through the entire developer reference in detail, to make sure I've got everything, and because that's a lot easier than wading through the wiki. At least for me it is, because that's the way my brain works.
22:51 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
22:51 < GreenIsMyPepper> Yeah, exotic sighash combinations are very rarely used. Some seem completely pointless until you think about it for a long time (sighash_none can turn a 2-of-2 into a 1-of-1)
22:51 < GreenIsMyPepper> multisig
22:51 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
22:52 < GreenIsMyPepper> after it hits the blockchain
22:52 < bramc> If you throw in schnorr signatures there isn't clear utility even for multisig, just regular sig, hash preimage, and nlocktime
22:53 < bramc> That first comma should probably have been a period.
22:55 < bramc> Here's the opposite question: Is there any real downside to making everything ANYONECANPAY?
22:56 < bramc> I mean, if you're starting over from scratch
22:57 -!- hearn [~mike@84-75-198-85.dclient.hispeed.ch] has joined #bitcoin-wizards
22:58 < GreenIsMyPepper> You may want to define the person paying. There is a minor side issue that the transaction fees are implicitly defined so by controlling both inputs and outputs you're implicitly writing the transaction fee as part of your signature. With anyonecanpay, the fee is not defined.
22:59 < GreenIsMyPepper> By subtracting inputs minus outputs.
22:59 < bramc> So how do you get the fee with anyonecanpay?
23:00 < GreenIsMyPepper> When you sign an anyonecanpay transaction the transaction fee is not defined, it is effectively set by the last payer
23:00 < GreenIsMyPepper> the last signer, i mean.
23:00 < bramc> So if you overshoot lighthouse the extra all goes to a transaction fee?
23:01 < GreenIsMyPepper> The miners get the extra fees
23:01 < GreenIsMyPepper> miner (no s)
23:02 < GreenIsMyPepper> So if total input is 1.1 BTC and output is 1 BTC, implicitly the transaction fee paid to the miner is 0.1 BTC
23:02 < bramc> Yeah that I understand. That edge case of lighthouse seems suboptimal though
23:02 < GreenIsMyPepper> TBH i don't know how lighthouse solves this.
23:03 < hearn> lighthouse does not let you over-pledge
23:03 < bramc> My suspicion is that it tries to keep everyone from overshooting. That of course has problems with a miner who messes with the transaction making everybody think it's short when it isn't
23:04 < hearn> miners do not have access to the pledge data before the contract is finalised and broadcast
23:04 < bramc> hearn, how does it enforce that?
23:04 < hearn> enforce what?
23:04 < bramc> A miner could participate in the transaction forming and mess with it
23:05 < hearn> "mess with it" how? pledges are typically stored on a server that's co-operating with the project owner. random people cannot simply delete other peoples pedges
23:05 < GreenIsMyPepper> Signatures are not exchanged between participants, only to the project owner?
23:05 < hearn> yes
23:05 -!- hktud0 [~ncidsk@unaffiliated/fluffybunny] has quit [Read error: Connection reset by peer]
23:05 < GreenIsMyPepper> So a zero-fee tx will never get broadcast? ok, makes sense.
23:06 -!- da2ce7_ [~da2ce7@opentransactions/dev/da2ce7] has joined #bitcoin-wizards
23:08 -!- hktud0 [ncidsk@unaffiliated/fluffybunny] has joined #bitcoin-wizards
23:09 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
23:09 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
23:11 < bramc> If you fix malleability properly ANYONECANPAY is a little weird because two different outputs could have nothing differentiating them
23:11 < bramc> Of course, if you don't reuse keys that won't happen...
23:18 -!- Ody10 [~Odysseas@client-8-29.eduroam.oxuni.org.uk] has joined #bitcoin-wizards
23:22 -!- hearn [~mike@84-75-198-85.dclient.hispeed.ch] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
23:27 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
23:28 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
23:31 < GreenIsMyPepper> Depends on what you mean by fixing malleability. For non-chained transactions you use a normalized transaction id by stripping scriptSig, you can't realistically spend from a different output. But yeah, if you strip all input sigs to fix malleability reusing keys can be disastrous.
23:33 < GreenIsMyPepper> Sorry, I meant, strip all input txids to fix malleability to fix malleability reusing keys can lose money.
23:35 < bramc> Depending on how it's implemented it might just result in the later transaction being declared invalid
23:35 < bramc> Because it's redundant
23:36 < bramc> Of course that could also mean that someone could permanently make a transaction non-committable on a reorg, which seems like a bad thing.
23:37 -!- Ody10 [~Odysseas@client-8-29.eduroam.oxuni.org.uk] has quit [Quit: Ody10]
23:37 < GreenIsMyPepper> Yes, using a normalized txid has situations which don't solve malleability in chained transactions and anyonecanpay transactions. Stripping out the input txid entirely can solve it, but entails risks.
23:38 < GreenIsMyPepper> for users that reuse transactions, but should be acceptable for wallets which don't expose bitcoin addresses.
23:38 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaways.net] has quit [Read error: Connection reset by peer]
23:39 -!- Dr-G3 [~Dr-G@gtng-d9bf77a0.pool.mediaWays.net] has joined #bitcoin-wizards
23:41 -!- arubi [~ese168@unaffiliated/arubi] has joined #bitcoin-wizards
23:46 -!- lclc [~lucas@unaffiliated/lclc] has joined #bitcoin-wizards
23:47 < bramc> In the case of one input and one output you might as well have both the input and the output be specified in a single descriptor
23:52 -!- shesek [~shesek@77.127.13.193] has joined #bitcoin-wizards
23:52 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has quit [Read error: Connection timed out]
23:52 < bramc> Okay, here's my thought: The utxo should be specified based on a list of all the inputs and the outputs. The real question is how signatures of the inputs can be combined to validate a transaction
23:53 -!- adam3us [~Adium@host-92-18-107-164.as13285.net] has joined #bitcoin-wizards
23:53 < bramc> So the simplest signature type is to give the whole utxo being signed. Next simplest is to sign its own input and the output and sign that.
23:55 < bramc> So utxos referring to each other directly with no reference to signatures is still the 'right' way to do it, but there has to be some kind of extension mechanism for signatures, or at least something equivalent to supporting anyonecanpay
23:55 < GreenIsMyPepper> Do you mean to use the index position in the utxo instead of txids?
23:56 < GreenIsMyPepper> because then reorgs start to get very messy...
23:57 < sipa> it means you're relying on blockchain functionality to define transaction validity
--- Log closed Sun Mar 01 00:00:08 2015