--- Log opened Fri Dec 13 00:00:51 2013
03:44 < epscy> does anyone know if 0.8.6 has the address index patch?
03:46 < sipa> hell no
03:55 < epscy> sipa: is the address index controversial?
03:56 < epscy> I thought it was going to be included in the next release
03:57 < sipa> unless someone brings it up to date, no
03:57 < sipa> and i,m no fan of it myself
03:57 < sipa> see the (closed) pull request for why
04:00 < epscy> thanks i will check it out later
04:02 < sipa> https://github.com/bitcoin/bitcoin/pull/2802
04:04 < wumpus> depending on the use case, you might use the watch-only pull which is more up to date: https://github.com/bitcoin/bitcoin/pull/3383
04:04 < sipa> wumpus: regarding watch-only, i agree having a way to query spendable vs unspendable balance
04:04 < wumpus> sipa: yep, I'm going to work on that
04:05 < sipa> (it applies equally to locked outputs)
04:08 < wumpus> indeed
04:11 < wumpus> unspendable unconfirmed, spendable confirmed, unspendable confirmed,, and spendable unconfirmed... hmm
04:15 < sipa> combinatorial explosion
04:16 < sipa> how about two booleans to be passed to getbalance
04:16 < sipa> in the gui maybe:
04:16 < wumpus> yes, well in this case one boolean passed to GetBalance and GetUnconfirmedBalance
04:16 < sipa> Balance: X (+ Y unspendable)
04:16 < wumpus> but yeah explaining it to the user is most difficult
04:17 < wumpus> ah that would work
04:17 < sipa> only shown if Y is nonzero
04:17 < wumpus> right
17:05 < gmaxwell> adam3us: if that wasn't a birthday search I'd assume that it would be 000000 or something and not two random looking ones. :)
17:06 < adam3us> gmaxwell: (referring to post on openpgp list for others context) yeah i didnt look at it, its easy to steer RSA v2 based keyids because they are the lsb of the RSA modulus however the v3 ones are teh lsb of the fingerprint
17:08 < adam3us> gmaxwell: i presume this is a v3 fingerprint so it would represent either a preimage attack of 2^64 on an RSA key (each RSA key being moderately expensive to compute) or a birthday attack on them (using a fair bit of ram or a tmto and more compute) and probably tossing aside security to make prime reuse and generation faster
17:08 < gmaxwell> adam3us: there is metadata like a timestamp in the fingerprint
17:08 < gmaxwell> so it's not hard to grind.
17:08 < adam3us> ah thats a bit of a defect :)
17:09 < adam3us> gmaxwell: you know i noticed petertodd and warren both put just the keyid on their biz card in lieu of a proper fp
17:10 < gmaxwell> adam3us: yea, thats why my cards had the full fingerprints. esp people with short ids (32 bit) on their cards. egads.
17:10 < adam3us> gmaxwell: peter put 64-bits warren only 32-bits.. i'm not sure i can sign warren's key on that basis - its trivial to brute force that espeically if can vary meta data
17:10 < adam3us> gmaxwell: peter said  yeah but 64-bits is reflective of the practical security (intentional humor or something)
17:11 < gmaxwell> adam3us: I'm planning, when I upgrade my pgp key to ECC to grind out a silly ID .. e.g something with 64 bits of zeros.
17:12 < adam3us> gmaxwell: awesome :) vanity keyid, vanity fp etc
17:12 < BlueMatt> adam3us: pm?
17:14 < BlueMatt> gmaxwell: you should share that code :)
17:14 < BlueMatt> (for the lazy among us)
17:14 < Luke-Jr> so we all have key id 000000000 ?
17:14 < gmaxwell> BlueMatt: I have an old patched up version to timestamp grind. .. but to get a 64 bit result I'm going to need to use a fpga cluster.
17:14 < gmaxwell> its just sha1 though, so it should be pretty fast.
17:15 < BlueMatt> ahh
17:15  * BlueMatt needs to invest in a fancy hardware setup with fpgas...
17:16 < gmaxwell> well I'm hoping to buy up some ex mining farm hardware but crazy people are bidding them up
17:19 < adam3us> u know the point of the guy who made this collision is that he thought gpg might do something stupid in this case :)
17:19 < adam3us> gmaxwell: u know there is opencl code for hashcash-sha1 mining contact the guy who did the 48-bit stamp on hashcash.org
17:20 < adam3us> gmaxwell: probably no hard to modify the existing sha256 opencl code either, according to the sha1 guy his code was not super optimized
17:22 < Luke-Jr> adam3us: the SHA256d OpenCL code is pretty super-optimised..
17:33 < adam3us> Luke-Jr: yeah, apparently the sha1 opencl not so much (he didnt release it but probably would on request), its probably better starting point to modify the otpimized sha256 to sha1
17:34 < gmaxwell> adam3us: all the password cracker projects now have stupidfast ocl SHA1.
17:34 < adam3us> perfect
17:34 < adam3us> gmaxwell: so you're going to fpga it?
17:35 < gmaxwell> that was my vague plan— but I was waiting for the 400 bit DJB curve stuff to make its way into openpgp.
17:36 < sipa> I have 5 ztex FPGA's that are unused now :)
17:36 < sipa> (each did around 200 MH/s of bitcoin-double-sha256-mining)
17:37 < gmaxwell> sipa: that hits the spot!  art had said that sha1 on the lx150s was much faster than sha256.
17:38 < sipa> but doing 2^64 iterations on those is still 584 years for double-SHA256
17:43 < gmaxwell> I think sha1 being 20x faster isn't unreasonable, but 500x faster seems unlikely. So obviously I'll need to find more fpgas. :P
18:23 < lolcat9> #bitcoin-dev
18:46 < sipa> gmaxwell: in some future keysigning party: "Dang, we have a bunch of former Bitcoin miners joining... they all have the same key id :("
18:47 < Luke-Jr> former? :<
18:49 < gmaxwell> hahah
18:50 < sipa> Luke-Jr: using pre-ASIC hardware
18:50 < Luke-Jr> sipa: hopefully we all upgraded to ASICs!
18:50 < Luke-Jr> gmaxwell: you have ops in #bitcoin-dev right?
18:51 < gmaxwell> yep
18:51 < sipa> so do i
18:51 < Luke-Jr> sipa: but you weren't there :P
21:15 < Skyminerlabs> http://www.skyminerlabs.com/ we have released our V2 of our mining simulator for the PCI-E 600GH/z product check this out!
21:16 < gmaxwell> Skyminerlabs: wtf. fuck of scammer.
21:58 < Emcy> mining simulator? what even is?
22:39 < andytoshi> i'm kinda curious about that too..
22:39 < andytoshi> i guess that's a way to scam, go into the wizards channel and post a link to something that's just gotta be some sorta something..
22:48 < nOgAn0o> Bearcubbys, I am loving you tonight.
22:49  * nOgAn0o toke
22:49  * Luke-Jr wonders how he learned about -wizards :<
22:50 < BlueMatt> we need #bitcoin-wizards-nospam
22:50 < nOgAn0o> Wow, like someone was talking about anything the 9 minutes prior?
22:50 < nOgAn0o> I apologize for disturbing!
22:51 < nOgAn0o> May the Lord Jesus Christ bless you all.
22:51 < nOgAn0o> And maybe if you wouldn't spend all day coding and on IRC you wouldn't be so grumpy all the time.  Just a suggestion.
22:53 < BlueMatt> nOgAn0o: no one was talking about you (until now)
22:54 < nOgAn0o> Oh.  *blushes*
23:05 < gmaxwell> Luke-Jr: I believe there is a way to /list with a wildcard.
23:05 < nOgAn0o> ./list bitcoin got me here
23:05 < nOgAn0o> mIRC
23:06 < BlueMatt> gmaxwell: I thought you werent supposed to be able to see what chans people are in unless you're in them too :(
23:06 < nOgAn0o> I just can't believe there are not more people in here watching what you guys are up to.. on an 11 billion dollar currency.. heh?
23:07 < gmaxwell> BlueMatt: there is a channel mode that hides the channels.
23:08 < gmaxwell> nOgAn0o: this channel isn't a production channel, little we talk about here has near term relevance to bitcoin.
23:08 < BlueMatt> gmaxwell: it will become relevant when we can get someone to hire bitcoin core devs to work on bitcoin core full time...
23:10 < nOgAn0o> gmaxwell, I need a favor.. I need to find an old ASIC.. Jalapeno or something.. 2GH USB stick.. or super cheap 336 Block Erupters.. I've been wanting to mine for 3 years and never had money for hardware.. But I need a small unit and good deal.
23:10 < BlueMatt> nOgAn0o: please at least ask that on #bitcoin, but probably not in a channel...
23:11 < nOgAn0o> I am sorry for the spam but please anyone who can help message me.. I have .22 BTC and 1.0 LTC and can access more.
23:11 < nOgAn0o> Sorry BlueMatt
--- Log closed Sat Dec 14 00:00:54 2013