1 2011-09-27 01:45:48 <CIA-101> bitcoin: Con Kolivas * r5a4dabe23381 cgminer/main.c: Add message about donation to startup.
  2 2011-09-27 02:11:08 <CIA-101> bitcoin-release: Dev Random master * rb2fcc7e / (3 files in 2 dirs): Add devrandom for 0.4.0 - http://git.io/VY4q6A
  3 2011-09-27 02:25:46 <CIA-101> bitcoin: Con Kolivas * r648c6b7c7c8b cgminer/main.c: Intensity is signed integer, fix its display.
  4 2011-09-27 02:25:47 <CIA-101> bitcoin: Con Kolivas * r35a490b90cf9 cgminer/main.c: Explicitly disable dynamic mode when an intensity is set.
  5 2011-09-27 02:35:43 <CIA-101> bitcoin: Con Kolivas * r1dc6e64b680d cgminer/main.c: Set dynamic to false for all devices given separate args...
  6 2011-09-27 02:45:43 <CIA-101> bitcoin: Con Kolivas * r75e214349ae3 cgminer/main.c: Display per device intensity in various status lines.
  7 2011-09-27 03:05:43 <CIA-101> bitcoin: Con Kolivas * rd2db7be54b41 cgminer/main.c: Roll any work we can even if other requests are staged.
  8 2011-09-27 03:25:43 <CIA-101> bitcoin: Con Kolivas * r454772efc502 cgminer/NEWS: Update NEWS.
  9 2011-09-27 03:25:44 <CIA-101> bitcoin: Con Kolivas * r16dce491f2f4 cgminer/configure.ac: Bump version to 2.0.5
 10 2011-09-27 03:45:03 <CIA-101> bitcoin: Luke Dashjr * r948dfa248460 gentoo/app-misc/cgminer/ (Manifest cgminer-2.0.5.ebuild): app-misc/cgminer-2.0.5
 11 2011-09-27 04:27:55 <CIA-101> poolserverj: shadders * ba951ab896d4 r148 /bitcoin-jsonrpc/src/main/java/com/shadworld/poolserver/conf/Res.java: add timestamps to logging
 12 2011-09-27 04:27:56 <CIA-101> poolserverj: shadders * fdcde6a76d49 r147 /poolserverj-main/src/main/java/com/shadworld/poolserver/ (5 files in 2 dirs): - duplicate change import from patch for - cleaner now checks for dead longpoll connections
 13 2011-09-27 04:27:57 <CIA-101> poolserverj: shadders * 4ff5adf74486 r146 /poolserverj-main/src/main/java/com/shadworld/poolserver/ (5 files in 2 dirs): - cleaner now checks for dead longpoll connections.
 14 2011-09-27 04:38:49 <luke-jr> ;;bc,stats
 15 2011-09-27 04:38:52 <gribble> Current Blocks: 147072 | Current Difficulty: 1755425.3203287 | Next Difficulty At Block: 147167 | Next Difficulty In: 95 blocks | Next Difficulty In About: 16 hours, 32 minutes, and 45 seconds | Next Difficulty Estimate: 1687809.56838232 | Estimated Percent Change: -3.85181591971
 16 2011-09-27 05:12:14 <jargon_> They're after me, guys. I saw a van today, it followed me to the food bank :(
 17 2011-09-27 05:12:26 <jargon_> The NSA knows that I know things.
 18 2011-09-27 05:13:32 <jargon_> I need a place to hide out for a while, guys. Anyone
 19 2011-09-27 05:13:42 <jargon_> I took out an NSA satellite, they're looking for me
 20 2011-09-27 05:16:07 <jargon_> Anyone, please?
 21 2011-09-27 05:16:45 <jargon_> I'm willing to trade a couch or even a floor for information about how broken bitcoin's security is. I've spent a lot of time reverse engineering the encryption protocols.
 22 2011-09-27 05:19:58 <[Tycho]> :)
 23 2011-09-27 05:20:40 <jargon_> [Tycho]: Can I hide at your house for a while? The NSA can't get a hold of me or bitcoin will be even more fucked than it is right now.
 24 2011-09-27 05:23:06 <jargon_> Seriously I need help, guys :(
 25 2011-09-27 06:00:43 <CIA-101> bitcoin: Con Kolivas * rf6d35a70a884 cgminer/main.c: Must initialise the donorpool mutex or it fails on windows.
 26 2011-09-27 07:43:55 <CIA-101> poolserverj: shadders * 4ae325cf0e19 r149 /bitcoin-jsonrpc/src/main/java/com/shadworld/poolserver/conf/Res.java: - tidy up trace targets
 27 2011-09-27 10:45:00 <CIA-101> bitcoinjs/bitcoinjs-lib: Stefan Thomas master * r7715c41 / (src/base58.js src/bitcoin.js): Wrapped Bitcoin and Base58 in platform-neutral closures. - http://git.io/A9LUdA
 28 2011-09-27 10:45:01 <CIA-101> bitcoinjs/bitcoinjs-lib: Stefan Thomas master * rd7ce1e5 / src/ecdsa.js : Corrected encoded form with correct padding. See #1. - http://git.io/84FIfw
 29 2011-09-27 10:47:53 <CIA-101> bitcoinjs/bitcoinjs-lib: Stefan Thomas master * rd985697 / src/ecdsa.js : Added credit on encoding fix. See #1. - http://git.io/Uc4-Iw
 30 2011-09-27 11:25:37 <CIA-101> bitcoinjs/node-bitcoin-exit: Stefan Thomas master * r4be2422 / server.js : Load settings from currently used instance of bitcoin-p2p. - http://git.io/zwTCfA
 31 2011-09-27 11:41:53 <sacarlson> what happend to the test dir in bitcoin?
 32 2011-09-27 11:44:15 <sacarlson> there was a ~bitcoin/src/test  before I was expecting more complete test but seems it was removed
 33 2011-09-27 12:04:11 <sipa> sacarlson: it's still there: https://github.com/bitcoin/bitcoin/tree/master/src/test
 34 2011-09-27 12:05:52 <sacarlson> sipa: ya I don't know what I was looking at now I see it
 35 2011-09-27 12:06:18 <sacarlson> I'm also very happy to see the new bitcoin-qt build,  I just compiled it on Ubuntu 10.04 with just a few warnings
 36 2011-09-27 12:12:42 <sacarlson> the new build commit 9a1ce869690fe87fbce169a4b685695dc9e575f6 seems to also be running fine on ubuntu 10.04,  I'll later try it on my ubuntu 11.04 box
 37 2011-09-27 12:24:48 <sacarlson> I've had to download the entire index on this build and I'm seeing alot of orphan blocks on the console is this normal to see now?  been a while since I've downloaded the index
 38 2011-09-27 12:25:25 <sacarlson> it's now at block number 11000
 39 2011-09-27 12:50:51 <luke-jr> ;;bc,stats
 40 2011-09-27 12:50:54 <gribble> Current Blocks: 147130 | Current Difficulty: 1755425.3203287 | Next Difficulty At Block: 147167 | Next Difficulty In: 37 blocks | Next Difficulty In About: 6 hours, 21 minutes, and 43 seconds | Next Difficulty Estimate: 1696465.95026453 | Estimated Percent Change: -3.3586942937
 41 2011-09-27 13:04:44 <sipa> casascius: did you test again with the addition of CWallet::MarkDirty() ?
 42 2011-09-27 13:05:09 <casascius> I will, real quick
 43 2011-09-27 13:06:58 <casascius> importing something now, waiting for rescan
 44 2011-09-27 13:09:41 <casascius> yeah it works now
 45 2011-09-27 13:10:00 <sipa> o/
 46 2011-09-27 13:11:51 <CIA-101> bitcoin-release: Matt Corallo master * re9bc7e8 / (2 files): Add bluematt for 0.4.0. - http://git.io/CdDe6w
 47 2011-09-27 13:12:00 <BlueMatt> ;;later tell devrandom nice, forgot to add mine...just did
 48 2011-09-27 13:12:00 <gribble> The operation succeeded.
 49 2011-09-27 13:12:48 <copumpkin> BlueMatt: out of curiosity, you understand elliptic curves? I saw you asking about them yesterday
 50 2011-09-27 13:13:34 <BlueMatt> understand...meh mostly, never done too much reading on them, but I get the concept
 51 2011-09-27 13:15:52 <BlueMatt> devrandom: ping
 52 2011-09-27 13:16:53 <pakiar> good morning
 53 2011-09-27 13:16:59 <BlueMatt> morning
 54 2011-09-27 13:17:07 <BlueMatt> (ish)
 55 2011-09-27 13:20:17 <CIA-101> bitcoin: Gavin Andresen master * ra8c108b / src/main.cpp : Remove DoS penalty for SigOpCount or immature transactions - http://git.io/feogMw
 56 2011-09-27 13:23:01 <devrandom> BlueMatt: pong
 57 2011-09-27 13:24:14 <BlueMattBot> Yippie, build fixed!
 58 2011-09-27 13:24:29 <BlueMatt> devrandom: what do you think of moving https://github.com/devrandom/bitcoin-release to bitcoin/bitcoin-release to make the gitian process more "official"?
 59 2011-09-27 13:25:25 <sipa> sounds like a good idea to m
 60 2011-09-27 13:25:26 <sipa> e
 61 2011-09-27 13:25:30 <devrandom> sure... I don't know if you can do a move on github, but you can fork it
 62 2011-09-27 13:25:41 <BlueMatt> devrandom: in other news, Im looking at getting gitian-downloader working on win32, Ive gotten it compiled but now I need to get it packaged nicely with gpg and sha256sum binaries
 63 2011-09-27 13:25:47 <devrandom> or git push/pull
 64 2011-09-27 13:25:56 <BlueMatt> (though it might have to wait till after I can get qt and bitcoin-qt compiled in mingw)
 65 2011-09-27 13:26:18 <sipa> how were the bitcoin-qt binaries for windows compiled before?
 66 2011-09-27 13:26:27 <BlueMatt> using windows afaik
 67 2011-09-27 13:26:31 <sipa> ah, right
 68 2011-09-27 13:27:10 <devrandom> thanks for dealing with the windoze stuff
 69 2011-09-27 13:27:32 <BlueMatt> not done yet...
 70 2011-09-27 13:28:29 <devrandom> I was thinking of building something like Jenkins for gitian... or maybe I should integrate with Jenkins
 71 2011-09-27 13:29:00 <BlueMatt> that would be cool, jenkins does already have a nice plugin system...
 72 2011-09-27 13:29:04 <devrandom> I want to have automated builds with a way to drill down to files to more easily look at diffs
 73 2011-09-27 13:29:26 <devrandom> can you display arbitrary data?
 74 2011-09-27 13:29:34 <devrandom> it will be pretty structured...
 75 2011-09-27 13:29:36 <BlueMatt> afaik yea
 76 2011-09-27 13:29:45 <BlueMatt> you can do some crazy things afaik
 77 2011-09-27 13:30:06 <BlueMatt> as long as it fits in html/css/js...or not (the irc bot is a plugin)
 78 2011-09-27 13:30:09 <BlueMatt> BlueMattBot: help
 79 2011-09-27 13:30:10 <BlueMattBot> Available commands:
 80 2011-09-27 13:30:11 <BlueMattBot> alias [<alias> [<command>]] - defines a new alias, deletes one or lists all existing aliases
 81 2011-09-27 13:30:12 <BlueMattBot> botsnack [<snack>] - om nom nom
 82 2011-09-27 13:30:13 <BlueMattBot> cb - list jobs which are currently in progress
 83 2011-09-27 13:30:14 <BlueMattBot> currentlyBuilding - list jobs which are currently in progress
 84 2011-09-27 13:30:15 <BlueMattBot> health [<job>|-v <view>] - show the health of a specific job, jobs in a view or all jobs
 85 2011-09-27 13:30:15 <BlueMatt> oh god...why did I do that
 86 2011-09-27 13:30:16 <BlueMattBot> q - show the state of the build queue
 87 2011-09-27 13:30:17 <BlueMattBot> s [<job>|-v <view>] - show the status of a specific job, jobs in a view or all jobs
 88 2011-09-27 13:30:27 <gmaxwell> haha it wouldn't have gone on much longer.
 89 2011-09-27 13:30:42 <BlueMatt> oh well, jenkins is gonna restart for updates in a sec anyway
 90 2011-09-27 13:32:37 <nanotube> BlueMattBot: botsnack donut
 91 2011-09-27 13:32:38 <BlueMattBot> nanotube: thanks a lot! om nom nom. I could eat donut all day long
 92 2011-09-27 13:32:42 <nanotube> heh
 93 2011-09-27 13:33:07 <BlueMatt> ;;botsnack
 94 2011-09-27 13:33:07 <gribble> Forget the snack, just send me some bitcoins at 1MgD6rah5zUgEGYZnNmdpnXMaDR3itKYzU :)
 95 2011-09-27 13:33:47 <sipa> BlueMattBot: botsnack and compile
 96 2011-09-27 13:33:48 <BlueMattBot> sipa: great! yum yum. I really like that and compile
 97 2011-09-27 13:33:52 <BlueMattBot> sipa: great! yum yum. I really like that and compile
 98 2011-09-27 13:33:52 <sipa> BlueMattBot: botsnack and compile
 99 2011-09-27 13:35:02 <devrandom> BlueMatt: recently ran across http://www.sonarsource.org/
