| 00:45:46 | contrapumpkin: | contrapumpkin is now known as copumpkin |
| 02:12:00 | sipa1024: | sipa1024 is now known as sipa |
| 03:06:45 | fanquake_: | fanquake_ is now known as fanquake |
| 04:51:45 | jgarzik: | jgarzik is now known as jgarzik_ |
| 05:59:15 | rhadamanthus: | rhadamanthus has left #bitcoin-wizards |
| 06:46:22 | lclc_bnc: | lclc_bnc is now known as lclc |
| 07:28:21 | lclc: | lclc is now known as lclc_bnc |
| 07:56:23 | lclc_bnc: | lclc_bnc is now known as lclc |
| 09:05:13 | barjavel.freenode.net: | topic is: This channel is not about short-term Bitcoin development | http://bitcoin.ninja/ | This channel is logged. | For logs and more information, visit http://bitcoin.ninja |
| 09:05:13 | barjavel.freenode.net: | Users on #bitcoin-wizards: andy-logbot soundx Luke-Jr koshii Quanttek hktud0 Mably shesek paveljanik cletus11 zwischenzug orik e1782d11df4c9914 TheSeven bit2017 OneFixt ryanxcharles eslbaer__ fanquake koad Dr-G3 sipa p15 justanot1eruser prodatalab zooko epscy_ Graftec Guest89184 moa DoctorBTC grandmaster hashtag Apocalyptic MoALTz xabbix_ gavinandresen c0rw1n hashtag_ orperelman dansmith_btc brand0 spinza copumpkin gnusha_ Meeh_ Cory andytoshi tromp__ NikolaiToryzin |
| 09:05:13 | barjavel.freenode.net: | Users on #bitcoin-wizards: devrandom wiz btcdrak PaulCapestany d1ggy tromp_ Hunger- platinuum mappum use_zfs_yo Oizopower jbenet cluckj Tjopper jaekwon espes__ qwopqwop huseby lclc ebfull indolering mortale adlai alawson Xzibit17 nuke1989 kinlo Starduster_ michagogo waxwing hollandais otoburb hguux__ ahmed_ PRab yrashk luny Emcy nsh kyletorpey dgenr8 delll bosma HaltingState amincd SubCreative binaryatrocity wizkid057 so HM2 berndj Krellan phedny [d__d] stonecoldpat |
| 09:05:14 | barjavel.freenode.net: | Users on #bitcoin-wizards: TD-Linux warptangent maaku roasbeef gwillen CodeShark isis BrainOverfl0w burcin_ BlueMatt wumpus sdaftuar MRL-Relay nickler Alanius harrow Iriez Logicwax a5m0 phantomcircuit sl01 yoleaux catcow brad_ earlz davout btc___ PFate nick1234abcd__ gmaxwell Anduck bobke_ comboy_ null_radix poggy dasource LarsLarsen amiller artifexd deego fluffypony cryptowest rw_8197 dardasaba veox warren gribble K1773R CryptOprah Muis kumavis coryfields optimator |
| 09:05:14 | barjavel.freenode.net: | Users on #bitcoin-wizards: weex jcorgan Fistful_of_Coins EasyAt jaromil mr_burdell forrestv cfields Eliel_ morcos nanotube s1w Keefe bbrittain petertodd tripleslash BananaLotus smooth @ChanServ ryan-c ajweiss lechuga_ Graet helo throughnothing Adrian_G fenn JonTitor heath kanzure catlasshrugged pigeons asoltys_ livegnik eric azariah Taek crescendo d9b4bef9 lnovy sneak |
| 09:19:54 | lclc: | lclc is now known as lclc_bnc |
| 12:04:33 | Meeh_: | Meeh_ is now known as Meeh |
| 12:18:02 | cletus11: | cletus11 has left #bitcoin-wizards |
| 12:18:19 | lclc_bnc: | lclc_bnc is now known as lclc |
| 13:57:52 | instagibbs: | come on wizards it's not e^{} or e^() it's exp() :) |
| 14:11:49 | Anduck: | Anduck is now known as Guest67385 |
| 14:13:20 | Guest67385: | Guest67385 is now known as Anduck |
| 15:03:27 | dgenr8: | watched gmaxwell and adam3us dealing with a really crappy video link ... fascinating interview. my eyebrows raised at the part where you talked about using moxiebox to keep miners from modifying their software |
| 15:03:53 | dgenr8: | are we talking about closed source? or do I have this all wrong (I hope) |
| 15:13:49 | andytoshi: | dgenr8: definitely not closed source |
| 15:14:19 | andytoshi: | dgenr8: the idea is that the consensus code is in a (small enough to be interpreted by auditable and clearly-correct code) assembler language |
| 15:14:45 | andytoshi: | dgenr8: then it is hashed before execution to ensure that everyone is running exactly the same code |
| 15:15:06 | andytoshi: | this only applies to consensus code, not policy issues, network transport, etc |
| 15:32:22 | dgenr8: | if a misguided miner wanted to modify it, could he? |
| 15:32:36 | dgenr8: | yes, the consensus code |
| 15:40:06 | CoinMuncher: | yes, but the point is that would be his problem, not anyone elses. |
| 15:49:21 | dgenr8: | how does a remote node know what code I'm running? and supposing this is possible, btcd must adapt or die? |
| 15:57:56 | nsh: | * nsh blinks |
| 15:58:08 | nsh: | i think there's a misunderstanding |
| 15:58:21 | andytoshi: | dgenr8: ofc a miner -could- modify the code, but he'd gain literally nothing except to have stopped mining bitcoin |
| 15:58:45 | andytoshi: | dgenr8: and if btcd is running functionally different code than bitcoin core (and no doubt they are) they already have a problem |
| 16:00:27 | dgenr8: | nsh: could you point me to the source of your understanding please |
| 16:02:28 | nsh: | well, i haven't seen the video you're referring to and don't know awfully much about the moxiebox ideas in general |
| 16:02:36 | nsh: | so i should reserve comment until i'm better informed |
| 16:08:56 | andytoshi: | you can probably search the logs for "moxie" ... i don't think this has been written up anywhere |
| 16:14:17 | siraj: | any thoughts on automated transactions? It would allow for atomic cross chain transfers between blockchains with this implemented http://ciyam.org/at/ |
| 16:16:15 | maaku: | siraj: you can do atomic cross chain transactions today |
| 16:16:18 | siraj: | if this was implemented in bitcoin you could spend bitcoin on filecoin based storage (IPFS) assuming both implemented AT. Seamless. It could be apart of the W3C of the internet of money |
| 16:16:43 | siraj: | maaku: what was the enabling technology for that in BTC? |
| 16:16:54 | nsh: | internet-of-X considered harmful |
| 16:16:56 | maaku: | siraj: bitcoin script. |
| 16:17:28 | maaku: | siraj: to the rest, AT is hideously complex and will never be implemented in bitcoin |
| 16:18:28 | maaku: | we may hopefully see some more targetted changes to bitcoin script that make it more expressive, but it would need to be sensitive to consensus issues |
| 16:19:01 | zooko: | siraj: https://en.bitcoin.it/wiki/Atomic_cross-chain_trading |
| 16:19:10 | siraj: | dope, reading up on it thx |
| 16:19:10 | fluffypony: | andytoshi: have you got the alts.pdf commit history up on github or not? |
| 16:19:15 | zooko: | siraj: but be warned, I think there is an attack on that through txn malleability. |
| 16:19:35 | zooko: | Maybe someone should add that caveat to that wiki page... maybe me... |
| 16:19:49 | nsh: | * nsh smiles |
| 16:19:53 | fluffypony: | nsh: you mean you don't want your connected lightbulb ordering you replacement toilet paper? |
| 16:19:53 | siraj: | zooko: plz do |
| 16:20:33 | nsh: | well, once you put it that way, i'm very excited. i might write a book for tim o'reilly! |
| 16:20:59 | nsh: | https://i.imgur.com/AwxjWZF.png |
| 16:21:11 | nsh: | ^ DARPA cyber-grand-challenge *smg* |
| 16:21:39 | nsh: | the fingerprint-bone's connected to the wifi-bone. the wifi-bone's connected to the washingmachine-bone |
| 16:21:48 | fluffypony: | "smart fingerprints" |
| 16:22:41 | nsh: | Now heaaaaar the word of the Lord! |
| 16:45:08 | andytoshi: | fluffypony: no, sorry, it's on my todo list... right now it's at git://git.wpsoftware.net/bitcoin/alt-essay.git |
| 16:45:19 | fluffypony: | tks |
| 16:51:22 | andytoshi: | zooko: i'm blocked by cloudflare .. can you say whether the wiki version is comprehensible? if not you may want to copy the version from the sidechains whitepaper http://blockstream.com/sidechains.pdf |
| 16:51:41 | andytoshi: | the tiernolan bct thread that i adapted that from wasn't really comprehensible |
| 16:52:14 | andytoshi: | (the sidechains wp should also have a malleability caveat, but i think we didn't because bip62 was already in progress |
| 16:56:31 | zooko: | For future reference, it might be worth mentioning that malleability *would* be a problem in the following way, if malleability were possible. |
| 16:56:40 | zooko: | Although I recognize that the side-chains paper was already long and dense. :-) |
| 16:57:29 | zooko: | andytoshi: https://en.bitcoin.it/wiki/Atomic_cross-chain_trading looks good to me. |
| 18:10:16 | lclc: | lclc is now known as lclc_bnc |
| 19:41:05 | lclc_bnc: | lclc_bnc is now known as lclc |
| 20:28:11 | maaku: | andytoshi: we aren't building chains of unconfirmed transactions though |
| 20:28:30 | maaku: | oh you mean in referening the atomic cross-chain work |
| 21:42:42 | dgenr8: | andytoshi: How can a remote node know what code I'm running? I can think only of some kind of signature performed by obfuscated code. |
| 21:49:54 | lclc: | lclc is now known as lclc_bnc |
| 22:04:53 | gmaxwell: | dgenr8: I think adam misspoke when he said something like "prevent soft forks"; though you can do ugly things to prevent people from changing software he wasn't talking about that, but rather have a strong public commitment to no intentional changes (e.g. never again have some coordinated soft fork) to the core, and have a design that makes accidental changes unlikely. |
| 22:05:26 | gmaxwell: | (you can 'prevent' people from changing the software by using remote attest, though the strength of that is limited.) |
| 22:08:50 | dgenr8: | gmaxwell, thanks :) |
| 22:11:32 | nsh: | remote attestation as only as strong as the the precision of timing measurement crossed the optimality of the attested algorithm |
| 22:53:28 | fanquake_: | fanquake_ is now known as fanquake |