| 00:28:41 | a5m0_: | a5m0_ is now known as a5m0 |
| 02:33:33 | rdymac-: | rdymac- is now known as rdymac |
| 06:08:40 | phantomcircuit: | i probably need to rethink this audit procedure |
| 06:08:43 | phantomcircuit: | it takes 3 hours |
| 06:08:44 | phantomcircuit: | >.> |
| 07:50:58 | petertodd: | sipa: my therapist tells me I wrote a compiler in PHP, but the memories are repressed |
| 07:51:22 | sipa: | my condolences |
| 07:51:35 | petertodd: | gmaxwell: yeah probably - I need to implement a ChainState class and associated tests first though before I'm going to worry much... :) |
| 08:31:08 | RoboTeddy: | would it work to publish additional blocks (along the lines of GHOST) even when the rarity of the discovered block is less than the current difficulty? |
| 08:31:43 | RoboTeddy: | (just the block header -- not the contents -- since only the header is necessary to prove work) |
| 08:32:14 | RoboTeddy: | the idea being that this POW is useful for showing that a miner was working on a given chain, and perhaps should thus be counted by other nodes when determining which chain is valid |
| 10:39:21 | jtimon: | btw maaku I think we should change the nGranularity + nQuantity stuff on subtransactions, instead you could just have a "proportion" field replacing nquantity and just get rid of granularity. Alternative nQuantity can represent how much you take from the first output and the rest are calculated proportionally |
| 14:57:09 | [\\\]: | [\\\] is now known as Guest69368 |
| 16:32:02 | maaku: | jtimon: IIRC the point was to enable fill-or-kill orders |
| 16:32:37 | maaku: | but I also haven't considered how having nGranularity/nQuantity affects composition of sub-transactions |
| 16:33:36 | maaku: | i don't think special-treating one output would have the right semantics |
| 16:37:20 | zzyzx: | zzyzx is now known as roidster |
| 16:55:42 | jtimon: | mhmm, yes, fill-or-kill...I guess you could have granularity=0 to specify my behaviour, but it's still needed |
| 17:33:30 | HobGoblin: | HobGoblin is now known as Guest37104 |
| 17:38:21 | Aesthetic: | Aesthetic is now known as Logicwax |
| 17:56:59 | Guest37104: | Guest37104 is now known as UukGoblin |
| 18:01:51 | lnovy: | lnovy is now known as MagicalG1g |
| 18:02:04 | MagicalG1g: | MagicalG1g is now known as lnovy |
| 18:13:37 | pigeons_: | pigeons_ is now known as pigeons |
| 18:51:55 | BCB: | anyone watching the US House hearing on bitcoin |
| 18:52:56 | eristisk: | Is there another one BCB? |
| 18:52:59 | eristisk: | On C-SPAN? |
| 18:53:13 | BCB: | http://www.ustream.tv/channel/hclive15 |
| 18:53:19 | BCB: | it's getting a little hostile |
| 18:53:25 | BCB: | Dr. Bitcorn is back |
| 21:16:35 | BCB: | "Bitcoin is written in a language NO ONE can understand is contains about 17MB of source code" - David Andolfatto St. Louis Fed - http://www.stlouisfed.org/dialogue-with-the-fed/bitcoin-and-beyond.cfm |
| 21:16:59 | jrmithdobbs: | haha, what |
| 21:17:26 | jrmithdobbs: | it's like 2k lines of (bad) c++ last i looked ... |
| 21:17:56 | sipa: | quite a bit more than that |
| 21:18:14 | maaku: | wtf? |
| 21:18:17 | sipa: | though ehm... qrc_bitcoin.cpp already is like 11 MB, and it is autogenerated :p |
| 21:18:55 | Emcy: | what does that module do |
| 21:19:04 | sipa: | resources, i guess |
| 21:19:17 | sipa: | images |
| 21:19:20 | sipa: | translations |
| 21:19:22 | Emcy: | oh |
| 21:19:54 | gmaxwell: | BCB: the slide says "almost nobody understands" which is probably arguable... what percentage of the world population has a working familairity with C++? How many really understand it? |
| 21:20:22 | BCB: | what about side of code base 17MB ?? |
| 21:20:34 | maaku: | it's only ... one of the most popular and successful ISO standard languages? |
| 21:20:59 | sipa: | there's 1.4 MB in the non-gui code |
| 21:21:07 | sipa: | also, #bitcoin-dev |
| 22:56:33 | petertodd: | all the discussion about whether or not the code can be understood is silly anyway - the idea behind the bitcoin system is plenty simple, and there probably exists enough social consensus to make the technical consensus follow suite |
| 22:57:10 | petertodd: | modulo uncertainty risk of course |
| 23:12:59 | nsh: | funny story about source code and the st. louis federal reserve bank |
| 23:13:03 | nsh: | i'll tell you in six years |
| 23:19:45 | gmaxwell: | * gmaxwell imagines the statue of limitations big read clock on nsh's wall |
| 23:19:50 | gmaxwell: | s/read/red/ |
| 23:24:10 | nsh: | * nsh smiles |