2015-06-22.log

--- Log opened Mon Jun 22 00:00:48 2015
-!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has quit [Quit: Leaving]00:09
-!- bramc [~bram@99-75-88-206.lightspeed.sntcca.sbcglobal.net] has quit [Quit: This computer has gone to sleep]00:09
-!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 252 seconds]00:11
-!- n0n0_ [~n0n0___@x5f7687b6.dyn.telefonica.de] has joined #bitcoin-wizards00:19
-!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Ping timeout: 264 seconds]00:26
-!- priidu [~priidu@unaffiliated/priidu] has joined #bitcoin-wizards00:27
-!- rht__ [uid86914@gateway/web/irccloud.com/x-hbtnhrnlcydjzjwl] has joined #bitcoin-wizards00:46
-!- jtimon [~quassel@69.29.134.37.dynamic.jazztel.es] has joined #bitcoin-wizards00:58
-!- Aquentin [~Aquentin@cpc13-walt14-2-0-cust31.13-2.cable.virginm.net] has joined #bitcoin-wizards00:59
-!- Aquentin is now known as Guest8657400:59
-!- andy-logbot [~bitcoin--@wpsoftware.net] has quit [Remote host closed the connection]01:03
-!- andy-logbot [~bitcoin--@wpsoftware.net] has joined #bitcoin-wizards01:03
* andy-logbot is logging01:03
-!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards01:06
-!- antanst [~Adium@ppp-2-86-206-246.home.otenet.gr] has left #bitcoin-wizards []01:07
-!- jcluck [~cluckj@pool-108-16-231-242.phlapa.fios.verizon.net] has quit [Read error: Connection reset by peer]01:08
-!- mkarrer [~mkarrer@148.Red-88-8-116.dynamicIP.rima-tde.net] has quit [Read error: Connection reset by peer]01:08
-!- jcluck [~cluckj@pool-108-16-231-242.phlapa.fios.verizon.net] has joined #bitcoin-wizards01:08
-!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-wizards01:08
-!- mkarrer [~mkarrer@148.Red-88-8-116.dynamicIP.rima-tde.net] has joined #bitcoin-wizards01:09
-!- Guest86574 [~Aquentin@cpc13-walt14-2-0-cust31.13-2.cable.virginm.net] has quit [Quit: Leaving]01:09
-!- darwin__ [~darwin@88-103-255-166.jes.cz] has joined #bitcoin-wizards01:09
-!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #bitcoin-wizards01:10
-!- phantomcircuit [~phantomci@smartcontracts.us] has quit [Ping timeout: 250 seconds]01:12
-!- kanzure [~kanzure@unaffiliated/kanzure] has quit [Ping timeout: 250 seconds]01:12
-!- kanzure [~kanzure@unaffiliated/kanzure] has joined #bitcoin-wizards01:13
-!- rubensayshi [~ruben@91.206.81.13] has joined #bitcoin-wizards01:13
-!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Quit: Leaving.]01:15
-!- yossef [~androirc@114.121.154.91] has quit [Ping timeout: 255 seconds]01:15
-!- phantomcircuit [~phantomci@smartcontracts.us] has joined #bitcoin-wizards01:16
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has quit [Ping timeout: 264 seconds]01:18
phantomcircuit<phantomcircuit> petertodd, note that micropayment channels make leaking of the change address significantly less of an issue01:18
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has joined #bitcoin-wizards01:18
-!- dEBRUYNE [~dEBRUYNE@239-196-ftth.onsbrabantnet.nl] has joined #bitcoin-wizards01:31
-!- hearn [~mike@84-75-197-78.dclient.hispeed.ch] has joined #bitcoin-wizards01:36
-!- Quanttek [~quassel@ip1f10af17.dynamic.kabel-deutschland.de] has joined #bitcoin-wizards01:40
-!- CoinMuncher [~jannes@178.132.211.90] has joined #bitcoin-wizards01:41
-!- dEBRUYNE [~dEBRUYNE@239-196-ftth.onsbrabantnet.nl] has quit [Ping timeout: 244 seconds]01:47
-!- hearn [~mike@84-75-197-78.dclient.hispeed.ch] has quit [Read error: Connection reset by peer]01:49
-!- hearn [~mike@84-75-197-78.dclient.hispeed.ch] has joined #bitcoin-wizards01:49
-!- JackH [~Jack@host81-154-202-222.range81-154.btcentralplus.com] has joined #bitcoin-wizards01:50
-!- orperelman [~orperelma@109.67.207.175] has joined #bitcoin-wizards01:53
-!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Quit: Quitte]01:53
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has quit [Ping timeout: 246 seconds]01:54
CodeSharkhow far along are you with the segregated witness thing, sipa?01:55
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has joined #bitcoin-wizards01:55
CodeSharkis there anything I can help you with? :)01:55
-!- cdecker [~cdecker@pc-10367.ethz.ch] has joined #bitcoin-wizards01:57
sipano, it was trivial to implement, it works01:58
sipawe need tests :)01:58
-!- priidu [~priidu@unaffiliated/priidu] has quit [Ping timeout: 252 seconds]02:00
-!- priidu [~priidu@unaffiliated/priidu] has joined #bitcoin-wizards02:02
CodeSharkso you essentially added an extra hash method02:03
CodeSharkyou have four hashes now02:03
CodeSharkhash, hashWitness, hashFull, hashBitcoin02:04
sipathe last one is for compatibility reasons02:05
sipabut essentially, txid = hash of everything except witness data02:05
sipatxidwitness = hash of just witness data02:05
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has quit [Ping timeout: 244 seconds]02:05
sipablocks commit to txidfull = H(txid || txidwitness)02:05
sipabut everything else just uses txid02:06
-!- Quanttek [~quassel@ip1f10af17.dynamic.kabel-deutschland.de] has quit [Ping timeout: 276 seconds]02:06
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has joined #bitcoin-wizards02:06
sipawitness data is scriptsigs, but also the range proofs needed for confidential transactions02:06
sipathey don't change the effect of a transaction, only theit validity02:07
-!- Quanttek [~quassel@2a02:8108:73f:f6e4:e23f:49ff:fe47:9364] has joined #bitcoin-wizards02:07
CodeSharkright02:08
-!- airbreather [~airbreath@d149-67-99-43.nap.wideopenwest.com] has joined #bitcoin-wizards02:08
sipaand since the range proofs are huge, this makes a large difference in the amount of data you need to download02:09
sipaif you do not care for signature validation02:09
CodeSharkyeah, for sure02:09
CodeSharkwe'll eventually want to move to a model where not everyone has to validate everything :)02:10
CodeSharkbut something that actually works, unlike SPV02:10
-!- paveljanik [~paveljani@unaffiliated/paveljanik] has joined #bitcoin-wizards02:10
-!- stonecoldpat [~a9380004@janus-nat-128-240-225-56.ncl.ac.uk] has joined #bitcoin-wizards02:12
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has quit [Ping timeout: 265 seconds]02:12
CodeSharkand something where you CAN validate what's important to you without having to trust the prover02:13
CodeSharkso what you should do then is use H(txid || H(txidwitness))02:14
phantomcircuitCodeShark, tree of hashes of all the things in the transaction02:14
CodeSharkyeah02:14
phantomcircuitdownload/validate only what you care about02:14
CodeSharkexactly02:15
-!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards02:15
CodeSharkI've also been thinking about how to reduce the reorg fragility if we ever want to move to a model where even miners might not validate everything02:19
-!- sparetire_ [~sparetire@unaffiliated/sparetire] has quit [Quit: sparetire_]02:19
CodeSharkin principle, we don't need to revert an entire block just because of one bad transaction02:19
CodeSharkwe can still use the block for PoW02:19
CodeSharkbut just revert all the dependencies of that transaction02:19
sipaamiller had a model a long time ago, where a block could commit to multiple parents, but only one counted for effects; the rest only for pow02:20
sipaand the system's difficulty aimed for a constant not-on-main-chain rate, rather then constant block rate02:21
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has joined #bitcoin-wizards02:22
CodeSharkwhat do you mean by not-on-main-chain rate?02:22
sipait measures the recent percentage of blocks that are in such secondary parents02:22
CodeSharkare we still talking a single blockchain? or multiple blockchains?02:23
sipaone dag02:23
sipawhich defines a chain by following only primary parents02:23
-!- Mably [56401ec5@gateway/web/freenode/ip.86.64.30.197] has quit [Ping timeout: 246 seconds]02:24
CodeSharkstill not sure I fully get it - so the same block is used for both effects and pow but is inserted in multiple parents of this dag?02:25
-!- Mably [56401ec3@gateway/web/freenode/ip.86.64.30.195] has joined #bitcoin-wizards02:26
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has quit [Ping timeout: 264 seconds]02:27
CodeSharkso if the block turns out to be invalid, it is still used for PoW but the effects are voided?02:27
CodeSharkor two separate blocks entirely - one only used for PoW and the other used only for effects?02:28
sipano02:29
sipaevery block has two parents02:29
sipaone from which it inherits utxo state and pow02:29
sipaanother from which it only inheritd pow02:29
sipathe best-pow one with only valid first-parents wins02:30
-!- cdecker [~cdecker@pc-10367.ethz.ch] has quit [Ping timeout: 276 seconds]02:30
-!- cdecker [~cdecker@pc-10367.ethz.ch] has joined #bitcoin-wizards02:30
sipathe utxo set is defined by purely following the first parents up, and these need to be valid02:30
sipathe blocks reachable through non-first parents count for pow, but are otherwise not validated02:31
CodeSharkah, so the objective is to allow miners to create usable blocks without having to validate anything?02:31
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has joined #bitcoin-wizards02:31
CodeSharkdo these PoW-only parents have parents as well?02:32
CodeSharkstill not sure I'm getting it p02:32
sipathey are just blocks02:32
sipaand miners still have to validate everything02:33
sipait is just blocks that would have beenbreorged out in bitcoin02:33
CodeSharkoh, so something more akin to GHOST, in a sense02:33
amillerits not a lot different than GHOST02:33
sipanow become linked into the chain again as such a second parent02:33
-!- hearn [~mike@84-75-197-78.dclient.hispeed.ch] has quit [Read error: Connection reset by peer]02:33
CodeSharkok :)02:33
sipalol02:33
CodeSharkthe pow parents are what some are calling "uncles"02:34
-!- hearn [~mike@84-75-197-78.dclient.hispeed.ch] has joined #bitcoin-wizards02:35
-!- cdecker [~cdecker@pc-10367.ethz.ch] has quit [Ping timeout: 276 seconds]02:35
amilleryes02:36
amillerso the difference is02:36
-!- cdecker [~cdecker@82.130.102.226] has joined #bitcoin-wizards02:36
amillerGHOST has some proposed incentive policy about how much reward the uncles get02:36
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has quit [Ping timeout: 246 seconds]02:36
amillerit's kind of a loose parameter IMO, they don't justify that choice too well.. i think they have an exponential decay thing02:36
amilleralso, in every GHOST proposal I know of, including ethereum's, there's still a fixed minimum-time parameter02:37
amillerso... retrofitting that idea as an extension to GHOST, the point of this thing is to use the GHOST incentives to *tune* the block arrival rate.02:38
amillerno more magic block time number! hooray! defeating a magic parameter is its own reward02:38
CodeSharkso basically narrowing the variance02:39
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has joined #bitcoin-wizards02:39
CodeSharkand not wasting PoW in side chains02:39
amilleryes02:40
amilleri still think thats a good idea but i didn't finish it02:40
amilleralso why should there be any particular fixed fraction02:41
CodeSharkif you can incorporate pooled mining into it as well somehow, even more horray! :)02:42
-!- Mably [56401ec3@gateway/web/freenode/ip.86.64.30.195] has quit [Ping timeout: 246 seconds]02:43
amillerbasically i think people should spam their partial proofs of work as far as they can02:43
CodeSharkyeah02:43
amillersomehow those shares should tolerate a "lossy" network02:44
amillerlike, it's okay if not everyone gets all of those02:44
-!- Mably [56401ec3@gateway/web/freenode/ip.86.64.30.195] has joined #bitcoin-wizards02:44
amillerthe things that are currently really02:44
amillerinfrequent, and worth thousands of dollars, should still propagate everywhere02:45
-!- Tiraspol [~Tiraspol3@unaffiliated/tiraspol] has joined #bitcoin-wizards02:45
amilleri think this is about as well thought out as treechains :O02:45
-!- Tiraspol_ [~Tiraspol3@x5ce0998c.dyn.telefonica.de] has quit [Ping timeout: 272 seconds]02:46
CodeSharkit's a good start of something :)02:47
-!- cdecker [~cdecker@82.130.102.226] has quit [Ping timeout: 276 seconds]02:50
-!- hearn [~mike@84-75-197-78.dclient.hispeed.ch] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]02:51
-!- cdecker [~cdecker@pc-10367.ethz.ch] has joined #bitcoin-wizards02:52
-!- bedeho [~bedeho@195.159.234.190] has quit [Ping timeout: 272 seconds]02:53
CodeSharkhave you gotten as far as modeling anything, amiller?02:53
-!- jmcn [~jamie@2.24.158.30] has quit [Ping timeout: 276 seconds]02:57
-!- jmcn [~jamie@2.24.158.30] has joined #bitcoin-wizards02:58
-!- bedeho [~bedeho@195.159.234.190] has joined #bitcoin-wizards03:00
amilleruh, i remember trying to cram it into the pretty limited set of byzantine generals problem things i knew about, and it didn't work very well03:00
amillersince then, some actual people who know what they're doing in that field modeled the "backbone protocol", and i've also learned to use more abstract tools to talk to cryptographers, like Fblockchain03:03
CodeSharkfblockchain - not sure I'm familiar with that one03:04
-!- jmcn [~jamie@2.24.158.30] has quit [Ping timeout: 277 seconds]03:05
CodeSharkwho are some of these actual people, btw? :)03:05
amillerits kind of an overidealized "proof of publication"... it's a "simulation based definition"03:05
amillerhttps://eprint.iacr.org/2014/76503:06
-!- btcdrak [uid52049@gateway/web/irccloud.com/x-nabfjrkamedlfrit] has joined #bitcoin-wizards03:06
amiller.title03:06
yoleauxCryptology ePrint Archive: Report 2014/76503:06
amilleroh well: The Bitcoin Backbone Protocol: Analysis and Applications. Juan Garay and Aggelos Kiayias and Nikos Leonardos03:06
-!- jmcn [~jamie@2.24.158.30] has joined #bitcoin-wizards03:08
stonecoldpatCodeShark: for f_{blockchain}, i'm guessing amiller is using the terminology that his supervisor used during a presentation to describe the blockchain as a function, https://youtu.be/FQ6Hii69b5U?t=26803:14
CodeSharkah, I see03:15
-!- afk11 [~thomas@46.7.4.219] has joined #bitcoin-wizards03:15
amilleryes! :D also we will release a preprint of that in a couple days or something03:15
-!- Populus [Populus@gateway/vpn/mullvad/x-lenzbkcyfmpxthsf] has joined #bitcoin-wizards03:16
-!- d1ggy [~d1ggy@dslc-082-082-155-231.pools.arcor-ip.net] has joined #bitcoin-wizards03:16
-!- d1ggy_ [~d1ggy@dslb-178-003-120-184.178.003.pools.vodafone-ip.de] has quit [Ping timeout: 265 seconds]03:19
-!- dEBRUYNE [~dEBRUYNE@239-196-ftth.onsbrabantnet.nl] has joined #bitcoin-wizards03:19
CodeSharksipa: no new genesis block for elements alpha?03:23
sipaeh yes there is03:24
sipathe format for blocks is even different03:24
CodeSharkso then it must be somewhere other than chainparams.cpp03:24
sipano?03:25
-!- pavel_ [~paveljani@14.150.broadband14.iol.cz] has joined #bitcoin-wizards03:25
CodeSharkbecause in there I only see the familiar one03:25
CodeSharkor the familiar two, I should say :p03:25
sipaare you looking in the ElementsProject/elements, branch alpha?03:25
CodeSharkThe Times 03/Jan/2009 Chancellor on brink of second bailout for banks03:25
CodeSharkoh, branch alpha03:25
CodeSharkyes03:25
CodeSharkI am03:25
CodeSharkhttps://github.com/ElementsProject/elements/blob/alpha/src/chainparams.cpp03:25
stonecoldpatamiller: awesome looking forward to it03:26
-!- pavel_ [~paveljani@14.150.broadband14.iol.cz] has quit [Client Quit]03:26
sipaCodeShark: perhaps the message wasn't changed03:27
sipabut the serialized format of blocks is different03:27
sipaas it has signatures instead of pow03:27
CodeSharkbut the hash is the same, too :)03:27
CodeShark0x000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f03:27
-!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Ping timeout: 244 seconds]03:28
CodeSharkdid you break sha256, sipa? :)03:28
sipaheh03:31
sipawhat are you looking at?03:31
CodeSharkchainparams.cpp03:31
CodeSharkclass CMainParams03:32
CodeSharkit looks a little bit too familiar ;)03:32
sipalook at testnet03:37
sipathere is no alpha mainnet03:38
sipabut we probably did not remove it from chainparams03:38
CodeSharkok, yeah - CTestNetParams does look a little different03:39
-!- SDCDev [~quassel@unaffiliated/sdcdev] has joined #bitcoin-wizards03:40
-!- prodatalab [~prodatala@2602:306:ceef:a750:577:5919:1b9c:af13] has joined #bitcoin-wizards03:40
CodeSharkso when it runs it just uses testnet...and the --testnet option does nothing?03:40
-!- Netsplit over, joins: cfields03:41
-!- Netsplit *.net <-> *.split quits: ThinThread, rasengan, afk11, adams__, null_rad-, Jaamg, lnovy, Zouppen, Taek, jonasschnelli, (+4 more, use /NETSPLIT to show all of them)03:41
-!- Netsplit over, joins: lnovy03:41
-!- Netsplit over, joins: rasengan03:42
-!- Netsplit over, joins: afk1103:42
-!- tromp [~tromp@ool-18be0b4d.dyn.optonline.net] has joined #bitcoin-wizards03:42
-!- Netsplit over, joins: Luke-Jr03:42
-!- Netsplit over, joins: Taek03:42
CodeSharkthe default datadir needs to be changed as well03:45
-!- adams__ [sid73416@gateway/web/irccloud.com/x-crnvejqpkuszikbh] has joined #bitcoin-wizards03:45
CodeSharkand the pid03:45
-!- catcow [sid62269@gateway/web/irccloud.com/x-chpuajbjcwkdnyow] has joined #bitcoin-wizards03:46
-!- null_radix [Elite7851@gateway/shell/elitebnc/x-zcjbwsuouzbugkvr] has joined #bitcoin-wizards03:47
-!- huseby [~huseby@unaffiliated/huseby] has joined #bitcoin-wizards03:48
-!- jmcn [~jamie@2.24.158.30] has quit [Ping timeout: 276 seconds]03:48
-!- jmcn [~jamie@2.24.158.30] has joined #bitcoin-wizards03:49
-!- jonasschnelli [~jonasschn@2a01:4f8:200:7025::2] has joined #bitcoin-wizards03:51
-!- adam3us1 [~Adium@195.138.228.37] has quit [Ping timeout: 265 seconds]03:55
-!- orperelman [~orperelma@109.67.207.175] has quit [Ping timeout: 276 seconds]03:56
-!- adam3us [~Adium@c3-219.i07-1.onvol.net] has joined #bitcoin-wizards03:57
-!- orperelman [~orperelma@bzq-109-67-207-175.red.bezeqint.net] has joined #bitcoin-wizards03:58
sipaCodeShark: you can run --notestnet, but it will fail if you fo04:05
sipathe datadir should be ~/.bitcoin/alphatestnet304:05
CodeSharkoh, hmmm04:06
CodeSharkI was thinking perhaps it would be a good idea to move it into an entirely separate directory04:07
CodeSharkmakes it harder to corrupt an existing bitcoind installation04:07
CodeSharkthe two databases are diverging quickly, after all - and will be less and less mutually compatible :p04:09
-!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 256 seconds]04:11
CodeSharkand then https://github.com/ElementsProject/elements/blob/alpha/src/util.cpp#L48004:11
-!- _biO_ [~biO_@80.156.183.43] has joined #bitcoin-wizards04:13
-!- jrayhawk_ is now known as jrayhawk04:14
-!- hashtag_ [~hashtag@cpe-69-23-213-3.ma.res.rr.com] has joined #bitcoin-wizards04:17
-!- damethos [~damethos@unaffiliated/damethos] has quit [Remote host closed the connection]04:21
-!- hearn [~mike@79.108.199.178.dynamic.wline.res.cust.swisscom.ch] has joined #bitcoin-wizards04:27
-!- orperelman [~orperelma@bzq-109-67-207-175.red.bezeqint.net] has quit [Read error: No route to host]04:28
CodeSharktime for bed - I'll continue checking it out tomorrow, sipa04:29
-!- orperelman [~orperelma@bzq-109-67-207-175.red.bezeqint.net] has joined #bitcoin-wizards04:30
-!- c0rw|zZz is now known as c0rw1n04:32
-!- SDCDev [~quassel@unaffiliated/sdcdev] has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]04:38
-!- SDCDev [~quassel@unaffiliated/sdcdev] has joined #bitcoin-wizards04:38
-!- wallet42 [~wallet42@88.229.219.239] has quit [Quit: Leaving.]04:41
sipaCodeShark: 'diverging' ?04:43
sipathey're entirely separate, all the time04:43
-!- wallet42 [~wallet42@88.229.219.239] has joined #bitcoin-wizards04:46
-!- bliljerk101 [~bliljerk1@pool-74-109-193-20.pitbpa.fios.verizon.net] has quit [Ping timeout: 248 seconds]04:47
-!- orperelman [~orperelma@bzq-109-67-207-175.red.bezeqint.net] has quit [Ping timeout: 256 seconds]04:50
-!- stonecoldpat [~a9380004@janus-nat-128-240-225-56.ncl.ac.uk] has quit [Quit: Leaving.]04:51
-!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards04:55
-!- SDCDev [~quassel@unaffiliated/sdcdev] has quit [Ping timeout: 276 seconds]04:57
-!- chmod755 [~chmod755@unaffiliated/chmod755] has joined #bitcoin-wizards05:02
-!- lnovy [~lnovy@2002:4d57:f055::1] has quit [Ping timeout: 248 seconds]05:06
-!- lnovy [~lnovy@2002:4d57:f055::1] has joined #bitcoin-wizards05:07
-!- jmcn [~jamie@2.24.158.30] has quit [Ping timeout: 276 seconds]05:10
-!- jmcn [~jamie@2.24.158.30] has joined #bitcoin-wizards05:11
-!- SDCDev [~quassel@unaffiliated/sdcdev] has joined #bitcoin-wizards05:18
-!- SDCDev [~quassel@unaffiliated/sdcdev] has quit [Client Quit]05:18
-!- SDCDev [~quassel@unaffiliated/sdcdev] has joined #bitcoin-wizards05:22
-!- mjerr [~mjerr@p578EAB34.dip0.t-ipconnect.de] has quit [Ping timeout: 250 seconds]05:22
-!- erasmospunk [~erasmospu@179.43.169.226] has joined #bitcoin-wizards05:24
-!- stonecoldpat [~a9380004@janus-nat-128-240-225-56.ncl.ac.uk] has joined #bitcoin-wizards05:27
-!- erasmospunk [~erasmospu@179.43.169.226] has quit [Ping timeout: 244 seconds]05:28
-!- moa [~kiwigb@opentransactions/dev/moa] has quit [Quit: Leaving.]05:29
-!- erasmospunk [~erasmospu@179.43.144.66] has joined #bitcoin-wizards05:39
-!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 246 seconds]05:47
-!- instagibbs [32f65962@gateway/web/freenode/ip.50.246.89.98] has joined #bitcoin-wizards05:48
-!- hearn [~mike@79.108.199.178.dynamic.wline.res.cust.swisscom.ch] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]05:53
-!- droark [~droark@209-6-53-207.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com] has joined #bitcoin-wizards05:59
-!- cdecker [~cdecker@pc-10367.ethz.ch] has quit [Ping timeout: 275 seconds]06:06
-!- cdecker [~cdecker@pc-10367.ethz.ch] has joined #bitcoin-wizards06:06
-!- pollux-bts [uid52270@gateway/web/irccloud.com/x-hcjzxsdttbtkpezw] has joined #bitcoin-wizards06:09
-!- instagibbs [32f65962@gateway/web/freenode/ip.50.246.89.98] has quit [Quit: Page closed]06:12
-!- SDCDev [~quassel@unaffiliated/sdcdev] has quit [Ping timeout: 256 seconds]06:14
-!- p15x [~p15x@182.50.108.35] has joined #bitcoin-wizards06:16
-!- p15x_ [~p15x@182.50.108.81] has joined #bitcoin-wizards06:19
-!- p15x [~p15x@182.50.108.35] has quit [Ping timeout: 256 seconds]06:21
-!- antanst [~Adium@ppp-2-86-206-246.home.otenet.gr] has joined #bitcoin-wizards06:21
-!- antanst [~Adium@ppp-2-86-206-246.home.otenet.gr] has left #bitcoin-wizards []06:21
-!- eudoxia [~eudoxia@r167-57-170-84.dialup.adsl.anteldata.net.uy] has joined #bitcoin-wizards06:22
-!- p15x_ [~p15x@182.50.108.81] has quit [Client Quit]06:23
-!- p15x [~p15x@182.50.108.81] has joined #bitcoin-wizards06:23
-!- paveljanik [~paveljani@unaffiliated/paveljanik] has joined #bitcoin-wizards06:30
-!- orperelman [~orperelma@bzq-109-67-207-175.red.bezeqint.net] has joined #bitcoin-wizards06:32
-!- erasmospunk [~erasmospu@179.43.144.66] has quit [Ping timeout: 250 seconds]06:34
-!- erasmospunk [~erasmospu@gateway/vpn/privateinternetaccess/erasmospunk] has joined #bitcoin-wizards06:36
-!- StephenM347 [~stephenm3@static-64-223-246-218.port.east.myfairpoint.net] has joined #bitcoin-wizards06:38
-!- erasmosp_ [~erasmospu@gateway/vpn/privateinternetaccess/erasmospunk] has joined #bitcoin-wizards06:40
-!- erasmospunk [~erasmospu@gateway/vpn/privateinternetaccess/erasmospunk] has quit [Ping timeout: 252 seconds]06:42
-!- Aquentin [~Aquentin@unaffiliated/aquentin] has joined #bitcoin-wizards06:45
-!- p15x_ [~p15x@182.50.108.107] has joined #bitcoin-wizards06:47
-!- p15x [~p15x@182.50.108.81] has quit [Ping timeout: 276 seconds]06:49
-!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-wizards06:49
-!- mountaingoat [~mountaing@unaffiliated/mountaingoat] has quit [Ping timeout: 255 seconds]06:50
-!- SDCDev [~quassel@unaffiliated/sdcdev] has joined #bitcoin-wizards06:59
-!- AndroUser2 [~androirc@180.252.72.109] has joined #bitcoin-wizards07:01
-!- temujin [~temujin@38.121.165.30] has joined #bitcoin-wizards07:02
-!- SDCDev [~quassel@unaffiliated/sdcdev] has quit [Client Quit]07:03
-!- cdecker [~cdecker@pc-10367.ethz.ch] has quit [Ping timeout: 276 seconds]07:03
-!- cdecker [~cdecker@pc-10367.ethz.ch] has joined #bitcoin-wizards07:05
-!- stonecoldpat [~a9380004@janus-nat-128-240-225-56.ncl.ac.uk] has quit [Quit: Leaving.]07:06
-!- SDCDev [~quassel@unaffiliated/sdcdev] has joined #bitcoin-wizards07:06
-!- orperelman [~orperelma@bzq-109-67-207-175.red.bezeqint.net] has quit [Ping timeout: 256 seconds]07:06
-!- orperelman [~orperelma@bzq-109-67-207-175.red.bezeqint.net] has joined #bitcoin-wizards07:07
-!- stonecoldpat [~a9380004@janus-nat-128-240-225-56.ncl.ac.uk] has joined #bitcoin-wizards07:10
-!- hashtagg_ [~hashtag@cpe-69-23-213-3.ma.res.rr.com] has joined #bitcoin-wizards07:11
-!- orperelman [~orperelma@bzq-109-67-207-175.red.bezeqint.net] has quit [Ping timeout: 252 seconds]07:11
-!- hashtag_ [~hashtag@cpe-69-23-213-3.ma.res.rr.com] has quit [Ping timeout: 246 seconds]07:11
-!- damethos [~damethos@unaffiliated/damethos] has joined #bitcoin-wizards07:16
-!- Madars [~null@unaffiliated/madars] has quit [Read error: Connection reset by peer]07:17
-!- Madars [~null@unaffiliated/madars] has joined #bitcoin-wizards07:18
-!- jmcn [~jamie@2.24.158.30] has quit [Ping timeout: 277 seconds]07:19
-!- jmcn [~jamie@2.24.158.30] has joined #bitcoin-wizards07:19
-!- eudoxia_ [~eudoxia@r167-57-17-47.dialup.adsl.anteldata.net.uy] has joined #bitcoin-wizards07:21
-!- eudoxia_ [~eudoxia@r167-57-17-47.dialup.adsl.anteldata.net.uy] has quit [Read error: Connection reset by peer]07:22
-!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has joined #bitcoin-wizards07:22
-!- b_lumenkraft [~b_lumenkr@unaffiliated/b-lumenkraft/x-4457406] has joined #bitcoin-wizards07:23
-!- eudoxia_ [~eudoxia@r167-57-17-47.dialup.adsl.anteldata.net.uy] has joined #bitcoin-wizards07:23
-!- eudoxia_ [~eudoxia@r167-57-17-47.dialup.adsl.anteldata.net.uy] has quit [Remote host closed the connection]07:23
-!- eudoxia [~eudoxia@r167-57-170-84.dialup.adsl.anteldata.net.uy] has quit [Ping timeout: 264 seconds]07:25
-!- eudoxia [~eudoxia@r167-57-17-47.dialup.adsl.anteldata.net.uy] has joined #bitcoin-wizards07:26
-!- jmcn [~jamie@2.24.158.30] has quit [Ping timeout: 276 seconds]07:28
-!- jmcn [~jamie@2.24.158.30] has joined #bitcoin-wizards07:28
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has quit [Ping timeout: 276 seconds]07:29
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has joined #bitcoin-wizards07:29
-!- davi [~davi@gnu/davi] has joined #bitcoin-wizards07:30
-!- p15x_ [~p15x@182.50.108.107] has quit [Ping timeout: 256 seconds]07:30
-!- p15x [~p15x@111.193.161.178] has joined #bitcoin-wizards07:30
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has quit [Ping timeout: 265 seconds]07:35
-!- CoinMuncher [~jannes@178.132.211.90] has quit [Ping timeout: 250 seconds]07:37
-!- bramc [~bram@99-75-88-206.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-wizards07:38
-!- jmcn [~jamie@2.24.158.30] has quit [Ping timeout: 276 seconds]07:43
-!- CoinMuncher [~jannes@178.132.211.90] has joined #bitcoin-wizards07:45
-!- temujin [~temujin@38.121.165.30] has quit [Quit: temujin]07:46
-!- temujin [~temujin@38.121.165.30] has joined #bitcoin-wizards07:46
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has joined #bitcoin-wizards07:47
-!- jmcn [~jamie@2.24.158.30] has joined #bitcoin-wizards07:49
bramcBecause the subject hasn't been done to death already: https://medium.com/@bramcohen/bitcoin-s-ironic-crisis-32226a85e39f07:58
-!- jgarzik [~jgarzik@unaffiliated/jgarzik] has quit [Quit: This computer has gone to sleep]07:58
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has quit [Ping timeout: 244 seconds]07:59
chmod755"principles on which Bitcoin was founded".........08:00
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has joined #bitcoin-wizards08:02
-!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards08:02
-!- spinza [~spin@197.89.39.101] has quit [Excess Flood]08:04
-!- nwilcox [~nwilcox@74-95-207-205-SFBA.hfc.comcastbusiness.net] has joined #bitcoin-wizards08:05
-!- SDCDev [~quassel@unaffiliated/sdcdev] has quit [Ping timeout: 256 seconds]08:06
-!- Giszmo [~leo@pc-185-201-214-201.cm.vtr.net] has joined #bitcoin-wizards08:07
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has quit [Ping timeout: 276 seconds]08:07
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has joined #bitcoin-wizards08:08
-!- spinza [~spin@197.89.39.101] has joined #bitcoin-wizards08:09
-!- DougieBot5000_ [~DougieBot@unaffiliated/dougiebot5000] has joined #bitcoin-wizards08:09
-!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has quit [Killed (wolfe.freenode.net (Nickname regained by services))]08:10
-!- DougieBot5000_ is now known as DougieBot500008:10
-!- zooko [~user@2601:281:8101:3c71:40d1:c44c:ba43:df6b] has joined #bitcoin-wizards08:10
-!- austinhill [~Adium@bas1-montreal43-1177755675.dsl.bell.ca] has joined #bitcoin-wizards08:11
-!- jmcn [~jamie@2.24.158.30] has quit [Ping timeout: 276 seconds]08:11
-!- jmcn [~jamie@2.24.158.30] has joined #bitcoin-wizards08:17
-!- Giszmo [~leo@pc-185-201-214-201.cm.vtr.net] has quit [Read error: Connection timed out]08:18
-!- Giszmo [~leo@pc-185-201-214-201.cm.vtr.net] has joined #bitcoin-wizards08:19
-!- ThinThread [~far@onegrandcircle.com] has joined #bitcoin-wizards08:21
-!- temujin [~temujin@38.121.165.30] has left #bitcoin-wizards []08:23
-!- temujin [~temujin@38.121.165.30] has joined #bitcoin-wizards08:24
-!- lnsybrd [~lnsybrd@fwsm-io-azp-dmz.phx1.ip.io.com] has joined #bitcoin-wizards08:24
-!- temujin [~temujin@38.121.165.30] has quit [Client Quit]08:26
-!- temujin [~temujin@38.121.165.30] has joined #bitcoin-wizards08:26
-!- fragzle [~fr4ggs@li578-62.members.linode.com] has joined #bitcoin-wizards08:27
-!- c0rw1n is now known as c0rw|away08:28
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has quit [Ping timeout: 248 seconds]08:29
-!- _biO__ [~biO_@ip-37-24-195-112.hsi14.unitymediagroup.de] has joined #bitcoin-wizards08:29
-!- airbreather [~airbreath@d149-67-99-43.nap.wideopenwest.com] has quit [Remote host closed the connection]08:31
-!- rubensayshi [~ruben@91.206.81.13] has quit [Ping timeout: 252 seconds]08:33
-!- zmanian [~zmanian@c-24-5-125-31.hsd1.ca.comcast.net] has quit [Ping timeout: 256 seconds]08:37
-!- binaryFate [~binaryFat@94.139.57.106] has joined #bitcoin-wizards08:38
-!- eudoxia [~eudoxia@r167-57-17-47.dialup.adsl.anteldata.net.uy] has quit [Quit: Leaving]08:40
-!- eudoxia [~eudoxia@r167-57-17-47.dialup.adsl.anteldata.net.uy] has joined #bitcoin-wizards08:40
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has joined #bitcoin-wizards08:41
-!- hearn [~mike@79.108.199.178.dynamic.wline.res.cust.swisscom.ch] has joined #bitcoin-wizards08:42
-!- jb55 [~jb55@208.98.200.100] has joined #bitcoin-wizards08:42
-!- priidu [~priidu@unaffiliated/priidu] has quit [Ping timeout: 255 seconds]08:44
-!- cdecker [~cdecker@pc-10367.ethz.ch] has quit [Ping timeout: 276 seconds]08:46
-!- cdecker [~cdecker@pc-10367.ethz.ch] has joined #bitcoin-wizards08:48
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has quit [Ping timeout: 256 seconds]08:52
-!- jmcn [~jamie@2.24.158.30] has quit [Ping timeout: 276 seconds]08:56
-!- jmcn [~jamie@2.24.158.30] has joined #bitcoin-wizards08:56
-!- antanst [~Adium@37.6.195.164] has joined #bitcoin-wizards08:56
-!- MrTratta [~MrTratta@2.228.102.98] has joined #bitcoin-wizards09:04
-!- davi [~davi@gnu/davi] has quit [Ping timeout: 246 seconds]09:05
-!- cdecker [~cdecker@pc-10367.ethz.ch] has quit [Ping timeout: 272 seconds]09:06
-!- spinza [~spin@197.89.39.101] has quit [Ping timeout: 276 seconds]09:06
-!- MrTratta [~MrTratta@2.228.102.98] has quit [Ping timeout: 276 seconds]09:13
-!- wallet421 [~wallet42@88.229.219.239] has joined #bitcoin-wizards09:13
-!- wallet421 [~wallet42@88.229.219.239] has quit [Changing host]09:13
-!- wallet421 [~wallet42@unaffiliated/wallet42] has joined #bitcoin-wizards09:13
-!- wallet42 is now known as Guest914909:13
-!- Guest9149 [~wallet42@88.229.219.239] has quit [Killed (sendak.freenode.net (Nickname regained by services))]09:13
-!- wallet421 is now known as wallet4209:13
-!- MrTratta [~MrTratta@2-228-102-98.ip191.fastwebnet.it] has joined #bitcoin-wizards09:13
-!- shen_noe [~shen_noe@wired042.math.utah.edu] has joined #bitcoin-wizards09:15
-!- davi [~davi@gnu/davi] has joined #bitcoin-wizards09:17
-!- Cory [~Cory@unaffiliated/cory] has quit [Ping timeout: 264 seconds]09:19
-!- sy5error [~sy5error@unaffiliated/sy5error] has joined #bitcoin-wizards09:20
-!- Pasha [~Cory@unaffiliated/cory] has joined #bitcoin-wizards09:20
-!- AndroUser2 [~androirc@180.252.72.109] has quit [Remote host closed the connection]09:21
-!- cdecker [~cdecker@82.130.102.226] has joined #bitcoin-wizards09:24
-!- kmels [~kmels@186.64.110.122] has joined #bitcoin-wizards09:25
-!- gill3s [~gill3s@pat35-3-82-245-143-153.fbx.proxad.net] has quit [Quit: My Mac has gone to sleep. ZZZzzz…]09:27
-!- Pasha is now known as Cory09:27
-!- JackH [~Jack@host81-154-202-222.range81-154.btcentralplus.com] has quit [Ping timeout: 244 seconds]09:27
-!- lnsybrd [~lnsybrd@fwsm-io-azp-dmz.phx1.ip.io.com] has quit [Quit: lnsybrd]09:32
-!- Mably [56401ec3@gateway/web/freenode/ip.86.64.30.195] has quit [Quit: Page closed]09:32
-!- blablaa [~st4fdds@unaffiliated/blablaa] has joined #bitcoin-wizards09:34
blablaaare there some altcoins working entirely using tx fees?09:35
sipadid you use 'altcoins' and 'working' in the same sentence?09:35
blablaasipa, well yes...09:36
sipathere are a few who have done interesting development, but they are a very small minority09:36
sipaalso, offtopic here09:36
blablaasipa, it's related to bitcoin because bitcoin as it is is supposed to be funded by tx fees in the future09:37
sipablablaa: that is a controversial position09:37
blablaasipa, i'm wondering if fees will stay sufficiently high without a strict cap on block size. i know all this is controversial, but it's also interesting, so i'm throwing the question here.09:39
zookoblablaa: I think your question is a good one.09:40
zookoblablaa: I think the answer to it is: the evidence from altcoins so far doesn't tell us.09:40
sipaagree with zooko09:40
-!- gill3s [~gill3s@pat35-3-82-245-143-153.fbx.proxad.net] has joined #bitcoin-wizards09:41
-!- Burrito [~Burrito@unaffiliated/burrito] has joined #bitcoin-wizards09:41
-!- Emcy_ [~MC@cpc3-swan1-0-0-cust996.7-3.cable.virginm.net] has joined #bitcoin-wizards09:42
-!- Emcy_ [~MC@cpc3-swan1-0-0-cust996.7-3.cable.virginm.net] has quit [Changing host]09:42
-!- Emcy_ [~MC@unaffiliated/mc1984] has joined #bitcoin-wizards09:42
blablaazooko, ok, thx for your answer, i'll wait for more answers :)09:43
-!- Emcy [~MC@unaffiliated/mc1984] has quit [Ping timeout: 276 seconds]09:45
bramcThe current transaction rate in altcoins seems unlikely to be able to keep things stable based on transaction fees alone09:46
sipayes, you need a simulation of an economy for that09:47
sipablablaa: also, apologies, i thought we were on #bitcoin-dev09:47
zookosipa: Oh, I was wondering about that. So this topic *is* on topic here?09:47
sipai would say so09:47
zookoCool.09:47
sipapeople talk about (interesting) changes to bitcoin all the time here, including those implemented in altcoins09:48
tromp_this could be called bitcoin-fantasies :)09:48
zookolol09:48
-!- jmcn [~jamie@2.24.158.30] has quit [Ping timeout: 276 seconds]09:48
-!- elastoma [~elastoma@162.248.160.175] has quit [Ping timeout: 276 seconds]09:49
-!- jmcn [~jamie@2.24.158.30] has joined #bitcoin-wizards09:49
-!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 252 seconds]09:49
-!- damethos [~damethos@unaffiliated/damethos] has quit [Quit: Bye]09:50
-!- tucenaber [~tucenaber@unaffiliated/tucenaber] has quit [Remote host closed the connection]09:51
-!- lnsybrd [~lnsybrd@72.44.238.238] has joined #bitcoin-wizards09:51
-!- erasmosp_ [~erasmospu@gateway/vpn/privateinternetaccess/erasmospunk] has quit [Quit: ttm]09:54
-!- erasmospunk [~erasmospu@gateway/vpn/privateinternetaccess/erasmospunk] has joined #bitcoin-wizards09:54
-!- gill3s [~gill3s@pat35-3-82-245-143-153.fbx.proxad.net] has quit [Quit: My Mac has gone to sleep. ZZZzzz…]09:55
adam3usbramc: note in your medium post gavin's latest proposal ses blocks auto-growing from 8MB to 8GB in 2x increments on a biennial schedule.09:56
-!- mjerr [~mjerr@p578EAB34.dip0.t-ipconnect.de] has joined #bitcoin-wizards09:56
kanzure"Eventually the two currencies will be completely separated and peacefully coexist," this is not always going to be the outcome, especially if people lose tremendous amounts of BTC during the transition (or when software is spending to the wrong addresses on the worng blockchains, etc.)09:57
adam3usbramc: not that that is necessarily any better. effect i shard to predict but if understand the intent is to subsidise fees to something approximating effectively free fees for foreseeable future09:58
-!- Mably [~Mably@unaffiliated/mably] has joined #bitcoin-wizards09:58
adam3usbramc: wow that text got mangled some how!09:58
bramcadam3us, I'm trying to word what I'm saying carefully to not be accused of misrepresenting what somebody else says. I included some comments about gavin's latest proposal being even more extreme and him saying specifically that he's doing it because of people arguing with him originally but removed them because it sounded a bit personal09:59
adam3usbramc: try again.  not that that is necessarily any better. the effect is hard to predict, but if understand Gavin's intent, he aims to subsidise fees so that there are effectively free fees for the foreseeable future09:59
-!- wallet42 [~wallet42@unaffiliated/wallet42] has quit [Quit: Leaving.]09:59
bramcadam3us, I'm going to write another essay later about the long term effects of all this stuff, I'll include all that thinking in there10:00
adam3usbramc: fair enough.  thanks for writing anyway - for some reason the tech news seems to focus on some confusion that industry wants this or that gavin is lead developer and other things.10:00
bramc(because, apparently, there isn't enough stress in my life, so I'm proactively delving into bitcoin)10:00
-!- goregrind [~goregrind@unaffiliated/goregrind] has quit [Ping timeout: 252 seconds]10:00
bramcThanks for the props, adam3us10:00
-!- nwilcox_ [~nwilcox@74-95-207-205-SFBA.hfc.comcastbusiness.net] has joined #bitcoin-wizards10:01
bramcI've gotta run now, laters everybody10:01
-!- bramc [~bram@99-75-88-206.lightspeed.sntcca.sbcglobal.net] has quit [Quit: Leaving]10:01
-!- jmcn [~jamie@2.24.158.30] has quit [Ping timeout: 276 seconds]10:02
-!- jmcn [~jamie@2.24.158.30] has joined #bitcoin-wizards10:02
-!- nwilcox [~nwilcox@74-95-207-205-SFBA.hfc.comcastbusiness.net] has quit [Ping timeout: 256 seconds]10:04
-!- dEBRUYNE [~dEBRUYNE@239-196-ftth.onsbrabantnet.nl] has quit [Ping timeout: 255 seconds]10:04
-!- nwilcox [~nwilcox@74-95-207-205-SFBA.hfc.comcastbusiness.net] has joined #bitcoin-wizards10:06
-!- nwilcox_ [~nwilcox@74-95-207-205-SFBA.hfc.comcastbusiness.net] has quit [Ping timeout: 252 seconds]10:06
-!- priidu [~priidu@unaffiliated/priidu] has joined #bitcoin-wizards10:07
-!- wallet42 [~wallet42@88.229.219.239] has joined #bitcoin-wizards10:08
-!- wallet42 [~wallet42@88.229.219.239] has quit [Client Quit]10:09
-!- wallet42 [~wallet42@88.229.219.239] has joined #bitcoin-wizards10:10
-!- elastoma [~elastoma@162.248.160.175] has joined #bitcoin-wizards10:11
-!- bliljerk101 [~bliljerk1@pool-74-109-193-20.pitbpa.fios.verizon.net] has joined #bitcoin-wizards10:11
-!- n0n0_ [~n0n0___@x5f7687b6.dyn.telefonica.de] has quit [Ping timeout: 256 seconds]10:12
-!- wallet42 [~wallet42@88.229.219.239] has quit [Client Quit]10:13
-!- damethos [~damethos@unaffiliated/damethos] has joined #bitcoin-wizards10:16
-!- wallet42 [~wallet42@88.229.219.239] has joined #bitcoin-wizards10:16
-!- Emcy_ [~MC@unaffiliated/mc1984] has quit [Ping timeout: 255 seconds]10:16
-!- goregrind [~goregrind@89.137.127.229] has joined #bitcoin-wizards10:17
-!- goregrind [~goregrind@89.137.127.229] has quit [Changing host]10:17
-!- goregrind [~goregrind@unaffiliated/goregrind] has joined #bitcoin-wizards10:17
-!- gill3s [~gill3s@pat35-3-82-245-143-153.fbx.proxad.net] has joined #bitcoin-wizards10:18
-!- damethos [~damethos@unaffiliated/damethos] has quit [Ping timeout: 255 seconds]10:20
-!- gill3s [~gill3s@pat35-3-82-245-143-153.fbx.proxad.net] has quit [Quit: My Mac has gone to sleep. ZZZzzz…]10:24
-!- binaryFate [~binaryFat@94.139.57.106] has quit [Ping timeout: 255 seconds]10:27
-!- Emcy [~MC@cpc3-swan1-0-0-cust996.7-3.cable.virginm.net] has joined #bitcoin-wizards10:28
-!- Emcy [~MC@cpc3-swan1-0-0-cust996.7-3.cable.virginm.net] has quit [Changing host]10:28
-!- Emcy [~MC@unaffiliated/mc1984] has joined #bitcoin-wizards10:28
-!- wallet42 [~wallet42@88.229.219.239] has quit [Quit: Leaving.]10:29
-!- wallet42 [~wallet42@88.229.219.239] has joined #bitcoin-wizards10:30
-!- shen_noe [~shen_noe@wired042.math.utah.edu] has quit [Remote host closed the connection]10:31
-!- shen_noe [~shen_noe@wired042.math.utah.edu] has joined #bitcoin-wizards10:33
-!- wallet42 [~wallet42@88.229.219.239] has quit [Read error: Connection reset by peer]10:34
-!- wallet42 [~wallet42@88.229.219.239] has joined #bitcoin-wizards10:34
-!- blablaa [~st4fdds@unaffiliated/blablaa] has quit [Quit: Sto andando via]10:35
-!- erasmosp_ [~erasmospu@gateway/vpn/privateinternetaccess/erasmospunk] has joined #bitcoin-wizards10:35
-!- erasmospunk [~erasmospu@gateway/vpn/privateinternetaccess/erasmospunk] has quit [Ping timeout: 276 seconds]10:36
-!- JackH [~Jack@host-80-43-142-154.as13285.net] has joined #bitcoin-wizards10:37
-!- jgarzik [~jgarzik@unaffiliated/jgarzik] has joined #bitcoin-wizards10:38
-!- dEBRUYNE [~dEBRUYNE@239-196-ftth.onsbrabantnet.nl] has joined #bitcoin-wizards10:39
-!- erasmosp_ [~erasmospu@gateway/vpn/privateinternetaccess/erasmospunk] has quit [Quit: ttm]10:41
-!- erasmospunk [~erasmospu@gateway/vpn/privateinternetaccess/erasmospunk] has joined #bitcoin-wizards10:41
-!- wallet42 [~wallet42@88.229.219.239] has quit [Quit: Leaving.]10:42
-!- wallet42 [~wallet42@88.229.219.239] has joined #bitcoin-wizards10:43
-!- lnsybrd [~lnsybrd@72.44.238.238] has quit [Quit: lnsybrd]10:43
-!- GAit [~lnahum@2-230-161-158.ip202.fastwebnet.it] has joined #bitcoin-wizards10:43
-!- hearn [~mike@79.108.199.178.dynamic.wline.res.cust.swisscom.ch] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]10:46
-!- jaekwon [~jae@2601:645:8001:f5c8:dcd4:830:a4df:e259] has joined #bitcoin-wizards10:46
-!- wallet42 [~wallet42@88.229.219.239] has quit [Client Quit]10:46
-!- wallet42 [~wallet42@88.229.219.239] has joined #bitcoin-wizards10:47
-!- jmcn [~jamie@2.24.158.30] has quit [Ping timeout: 275 seconds]10:47
-!- cdecker [~cdecker@82.130.102.226] has quit [Ping timeout: 275 seconds]10:47
-!- jmcn [~jamie@2.24.158.30] has joined #bitcoin-wizards10:47
-!- eudoxia [~eudoxia@r167-57-17-47.dialup.adsl.anteldata.net.uy] has quit [Quit: Leaving]10:47
heathdid discussion die down in the mailing list or all the messages ping requests / test messages10:48
heathor +are all the...10:48
-!- cdecker [~cdecker@pc-10367.ethz.ch] has joined #bitcoin-wizards10:48
-!- lnsybrd [~lnsybrd@72.44.238.238] has joined #bitcoin-wizards10:51
-!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards10:52
-!- wallet42 [~wallet42@88.229.219.239] has quit [Quit: Leaving.]10:53
-!- hashtag_ [~hashtagg_@cpe-69-23-213-3.ma.res.rr.com] has joined #bitcoin-wizards10:54
-!- antanst [~Adium@37.6.195.164] has left #bitcoin-wizards []10:55
-!- jgarzik [~jgarzik@unaffiliated/jgarzik] has quit [Quit: This computer has gone to sleep]10:56
-!- hashtag [~hashtagg_@cpe-69-23-213-3.ma.res.rr.com] has quit [Ping timeout: 244 seconds]10:56
-!- jgarzik [~jgarzik@unaffiliated/jgarzik] has joined #bitcoin-wizards10:57
-!- jgarzik [~jgarzik@unaffiliated/jgarzik] has quit [Client Quit]10:57
-!- stonecoldpat [~a9380004@janus-nat-128-240-225-56.ncl.ac.uk] has quit [Quit: Leaving.]10:58
-!- jmcn [~jamie@2.24.158.30] has quit [Ping timeout: 276 seconds]11:00
-!- jmcn [~jamie@2.24.158.30] has joined #bitcoin-wizards11:01
-!- adam3us [~Adium@c3-219.i07-1.onvol.net] has left #bitcoin-wizards []11:01
-!- nwilcox [~nwilcox@74-95-207-205-SFBA.hfc.comcastbusiness.net] has quit [Quit: leaving]11:04
-!- jcluck [~cluckj@pool-108-16-231-242.phlapa.fios.verizon.net] has quit [Quit: Leaving]11:04
-!- p15x [~p15x@111.193.161.178] has quit [Max SendQ exceeded]11:09
-!- p15x [~p15x@111.193.161.178] has joined #bitcoin-wizards11:10
-!- mountaingoat [~mountaing@unaffiliated/mountaingoat] has joined #bitcoin-wizards11:16
-!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 255 seconds]11:18
-!- spinza [~spin@197.89.24.164] has joined #bitcoin-wizards11:22
-!- lnsybrd [~lnsybrd@72.44.238.238] has quit [Quit: lnsybrd]11:22
-!- CoinMuncher [~jannes@178.132.211.90] has quit [Quit: Leaving.]11:22
-!- erasmospunk [~erasmospu@gateway/vpn/privateinternetaccess/erasmospunk] has quit [Remote host closed the connection]11:30
-!- erasmospunk [~erasmospu@gateway/vpn/privateinternetaccess/erasmospunk] has joined #bitcoin-wizards11:30
-!- jgarzik [~jgarzik@207.140.24.78] has joined #bitcoin-wizards11:32
-!- jgarzik [~jgarzik@207.140.24.78] has quit [Changing host]11:32
-!- jgarzik [~jgarzik@unaffiliated/jgarzik] has joined #bitcoin-wizards11:32
-!- erasmospunk [~erasmospu@gateway/vpn/privateinternetaccess/erasmospunk] has quit [Ping timeout: 244 seconds]11:35
* heath finally sees acitivity beyond ping requests \o/11:35
-!- erasmospunk [~erasmospu@lw.serv66.quikefall.com] has joined #bitcoin-wizards11:37
-!- cosmo [~james@unaffiliated/cosmo] has joined #bitcoin-wizards11:41
-!- cdecker [~cdecker@pc-10367.ethz.ch] has quit [Ping timeout: 276 seconds]11:42
-!- lnsybrd [~lnsybrd@fwsm-io-azp-dmz.phx1.ip.io.com] has joined #bitcoin-wizards11:42
-!- cdecker [~cdecker@pc-10367.ethz.ch] has joined #bitcoin-wizards11:42
-!- shen_noe [~shen_noe@wired042.math.utah.edu] has quit [Remote host closed the connection]11:42
-!- getplank [~getplank@65.88.88.203] has joined #bitcoin-wizards11:44
-!- erasmospunk [~erasmospu@lw.serv66.quikefall.com] has quit [Remote host closed the connection]11:45
-!- tcrypt [~tylersmit@173.247.206.110] has joined #bitcoin-wizards11:45
-!- erasmospunk [~erasmospu@lw.serv66.quikefall.com] has joined #bitcoin-wizards11:45
-!- shen_noe [~shen_noe@wired042.math.utah.edu] has joined #bitcoin-wizards11:46
-!- Xh1pher [~Xh1pher@pD9E38632.dip0.t-ipconnect.de] has quit [Read error: Connection reset by peer]11:46
-!- erasmospunk [~erasmospu@lw.serv66.quikefall.com] has quit [Ping timeout: 256 seconds]11:50
-!- davi [~davi@gnu/davi] has quit [Ping timeout: 246 seconds]11:55
-!- cdecker [~cdecker@pc-10367.ethz.ch] has quit [Ping timeout: 277 seconds]11:57
-!- cdecker [~cdecker@pc-10367.ethz.ch] has joined #bitcoin-wizards12:03
-!- qawap_ is now known as qawap12:05
-!- cdecker [~cdecker@pc-10367.ethz.ch] has quit [Write error: Broken pipe]12:11
-!- cdecker [~cdecker@pc-10367.ethz.ch] has joined #bitcoin-wizards12:12
-!- cdecker [~cdecker@pc-10367.ethz.ch] has quit [Ping timeout: 276 seconds]12:17
-!- cdecker [~cdecker@pc-10367.ethz.ch] has joined #bitcoin-wizards12:20
-!- rht__ [uid86914@gateway/web/irccloud.com/x-hbtnhrnlcydjzjwl] has quit [Quit: Connection closed for inactivity]12:28
-!- frankenmint [~frankenmi@c-24-22-67-17.hsd1.or.comcast.net] has joined #bitcoin-wizards12:31
-!- mjerr [~mjerr@p578EAB34.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds]12:33
-!- frankenmint [~frankenmi@c-24-22-67-17.hsd1.or.comcast.net] has quit [Client Quit]12:35
StephenM347"Your membership in the mailing list Bitcoin-development has been disabled due to excessive bounces..."12:36
StephenM347Anyone else get this?12:36
-!- eudoxia [~eudoxia@r167-57-17-47.dialup.adsl.anteldata.net.uy] has joined #bitcoin-wizards12:36
kanzureyep12:37
kanzurecheck #bitcoin-dev irc logs12:37
StephenM347kanzure: thanks, will do12:37
StephenM347kanzure: http://bitcoinstats.com/irc/bitcoin-dev/logs/ doesn't seem to offer a search?12:41
kanzurebrutal... hmm.12:43
kanzurewell, one of the emails to bitcoin-development@lists.sourceforge.net mentioned this, so perhaps view that email thread12:43
-!- contrapumpkin [~copumpkin@unaffiliated/copumpkin] has quit [Ping timeout: 252 seconds]12:46
-!- copumpkin [~copumpkin@unaffiliated/copumpkin] has joined #bitcoin-wizards12:46
-!- copumpkin [~copumpkin@unaffiliated/copumpkin] has quit [Excess Flood]12:50
-!- jmcn [~jamie@2.24.158.30] has quit [Ping timeout: 276 seconds]12:50
-!- jmcn [~jamie@2.24.158.30] has joined #bitcoin-wizards12:51
-!- _biO__ [~biO_@ip-37-24-195-112.hsi14.unitymediagroup.de] has quit [Remote host closed the connection]12:54
-!- lnsybrd [~lnsybrd@fwsm-io-azp-dmz.phx1.ip.io.com] has quit [Quit: lnsybrd]13:01
-!- nessence_ [~alexl@c-68-51-194-2.hsd1.mi.comcast.net] has quit []13:06
-!- copumpkin [~copumpkin@unaffiliated/copumpkin] has joined #bitcoin-wizards13:08
-!- sparetire_ [~sparetire@unaffiliated/sparetire] has joined #bitcoin-wizards13:08
-!- eudoxia [~eudoxia@r167-57-17-47.dialup.adsl.anteldata.net.uy] has quit [Quit: Leaving]13:13
-!- lnsybrd [~lnsybrd@fwsm-io-azp-dmz.phx1.ip.io.com] has joined #bitcoin-wizards13:14
-!- kmels [~kmels@186.64.110.122] has quit [Ping timeout: 265 seconds]13:17
-!- zooko [~user@2601:281:8101:3c71:40d1:c44c:ba43:df6b] has quit [Remote host closed the connection]13:19
-!- Quanttek [~quassel@2a02:8108:73f:f6e4:e23f:49ff:fe47:9364] has quit [Ping timeout: 252 seconds]13:20
-!- mjerr [~mjerr@p578EAB34.dip0.t-ipconnect.de] has joined #bitcoin-wizards13:26
-!- adam3us [~Adium@c3-219.i07-1.onvol.net] has joined #bitcoin-wizards13:29
-!- cdecker [~cdecker@pc-10367.ethz.ch] has quit [Ping timeout: 276 seconds]13:29
-!- cdecker [~cdecker@pc-10367.ethz.ch] has joined #bitcoin-wizards13:29
-!- nessence [~alexl@162.17.137.27] has joined #bitcoin-wizards13:32
-!- mjerr [~mjerr@p578EAB34.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds]13:33
-!- zooko [~user@2601:281:8101:3c71:1952:c3a0:6717:7d18] has joined #bitcoin-wizards13:35
-!- zmanian [~zmanian@12.226.88.52] has joined #bitcoin-wizards13:36
-!- nwilcox [~nwilcox@c-24-23-245-115.hsd1.ca.comcast.net] has joined #bitcoin-wizards13:40
-!- justanotherusr [~Justan@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds]13:40
-!- justanotherusr [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-wizards13:42
-!- lnsybrd_ [~lnsybrd@jsr.6502.ws] has joined #bitcoin-wizards13:51
-!- UllrSkis [~UllrSkis@c-66-41-201-92.hsd1.mn.comcast.net] has joined #bitcoin-wizards13:51
-!- justanotherusr [~Justan@unaffiliated/justanotheruser] has quit [Ping timeout: 256 seconds]13:51
-!- justanotherusr [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-wizards13:52
-!- lnsybrd [~lnsybrd@fwsm-io-azp-dmz.phx1.ip.io.com] has quit [Ping timeout: 256 seconds]13:52
-!- lnsybrd_ is now known as lnsybrd13:52
-!- jmcn [~jamie@2.24.158.30] has quit [Ping timeout: 276 seconds]13:54
-!- jmcn [~jamie@2.24.158.30] has joined #bitcoin-wizards13:54
-!- hearn [~mike@84-75-197-78.dclient.hispeed.ch] has joined #bitcoin-wizards13:55
-!- mjerr [~mjerr@p578EAB34.dip0.t-ipconnect.de] has joined #bitcoin-wizards13:57
-!- JackH [~Jack@host-80-43-142-154.as13285.net] has quit [Ping timeout: 264 seconds]14:03
-!- lnsybrd [~lnsybrd@jsr.6502.ws] has quit [Quit: lnsybrd]14:03
-!- mjerr [~mjerr@p578EAB34.dip0.t-ipconnect.de] has quit [Ping timeout: 255 seconds]14:08
-!- Populus [Populus@gateway/vpn/mullvad/x-lenzbkcyfmpxthsf] has quit [Remote host closed the connection]14:14
-!- b_lumenkraft [~b_lumenkr@unaffiliated/b-lumenkraft/x-4457406] has quit [Quit: b_lumenkraft]14:17
-!- tucenaber [~tucenaber@unaffiliated/tucenaber] has joined #bitcoin-wizards14:23
-!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)]14:24
-!- wallet42 [~wallet42@88.229.225.11] has joined #bitcoin-wizards14:25
-!- Tebbo [~Jerry`@ip72-211-88-176.no.no.cox.net] has quit [Read error: Connection reset by peer]14:38
-!- rht__ [uid86914@gateway/web/irccloud.com/x-zwbthifqrbevlaks] has joined #bitcoin-wizards14:38
-!- Tebbo [~Jerry`@ip72-211-88-176.no.no.cox.net] has joined #bitcoin-wizards14:38
-!- tcrypt [~tylersmit@173.247.206.110] has quit [Read error: Connection reset by peer]14:39
-!- Luke-Jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood]14:39
-!- tcrypt [~tylersmit@173.247.206.110] has joined #bitcoin-wizards14:39
-!- Luke-Jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-wizards14:39
-!- AnoAnon [~AnoAnon@197.39.199.200] has joined #bitcoin-wizards14:43
-!- AnoAnon [~AnoAnon@197.39.199.200] has quit [Max SendQ exceeded]14:43
-!- wallet421 [~wallet42@78.179.116.60] has joined #bitcoin-wizards14:46
-!- wallet42 [~wallet42@88.229.225.11] has quit [Killed (sinisalo.freenode.net (Nickname regained by services))]14:46
-!- wallet421 is now known as wallet4214:46
-!- wallet42 [~wallet42@78.179.116.60] has quit [Changing host]14:46
-!- wallet42 [~wallet42@unaffiliated/wallet42] has joined #bitcoin-wizards14:46
-!- wallet42 [~wallet42@unaffiliated/wallet42] has quit [Read error: Connection reset by peer]14:47
-!- wallet42 [~wallet42@78.179.116.60] has joined #bitcoin-wizards14:47
-!- gnusha [~gnusha@unaffiliated/kanzure/bot/gnusha] has joined #bitcoin-wizards14:53
-!- Topic for #bitcoin-wizards: This channel is not about short-term Bitcoin development | http://bitcoin.ninja/ | This channel is logged. | For logs and more information, visit http://bitcoin.ninja14:53
-!- Topic set by andytoshi [~andytoshi@unaffiliated/andytoshi] [Fri Aug 22 14:51:37 2014]14:53
[Users #bitcoin-wizards]14:53
[@ChanServ ] [ catlasshrugged ] [ Giszmo ] [ kanzure ] [ nwilcox ] [ stevenroose ] 14:53
[ [ace] ] [ cdecker ] [ gnusha ] [ kinlo ] [ OneFixt ] [ STRML ] 14:53
[ [d__d] ] [ cfields ] [ go1111111 ] [ koshii ] [ optimator ] [ sturles ] 14:53
[ _biO_ ] [ chmod755 ] [ goregrind ] [ Krellan ] [ otoburb ] [ SubCreative ] 14:53
[ _whitelogger ] [ CodeShark ] [ Graet ] [ kumavis ] [ p15x ] [ sundance ] 14:53
[ a5m0_ ] [ comboy ] [ grandmaster ] [ kyuupichan ] [ paveljanik ] [ superobserver ] 14:53
[ AaronvanW ] [ copumpkin ] [ GreenIsMyPepper] [ larraboj_ ] [ petertodd ] [ SwedFTP ] 14:53
[ adam3us ] [ Cory ] [ gribble ] [ lclc ] [ phantomcircuit ] [ sy5error ] 14:53
[ adams__ ] [ coryfields_ ] [ grubles ] [ leakypat ] [ pigeons ] [ Taek ] 14:53
[ AdrianG ] [ cosmo ] [ Guest68586 ] [ LeMiner ] [ platinuum ] [ tcrypt ] 14:53
[ afdudley0 ] [ crescendo ] [ guruvan ] [ livegnik ] [ poggy ] [ TD-Linux ] 14:53
[ afk11 ] [ CryptoGoon ] [ gwillen ] [ lmatteis ] [ pollux-bts ] [ Tebbo ] 14:53
[ ajweiss ] [ cryptowe- ] [ harrigan ] [ lnovy ] [ PRab_ ] [ temujin ] 14:53
[ akrmn ] [ d1ggy ] [ harrow ] [ Logicwax ] [ priidu ] [ TheSeven ] 14:53
[ akstunt600 ] [ dansmith_ ] [ hashtag_ ] [ Luke-Jr ] [ prodatalab ] [ theymos ] 14:53
[ Alanius_ ] [ darwin__ ] [ hashtagg_ ] [ luny` ] [ prosodyContext_] [ ThinThread ] 14:53
[ AlexStraunoff ] [ dasource ] [ hearn ] [ maaku ] [ qawap ] [ thrasher` ] 14:53
[ amiller ] [ davout ] [ heath ] [ Mably ] [ rasengan ] [ throughnothing] 14:53
[ Anduck ] [ dc17523be3 ] [ helo ] [ Madars ] [ rht__ ] [ Tiraspol ] 14:53
[ andy-logbot ] [ dEBRUYNE ] [ HM ] [ mappum ] [ richardus ] [ triazo ] 14:53
[ andytoshi ] [ dgenr8 ] [ hulkhogan_ ] [ mariorz ] [ roasbeef ] [ tromp ] 14:53
[ Apocalyptic ] [ dignork ] [ huseby ] [ Meeh_ ] [ runeks ] [ tromp_ ] 14:53
[ Aquentin ] [ DougieBot5000 ] [ iddo ] [ melvster1 ] [ rustyn ] [ ttttemp ] 14:53
[ artifexd ] [ Dr-G ] [ indolering ] [ mengine ] [ ryan-c ] [ tucenaber ] 14:53
[ arubi_ ] [ droark ] [ Iriez ] [ merlincorey ] [ s1w ] [ veox ] 14:53
[ austinhill ] [ EasyAt ] [ isis ] [ michagogo ] [ sadoshi ] [ vonzipper ] 14:53
[ azariah_ ] [ ebfull ] [ JackH ] [ midnightmagic] [ scoria ] [ wallet42 ] 14:53
[ badmofo ] [ elastoma ] [ jaekwon ] [ mikolalysenko] [ sdaftuar ] [ warptangent ] 14:53
[ BananaLotus ] [ Eliel ] [ jaromil ] [ mkarrer ] [ shen_noe ] [ warren ] 14:53
[ bedeho ] [ Emcy ] [ jb55 ] [ mm_1 ] [ shesek ] [ waxwing ] 14:53
[ berndj ] [ epscy ] [ jbenet ] [ MoALTz ] [ sipa ] [ weex ] 14:53
[ binaryatrocity_] [ eric ] [ jcorgan ] [ morcos ] [ sl01 ] [ wiz ] 14:53
[ bliljerk101 ] [ face ] [ jessepollak ] [ mountaingoat ] [ smooth ] [ wizkid057 ] 14:53
[ BlueMatt ] [ fenn ] [ jgarzik ] [ MrTratta ] [ sneak ] [ wumpus ] 14:53
[ BrainOverfl0w ] [ Fistful_of_Coins] [ jmcn ] [ Muis ] [ so ] [ xabbix ] 14:53
[ brand0 ] [ fluffypony ] [ jonasschnelli ] [ nanotube ] [ sparetire ] [ Xzibit17 ] 14:53
[ bsm117532 ] [ fragzle ] [ jouke ] [ nephyrin` ] [ sparetire_ ] [ yoleaux ] 14:53
[ btcdrak ] [ GAit ] [ jrayhawk ] [ nessence ] [ spinza ] [ yorick ] 14:53
[ Burrito ] [ gavinand1esen ] [ jtimon ] [ nickler_ ] [ Starduster ] [ yrashk ] 14:53
[ c0rw|away ] [ ggreer ] [ justanotherusr ] [ nsh ] [ starsoccer ] [ zmanian ] 14:53
[ catcow ] [ gielbier ] [ K1773R ] [ null_radix ] [ StephenM347 ] [ zooko ] 14:53
-!- Irssi: #bitcoin-wizards: Total of 246 nicks [1 ops, 0 halfops, 0 voices, 245 normal]14:53
-!- Channel #bitcoin-wizards created Mon Feb 25 23:24:47 201314:53
-!- Irssi: Join to #bitcoin-wizards was synced in 16 secs14:53
-!- espes [~espes@205.185.120.132] has joined #bitcoin-wizards14:53
-!- jmcn [~jamie@2.24.158.30] has quit [Ping timeout: 276 seconds]14:54
-!- jmcn [~jamie@2.24.158.30] has joined #bitcoin-wizards14:56
-!- UllrSkis [~UllrSkis@c-66-41-201-92.hsd1.mn.comcast.net] has joined #bitcoin-wizards14:58
-!- forrestv [forrestv@unaffiliated/forrestv] has joined #bitcoin-wizards14:59
-!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards15:02
-!- temujin [~temujin@38.121.165.30] has left #bitcoin-wizards []15:06
-!- jmcn [~jamie@2.24.158.30] has quit [Ping timeout: 276 seconds]15:07
-!- ruby32 [~ruby32@38.121.165.30] has joined #bitcoin-wizards15:07
-!- jmcn [~jamie@2.24.158.30] has joined #bitcoin-wizards15:09
-!- moa [~kiwigb@opentransactions/dev/moa] has joined #bitcoin-wizards15:10
-!- adam3us1 [~Adium@c3-219.i07-1.onvol.net] has joined #bitcoin-wizards15:10
-!- adam3us [~Adium@c3-219.i07-1.onvol.net] has quit [Ping timeout: 272 seconds]15:12
-!- nwilcox [~nwilcox@c-24-23-245-115.hsd1.ca.comcast.net] has quit [Quit: leaving]15:14
-!- StephenM347 [~stephenm3@static-64-223-246-218.port.east.myfairpoint.net] has quit []15:16
-!- cdecker [~cdecker@pc-10367.ethz.ch] has quit [Ping timeout: 276 seconds]15:22
-!- droark [~droark@209-6-53-207.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com] has quit [Quit: Later.]15:23
-!- cdecker [~cdecker@pc-10367.ethz.ch] has joined #bitcoin-wizards15:23
-!- pavel_ [~paveljani@79-98-72-216.sys-data.com] has joined #bitcoin-wizards15:29
-!- droark [~droark@209-6-53-207.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com] has joined #bitcoin-wizards15:30
-!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Ping timeout: 276 seconds]15:30
-!- sdaftuar [~sdaftuar@static-100-38-11-146.nycmny.fios.verizon.net] has quit [Ping timeout: 272 seconds]15:32
-!- wallet42 [~wallet42@78.179.116.60] has quit [Quit: Leaving.]15:33
-!- wallet42 [~wallet42@78.179.116.60] has joined #bitcoin-wizards15:34
-!- airbreather [~airbreath@d149-67-99-43.nap.wideopenwest.com] has joined #bitcoin-wizards15:34
-!- zooko [~user@2601:281:8101:3c71:1952:c3a0:6717:7d18] has quit [Quit: BATTLE FOR WESNOTH!!!]15:35
-!- jmcn_ [~jamie@2.24.158.69] has joined #bitcoin-wizards15:36
-!- wallet42 [~wallet42@78.179.116.60] has quit [Client Quit]15:37
-!- nwilcox [~nwilcox@c-76-103-245-13.hsd1.ca.comcast.net] has joined #bitcoin-wizards15:38
-!- blazes816 [~tylersmit@173.247.206.110] has joined #bitcoin-wizards15:39
-!- jmcn [~jamie@2.24.158.30] has quit [Ping timeout: 275 seconds]15:39
-!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has quit [Quit: Leaving]15:41
-!- airbreather_ [~airbreath@d149-67-99-43.nap.wideopenwest.com] has joined #bitcoin-wizards15:42
-!- tcrypt [~tylersmit@173.247.206.110] has quit [Ping timeout: 246 seconds]15:42
-!- blazes816 [~tylersmit@173.247.206.110] has quit [Ping timeout: 276 seconds]15:43
-!- airbreather [~airbreath@d149-67-99-43.nap.wideopenwest.com] has quit [Ping timeout: 276 seconds]15:46
-!- PRab_ [~chatzilla@c-68-34-102-231.hsd1.mi.comcast.net] has quit [Quit: ChatZilla 0.9.91.1 [Firefox 38.0.5/20150525141253]]15:46
-!- darwin__ [~darwin@88-103-255-166.jes.cz] has quit []15:47
-!- ruby32 [~ruby32@38.121.165.30] has quit [Quit: ruby32]15:47
-!- belcher [~belcher-s@unaffiliated/belcher] has joined #bitcoin-wizards15:51
-!- Mably [~Mably@unaffiliated/mably] has quit [Ping timeout: 264 seconds]15:54
-!- jmcn_ [~jamie@2.24.158.69] has quit [Ping timeout: 276 seconds]15:55
-!- jmcn [~jamie@2.24.158.69] has joined #bitcoin-wizards15:56
-!- hearn [~mike@84-75-197-78.dclient.hispeed.ch] has quit [Ping timeout: 252 seconds]15:57
-!- hearn [~mike@84-75-197-78.dclient.hispeed.ch] has joined #bitcoin-wizards15:58
-!- hearn [~mike@84-75-197-78.dclient.hispeed.ch] has quit [Client Quit]16:00
-!- JackH [~Jack@host-80-43-142-154.as13285.net] has quit [Ping timeout: 252 seconds]16:01
-!- jgarzik [~jgarzik@unaffiliated/jgarzik] has quit [Quit: This computer has gone to sleep]16:01
-!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-wizards16:04
-!- rustyn [~rustyn@unaffiliated/rustyn] has quit [Ping timeout: 250 seconds]16:19
-!- rustyn [~rustyn@unaffiliated/rustyn] has joined #bitcoin-wizards16:21
-!- ThomasV [~ThomasV@unaffiliated/thomasv] has quit [Ping timeout: 272 seconds]16:21
-!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has joined #bitcoin-wizards16:25
-!- Tebbo [~Jerry`@ip72-211-88-176.no.no.cox.net] has quit [Read error: Connection reset by peer]16:29
-!- Tebbo [~Jerry`@ip72-211-88-176.no.no.cox.net] has joined #bitcoin-wizards16:30
-!- lnovy [~lnovy@2002:4d57:f055::1] has quit [Ping timeout: 252 seconds]16:32
-!- lnovy [~lnovy@2002:4d57:f055::1] has joined #bitcoin-wizards16:33
-!- sipa [~pw@unaffiliated/sipa1024] has left #bitcoin-wizards []16:35
-!- zmanian [~zmanian@12.226.88.52] has quit [Ping timeout: 252 seconds]16:36
-!- jgarzik [~jgarzik@unaffiliated/jgarzik] has joined #bitcoin-wizards16:37
-!- zmanian [~zmanian@12.226.88.52] has joined #bitcoin-wizards16:40
-!- gmaxwell [greg@wikimedia/KatWalsh/x-0001] has joined #bitcoin-wizards16:43
-!- PRab [~chatzilla@2601:40a:8000:8f9b:959b:96b6:9b51:62f5] has joined #bitcoin-wizards16:43
-!- melvster1 [~melvster@ip-86-49-18-198.net.upcbroadband.cz] has quit [Ping timeout: 252 seconds]16:45
CodeSharkis it possible to create an efficient accumulator that can be used to validate an entire transaction graph?16:46
gmaxwellnwilcox: I think we identified some time ago what additional commitments are needed to efficiently randomly verify all rules (or at least most of them).  Indeed, that could have some nice properties; but we're left with a couple issues:16:46
-!- dEBRUYNE [~dEBRUYNE@239-196-ftth.onsbrabantnet.nl] has quit [Read error: Connection reset by peer]16:47
gmaxwellone is that the additional commiments are expensive to maintain (e.g. vaguely a 20 fold increase in IO costs for full nodes) which is a bit unfortunate but perhaps surmountable, more problematic is the issue of censorship, how do you avoid the case where everyone just plays dumb about some invalidity to prevent you from detecting it?16:48
gmaxwellThat latter issue makes it less exciting.16:48
nwilcoxCodeShark: I'm curious if an "accumulator" is also possible...16:49
nwilcoxgmaxwell: Are these additional comments merkle paths to block header for each txin?16:49
nwilcoxs/comments/commitments/16:50
-!- c0rw|away is now known as c0rw1n16:50
CodeSharkrecent results on zkSNARKs give proofs that do not depend on the size of the program nor input...but constructing the proof still is expensive16:51
gmaxwellnwilcox: no, that wouldn't be sufficient because it can't be used to efficiently show the absense of a double spend.  State commitments ("an accumulator" as you note) are sufficient (and I think necessary).  https://en.bitcoin.it/wiki/User:Gmaxwell/features#Proofs  is the circa 2011/2012 stuff. IIRC there was something else that needed to be commited to that I forget now that isn't there. (kinda16:51
gmaxwellstopped updating it when 99% of the effect it was having was feeding plagerism)16:51
gmaxwellCodeShark: the proof in that space isn't 'recent results' it was always the case that the proofs were constant size, the name even means that  ('Succinct' argument of knoweldge). :)16:52
CodeSharkright, well I only encountered it recently...so I'm a little behind :p16:53
CodeSharkif the cost of proofs are moved over to the sender, it could be conceivably made to scale16:53
CodeSharkthe sender would only have to incorporate one more witness into the proof they got from each of their inputs16:54
gmaxwellCodeShark: you still need publicaiton unfortunately, proving that a block is valid is fine, but if no one but the block author had the updated accumulator state then only they can produce more blocks. :(16:54
CodeSharkwhy would only the block author have the updated accumulator state?16:56
nwilcoxgmaxwell: (I haven't read the wiki link yet...) I was imagining SPV-style PoW verification as a "strong bet" against double spends, so I don't quite follow your comment.16:58
CodeSharkwouldn't it be sufficient for a sender to prove that the output they've created has witnesses all the way back to valid coinbase transactions?16:58
* nwilcox skims wiki page.16:58
-!- zooko [~user@2601:281:8101:3c71:9422:f2cb:c0e2:3299] has joined #bitcoin-wizards17:00
-!- melvster [~melvster@ip-86-49-18-198.net.upcbroadband.cz] has joined #bitcoin-wizards17:02
gmaxwellnwilcox: if you're trusting the hashpower then you can stop at just whats in bitcoin today. No more is needed. But _why_ trust the hashpower? it's a necessarily anonymous self-selecting group (you hope) of parties. :P   There is a hope that the hashpower is economically incentivized to conform to the protocol because if they don't they'll get caught and their blocks ignored; but there needs to be17:02
gmaxwell a mechenism for that to actually happen. :P17:02
gmaxwellCodeShark: no because that doesn't show the absense of a double spend.17:03
nwilcoxgmaxwell: Well, yes, removing the reliance on PoW assumptions would be awesome. I wasn't considering that.17:04
-!- jmcn [~jamie@2.24.158.69] has quit [Ping timeout: 276 seconds]17:05
gmaxwellK. well if you're willing to make them, then bitcoin's SPV ought to be enough.17:05
-!- jmcn [~jamie@2.24.158.69] has joined #bitcoin-wizards17:05
nwilcoxCodeShark: That sounds sufficient to me *iff* you assume PoW validation protects against double spends, right?17:05
gmaxwellit's totally wasteful though, because you don't have to do that at all if you're trusting pow, just check the initial membership.  Also I suggest traversing the graph of some coins sometime, for a great many you are rapidly casually connected to a signficant fraction of all transactions. :)17:06
gmaxwell(thanks betting sites. :) )17:07
nwilcoxI blame non-hoarders for tightly interweaving the transaction graph.17:09
-!- erasmospunk [~erasmospu@gateway/vpn/privateinternetaccess/erasmospunk] has joined #bitcoin-wizards17:09
gmaxwellnwilcox: there have been a number of on-blockchain betting services that their specific design required them to jointly spend coins from multiple sources that are atypically good at comingling histories, esp since moast of the transactions to them are numerous tiny amounts..17:10
gmaxweller most17:10
-!- d1ggy_ [~d1ggy@dslb-088-070-161-193.088.070.pools.vodafone-ip.de] has joined #bitcoin-wizards17:15
-!- d1ggy [~d1ggy@dslc-082-082-155-231.pools.arcor-ip.net] has quit [Ping timeout: 265 seconds]17:18
CodeSharkgmaxwell: what about schemes that incentivize demonstration of double-spend proofs?17:19
CodeSharkpoint is construction of the proof could be offloaded to specialists who make it their business to detect them17:20
CodeSharkyes, there could be a conspiracy to withhold them17:20
CodeSharkbut assuming the incentives are not misplaced and the system is sufficiently decentralized, can't it be made at least extremely difficult to enforce withholding?17:21
-!- erasmospunk [~erasmospu@gateway/vpn/privateinternetaccess/erasmospunk] has quit [Remote host closed the connection]17:21
CodeSharkactually...if you were to keep track of the total amount of existing coins on the network, wouldn't that also be a way to track double-spends?17:23
CodeSharkor detect them, rather17:23
gmaxwellCodeShark: I am disappoint at your lack of reading sometimes, it makes talking with you a lot less fun.17:23
CodeSharkwhat should I read?17:23
gmaxwellWhat I said in the discussion here (and #bitcoin-dev!) if I say something you don't get please ask me to cliarify.    State commitments are sufficent to make the checks efficient (maybe necessary, not quite sure, e.g. commitments to a hashtree over the utxo set.17:24
gmaxwellThen there are compact proofs for both double spending and spending a non-existing coin.17:24
-!- tcrypt [~tylersmit@c-67-169-17-114.hsd1.ca.comcast.net] has joined #bitcoin-wizards17:25
-!- tcrypt [~tylersmit@c-67-169-17-114.hsd1.ca.comcast.net] has quit [Remote host closed the connection]17:25
CodeSharkthe thing you seemed to be concerned about was withholding attacks17:26
CodeSharkeveryone playing dumb17:26
CodeSharkand I, admittedly, hadn't clicked on your proofs link17:27
gmaxwellit's okay, it's just that you seem to be reinventing this I'd just mentioned! :)17:28
CodeSharkso then what's the downside to state commitments?17:29
CodeShark:)17:29
nwilcoxminer overhead?17:30
CodeSharkpresumably we need a scheme that does not require even miners to perform full validation17:30
CodeSharkso asymptotically, it would actually reduce miner overhead17:30
gmaxwellCodeShark: it's a large overhead for verifiying, because now you have to verify that the stat updates are faithful, which needs a bunch more random IO.17:31
gmaxwell"asymptotically" is a good way to talk yourself into a lala land of irrelevance though. :)17:31
CodeSharkwell, even for finite systems that are growing exponentially :)17:32
dgenr8i don't read either.  what stops somebody from presenting a perfectly good UTXO proof from two years ago when it was spent an hour ago?17:32
gmaxwellbasically with the right commitment sets you can avoid having anyone store the state, but then you end up carrying around membership and update proofs for each input (hashtree fragments) and for our current utxo set size they end up being a couple kilobytes.17:32
gmaxwell"so great, you've saved a $1 one time disk space cost for a $50/mo bandwidth cost. :P (or what have you, random numbers -- the point I'm making is that asymptotics can be misleading)17:33
CodeSharkI'm talking about a model that can survive exponential growth in usage (at least for a while)17:34
CodeSharkif the usage were to remain constant, then yes, it's silly17:35
dgenr8CodeShark: with full-node security, or SPV?17:35
CodeSharkwith something a lot better than SPV - but not necessarily deterministic17:35
CodeSharklet's say with negligible failure rate17:35
CodeSharkor with mitigated failure17:36
dgenr8CodeShark: akin to SPV with arbitrarily many peers?17:36
gmaxwellas I said, these are not new ideas; you are _years_ behind on this, please go actually crunch the numbers on what it looks like and you'll see the tradeoffs are not attractive at least anywhere within the realm of reasonable loads (e.g. supportable on today's hardware)17:37
nwilcox"CodeShark> presumably we need a scheme that does not require even miners to perform full validation" Woah... so, relaxing global consensus?17:37
CodeSharkgmaxwell: forgive me for being behind - I have not seen the literature with these numbers and can't possibly follow all the forums and mailing lists and read everything back to the beginning of time17:37
gmaxwelldgenr8: SPV security is not really improved by 'arbitrarily many peers'.17:37
CodeSharkso if you have some good literature with a summary it would be greatly appreciated17:38
dgenr8gmaxwell: no? if an SPV node connects to the entire network, how does withholding work?17:39
nwilcox+1 for literature summaries for people catching up (if you can afford the effort/time).17:39
gmaxwellCodeShark: you're forgiven, there is no great one stop shop to catch up in an instant; thats not what I'm barking about. But actually following the links I give in context would be good.17:40
gmaxwellThe key words in this space are "txo commitments" "stxo commitments" "utxo commitments"  and "stateless mining".17:41
CodeSharkI usually do - I got interrupted by a phone call in this instance17:41
gmaxwell:)17:41
gmaxwelldgenr8: withholding _what_?17:41
CodeSharkbelieve me, gmaxwell, there's nothing I'd rather be working on more than solving these exact issues...unfortunately I also have a bunch of other stuff to attend to :p17:42
CodeSharkso if you can help me catch up so I can usefully contribute it would be very much appreciated17:42
-!- jtimon [~quassel@69.29.134.37.dynamic.jazztel.es] has quit [Ping timeout: 246 seconds]17:42
gmaxwellWill do. (But I don't have the time to do so right this second, but indeed collecting pointers on this would be very useful; since it seems a few new people have shown up)17:43
dgenr8gmaxwell: spentness17:43
CodeSharkI think a bunch of people are essentially trying to invent the same thing here...and there isn't the best amount of communication17:43
gmaxwellCodeShark: there was a ton of communication this litterally 100s of posts, mailing lists entries, presentations, wiki articles, implementations.17:44
CodeSharkplease point :)17:45
CodeSharkmost of the stuff on these things is noise17:45
gmaxwellAs I mentioned at the top, enthusasim has waned in part because of those two technical issues.17:45
CodeSharkand I just can't go through all of it17:45
phantomcircuitEmcy, IPC is roughly irrelevant for bitcoin validation speed17:45
phantomcircuitEmcy, i would be entirely surprised if intel is holding back on raw processing speed17:45
Emcywhat about moar coars17:45
phantomcircuitprobably the only way to significantly increase validation speed would be ops specifically intended for it17:45
hulkhogan_ CodeShark, grep ;p17:46
gmaxwelldgenr8: what if no one at all knows? CodeShark's premise was that there are not full nodes at all, not even miners. So what if you create an invalid block and then just plead ignornace?17:46
Emcythye prob would put EC hardware in the cpu eventually but very liekly not the curve bitcoin uses17:46
gmaxwell"oh, you want to test this part of it.. oh nope, don't know anything about that part"17:46
EmcyEC is getting some widespread use now i think17:46
Emcythough something bothers me about a CPU having all this hardware for very specific functions17:47
gmaxwellEmcy: intel IPC has actually increased tremendously in recent parts.. count the actual cores.17:47
gmaxwellthey now ship 18 core parts...17:48
-!- shen_noe [~shen_noe@wired042.math.utah.edu] has quit [Quit: Leaving]17:49
dgenr8gmaxwell: the interesting question is how to serve a couple billion SPV nodes.  for that, the network should not need to be all full nodes.  miners though, they need full node security afaict17:50
-!- Aquentin [~Aquentin@unaffiliated/aquentin] has quit [Ping timeout: 265 seconds]17:50
CodeSharkthe only thing useful about the SPV concept is the hash tree - everything else I'd be totally happy scrapping :p17:51
gmaxwelldgenr8: then you're talking about something different from codeshark.17:51
Emcy18 cores damn17:52
Emcynot consumer though17:52
gmaxwellEmcy: right because consumers would have no clue what to do with it, unfortunately.17:52
gmaxwellapplications have not scaled well to multicore in general, and consumers are (as we've noticed) now been conditioned to believe that fully using a core for more than a fraction of a second means the software broken. :(17:53
Emcyhow do we make sure bitcoin wont end up only runnable on server market parts17:53
jgarzikthrottle adoption17:54
gmaxwellEmcy: non-server market seems mostly to be optimizing for power usage and size right now.17:54
leakypatjgarzik: +117:54
-!- belcher [~belcher-s@unaffiliated/belcher] has quit [Quit: Leaving]17:54
-!- c0rw1n is now known as c0rw|zZz17:54
gmaxwelldisagree that throttle adoption is necessary or sufficient.17:55
gmaxwellA single person could drive bitcoin to require a 18 core server cpu to keep up with absent limits, behold the power of "while true"; mean while the overwhleming majority of bitcoin denominated transactions happen without perturbing the blockchain (inside exchanges.).17:56
leakypatTo clarify, I mean adoption of blockchain written transactions17:56
-!- nwilcox [~nwilcox@c-76-103-245-13.hsd1.ca.comcast.net] has quit [Quit: leaving]17:57
gmaxwellleakypat: yea, with that context I agree more!17:57
-!- nessence [~alexl@162.17.137.27] has quit [Remote host closed the connection]17:57
dgenr8a UTXO set is a performance enhancement for a full node.  since "everyone playing dumb" is a problem, it's probably just as well to skip the whole exercise of trying to prove unspentness...17:58
dgenr8...and just directly distribute the exercise of proving spentness.  which just requires a tx index, not a summary database.17:58
-!- gmaxwell [greg@wikimedia/KatWalsh/x-0001] has left #bitcoin-wizards []17:58
dgenr8...and allows individual nodes to have less than the full blockchain.  ie they are capable of proving spentness for a certain part of the space17:59
CodeSharkwhat about an incentives model?18:00
CodeSharkwhy would they be interested in proving it?18:00
Emcyit seems the only consumer hardware still going for raw power is gfx cards18:00
Emcyso bitcoin has to better utilise those right18:00
dgenr8CodeShark: well when resource requirements were lower, I hear there were 350K nodes18:01
Emcyamd is pretty good at the gpu compute stuff right18:01
CodeSharkdgenr8: but generally, yes - incentives for proofs of spentness seems like a promising approach18:02
phantomcircuitEmcy, even gpu's aren't designed for continuous load18:03
Emcywell bitcoin isnt continuous18:04
-!- rht__ [uid86914@gateway/web/irccloud.com/x-zwbthifqrbevlaks] has quit [Quit: Connection closed for inactivity]18:08
-!- shen_noe [~shen_noe@wired042.math.utah.edu] has joined #bitcoin-wizards18:08
dgenr8CodeShark: suppose you had both.  if you ask about a txout, and you get both an "unspent proof" and a "spent proof", guess which one wins ;)18:09
CodeSharkunspent proof seems a lot harder18:09
dgenr8lack of an unspent proof is a lousy substitute for a spent proof.  lack of a spent proof gets more interesting the larger the set who fail to provide it18:13
CodeSharkthe only person who might perhaps have the proper incentives to provide unspent proofs are the spenders18:14
CodeShark*is the spender18:15
CodeSharkfor anyone else it18:15
CodeSharkit's too expensive18:15
CodeSharknot worth it18:15
CodeSharkhowever spent proofs are relatively cheap18:16
-!- jb55 [~jb55@208.98.200.100] has quit [Remote host closed the connection]18:17
-!- jb55 [~jb55@208.98.200.100] has joined #bitcoin-wizards18:18
CodeSharkpresumably if you got a spent and an unspent proof something broke :p18:18
dgenr8CodeShark: unspent is fleeting.  spent is forever (modulo reorgs)18:19
CodeSharkright - the unspent proof would only say "unspent within this particular chain"18:20
CodeSharkonce the chain grows or changes, all bets are off18:21
CodeSharkso if a spender were to want to provide a proof of unspent, they'd have to continue updating the proof as the chain grew18:22
-!- jb55 [~jb55@208.98.200.100] has quit [Ping timeout: 255 seconds]18:22
-!- erasmospunk [~erasmospu@lw.serv194.quikefall.com] has joined #bitcoin-wizards18:23
dgenr8i'm not sure that's harder than keeping a txindex, but the logical properties of an sxto query seem superior18:23
CodeSharkwell, it's also difficult because the witness must be compressed18:23
CodeSharkit must use some SNARG or SNARK of some sort18:24
CodeSharkwhereas proof-of-spent can be easily accomplished with a single witness...the transaction that spends it18:24
dgenr8yes. the other stuff is reading-list material for me ;)18:25
-!- bramc [~bram@99-75-88-206.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-wizards18:25
phantomcircuitEmcy, IBD is continuous load18:25
bramcThere seems to be a law of commenting on bitcoin online: No matter what you say, somebody will accuse you of being a socialist18:25
CodeSharkpinko!18:26
CodeSharkhmm, not sure I've gotten that accusation from bitcoin specifically, bramc18:27
zookobramc: I'm just saving up my favorite Bram Cohen quote about Bitcoin for the right moment.18:27
Emcyyes but not forever18:27
Emcycards are coming with stock waterloop snow anyway18:27
bramczooko, Huh?18:29
Emcy>mfw "If there is hope, it lies with the gamers"18:30
-!- GAit [~lnahum@2-230-161-158.ip202.fastwebnet.it] has quit [Read error: Connection reset by peer]18:30
Emcysocialism is ok18:31
Emcyit saved my nans life a few months back after a series of 4 minor strokes18:31
-!- priidu [~priidu@unaffiliated/priidu] has quit [Ping timeout: 264 seconds]18:32
-!- GAit [~lnahum@2-230-161-158.ip202.fastwebnet.it] has joined #bitcoin-wizards18:32
bramcEmcy, My own economic outlook isn't so simplistic, I'm just confuzzled that people are accusing me of being a socialist for wanting to have prices set by market demand instead of subsidizing them to be zero18:33
bramcsupply and demand I mean18:33
zookobramc: I was just reminded of my favorite quote by Bram Cohen about how stupid Bitcoin is.18:33
zookobramc: I was teasingly claiming that I'm waiting for the worst possible moment to quote you on it.18:33
bramczooko, Using bitcoin as a 'store of value' continues to be ridiculous18:33
* zooko cackles gleefully18:33
Emcysubsidising the fees?18:34
bramczooko, People are quoting me on it to attack me now, I don't care. I will happily remind people about the track record of bitcoin to date in terms of what's it's done to people who have bought into it18:34
Emcywhat you described seems the opposite of socialism18:35
bramcEmcy, subsidizing the transaction costs I mean. I just finished driving for two hours and am not wording good18:35
bramcEmcy, Hence my being confuzzled!18:36
-!- erasmospunk [~erasmospu@lw.serv194.quikefall.com] has quit [Remote host closed the connection]18:36
Emcyexcept if it counts as corporate socialism to the miners, which is the only kind of socialism people seem to be blind to heh18:36
zookobramc: wait, they're already quoting you from when you said something like "Bitcoin is just digital goldbuggery, which is even more idiotic than normal goldbuggery" ? Damn, there goes my chance to embarass you in public.18:42
bramczooko, It's golbuggism not goldbuggery, and yes they are18:42
amillerrofl goldbuggery18:42
bramcAnd I've always said, and continue to say, that getting excited about bitcoin because the value is going up is stupid, and saying it's a failure because the value is going down only marginally less so.18:43
Emcy>goldbuggery18:43
Emcyit seems it is you who has provided a quote for the ages zooko18:43
zookolol18:44
-!- zmanian [~zmanian@12.226.88.52] has quit [Ping timeout: 272 seconds]18:44
-!- shen_noe [~shen_noe@wired042.math.utah.edu] has quit [Quit: Leaving]18:52
-!- erasmospunk [~erasmospu@179.43.144.98] has joined #bitcoin-wizards18:52
-!- Dr-G [~Dr-G@unaffiliated/dr-g] has quit [Disconnected by services]18:52
-!- Dr-G2 [~Dr-G@xd9bf77f7.dyn.telefonica.de] has joined #bitcoin-wizards18:52
-!- Dazik [~Dazik@2607:fcc8:bd85:fa00:44d9:c7ff:a324:29df] has joined #bitcoin-wizards18:54
-!- jaekwon [~jae@2601:645:8001:f5c8:dcd4:830:a4df:e259] has quit [Remote host closed the connection]19:03
-!- nessence [~alexl@c-68-51-194-2.hsd1.mi.comcast.net] has joined #bitcoin-wizards19:11
-!- airbreather_ [~airbreath@d149-67-99-43.nap.wideopenwest.com] has quit [Remote host closed the connection]19:13
-!- erasmospunk [~erasmospu@179.43.144.98] has quit [Remote host closed the connection]19:19
-!- cosmo [~james@unaffiliated/cosmo] has quit [Quit: Leaving]19:23
-!- Dazik [~Dazik@2607:fcc8:bd85:fa00:44d9:c7ff:a324:29df] has quit [Ping timeout: 248 seconds]19:42
-!- Dazik [~Dazik@2607:fcc8:bd85:fa00:9977:2873:8a6f:97cf] has joined #bitcoin-wizards19:44
-!- PRab [~chatzilla@2601:40a:8000:8f9b:959b:96b6:9b51:62f5] has quit [Quit: ChatZilla 0.9.91.1 [Firefox 38.0.5/20150525141253]]19:49
-!- erasmospunk [~erasmospu@46-198-64-31.adsl.cyta.gr] has joined #bitcoin-wizards19:50
bramcAaand Gavin's proposed BIP uses nlocktime instead of block height for rollout dates. The whole subject is horribly depressing.19:54
Dazikjoin #warez19:58
-!- Dazik [~Dazik@2607:fcc8:bd85:fa00:9977:2873:8a6f:97cf] has left #bitcoin-wizards ["Leaving"]19:58
-!- prodatalab [~prodatala@2602:306:ceef:a750:577:5919:1b9c:af13] has quit [Ping timeout: 248 seconds]20:05
-!- PRab [~chatzilla@2601:40a:8000:8f9b:959b:96b6:9b51:62f5] has joined #bitcoin-wizards20:27
-!- copumpkin [~copumpkin@unaffiliated/copumpkin] has quit []20:32
-!- copumpkin [~copumpkin@unaffiliated/copumpkin] has joined #bitcoin-wizards20:35
CodeSharkbramc: you mean block_timestamp, not nlocktime (I hope) :)20:35
CodeSharkalthough block_timestamp is almost as bad :p20:36
jgarzikindeed, it is block_timestamp20:36
jgarzikmedian time has been suggested on the list20:37
-!- erasmosp_ [~erasmospu@104.238.169.23] has joined #bitcoin-wizards20:37
bramcIf you want to be more precise about future time, you can have block_timestamp be used at some point to determine an amount of extra height before things kick in20:38
bramcThat would be a few minutes noisy but not have weird reorg problems20:39
CodeSharkI don't quite get the rationale for not using block_height either - I mean, I can understand that block height doesn't accurately predict a moment in time...but the rationale given is that the block height isn't available in the block header.20:39
CodeSharktwo things: you still need to calculate block height to validate difficulty20:39
CodeSharkand...if we're going to hard-fork, might as well move the block height into the header rather than using that ridiculous coinbase hack20:40
-!- erasmospunk [~erasmospu@46-198-64-31.adsl.cyta.gr] has quit [Ping timeout: 276 seconds]20:41
CodeSharkand let's add an extra arbitrary 256 field to the header to allow for future extensions20:41
CodeSharkoh, right...that breaks miners20:41
CodeSharkalso, if we can't hack around the coinbase data issue, we could have a way of requesting only the merkle tree for the coinbase transaction20:42
-!- erasmosp_ [~erasmospu@104.238.169.23] has quit [Remote host closed the connection]20:45
-!- TheSeven [~quassel@rockbox/developer/TheSeven] has quit [Ping timeout: 256 seconds]20:45
CodeSharkstill is an utterly rube-goldbergish hack...but at least it can be easily encapsulated so we never have to ever look at it in our code again20:46
CodeSharkI can already imagine miners creating coinbase transactions with a zillion outputs just to piss us off :p20:48
-!- TheSeven [~quassel@rockbox/developer/TheSeven] has joined #bitcoin-wizards20:50
CodeSharkso someone please explain to me the use case for "not needing to know the block height when doing validation" ?20:52
CodeSharkit is quite depressing, bramc...21:06
CodeSharkah...I see Gavin's real reason in the ML21:08
CodeSharkit was easier for him to hack up something that only requires the timestamp :p21:09
CodeSharkgrabbing the block height was apparently too much work21:09
phantomcircuitCodeShark, the block height is not suitable because it can be +- the network hashrate growth from the expected day21:09
phantomcircuitie you calculate the expected height in 6 months21:09
phantomcircuitprice goes up and the hashrate goes up21:09
CodeSharkit's not particularly accurate - but it's very well-defined21:09
CodeSharksame thing goes for block reward halving21:10
phantomcircuitand the difficulty retarget lag causes that block height to be reached x% earlier21:10
phantomcircuitCodeShark, using the timestamp is reasonable, the way it's being used is comically absurd21:10
bramcIt could be set to the first block with a timestamp greater than X plus a certain amount of height21:13
phantomcircuitbramc, and we have a winner!21:14
CodeShark:)21:14
bramcThat would be fairly easy to hack up, and not have so many headaches.21:14
phantomcircuitbramc, it's really silly either way though21:15
phantomcircuitif you actually have a majority consensus you merely need to switch the nodes version of reality permanently21:15
phantomcircuitall the non believers be damned21:15
CodeSharkthe question is whether the reality really switched21:16
-!- Jaamg [jhpiloma@gateway/shell/tkk.fi/x-dhmfxcvcjxhrvrul] has joined #bitcoin-wizards21:16
CodeSharkif you can21:16
bramcMight as well move around some utxos while you're at it. Get rid of all the really old unspent mining rewards, maybe eliminate the ones known to have been seized my mt. gox.21:17
CodeSharklol21:17
phantomcircuitCodeShark, that's the great joke21:17
phantomcircuitwhat miners vote for is meaningless21:18
phantomcircuitusing that as the switch over criteria shows a fundamental failure to understand the matter21:18
CodeSharkwe lack any other objective metrics besides hashing power that can't easily be games21:18
CodeShark*gamed21:18
justanotherusrI think the idea is to assume everyone already switched over manually..21:18
CodeSharkthat's the unfortunate truth21:19
justanotherusrthe miner vote is just to get miners to agree with each other before they risk wasting moneey21:19
phantomcircuitCodeShark, the only metric that matters is user adoption21:19
phantomcircuitCodeShark, which cannot be reliably measured21:19
phantomcircuitthere is no safe way to hard fork21:19
CodeSharkphantomcircuit: precisely21:19
phantomcircuittada21:19
bramcphantomcircuit, Miner buy-in for compatible extensions works fine21:19
phantomcircuitbramc, yes for a soft fork it's fine21:20
phantomcircuitbramc, since it's essentially the miners colluding to censor transactions which violate the new rules21:21
bramcphantomcircuit, That's part of it, but it's also them agreeing that they'll all understand the extensions and deciding when to start issuing them21:21
-!- sundance30203 [6abc6be8@gateway/web/freenode/ip.106.188.107.232] has joined #bitcoin-wizards21:23
bramctechnically a soft fork where the miners all agreed to censor certain utxos and make them unspendable would also work21:23
bramcAlthough that... would be a bad idea21:23
phantomcircuitbramc, shh dont tell them21:24
CodeSharkfor a hardfork, if the vast majority of users are still on the old fork it just means miners waste their hashing power securing nothing21:24
phantomcircuitCodeShark, correct21:24
bramcCodeShark, The result of a hardfork doesn't tend towards one side or the other winning, it tends to mining hashpower going to the two sides proportionately to what their mining rewards are trading at on exchanges21:25
-!- mjerr [~mjerr@p578EAB34.dip0.t-ipconnect.de] has joined #bitcoin-wizards21:25
phantomcircuitbramc, thus it being almost certainly a disaster unless you can achieve near universal consensus first21:25
bramcJust like they're two completely unrelated altcoins, which basically they are21:25
CodeSharkbramc: yes, but I would think that's highly correlated with the proportion of actual users21:25
CodeSharkthe price at exchanges, that is21:26
bramcphantomcircuit, Yes exactly21:26
bramcCodeShark, There aren't very many exchanges, they're the ones who have the greater say21:26
CodeSharkthe exchanges will go with what they think is in their own economic self interest21:26
CodeSharkhigher volume of trading would generally be seen as better for their bottom line21:27
CodeSharkhowever...I don't think this forked ledger is a stable situation :p21:27
CodeSharkI think the ultimate outcome is both lose21:27
CodeSharkeither one wins overwhelmingly...or both lose21:27
CodeSharkand the longer the fork carries on without an overwhelming victor, the more likely they'll both lose21:29
phantomcircuitCodeShark, except a bunch of them are planning to do centralized offchain transactions also21:29
phantomcircuitso whose to say?21:30
CodeSharkI don't quite follow21:30
CodeSharkwas that meant sarcastically? :)21:30
phantomcircuitCodeShark, lots of them have -- as part of their business model -- operating trusted off chain transaction systems21:30
phantomcircuitwhich mucks up the question about rational actors21:31
CodeSharksure - that's fine for internal trades. the issue only applies to on-chain deposits and withdrawals21:31
CodeSharkbut if it's easier for someone to get into and out of positions, they're more likely to want to trade21:31
jgarzika longstanding forked ledger is incredibly unlikely21:31
jgarzikc.f. "50 BTC or die" folks :)21:32
phantomcircuitjgarzik, at a 75% switch over it's practically guaranteed to happen for some period of time exceeding a week21:32
phantomcircuitthere's a fairly substantial amount of mining infrastructure that's entirely on autopilot21:33
phantomcircuitnobody would even notice21:33
-!- sundance30203_ [6abc6be8@gateway/web/freenode/ip.106.188.107.232] has joined #bitcoin-wizards21:34
phantomcircuithell even if 1% stays21:34
phantomcircuitthat's 1 block/day21:34
jgarzikc.f. P2SH :)21:35
CodeSharkand not only do both forks lose in this scenario - any potential future cryptocoin loses as well21:35
jgarzikThat's perfectly OK...  miners are allowed to piss money away21:35
CodeSharkconfidence in the whole idea suffers21:35
-!- sundance30203 [6abc6be8@gateway/web/freenode/ip.106.188.107.232] has quit [Ping timeout: 246 seconds]21:35
CodeSharkif a few miners are the only ones left behind I don't think anyone will shed a tear21:36
jgarzika few miners + MP21:37
jgarzik;p21:37
jgarzikhmmmmm.  Now I like forking even more ;p21:37
CodeSharklol21:37
phantomcircuitjgarzik, soft fork experience is meaningless21:40
CodeSharkthe march 11th fork is actually a great example of user adoption did defeat hashing power adoption...but only by human intervention21:40
CodeSharkand willing cooperation from said miners21:41
-!- rht__ [uid86914@gateway/web/irccloud.com/x-admfuxeqydaiinex] has joined #bitcoin-wizards21:41
moabramc: " it tends to mining hashpower going to the two sides proportionately to what their mining rewards are trading at on exchanges"21:42
moathis is exactly what happened in early days of namecoin21:42
moaand viiolent oscillations bettwen value and hashpower shifts21:42
CodeSharkare you talking about miners who mined both bitcoin and namecoin? not sure how this example fits in21:43
phantomcircuitmoa, and now namecoin is worthless21:44
phantomcircuitso historical precedent is not good21:44
CodeSharktwo merge-mined distinct ledgers is a whole lot better than one fork-mined ledger :p21:44
phantomcircuitCodeShark, namecoin forked a bunch of times21:44
phantomcircuitCodeShark, which resulted in diffent exchanges trading different forks21:45
CodeSharkah21:45
CodeSharkthat must have been a few weeks before I came into this space21:46
moaCodeShark: this was before merge mining21:47
CodeSharkmerged mining is perhaps namecoin's most significant legacy. unfortunately, namecoin's merged mining implementation is just about the worst possible way it can be done :p21:48
moadepending on points in the cycle it was more profitable to mine namecoin or bitcoin, with same hashpower21:49
CodeSharkI missed out on all that mining fun - I never got to do any bitcoin mining21:50
moaso hashpower was jumping back and forward between ... and exchange rate and difficulty oscillating wildly21:50
moawhich was partly the incentive to implement merge mining21:51
CodeSharkwhen I came into this space, GPU mining probably at its peak21:51
moahurredly admittably ... but hey21:51
moait works right21:51
CodeSharkit actually explains a bunch, moa21:51
-!- wallet42 [~wallet42@78.179.116.60] has joined #bitcoin-wizards21:51
moalesson being you do NOT want the sha(256) hash power to split and start competing against each other21:54
moait's like a dragon eating it's own tail21:54
CodeSharkswitching between different coins is not nearly as bad as switching between different ledgers of the same coin :p21:56
CodeSharkduring the march 11th fork, the recommended policy for merchants and exchanges was to stop all transactions until the fork is resolved21:57
phantomcircuitCodeShark, which is the only rational behavior during a hard fork22:00
phantomcircuitwhich means there's no rational way to decide which side to goto as a user/miner22:00
phantomcircuitand tada22:00
phantomcircuitsystemic collaprse22:00
CodeSharkthere could be a rational reason to back one fork rather than the other if you strongly believe it will ultimately prevail22:01
CodeSharkas a miner, that is22:01
CodeSharkas a user, I think the rational thing to do is wait :)22:02
CodeSharkbarring criminal intent, of course22:02
CodeSharkas a miner, the only real downside to backing one side and losing, really, is cost of electricity and a few missed blocks22:03
CodeSharkso one could even argue that it's more rational to mine on either fork (even without having any idea which will prevail) than not mining at all22:04
phantomcircuitCodeShark, the rational decision for miners is to turn off their equipment22:07
phantomcircuitfun right?22:07
CodeSharkso the conclusion is 75% of hashing power is an extremely poor metric to use here :p22:08
CodeSharkbut any other metric likely requires some level of human intervention22:08
jgarzikminers follow users after a hard fork22:10
jgarzikexcept the ones on autopilot that get ignored22:10
CodeSharkjgarzik: that only happened on march 11th because of pressure applied on a few big pool operators22:11
CodeSharkhad that not been done, they might not have noticed for a while :)22:11
CodeSharkautopilot definitely favored the minority fork in that situation22:12
phantomcircuitCodeShark, i believe it is actually the worst possible22:14
phantomcircuitit's high enough that the uninformed will believe it's meaningful22:14
phantomcircuitwill also being a useless metric22:14
phantomcircuitAND basically gurantees a true network split22:14
CodeSharkcan't we conduct a poll somehow and decide based on that? (yes, I know polls can be sybilled...but let's not be such geeks for a moment and think practically)22:15
-!- sy5error [~sy5error@unaffiliated/sy5error] has quit [Remote host closed the connection]22:15
phantomcircuitjgarzik, you really have no way of knowing that, the march fork had an entirely clear course of action once it became clear what was happening22:15
phantomcircuitCodeShark, no because sybil22:15
CodeSharklol22:15
phantomcircuitCodeShark, the polls people have put up are actually being attacked in this manner22:16
CodeSharkwe don't just place an online questionaire up for anonymous responses - we'd have to have the process monitored by actual people...and yes, it can get political22:16
jgarzikphantomcircuit, outside of hyperventilating wizards, the near unanimous majority I hear wants the network to continue to scale.  If the network hard forks to 2MB in 6 months, the network will not fall over.  Hard forks include big risks, but it is being blown way out of proportion -- on here & by Mike Hearn both.  Mountains are being made out of molehills.22:19
jgarzikAs a result, when the block limit is higher and there is truly a danger to decentralization, the wizards will get ignored because they squawked too loudly, too early.22:19
jgarzikOn the conservative side there is a noted lack of proposals, which leads to difficulty in taking that side seriously.  At least Adam has his thinking cap on.22:20
CodeSharkI don't think we're only talking about this block size issue, jgarzik - I think this applies generally to having any sort of hard fork process22:20
CodeSharkit's not about people wanting the network to scale, ultimately...that's a red herring22:21
jgarzikCodeShark, perhaps - the context is unavoidable.  _This_ hard fork is not going to end the world.22:21
CodeSharkit's about one group of developers wanting control over the network vs. another22:21
jgarzikand painting is thusly is disengenuous22:21
CodeSharkthat's really what it will come down to22:21
CodeSharklet's not be naive here22:22
-!- antanst [~Adium@athedsl-341422.home.otenet.gr] has joined #bitcoin-wizards22:22
phantomcircuitjgarzik, i've heard things from "what the fuck" to "i want bigger blocks without a hard fork"22:22
jgarzikleave the cloister22:22
jgarzikand get out into the world22:22
phantomcircuitjgarzik, i've yet to speak to anybody who both wanted larger blocks and understood that they required a hard fork22:22
phantomcircuit"your sample size is small and you should feel bad!"22:23
jgarzikI've literally been flying all over the world taking samples ;p22:24
CodeSharkalso, the block size increase push has a lot more to do with avoiding fee pressures than scaling22:25
CodeSharklet's also not be naive about that one :)22:25
leakypatI couldn't find anyone at my meet up who didn't want to raise the block limit, some wanted it removed with no limit22:26
phantomcircuitjgarzik, i suspect your samples are strongly biased22:26
jgarzikCodeShark, yes - and they go hand in hand.  To review, the _years long_ policy has been avoiding fee pressure.  That is the market expectation.   It is a major - and conscious - market shift to change that.22:26
jgarzikThat is not a judgement of good/bad, just a statement of fact.22:26
phantomcircuiteither way22:26
phantomcircuitnobody will be happen when shit explodes22:26
jgarzikMaybe you want fee pressure, maybe you don't.22:27
jgarzikeither way, it is a delta22:27
phantomcircuitnote: i personally will divest entirely before the fork date...22:27
jgarzikto argue to _begin_ fee pressure is a market change22:27
leakypatMost people I talk to aren't aware that fees are subsidized22:27
jgarzikand an economic policy change22:27
moajust a little fee pressure then?22:27
bramcjgarzik, 'Leave things be' as a proposal is hard to take seriously?22:27
Luke-Jrjgarzik: we have had fee pressure before22:27
jgarzikbramc, No semantics will get around the fact that it is an change in economic policy to introduce consistent fee pressure.22:28
jgarzikLuke-Jr, not consistently, http://hashingit.com/analysis/39-the-myth-of-the-megabyte-bitcoin-block22:28
bramcjgarzik, arguably the market expectation has been that the rules which everyone has bought into by participating in the system will continue to be followed22:28
Luke-Jrjgarzik: also, it's becoming more and more apparent that we will have fee pressure no matter what very soon: "stress test" spammers are going to be filling blocks as much as they can.22:29
-!- shen_noe [~shen_noe@wired042.math.utah.edu] has joined #bitcoin-wizards22:29
Luke-Jrjgarzik: I'm not sure what the link is meant to suggest.22:29
bramcjgarzik, Is a balloon at the end of a mortgage schedule a sudden change in policy?22:29
jgarzikbramc, If you want to argue for economic change, that's fine22:29
jgarzikbramc, but be honest and admit that it is different from current policy22:29
Luke-Jrjgarzik: we haven't consistently had no-fee-pressure either22:29
-!- arubi_ [~ese168@unaffiliated/arubi] has quit [Quit: Leaving]22:30
jgarzikLuke-Jr, on average yes we have.  each time the situation arises, Hearn lobbies miners to increase their block size soft limit, and/or Bitcoin Core increases default miner soft limit.22:30
jgarzikthe history is quite clear.22:30
bramcjgarzik, I am arguing for economic change, but it's also coming right on schedule, as everyone paying attention has been aware of for years22:30
-!- GAit [~lnahum@2-230-161-158.ip202.fastwebnet.it] has quit [Read error: Connection reset by peer]22:30
jgarzikthe numbers are quite clear.22:30
jgarzikbursts of fee pressure are inevitable and natural.  the long run average is low pressure / subsidized however.22:31
moafull nodes could be incentivised to pay miners for smaller blocks I suppose22:32
dgenr8people keep saying that word "subsidized". i dont think it means what they think it means22:32
gwillendgenr8: transactions are secured by miners, but miners are paid by inflation right now, not by transactions.22:32
gwillenSo the security of transactions is subsidized.22:32
bramcgwillen, Also subsidized by full nodes22:33
-!- GAit [~lnahum@2-230-161-158.ip202.fastwebnet.it] has joined #bitcoin-wizards22:33
dgenr8that makes all kinds of assumptions about the future economic value of the block reward22:33
moahearn is a good lobbyist, it has to be said ... the bitcoin foundation could have used him22:34
bramcdgenr8, Some members of the ecosystem are taking on significant costs to avoid those costs hitting others. 'subsidized' is a close enough word.22:34
dgenr8the exhg rate since the last halving pays for the next 3 halvings.22:34
bramcthe bitcoin foundation seems to be a collection of the sketchiest people you'll ever meet22:34
dgenr8so lets not get too up in arms about it22:35
-!- jmcn [~jamie@2.24.158.69] has quit [Ping timeout: 276 seconds]22:35
jgarzikmoa: hehehehe   I dunno I think hearn isn't so great as a lobbyist, he's angering everyone with this contentious fork stuff22:35
bramcdgenr8, Nobody is suggesting getting rid of the halving!22:35
jgarzikmaybe he is a lobbyist for keeping it at 1MB :)22:35
-!- jmcn [~jamie@2.24.158.69] has joined #bitcoin-wizards22:35
dgenr8read what i wrote again22:35
dgenr8exchange rate is up 10x since 2012 halving22:35
dgenr8gavin is right that this is the number miners should care about22:36
CodeSharkthere seem to be two main interests behind the fee pressure avoidance policy: 1) bitcoin maximalists who think if we only were able to convince more people to use bitcoin the network would magically be able to suddenly support hundreds of millions of new users. 2) lazy developers who don't want to try to figure out a good solution to fee bidding22:36
bramcI like fee bidding as a subject. I wish we were discussing that.22:37
jgarzikCodeShark, now who's being naive ;p22:37
CodeSharkI said "seem" :p22:37
gwillenbramc: I was interested to see that fee estimation is more widely deployed than I realized22:38
-!- droark [~droark@209-6-53-207.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com] has quit [Quit: ZZZzzz…]22:38
bramcgwillen, Where? How?22:38
gwillenthat plus safe-RBF (or CPFP) sort of gives you fee bidding22:38
gwillenbramc: let me see if I can find where I read that22:38
bramcsafe-rbf is something but it sucks. It directly reduces the potential throughput of the system as a whole, driving up prices even more22:39
jgarzikCodeShark, software & market are not prepared for consistent fee pressure.  c.f. economic policy change.22:39
-!- Giszmo [~leo@pc-185-201-214-201.cm.vtr.net] has quit [Quit: Leaving.]22:39
jgarzik"Let's change economic policies without preparing the ecosystem!" is not a responsible position.22:39
gwillenbramc: https://gist.github.com/petertodd/8e87c782bdf342ef18fb22:39
jgarziksorry bramc22:39
gwillenbramc: "As of v0.10.0 Bitcoin Core estimates fees for you based on the supply and demand observed on the network. By default it tries to pay a sufficiently large fee to get into the next block, so as demand increases it pays higher fees to compensate."22:39
gwillenjgarzik: it's clearly a chicken-and-egg problem22:39
gwillenjgarzik: nobody puts in engineering effort to fix problems that don't exist yet22:40
moamaybe we could have full nodes into a pool for assurance contracts that pays miners automatically when they produce smaller blocks ... and run it on lighthouse?22:40
bramcgwillen, *cringe* there are some control theory problems with that22:40
gwillenbramc: oh sure, but it's a first attempt at least22:40
gwillenit's better than _not_ doing it22:40
gwillenit at least gives a better starting point for RBF than just guessing blindly22:40
-!- pavel_ [~paveljani@79-98-72-216.sys-data.com] has quit [Quit: Leaving]22:40
-!- paveljanik [~paveljani@79-98-72-216.sys-data.com] has joined #bitcoin-wizards22:41
-!- paveljanik [~paveljani@79-98-72-216.sys-data.com] has quit [Changing host]22:41
-!- paveljanik [~paveljani@unaffiliated/paveljanik] has joined #bitcoin-wizards22:41
gwillenyou're right that a real auction would be better economically, but I'm not even sure how you'd begin to do that22:41
-!- ThomasV [~ThomasV@unaffiliated/thomasv] has joined #bitcoin-wizards22:41
CodeSharkit clearly is chicken-and-egg...we need to push the envelope...and can't expect things to always be economically smooth22:41
bramcjgarzik, I very much want to discuss economic preparation, but the conversation is all getting derailed by talk about a hard fork and rbf not being supported and things which are generally sabotaging forward progress :-P22:41
CodeSharkwe need to be faced with the problem to motivate us to find a solution - and it's arguably easier to solve it now rather than later...while blocks are still mostly subsidized by reward22:41
bramcI've also talked with the lightning network guys and am trying to help with that as I can22:42
gwillenjgarzik: do you follow rusty's blog at all? http://rusty.ozlabs.org/22:42
gwillenjgarzik: he has good posts recently about (1) what gets crowded out if blocks fill, and (2) what happens to latency if blocks grow. (Both simulations based on guesses, obviously.)22:43
bramcgwillen, Miner algorithms for what to accept are *mostly* straightforward, it's the clients deciding on fees which is hard.22:44
gwillenbramc: agree on that, yes22:44
bramcCome to think of it, a lot of people not cringing about the suggested fee estimation techniques is because they don't have much experience with control theory. I have, uh, a lot more experience than I ever cared to with control theory.22:45
gwillenWhen you talk about control theory, is the issue that you can't reason adequately about what fees are required based on the data you have? Or that a bunch of clients trying to naively do so at the same time will interact badly with each other?22:46
gwillenI.e. fees will oscillate wildly or something?22:46
moabramc ... multivariate problem requiring LQR, perhaps with LQE thrown in?22:47
gwillenBecause I could imagine both of these being an issue although it seems like both of them _could_ be fine in practice.22:47
-!- Mably [~Mably@unaffiliated/mably] has joined #bitcoin-wizards22:48
bramcgwillen, oscillation is one example of a problem. The issue is that if you have some algorithm for setting prices, and everybody's using it, then prices will be set based on what the previous prices were... which were also set by algorithm22:48
gwillenThat's not inherently bad... but I agree that it could be22:48
bramcmoa, unfortunately each participant only does things very sporadically, so those kinds of information-heavy approaches don't even apply22:49
bramcI believe that no matter what your general approach to price setting is, you always want to make an attempt to lowball early and only raise the price if it fails22:50
bramcOtherwise prices have a tendency to get high and get stuck there for no particular reason22:50
gwillenwell, this particular problem doesn't seem too likely to get stuck there22:51
gwillendepends on how the estimator works I guess, but the marginal price to get into a block is just above the minimum price of any transaction in that block22:52
gwillenand if a block is literally full of transactions above a given price, it's hard to imagine the fair price being below that22:52
CodeSharkgwillen, miners could fake them22:52
gwillenmmmmmm, true22:52
bramcgwillen, Yes, but if everybody assumes that they need to offer that same amount to get into the next block then it may happen, even if it's untrue22:53
gwillenbramc: if everybody is _willing_ to offer that amount to get into the next block, it can't be untrue22:53
CodeSharkunfortunately, without listening to the network gossip it seems very difficult to accurately assess fees...22:53
gwillenthe only way the true price could be lower is if people are letting the fee estimator pay money it's not actually worth to them, because they're asleep at the switch22:53
bramcgwillen, maybe it looks like it's true because the miners fill up the extra space with self-payments22:54
CodeSharkjust looking at past blocks is not enough22:54
gwillenyes, miner cheating could do it22:54
gwillenalthough you'd need a minimum hashrate fraction or a cartel, to make it profitable22:54
gwillenI don't know what that fraction would be22:54
gwillenotherwise you'd be bleeding fake fees to other miners22:54
-!- spinza [~spin@197.89.24.164] has quit [Ping timeout: 252 seconds]22:55
gwillen(oh, that's a lie, nevermind.... of course you only mine your fake fees into your own blocks)22:55
bramcAlso it could be that the fees on the next block will be dramatically lower than the last one, so maybe offering the same amount is a bad idea because you're paying too much.22:55
CodeSharkin principle, if miners are checked by sufficient parties, recent blocks would tend to be a fairly good guide...but I think bramc's claim of the "stuck" phenomenon is clients that aren't smart enough to figure out when miners start cheating22:55
gwillenright, although that can be counteracted by looking at multiple past blocks, and looking at the mempool22:55
gwillenyeah, miner cheating is the only serious issue I'm seeing here, but it's pretty serious22:55
bramcLooking at the mempool can help, although it's fraught with danger22:56
bramcAnd it requires new logic to get that info, and whoever you're talking to might lie about it if you're on spf...22:56
gwillenthe mempool can be full of lies but if you're smart you can't be fooled for long22:56
phantomcircuiti doubt very much that there is a general solution to the problem that doesn't as it's first step assume that miners are ordering transactions on a feerate priority basis22:56
gwillenphantomcircuit: that's fine, they largely do...22:57
bramcphantomcircuit, Yes we all agree on that22:57
CodeSharkand they are more likely to do so even more if we have a real fee market22:57
CodeSharkassuming perfect transparency, it's the economically rational strategy22:57
bramcAs a general rule, there will always be some tradeoff between time for transactions to complete and fee paid22:59
CodeSharkof course, off-chain mining contracts might screw up even that assumption, though :)22:59
bramcAt the extremes there will undoubtedly be daily and weekly cycles22:59
bramcSo if there's a situation where, for example, there's fee pressure during peak times but none at all at other times, which will most likely happen for a while, you have to make a choice about how much you care about speed vs. fee23:00
phantomcircuitgwillen, in that case it's as simple as sorting the mempool using some f(feerate, age) priority basis23:00
phantomcircuit(age being a proxy for whatever other policies miners might have in place)23:01
CodeSharkthe communication complexity (especially for thin clients) is significant for mempool stuff23:01
phantomcircuitCodeShark, there's no way around that23:02
phantomcircuitthin clients need to have a mempool23:02
bramcCodeShark, the easy thing to do is for thin clients to simply ask the going rate. This has an obvious and horrific attack...23:02
phantomcircuitalthough maybe it's not unreasonable to outsource fee estimation23:03
phantomcircuit(on a strict fee rate basis)23:03
zookosecond-price auction23:03
-!- spinza [~spin@197.89.24.164] has joined #bitcoin-wizards23:03
CodeSharkfee market makers :p23:03
bramcphantomcircuit, There aren't many full nodes out there - it would be trivial for miners to run them just to lie to spf clients about how big the fees are23:04
moathin clients having a mempool (or sample of) is an intriguing idea23:04
zookohttps://en.wikipedia.org/wiki/Vickrey_auction23:04
phantomcircuitbramc, i was actually thinking an authenticated trusted source23:04
bramcThis is all making my 'conservative' approach sound like a good idea23:04
phantomcircuitthe alternative is for thin clients to receive all transactions23:04
bramczooko, Yes we've all agreed to assume that the miners follow the obvious algorithm23:04
-!- damethos [~damethos@unaffiliated/damethos] has joined #bitcoin-wizards23:05
moahttps://en.wikipedia.org/wiki/Dutch_auction23:05
bramczooko, In principle you could require that the fees charged to all transactions be the same but, well, that would allow miner stuffing, and Bitcoin Doesn't Work That Way23:05
zookoI didn't mean that -- I meant some vague generalization/extension that maintains the Vickrey property of true preference revelation.23:06
zookoMaybe when I wake up from this sleep I'll have an idea how that could actually work. Probably not. Goodnight!23:06
zooko(P.S. there's a thing called Generalized Second-Price Auction, used for keyword ad sales...)23:07
bramcMy conservative idea, for those who haven't seen me talk about it already, is that clients don't do any of this mempool or historical lookup stuff at all. They start at a nominal fee, maybe the minimum allowed, add a random amount between 0 and 10%, and for each block where their transaction isn't accepted add another 10% compounding23:08
phantomcircuitbramc, that's probably a good general solution if replace by fee is available23:09
phantomcircuit(and no not the ffs version...)23:09
bramcThis has the advantage of being completely trustless and easy to implement. It has the disadvantages that it requires real rbf, and makes transactions take longer23:09
bramcThe extreme amount of noise in the capacity rate due the the stochastic nature of mining blocks doesn't help anything23:11
bramcFor that reason alone being willing to wait a bit longer will get you lower fees23:12
CodeSharkperhaps that issue will be remedied with some of the proposals out there for reducing block time variance23:12
CodeSharkeventually23:12
bramcCodeShark, reducing block time variance comes with its own problems, like increasing the amount of orphan blocks23:13
CodeSharknot if you also use them for PoW23:13
bramcIt's probably best to assume that there will be fee/time tradeoffs as part of the new normal23:14
CodeSharkbut obviously such a change is unlikely in the very near term on the Bitcoin network...23:14
leakypatIf you have a transaction in the memory pool with a high fee and then you get a number of blocks in quick succession that clear down the pool but miss your transaction , there is no way to lower your fee23:15
bramcYou can also do a hybrid approach, where you figure out an expected fee based on recent history or mempools or something, then lowball it and slowly raise23:15
CodeSharkI think the fee/time tradeoff is inherent - the only question is how to optimize this for particular use cases and automate it as much as possible23:15
leakypatAs miners would always mine the one  with the highest fee23:15
-!- Mably [~Mably@unaffiliated/mably] has quit [Ping timeout: 272 seconds]23:16
bramcleakypat, Yes yet another reason to start low23:16
CodeSharkright, the "stuck" phenomenon doesn't even require cheating miners - just a bunch of dumb clients :)23:16
bramcIf the fees go down right after your transaction goes through then, well, you should have been wiling to raise your fee slower.23:16
bramcmempool has the other problem that it could potentially get fairly washed out, so you might be looking at only a fraction of what will eventually go into the block23:18
CodeSharkbeing able to listen to the network gossip will almost certainly help you estimate more accurately more quickly23:19
CodeSharkso those devices that have access to this should certainly make use of that information if they can23:20
CodeSharkthere's also the communication complexity/decentralization tradeoff23:21
bramcThe day/night cycle should be taken seriously. That's likely to be dominant at first23:22
CodeSharkI sort of like the model of fee market makers - where you can pay a fee to someone who guarantees inclusion within a certain number of blocks or you get a refund23:24
CodeSharkand they then work their complex algorithms using reliable broadband connections23:24
CodeSharkas long as there are enough of these out there23:25
CodeSharkif there's only one or two, it's dangerous :)23:25
CodeSharkit's a decentralized fee estimation model that still supports thin clients23:26
leakypatWallets could probably provide that as a service23:27
bramcAnother thing a wallet can do is use the last fee it successfully used as a starting point for the next one23:27
-!- zmanian [~zmanian@c-24-5-125-31.hsd1.ca.comcast.net] has joined #bitcoin-wizards23:28
leakypatFrom its pool of users (if a centralized wallet)23:29
leakypatPossibly could abstract fees completely , and charge per month or something for confirmation within n blocks guaranteed23:30
-!- antanst [~Adium@athedsl-341422.home.otenet.gr] has left #bitcoin-wizards []23:31
* leakypat ponders if that could be done trustless and seamlessly23:31
-!- cdecker [~cdecker@pc-10367.ethz.ch] has quit [Ping timeout: 276 seconds]23:32
-!- cdecker [~cdecker@pc-10367.ethz.ch] has joined #bitcoin-wizards23:33
leakypatThe wallet service that broadcasts the transaction can have its own pool of inputs to use for attaching inputs for fee escalation23:33
phantomcircuit<CodeShark> perhaps that issue will be remedied with some of the proposals out there for reducing block time variance23:34
phantomcircuitim not aware of any such proposals23:34
phantomcircuitindeed i dont believe they're possible...23:34
CodeSharkphantomcircuit: mostly the GHOST-like ideas23:34
CodeSharkamiller had such a proposal, too23:35
phantomcircuitCodeShark, iirc amiller's proposal was to prevent pooling right?23:36
CodeSharkthat's another potential benefit23:37
phantomcircuitthe problem there is that it... prevents pooling!23:37
CodeSharkwell, ultimately what you want is for pooling to be incorporated into the protocol itself23:37
CodeSharkyou can mine at lower difficulty and still have your work count towards the most difficult chain23:37
* phantomcircuit looks around for petertodd to say treechains23:38
CodeSharklol23:38
-!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has quit [Quit: Leaving]23:38
amillerphantomcircuit, no the point wasn't to prevent pooling23:39
amillerphantomcircuit, the point of that proposal (which predates ghost by a long time!) was to remove the block time magic setting23:39
-!- zmanian [~zmanian@c-24-5-125-31.hsd1.ca.comcast.net] has quit [Ping timeout: 272 seconds]23:41
phantomcircuitamiller, can you elaborate?23:42
amillerim not sure this is the best motivation for it now, so i can tell you what i thought the point was23:43
amillerthe point was just to get rid of the hardcoded 10 minute block time and replace it with an automatically adjusting mechanism23:44
phantomcircuitamiller, based on...?23:44
amillerit should increase the target difficulty when the network is losing too much stale work23:44
amillerit should lower the target difficulty as much as possible until it starts losing stale work23:45
amillerthe simple idea is to fix a desired 'target' for stale blocks23:45
amillerthe last time i asked i think it was 2%, maybe you should target 20% or 50%23:45
-!- orperelman [~orperelma@bzq-109-67-207-175.red.bezeqint.net] has joined #bitcoin-wizards23:45
phantomcircuitamiller, that's neat but probably fails to account for miners estimating costs23:46
amillerphantomcircuit, what do you mean23:46
amillerone thing i didn't pursue but now makes sense given ghost23:47
amilleris whether you should give some rewards to the stale blocks or punish them23:47
amillerghost gives them some discount factor, maybe they should be given full credit i dont know23:47
phantomcircuitamiller, it's currently fairly easy for a miner to calculate their revenues for the month23:49
phantomcircuitit seems like it would be difficult to implement something like this without changing that23:49
amillerok this shouldn't make that any worse (i think it would be a useful idea to *prevent* large miners from doing that anyway)23:49
amiller(or to put it another way, i think it would be a good idea to tempt large miners to gamble on an even bigger reward but more uncertainty)23:49
phantomcircuityeah that's probably true23:50
-!- p15 [~p15@111.193.161.178] has joined #bitcoin-wizards23:50
-!- priidu [~priidu@unaffiliated/priidu] has joined #bitcoin-wizards23:51
-!- bramc [~bram@99-75-88-206.lightspeed.sntcca.sbcglobal.net] has quit [Quit: Leaving]23:52
amillerbut i dont have any good idea for how to set the target time23:53
amillerer the target 'stale' blocks23:53
amilleri dont know how to attach it to any market mechanism23:53
amillermaybe there's a way to solve the lbocksize problem this way23:54
amillersdlerner wanted to decrease the block time rather than tinker with blocksize23:54
amillerso i dunno maybe there's some way to let the average txes in a block or txfees determine a target stale blocks rate, and then use that to set difficulty23:55
CodeSharkwe cannot assume that the tx fees are not the miners themselves if the model gives them any incentive to do so23:56
amilleryeah23:57
CodeSharkalso, variable block times has another potential danger...people need to understand that the security level is not proportional to the number of confirmations23:57
amillerthats true but i wouldn't let such a concern about presentation to users narrow my options at this point23:58
CodeSharkthe security level is given by how hard it is for someone to reverse the transaction - so this is what must be quantified23:58
--- Log closed Tue Jun 23 00:00:31 2015

Generated by irclog2html.py 2.15.0.dev0 by Marius Gedminas - find it at mg.pov.lt!