00:53:41jcrubino:is a provably fair high volume bitcoin currency exchange by 2015 achievable?
00:53:51jcrubino:provably solvent
00:55:09maaku:jcrubino: you could do that today
00:55:15maaku:but good luck getting people to use it
00:55:26jcrubino:businesses or customers?
00:55:38maaku:well, either
00:56:48maaku:jcrubino: there are already ways to do, e.g., voting pools for moving funds in or out of an open-transactions server
00:56:52maaku:which has the properties you asked for
00:57:36jcrubino:what practical limitations are there?
00:57:56jcrubino:limitations to the implemenation?
00:58:24maaku:if you want ot stay within the ecosystem, there are ways of doing similar things with colored coins, tagged assets (e.g. freimarkets), or scripting language extensions
00:58:30maaku:any one of which could be finished in 2014
00:58:45maaku:if given proper funding and attention
00:59:10maaku:jcrubino: performance limitations would be a question for #opentransactions
01:00:58jcrubino:where can I read about scripting language extentions?
01:02:32maaku:jcrubino: there isn't a good writeup on that, but I'm organizing a project to come up with a proposal
01:02:37maaku:you can read about that here: https://groups.yahoo.com/neo/groups/concatenative/conversations/messages/4950
01:03:27jcrubino:in your opinion will ethereum be successful enough to stand on its own?
01:04:22jcrubino:of course that fact that your working on extending scripting says alot.
01:04:24maaku:there's also the great thread on all the evil things that could be done with scripting language extensions : https://bitcointalk.org/index.php?topic=278122.0
01:04:32maaku:which actually has some good non-evil ideas in there too
01:04:42maaku:jcrubino: etherium as written? no.
01:05:08maaku:but that's why i'm working on my own proposal of course
01:05:50maaku:i see great practical utility in a more expressive script, but not in the way etherium is doing it
01:05:53maaku:but that's just my opinion
01:28:31irc.freenode.net:Disconnected from irc.freenode.net (ERROR :Closing Link: S0106c0c1c0894c25.vs.shawcable.net (Ping timeout: 245 seconds))
01:29:45holmes.freenode.net:topic is: "Bitcoin research, hardfork wishlist, ideas for the future - see also: https://en.bitcoin.it/wiki/Hardfork_Wishlist https://en.bitcoin.it/wiki/User:Gmaxwell/alt_ideas. This channel is logged at http://download.wpsoftware.net/bitcoin/wizards/. For questions about the logs talk to andytoshi."
01:29:45holmes.freenode.net:Users on #bitcoin-wizards: andytoshi-logbot K1773R DougieBot5000_ c--O-O shinybro_ CodeShark Emcy ghtdak1 roidster rdymac breesy RoboTeddy MoALTz Krellan_ spinza [\\\] HM_ andytoshi otoburb gribble mappum go1111111 samson_ Muis forrestv licnep IOI_ coryfields skinnkavaj c0rw1n nsh zacm heffner tucenaber shesek OneFixt ironzorg krypto pajarillo jtimon trn ryan-c Xarikins hnz ageis maaku austinhill Sangheili wangbus areaurbum firepacket perrier nOgAnOo jcrubino
01:29:45holmes.freenode.net:Users on #bitcoin-wizards: gavinandresen e4xit midnightmagic shinybro Luke-Jr Sorcier_FXK nanotube hno` michagogo|cloud Alanius azariah4 tacotime_ crucif0rm salsa poggy Guest982 warren Mikalv iddo aksyn matrixfox jron UukGoblin jgarzik Krellan asoltys pigeons petertodd gmaxwell fagmuffinz optimator_ espes___ wumpus poeticlobster jrmithdobbs heakins sipa realazthat a5m0 comboy bobke Graet harrow EasyAt Fistful_of_Coins typex Ryan52 phantomcircuit @ChanServ rs0_
01:29:45holmes.freenode.net:Users on #bitcoin-wizards: crescendo kinlo amiller helo qwertyoruiop grazs imsaguy BlueMatt sl01 edulix
01:29:45holmes.freenode.net:[freenode-info] channel trolls and no channel staff around to help? please check with freenode support: http://freenode.net/faq.shtml#gettinghelp
01:42:33areaurbum_:areaurbum_ is now known as areaurbum
02:41:49jcrubino:jcrubino has left #bitcoin-wizards
02:51:20fract:Not sure if any foundation members are here, but I think it would be prudent to ask Mark karpeles to step down from his board seat. He just threw bitcoin under the bus and caused substantial PR damage in the news today due to his misinformation and FUD. It was a reckless and irresponsible press release. Something has to be done.
03:32:30gribble:Coinjoin Status: current session is open for 12 more minutes. There are currently something like 1 transactions in the pot. The most popular output value is 0.02497. To participate, visit https://www.wpsoftware.net/coinjoin/ or http://xnpjsvp7crbzlj3w.onion/ .
03:33:58a5m0:i'm interested to see stats on bc.i coinjoin
03:37:02petertodd:a5m0: piuk said they're setting about 1.5 users per join
03:38:17luke-jr_:luke-jr_ is now known as Luke-Jr
03:51:20roidster:roidster is now known as Guest15262
04:00:50a5m0:ah so they just act as the counterparty for the needed coins i guess
04:13:23warren:hmm, no adam
04:50:44fract:what kind of a transaction is this/? http://webbtc.com/tx/aa62bdd690de061a6fbbd88420f7a7aa574ba86da4fe82edc27e2263f8743988
04:51:58petertodd:fract: a fuckup
04:52:14petertodd:fract: mtgox's custom code lost a few hundred (thousand?) btc a few years back
04:54:25fract:no shit.. there a few transactions like that
04:54:32fract:over 1000btc outputs unspendable
04:59:54Xarian:Xarian is now known as Xarikins
06:32:06tacotime_:tacotime_ is now known as tt_away
06:40:34maaku:re: sipa's normative txid patch, perhaps it'd be better to use a base58 serialization so it is visually distinctive?
06:40:57maaku:a checksum might even be useful in that context
07:14:11HobGoblin:HobGoblin is now known as Guest48059
08:03:32krypto:hello everybody
08:28:43c0rw1n:hello krypto
08:49:23krypto: is DMD just another shitty coin, or does it have anything going for it?
08:49:42c0rw1n:no idea. What's dmd?
08:50:20krypto:diamond coin
08:51:04krypto:it looks like a copycoin but i am no expert or programmer
08:54:06c0rw1n:never heard of it, but then i'm not following the appearance of every scamcoin that pops up
08:54:24maaku:krypto: wrong channel
08:55:05krypto:thanks guys
11:54:01Guest48059:Guest48059 is now known as UukGoblin
12:57:34nsh:nsh is now known as snh
13:03:34snh:snh is now known as nsh
15:05:17warren:adam3us: know anyone that would be good to prove that malleability is fully stopped?
15:05:27warren:adam3us: including "algebraic mutations of DSA beyond the single one we know"
15:06:00warren:adam3us: we could have a soft fork, but we have to know what we need first...
15:09:54adam3us:warren: i was thinking maybe (non-trivial) change to not use the signature but the public key making the signature, so then you would not need the sig algo to be non-crypto-level-malleable; its a new requirement on algorithms that people dont usually think about or care about strongly
15:11:46adam3us:are the tx-ids hashed at the leaves of the merkle tree sorted? or is it arbitrary/order received from the tree builders perspective?
15:12:00adam3us:"form the bottom row of the tree with the ordered double-SHA-256 hashes of the byte streams of the transactions in the block" in the wiki protocol specification... but what order is that?
15:23:19petertodd:adam3us: order is the order the transactions are evaluated when the block is received; ie the order the transactions modify the utxo set state
15:23:49petertodd:adam3us: which is kinda unfortunate as that makes block validation much harder to parallelize
15:34:04ghtdak1:ghtdak1 has left #bitcoin-wizards
15:38:24adam3us:petertodd: so the tx in the block are pre-validated by the block builder (the succesful miner), and the leaves are in the order in which the block builder received the tx.
15:38:50adam3us:petertodd: now if post-mining-event any tx in the block are invalid, the whole block is declared as invalid and ignored I presume?
15:39:36petertodd:adam3us: bingo
15:48:32roidster:roidster is now known as Guest45257
16:06:18adam3us:maaku: the utxo compaction and trie work.. does that imply a new coinbase version and format at some point?
16:07:34sipa:that would be a hard fork
18:17:26enodios:enodios has left #bitcoin-wizards
18:27:01maaku:adam3us: a new block version, yes
18:27:38maaku:similar to bip 34
18:28:20petertodd:adam3us: blockheader format would stay the same; you'd either commit to the (u)txo tree in the coinbase, or you can do a SPV-soft-fork by making merkleroot=H(actual-merkle-root | secondary tree)
18:30:37maaku:petertodd: that would be a hard-fork for bitcoin-qt, right?
18:31:32petertodd:maaku: yes, for full-nodes
21:11:09su_awesome:hi, so if I understand correctly, due to the malleability attack going on right now, it's insecure to send shared coin through blockchain.info?
21:11:29su_awesome:(using the coinjoin that blockchain.info implemented)
21:11:49andytoshi:su_awesome: absolutely the wrong channel
21:12:19su_awesome:andytoshi, oh sorry I thought this was a channel that discussed these sorts of things
21:12:53su_awesome:because of the "Bitcoin research" in the title
21:13:25andytoshi:su_awesome: o.O that means (academic) research, not anything to do with random companies or their software
21:13:29BlueMatt:su_awesome: coinjoin has been officially moved to non-research (ie #bitcoin-dev)
21:13:41BlueMatt:and discussing bc.i's implementation is probably more #bitcoin
21:13:58andytoshi:oh, i missed the coinjoin part, that's a reasonable misunderstanding
21:14:52su_awesome:I see, so this channel is more about theoretical side of BTC instead of what's already written and implemented?
21:15:12petertodd:su_awesome: it's not insecure, although it might not work
21:15:27petertodd:su_awesome: (bc.i won't lose funds if a cj fails part way through)
21:16:21andytoshi:su_awesome: correct. we try to keep it ontopic and low-volume because most regulars here have brain-intensive day jobs and are busy
21:16:53petertodd:su_awesome: specifically, most of the regulars read everything here
21:17:18su_awesome:petertodd, I see, a user on #bitcoin said that this tx was sent using coinjoin, it took quite a while to be verified, perhaps the attack was the cause? - https://blockchain.info/tx/0654039b8d8e9f97c06a448951d16918a9d1a9ccec4c8e3d252ceb54f843b6f3?show_adv=false
21:18:20petertodd:su_awesome: yeah, could be, bc.i uses multi-step mixes, so if one step is mutated the rest fail
21:19:05petertodd:su_awesome: coinjoin as a concept isn't vulnerable; multi-step mixes aren't required
21:20:21su_awesome:oh, good to know about that. I hope everything gets better soon. Anyway, I won't bother you guys with my simple questions. Thanks :)
21:21:07su_awesome:su_awesome has left #bitcoin-wizards
21:27:10nicksavers:nicksavers has left #bitcoin-wizards
22:01:18qwertyoruiop:qwertyoruiop is now known as xXx_1337masterqw
22:01:48xXx_1337masterqw:xXx_1337masterqw is now known as xXx1337swagqw3r7
22:01:57xXx1337swagqw3r7:xXx1337swagqw3r7 is now known as x1337swagqw3r7y0
22:14:26x1337swagqw3r7y0:x1337swagqw3r7y0 is now known as qwertyoruiop
23:59:21realazthat:sipa: lol all these problems with the exchanges, I tested for them when making the unit tests for my deposit system, when I was querying you a few weeks back
23:59:46realazthat:I remarked to someone else how I bet these things were not accounted for in other systems
23:59:52realazthat:so right :D