100 2011-09-27 13:35:44 <devrandom> here's the sonar installation for bitcoinj: http://ci.bitcoinj.org/job/BitCoinJ-trunk/
101 2011-09-27 13:36:54 <casascius> I posted a 25 BTC bounty for a blkindex.dat rebuild function in the forums: https://bitcointalk.org/index.php?topic=45864
102 2011-09-27 13:37:02 <BlueMatt> devrandom: looks cool, though I dont see a plugin for C++, but you might tell AlexWaters about it as well (he is now the official bitcoin testing/qa guy)
103 2011-09-27 13:37:49 <devrandom> ah, right...
104 2011-09-27 13:37:53 <devrandom> I haven't compared them yet
105 2011-09-27 13:38:04 <devrandom> dang, Jenkins has a lot of extension points
106 2011-09-27 13:38:26 <gmaxwell> The C rules in that are really thin.
107 2011-09-27 13:39:37 <sipa> casascius: in the discussion of pull #492 rose the idea of a separate tool that would do a full verification of a block chain file
108 2011-09-27 13:39:42 <devrandom> I'll focus on Jenkins for now
109 2011-09-27 13:40:05 <casascius> sipa: has anyone done any work on this tool
110 2011-09-27 13:40:06 <sipa> casascius: it sounds like the right place to allow that tool to perform blkindex.dat rebuilding as well
111 2011-09-27 13:40:10 <sipa> no
112 2011-09-27 13:40:30 <sipa> but i don't think it's hard, you can reuse (possibly share) quite some code with bitcoind
113 2011-09-27 13:40:49 <casascius> sipa: what would be verified?  the full chain structure?  or just that, for example, the file can be walked without any truncated blocks etc.
114 2011-09-27 13:41:12 <sipa> the same as is done now while downloading the chain
115 2011-09-27 13:41:21 <sipa> so, full check
116 2011-09-27 13:41:26 <sipa> including signatures
117 2011-09-27 13:41:28 <gmaxwell> I was thinking about writing a compressed format for the blockchain which validated it as a side effect (because most invalid things would be unrepresentable)
118 2011-09-27 13:41:30 <casascius> sipa: can you give me the tl;dr on why this would be desirable as a separate tool rather than as part of the client?
119 2011-09-27 13:42:15 <sipa> gmaxwell: what do you mean with compressed format?
120 2011-09-27 13:42:57 <sipa> casascius: the main client won't be doing signature verification for blocks below the last lock-in
121 2011-09-27 13:44:34 <casascius> sipa: do we need or want such verification to occur?  it seems to me that such verification would be skipped for a pretty good reason
122 2011-09-27 13:44:46 <gmaxwell> ...
123 2011-09-27 13:45:34 <sipa> it's certainly useful from a performance perspective
124 2011-09-27 13:45:40 <casascius> in fact, if it were embedded in the client, a rebuild might also be an opportunity to discard any orphaned blocks below the last checkin point
125 2011-09-27 13:46:17 <gmaxwell> sipa: Smaller files that can be distributed to new full nodes to avoid the need to syncup over the network, which conserves space by omitting data which can be calculated directly (e.g. the prev hash in the header is the hash of the prior block), or which is restricted by the rules e.g. timestamps can be coded as UINT(median of last 11+1,2^31) (or better, with an unequal pdf that favors the real timestamp distribution)
126 2011-09-27 13:47:11 <sipa> gmaxwell: sounds interesting
127 2011-09-27 13:47:53 <sipa> but how far will you go
128 2011-09-27 13:48:10 <casascius> what would really save a lot of space is if those "smaller files" could be stripped of all spent transactions, and the hash of them included in the block chain
129 2011-09-27 13:48:29 <sipa> eg, whether a particular txout is spent, can also be inferred
130 2011-09-27 13:48:36 <casascius> i realize there's more questions than answers with respect to that, but that's going to become a concern faster than it can be dealt with, i fear
131 2011-09-27 13:48:44 <sipa> casascius: a full node can't do that
132 2011-09-27 13:49:11 <gmaxwell> sipa: yes, for TXINs I was expecting to purely code the index of the possible unspent inputs instead of the hash.
133 2011-09-27 13:50:00 <gmaxwell> Of course, it would recover the hash, and that feeds into the signatures.. so ultimately a single hash will almost prove that the decode from such a tool is a valid rules following blockchain.
134 2011-09-27 13:50:11 <sipa> gmaxwell: hmm, what about a per-tx bit vector?
135 2011-09-27 13:58:09 <sacarlson> I've been working on a simple plugin  method for multicoin to enable added and modified features of the core bitcoin system to support testing and prototypes of new chains
136 2011-09-27 13:58:51 <sacarlson> and modifications of present chains
137 2011-09-27 13:59:37 <sacarlson> any one else working on such things?
138 2011-09-27 14:02:37 <sipa> gmaxwell: if time is a pure poisson process with rate factor 1/600s, you need 10.68 bits :)
139 2011-09-27 14:05:56 <sipa> gmaxwell: as the version is fixed, the prevhash is known, the merkle root can be calculated from the transactions, the timestamp doesn't need more than 16 bits, nBits can be derived from the previous blocks, only nonce remains in the block header
140 2011-09-27 14:06:26 <sipa> so you'd need let's say 6 bytes + #transactions for a block header?
141 2011-09-27 14:06:43 <gmaxwell> Yes, and if I want to be totally nuts I can drop 8 bits or so from the nonce and let the decoder solve the block.
142 2011-09-27 14:06:59 <gmaxwell> (and have a bit coded with very high probablity to signal that the first solution was the right one)
143 2011-09-27 14:07:16 <sipa> transactions themselves are harder
144 2011-09-27 14:07:39 <gmaxwell> Use a table of previously used scripts. So almost all scripts cost ~nothing to code.
145 2011-09-27 14:07:52 <sipa> yup
146 2011-09-27 14:08:16 <gmaxwell> tx_inputs get coded based on the set of all possible inputs.. but after they're selected the output values are constrained.
147 2011-09-27 14:08:32 <gmaxwell> I can't do much with the signature, but with it I can recover the public key.
148 2011-09-27 14:08:52 <sipa> use a reference of the style "N blocks ago, transaction M" instead of txins?
149 2011-09-27 14:09:14 <sipa> hmm, that's quite expensive
150 2011-09-27 14:09:21 <gmaxwell> Well I was thinking of simply sorting the inputs most recent to least recent and using a non-uniform coding of the integer.
151 2011-09-27 14:09:50 <gmaxwell> I'd have to look at the data to pick a good coding scheme.
152 2011-09-27 14:10:22 <sipa> most recent to least recent, disregarding already spent ones?
153 2011-09-27 14:10:34 <gmaxwell> Right.
154 2011-09-27 14:10:39 <gmaxwell> (I assume it would look like a linear ramp down to uniform probably a few hundred blocks back)
155 2011-09-27 14:12:17 <sipa> i'm very interesting :)
156 2011-09-27 14:13:03 <sipa> *interestED
157 2011-09-27 14:15:57 <casascius> I have expanded my bounty offering to include a payable bounty for implementing sweepprivkey, and the total bounty is 100 BTC
158 2011-09-27 14:16:13 <gmaxwell> One possibility is that instead of writing out a block chain (or in addition to) it writes out the final set of open transactions, and a minimal perfect hash for doing lookups against it... and we teach the node software to use that instead of a blockchain for validation prior to the checkpoint.  It would take up a LOT less disk.
159 2011-09-27 14:16:23 <gmaxwell> (and be a lot faster)
160 2011-09-27 14:18:08 <sipa> so you need a compact representation for a map txid:outid -> amount, for all unspent outputs?
161 2011-09-27 14:18:20 <sipa> oh, and script
162 2011-09-27 14:19:05 <gmaxwell> Well, you just write the actual txns out (perhaps with some compression, e.g. a common script table), and make a compact map to map the txid to byte offset.
163 2011-09-27 14:19:58 <gmaxwell> There are algorithims for writing these tables which produce encodings which are very efficient, much more so than anything that makes incremental updates cheap. :)
164 2011-09-27 14:20:22 <sipa> casascius: Privkeys appearing in transactions (e.g. coinbase) need to be converted to a binary bitcoin address before being added as keys to this index.
165 2011-09-27 14:20:27 <sipa> you mean pubkeys, i suppose?
166 2011-09-27 14:21:52 <gmaxwell> I suppose to make casascius happy it could also write out an address lookup structure too... though scanning all the open txn nicely packed would already be a lot cheaper than scanning the whole blockchain.
167 2011-09-27 14:23:06 <casascius> yep pubkeys, thanks, i will fix ity
168 2011-09-27 14:24:37 <sipa> gmaxwell: i expect that you're able to reduce the size of the blockchain by a factor, if you do all that
169 2011-09-27 14:31:05 <gmaxwell> Any idea what the total number of txouts there ever was is?
170 2011-09-27 14:36:00 <gmaxwell> In any case, it would be _much_ smaller than the current data. Possibly small enough that we could just ship the historic chain with the software.
171 2011-09-27 14:51:09 <epscy> casascius: i got some coins I ordered from you today, just wanted to say thanks
172 2011-09-27 14:51:23 <epscy> sorry i meant to priv msg that
173 2011-09-27 14:52:40 <epscy> but since i brought up the topic, did you consider translating the the address to a barcode and putting that on the hologram as well as the first 8 chars?
174 2011-09-27 14:53:22 <epscy> seems like that would make it easy to automatically verify the coin is worth what it says it is
175 2011-09-27 15:00:27 <sipa> gmaxwell: i'm generating some statistics
176 2011-09-27 15:03:24 <casascius> thanks for ordering the coins...yeah i consdiered the barcode but chose not to...limited space, and hologram company couldn't do 2d barcodes on them
177 2011-09-27 15:07:57 <nanotube> casascius: you sure 8 is enough? in the gpg keyid space, there are already known to be collisions at 8digit id level...
178 2011-09-27 15:09:29 <casascius> 8 is not enough to rule out collisions, just enough to make them unlikely for the casual task of verifying the balance.  I have PGP signed a full list of my coins
179 2011-09-27 15:09:40 <casascius> or at least the addresses I have generated and had printed on stickers
180 2011-09-27 15:09:43 <epscy> casascius: ahh fair enough, i didn't think i was the first to think of it
181 2011-09-27 15:09:57 <sipa> gmaxwell: 3608559 txouts, 1032828 unspent txouts
182 2011-09-27 15:15:06 <AlexWaters> sipa: do you have a recommendation for testing #524? Gavin mentioned unit tests, were these added in your 9/20 commit?
183 2011-09-27 15:15:19 <sipa> no, i didn't write any
184 2011-09-27 15:16:04 <gmaxwell> sipa: so... maybe on the order of 319 MB for the blockchain, from some fairly conservative numbers based on those counts.
185 2011-09-27 15:17:24 <AlexWaters> sipa: ok - i'll try some manual tests for now, but I think a unit test will help it get merged faster
186 2011-09-27 15:17:39 <gmaxwell> almost all of that is from signatures.
187 2011-09-27 15:19:50 <sipa> gmaxwell: i assume you can encode all scripts using the following trick: extract all constant numbers, match table of 255 most-frequently occuring scripts, if so, output # + constants, otherwise output 0 + original script
188 2011-09-27 15:20:27 <sipa> oh wait, you want pubkeys/hash160 using key recovery
189 2011-09-27 15:23:12 <sipa> AlexWaters: i'll add a test for base64 encoding/decoding
190 2011-09-27 15:23:22 <AlexWaters> sipa: awesome, thank you!
191 2011-09-27 15:24:33 <tcatm> do we have a testsuite that will compile bitcoin on all target platforms?
192 2011-09-27 15:24:52 <BlueMatt> jenkins does ubuntu+win32
193 2011-09-27 15:24:55 <BlueMatt> no osx
194 2011-09-27 15:25:16 <BlueMatt> (and does sanity testing of the binaries - open, download part of chain, make rpc calls, etc)
195 2011-09-27 15:25:39 <tcatm> hrm. I have replaced all crypto++ calls with openssl but I need to modify all makefiles to remove crypto++ completely
196 2011-09-27 15:25:46 <BlueMatt> well gui is disabled atm because I have to figure out how to compile qt on mingw on linux...
197 2011-09-27 15:27:05 <AlexWaters> BlueMatt: very cool, is the bot operational?
198 2011-09-27 15:27:41 <gmaxwell> sipa: hm. actually thats way high because I was also assuming signatures on the unspent tx.
199 2011-09-27 15:28:16 <BlueMatt> it exists, operational...not so much.  Ive got to get qt cross compiling first so jenkins kinda fell to the backburner...that said, you can take a look at jenkins.bluematt.me now (I can give you a login) and can easily clone the bitcoin job to point to any random git repo you like
200 2011-09-27 15:28:17 <gmaxwell> yea, can't recover pubkey in txout though... because it might never be spent.
201 2011-09-27 15:31:18 <AlexWaters> BlueMatt: that would be awesome. i'm interested to see what options are available when I log in
202 2011-09-27 15:31:42 <AlexWaters> which*
203 2011-09-27 15:33:15 <nanotube> casascius: well, i guess the question is, if you have a cascoin, you check by 8 digits, and you find a collision - is there any alternative to breaking open the coin to check, to verify what you have?
204 2011-09-27 15:33:43 <casascius> nanotube: yeah I published a pgp-signed pastebin of all the coins i have used so far...and put the link in the forums
205 2011-09-27 15:33:45 <AlexWaters> bluematt: do you know how many builds can this do simultaneously, and the build time? I'm curious about any performance limitations
206 2011-09-27 15:33:56 <nanotube> casascius: ah ok
207 2011-09-27 15:34:03 <casascius> i prepared 11000 addresses and published about the first 3500 of them
208 2011-09-27 15:34:49 <BlueMatt> AlexWaters: in theory as many as the vm can handle, its currently limited to 1 due to the way I originally wrote the test scripts (they collide if you start running a build while testing), but that could be changed
209 2011-09-27 15:35:14 <BlueMatt> in theory you could even add other vms so that you could do more...
210 2011-09-27 15:35:53 <casascius> http://pastebin.com/XebW67V4
211 2011-09-27 15:37:31 <AlexWaters> BlueMatt: this sounds awesome. I'm very excited. When did you add the blockchain download test, and is it public?
212 2011-09-27 15:38:21 <BlueMatt> AlexWaters: you can take a look at the scripts being run under configure in the side bar of any project
213 2011-09-27 15:38:31 <BlueMatt> the blockchain download sanity check is in Bitcoind-sanitytest
214 2011-09-27 15:39:55 <BlueMatt> bbiab
215 2011-09-27 15:42:48 <AlexWaters> BlueMatt: I have a bunch of questions, OK to email them to you?
216 2011-09-27 15:43:48 <tcatm> could someone have a look at https://github.com/tcatm/bitcoin/commit/e1632950ce1202b1cc421041a90715afbcb36521 before I make a pull request and check whether I got all makefiles right?
217 2011-09-27 15:47:36 <midnightmagic> tcatm: why are you stripping out cryptopp?
218 2011-09-27 15:48:23 <BlueMatt> midnightmagic: why keep it?
219 2011-09-27 15:48:47 <tcatm> midnightmagic: there's no good reason to keep it around when the internal mining isn't optimized for speed
220 2011-09-27 15:49:41 <midnightmagic> Well, the naive answer would be because Wei Dai is a god. But that's just because I don't know why it's going away because I haven't been paying much attention to bitcoin development the last few months.
221 2011-09-27 15:50:11 <jrmithdobbs> midnightmagic: it's only used in the mining code
222 2011-09-27 15:50:12 <BlueMatt> mostly because its an extra dep that is (for some reason?) in our src tree and it really isnt used for much of anything
223 2011-09-27 15:50:33 <midnightmagic> well okay then. :) i suppose all mining is going to be external, even for forks anyway.
224 2011-09-27 15:50:57 <midnightmagic> just curious really, I'm not challenging the wisdom of it or anything.
225 2011-09-27 15:52:29 <sipa> AlexWaters: simple test case added (RFC4648 test vectors)
226 2011-09-27 15:55:34 <sipa> AlexWaters: tests for message signing are somewhat harder, as they require a functional wallet with a key in it
227 2011-09-27 16:04:43 <AlexWaters> thanks sipa
228 2011-09-27 16:05:28 <sipa> though i think that would be very interesting, modifying CWallet so that it can manage an in-memory wallet
229 2011-09-27 16:05:48 <sipa> using a fake clock, and possibly artificially low difficulty
230 2011-09-27 16:05:57 <sipa> to simulate more complex situations
231 2011-09-27 17:53:09 <ByteCoin> ;;seen copumpkin
232 2011-09-27 17:53:09 <gribble> copumpkin was last seen in #bitcoin-dev 4 hours, 40 minutes, and 20 seconds ago: <copumpkin> BlueMatt: out of curiosity, you understand elliptic curves? I saw you asking about them yesterday
233 2011-09-27 17:55:35 <ByteCoin> ;;later tell copumpkin You were talking about ECC and pairing-based stuff. I am reasonably expert if you wish to discuss something.
234 2011-09-27 17:55:35 <gribble> The operation succeeded.
235 2011-09-27 17:56:16 <sipa> ByteCoin: did you see i modified the message signature thing to use key recovery?
236 2011-09-27 17:58:44 <copumpkin> yo
237 2011-09-27 17:58:55 <copumpkin> ByteCoin: oh, was just wondering if anyone around here had played with them :) didn't have any particular questions
238 2011-09-27 18:00:21 <ByteCoin> sipa: I saw it. It's excellent.
239 2011-09-27 18:00:40 <sipa> i hope the implementation is sound
240 2011-09-27 18:00:41 <ByteCoin> copumpkin: Ok.
241 2011-09-27 18:01:05 <ByteCoin> sipa: Me too. These things are hard to edge test
242 2011-09-27 18:01:06 <sipa> it's quite a few steps, and i've always learned you shouldn't implement cryptographic primitives yourself :)
243 2011-09-27 18:01:47 <copumpkin> unless it's in haskell
244 2011-09-27 18:01:54 <sipa> even then
245 2011-09-27 18:02:04 <sipa> agreed, there is less chance for implementation errors
246 2011-09-27 18:02:08 <ByteCoin> I'm glad we're using base64 too.
247 2011-09-27 18:02:12 <sipa> but there may be edge cases you need to be aware of
248 2011-09-27 18:02:18 <copumpkin> well, you'd want an Integer implementation that doesn't have short-circuiting
249 2011-09-27 18:02:29 <copumpkin> and would probably want to avoid being lazy :)
250 2011-09-27 18:02:34 <copumpkin> since that is also effectively short-circuiting
251 2011-09-27 18:02:42 <copumpkin> (to avoid leaking timing information)
252 2011-09-27 18:02:44 <ByteCoin> copumpkin: Timing attacks are not an issue
253 2011-09-27 18:02:55 <copumpkin> I was just talking about implementing crypto in general
254 2011-09-27 18:02:58 <copumpkin> in haskell
255 2011-09-27 18:03:01 <ByteCoin> Ok
256 2011-09-27 18:03:10 <copumpkin> not even sure what you guys are talking about :)
257 2011-09-27 18:03:20 <sipa> ECDSA key recovery
258 2011-09-27 18:03:49 <ByteCoin> If you want to avoid timing attacks then changing the curve basis to something like Edwards curves would be better
259 2011-09-27 18:04:35 <ByteCoin> sipa: When will your signature code go mainline?
260 2011-09-27 18:04:36 <gmaxwell> sipa: oh you implemented recovery for the signing?   <3
261 2011-09-27 18:04:44 <gmaxwell> <3 <3 <3
262 2011-09-27 18:04:58 <gmaxwell> and base 64 too?
263 2011-09-27 18:05:04 <sipa> yes
264 2011-09-27 18:05:10 <sipa> i suppose i should submit the ECDSA_SIG_recover_key_GFp function to OpenSSL, though
265 2011-09-27 18:05:14 <sipa> :)
266 2011-09-27 18:05:41 <gmaxwell> sipa: good, you've saved me the trouble of writing recovery for the compressor should I get around to writing it.
267 2011-09-27 18:06:18 <ByteCoin> gmaxwell: Were you asking about taking advanage of the special format of p for doing the ECC arithmetic?
268 2011-09-27 18:06:18 <sipa> gmaxwell: i wrote the actual key recovery function months ago