1 2013-05-29 00:10:25 <robbak_> Silly thing - I've fixed an issue, but I've got two commits in github - and one is just a missing space
2 2013-05-29 00:10:59 <SomeoneWeird> rebaseeeeee
3 2013-05-29 00:11:30 <robbak_> How do you squash those commits? OK, rebase. good. How do I do that again?
4 2013-05-29 00:11:46 <sipa> git fetch upstream
5 2013-05-29 00:11:46 <SomeoneWeird> goog
6 2013-05-29 00:11:48 <SomeoneWeird> :P
7 2013-05-29 00:11:51 <sipa> git rebase -i upstream/master
8 2013-05-29 00:12:15 <Arnavion> or just rebase -i HEAD~2
9 2013-05-29 00:12:50 <sipa> indeed
10 2013-05-29 00:12:52 <robbak_> Yes, I do that rebase, but the change cannot be pushed back to github. Complaints about ''non fast-forward"
11 2013-05-29 00:13:08 <sipa> use push -f
12 2013-05-29 00:13:22 <sipa> non fast-forward means you're rewriting history
13 2013-05-29 00:13:34 <sipa> which is what you want in this case
14 2013-05-29 00:13:45 <robbak_> Great. That's the clue. Thanks!
15 2013-05-29 00:14:58 <Luke-Jr> robbak_: better NOT to squash things unless they're the same thing really
16 2013-05-29 00:16:08 <robbak_> Luke-Jr: I had added a variable = 0, but had missed the space between the = and the 0.
17 2013-05-29 00:16:54 <TheLordOfTime> anyone in here familiar with vanitygen?
18 2013-05-29 00:17:17 <TheLordOfTime> and know what the probability of collision is between two systems running the same case-insensitive search/generation?
19 2013-05-29 00:18:00 <sipa> zero
20 2013-05-29 00:18:07 <sipa> for all practical purposes
21 2013-05-29 00:18:59 <Luke-Jr> bah, my kernel doesn't have oprofile support
22 2013-05-29 00:19:02 <Luke-Jr> what's 2nd best? :/
23 2013-05-29 00:19:06 <TheLordOfTime> so basically infinitesimally small
24 2013-05-29 00:19:11 <TheLordOfTime> sipa: ^
25 2013-05-29 00:19:38 <sipa> (convert all bitcoin hashing equipment into efficient address mining equipment, and you may start having a reasonable chance of getting a collision after a few thousand years)
26 2013-05-29 00:19:57 <sipa> note that collisions aren't nearly as interesting as preimages, which are way way less likely even
27 2013-05-29 00:21:07 <sipa> Luke-Jr: aren't you running an operating system where recompiling stuff with different options is trivial? :p
28 2013-05-29 00:21:19 <Luke-Jr> sipa: I'd need to reboot
29 2013-05-29 00:21:30 <Luke-Jr> which loses the bitcoind-has-broken-GBT state
30 2013-05-29 00:21:49 <sipa> ah
31 2013-05-29 00:21:53 <sipa> broken as in slow?
32 2013-05-29 00:22:18 <Luke-Jr> yes
33 2013-05-29 00:22:19 <TheLordOfTime> sipa: heh
34 2013-05-29 00:22:23 <Luke-Jr> 1m7s
35 2013-05-29 00:23:14 <sipa> :o
36 2013-05-29 00:24:35 <robbak_> Done - thanks. There it is as a pullreq - https://github.com/bitcoin/bitcoin/pull/2705
37 2013-05-29 00:25:52 <sipa> robbak_: it's very strange that it end sup being zero-sized
38 2013-05-29 00:26:08 <sipa> as it's written to a new file and then atomically moved over the old one
39 2013-05-29 00:27:09 <robbak_> sipa: I think it is when the file is in the cache,and the data is lost. It happens when the system loses power and has to fsck on restart.
40 2013-05-29 00:27:36 <sipa> still seems in violation of posix semantics
41 2013-05-29 00:28:04 <sipa> maybe we need a sync before moving; meh
42 2013-05-29 00:28:37 <robbak_> In this case it would be better if the file without data was discarded.
43 2013-05-29 00:29:40 <robbak_> But that is not always the case.
44 2013-05-29 00:30:54 <robbak_> Anyway, that much is a possible bug in fsck. But crashing on attempting to open it is ours ;D
45 2013-05-29 00:32:41 <sipa> agree
46 2013-05-29 00:34:41 <sipa> i ponder increasing the default -dbcache size
47 2013-05-29 00:35:27 <sipa> using only 25 MiB, when the whole thing easily takes 400 seems overly conservative
48 2013-05-29 00:35:31 <sipa> especially on desktop systems
49 2013-05-29 00:36:22 <robbak_> This is probably out of my league, but what are the upsides?
50 2013-05-29 00:36:45 <sipa> faster syncing
51 2013-05-29 00:37:10 <sipa> as it means less frequent writing to disk
52 2013-05-29 00:37:40 <Luke-Jr> sipa: maybe detect system free memory?
53 2013-05-29 00:38:26 <sipa> Luke-Jr: 1) how to do that in a portable way 2) a lot depends on what the system is being used for
54 2013-05-29 00:41:11 <warren> huh. addnode RPC won't let you specify a port number?
55 2013-05-29 00:41:27 <warren> oh. my mistake.
56 2013-05-29 00:51:48 <TheLordOfTime> just to recap i sent to an address just now, and it shows up on blockchain.info, but not in the destination address bitcoin-qt client. do i have to wait for the next block before bitcoin-qt will detect the receive?
57 2013-05-29 00:51:54 <TheLordOfTime> s/recap/clarify this/
58 2013-05-29 00:53:13 <sipa> "maybe"
59 2013-05-29 00:53:14 <TheLordOfTime> it had a 0.0005 tx fee, so not sure if that matters.
60 2013-05-29 00:53:25 <robbak_> blockchain.info is really annoying. They keep on having problems with sending their data out.
61 2013-05-29 00:53:45 <robbak_> Give us a transaction ID and I'll check if the world has seen it.
62 2013-05-29 00:53:48 <sipa> etotheipi_: how do you determine how much free memory there is, on OSX?
63 2013-05-29 00:53:58 <TheLordOfTime> robbak_: d519b9e0bc04397f75ac0e68168daa4c29f289acfd2624e5330e8037fb1aa9b3
64 2013-05-29 00:54:17 <TheLordOfTime> shows as "Transmitted through 8 nodes" on the system that had the wallet that sent.
65 2013-05-29 00:55:42 <sipa> my node has it
66 2013-05-29 00:56:14 <robbak_> Yup, that's right. I've seen it, so it should be in the next block.
67 2013-05-29 00:56:25 <TheLordOfTime> and when it's in the next block the other client should pick it up?
68 2013-05-29 00:56:39 <sipa> it won't necessarily be the next block
69 2013-05-29 00:56:45 <TheLordOfTime> but one of the next few?
70 2013-05-29 00:56:49 <sipa> but when it is in a block, the other node will definitely see it
71 2013-05-29 00:56:50 <TheLordOfTime> (it did have a TX fee attached)
72 2013-05-29 00:56:54 <robbak_> Yes, if it hasn't already. I've got it here. Yes, one of the next few.
73 2013-05-29 00:56:54 <sipa> maybe
74 2013-05-29 01:06:12 <TheLordOfTime> well this... is interesting..
75 2013-05-29 01:06:17 <TheLordOfTime> ACTION restarts bitcoin-qt
76 2013-05-29 01:07:16 <beethoven8201> is it possible to craft an address with a pre-defined hash160?
77 2013-05-29 01:07:44 <TheLordOfTime> robbak_: sipa: not sure if its a bug in bitcoin-qt or not, but I still haven't received the funds, and it was sent to an address i own...
78 2013-05-29 01:07:47 <TheLordOfTime> no clue what's up with that...
79 2013-05-29 01:08:29 <TheLordOfTime> should i be concerned i only see -0.0005 on the one client?
80 2013-05-29 01:08:45 <TheLordOfTime> and nothing on the other?
81 2013-05-29 01:13:51 <sipa> TheLordOfTime: are you synced?
82 2013-05-29 01:15:54 <gribble> 238442
83 2013-05-29 01:15:54 <TheLordOfTime> ;;blocks
84 2013-05-29 01:16:05 <TheLordOfTime> yep
85 2013-05-29 01:16:25 <TheLordOfTime> ... i should PROBABLY have mentioned i was sending to a wallet address that is watched by the same bitcoin-qt client
86 2013-05-29 01:16:55 <TheLordOfTime> ... which may or may not explain this line: "" : -0.24274848
87 2013-05-29 01:17:10 <TheLordOfTime> and this one: "label" : 0.24274848,
88 2013-05-29 01:17:17 <TheLordOfTime> when i do 'listaccounts' in the debug window
89 2013-05-29 01:17:31 <TheLordOfTime> because the labeled address which i sent to shows the correct amount...
90 2013-05-29 01:17:47 <TheLordOfTime> "labelfordestination" : 0.02610848, <--
91 2013-05-29 01:17:49 <TheLordOfTime> ACTION shrugs
92 2013-05-29 01:18:38 <TheLordOfTime> still... damn curious whyt it didn't show up the "Received" transaction, and only showed -0.0005 instead
93 2013-05-29 01:20:10 <robbak_> Your transaction is in a block, block 238441 One output to addrss 1DrTen?
94 2013-05-29 01:27:49 <etotheipi_> sipa: I don't
95 2013-05-29 01:27:59 <etotheipi_> sipa: (get RAM in OSX)
96 2013-05-29 01:29:46 <TheLordOfTime> robbak_: yep.
97 2013-05-29 01:30:02 <TheLordOfTime> robbak_: (sorry about the minor delay, phone rang)
98 2013-05-29 01:31:20 <robbak_> If it was a transaction from withing a wallet to an address in the same wallet, you can expect to just see the fee.
99 2013-05-29 01:31:59 <TheLordOfTime> robbak_: okay, that's 'what i was confused about because I had sent another transaction earlier from within a wallet to an address in the same wallet and it showed up as an all-sent, and then as an incoming transaction
100 2013-05-29 01:32:15 <TheLordOfTime> such that there ended up being two transactions, one for sending, one for receiving.
101 2013-05-29 01:32:17 <TheLordOfTime> *shrugs*
102 2013-05-29 01:33:35 <TheLordOfTime> robbak_: so you can see why I was understandably panicked :P
103 2013-05-29 01:42:10 <sipa> etotheipi_: hmm, i thought you did, to decide what to pass to -dbcache ?
104 2013-05-29 01:47:18 <etotheipi_> sipa: there's no bitcoind for OSX, so I never had to figure that out
105 2013-05-29 01:47:39 <etotheipi_> sipa: I have to still force OSX users (the ones that can use it) to run Bitcoin-Qt on their own
106 2013-05-29 01:48:41 <sipa> ah
107 2013-05-29 01:48:45 <sipa> right
108 2013-05-29 01:50:36 <sipa> etotheipi_: what formula do you use for other systems?
109 2013-05-29 01:51:48 <sipa> i was thinking about maybe trying to use up to 1/4 of available RAM, within some bounds, or so
110 2013-05-29 01:52:04 <sipa> for linux and windows, it seems relatively easy to determine available memory
111 2013-05-29 02:10:07 <etotheipi_> sipa: I do it in python
112 2013-05-29 02:10:12 <etotheipi_> and it was more complicated than I expected
113 2013-05-29 02:10:45 <etotheipi_> but I found some generic example code that worked great
114 2013-05-29 02:11:16 <etotheipi_> https://github.com/etotheipi/BitcoinArmory/blob/master/armoryengine.py#L761
115 2013-05-29 02:12:54 <sipa> hmm, that uses total memory, not free meory?
116 2013-05-29 02:13:04 <etotheipi_> sipa: yes
117 2013-05-29 02:15:13 <sipa> free memory seems like a better thing to judge cache sizes on
118 2013-05-29 02:16:37 <burton`> I'm trying to understand getblocktemplate. Both libblkmaker and python-blkmaker and the wiki talk about coinbasetxn, but (current git) bitcoind doesn't provide this value. This forum post says that if it's not there you have to make it yourself: https://bitcointalk.org/index.php?topic=108854.msg2046397#msg2046397. Is the wiki, and the blkmakers behind the bitcoind code base, or am I just very confused?
119 2013-05-29 02:17:23 <burton`> Neither libblkmaker and python-blkmaker examples work with the output of getblocktemplate from bitcoind...
120 2013-05-29 02:17:52 <sipa> burton`: talk to Luke-Jr
121 2013-05-29 02:19:47 <burton`> trying to msg him
122 2013-05-29 03:10:42 <midnightmagic> sipa: /window goto 37
123 2013-05-29 03:10:53 <midnightmagic> er.. sorry. :(
124 2013-05-29 03:11:06 <gonffen> YOU BEST BE
125 2013-05-29 03:11:09 <sipa> ACTION goes to window 37
126 2013-05-29 03:11:19 <gonffen> heh I hope you don't have 37 windows :(
127 2013-05-29 03:11:49 <sipa> in irc?
128 2013-05-29 03:11:59 <gonffen> ya that's too many
129 2013-05-29 03:12:16 <sipa> i have 52 now
130 2013-05-29 03:12:32 <sipa> usually i have more
131 2013-05-29 03:12:41 <gonffen> I feel for you
132 2013-05-29 03:13:07 <sipa> ok...
133 2013-05-29 03:18:42 <gonffen> win 12
134 2013-05-29 03:27:42 <Subo1978> wich IRV client do you use?
135 2013-05-29 03:27:55 <Subo1978> irc
136 2013-05-29 03:32:37 <sipa> irssi
137 2013-05-29 04:24:03 <pjorrit> that is impressive, not too easy to manage i assume or can you expand that statusbar vertically?
138 2013-05-29 04:26:09 <ne0futur> you can, ask on #irssi ;)
139 2013-05-29 04:26:18 <ne0futur> irssi ftw !
140 2013-05-29 04:50:02 <ne0futur> bitcoin-qt uses http://checkip-ams.dyndns.com/ ?
141 2013-05-29 04:50:09 <ne0futur> fyi <html><head><title>Current IP Check</title></head><body>Current IP Address: 172.25.0.91</body></html>
142 2013-05-29 04:50:19 <ne0futur> they are wrong if you are behind a proxy
143 2013-05-29 04:50:44 <ne0futur> they wont check the "forwarded for" headers
144 2013-05-29 05:54:47 <ahdinosaur> is it possible to call listtransactions with an empty 'account' argument, but a 'count' and 'from' argument, using bitcoind from cli?
145 2013-05-29 05:55:13 <sipa> yes, use '*' as account
146 2013-05-29 05:55:38 <ahdinosaur> thanks
147 2013-05-29 05:56:45 <petertodd> FWIW, first production version of replace-by-fee patch: https://github.com/petertodd/bitcoin/commit/494c86e39e00a5ab6cfccbc29c89407600454389
148 2013-05-29 05:57:31 <petertodd> punts on DoS issues by just not doing the replacement, but the advantage is it's dead simple
149 2013-05-29 05:58:24 <petertodd> replace-by-fee.bitcoin.petertodd.org is running a version (actually, the earlier one without DoS protections)
150 2013-05-29 06:00:19 <ne0futur> fyi https://twitter.com/neofutur/status/339635459300921344 wall street journal + microsoft advertising = phishing trojan against bitcoin ?
151 2013-05-29 06:02:57 <ne0futur> ( still here after more than 10 hours and they ve been warned
152 2013-05-29 06:12:41 <pjorrit> they should have processes for reporting this stuff right... 10 hours is a long time
153 2013-05-29 06:23:17 <sipa> wow, did anyone see abstruse goose today?
154 2013-05-29 06:24:16 <sipa> the alt text seems quite certain :)
155 2013-05-29 06:25:09 <ne0futur> pjorrit: yes thats why i start buzzing that
156 2013-05-29 06:25:13 <BlueMatt> sipa: yes, somehow I'm not sure that is quite realistic...
157 2013-05-29 07:57:04 <warren> The 600 seeds compiled into the 0.8 release were created from sipa's DNS seed data, like this:
158 2013-05-29 07:57:05 <warren> curl -s http://bitcoin.sipa.be/seeds.txt | head -1000 | makeseeds.py
159 2013-05-29 07:57:09 <warren> Error 404
160 2013-05-29 07:58:07 <jouke> https ?
161 2013-05-29 08:09:22 <t7> quoteth the server 404
162 2013-05-29 08:17:33 <warren> hmmm,
163 2013-05-29 08:17:34 <warren> static const CCheckpointData data = {
164 2013-05-29 08:17:44 <warren> it doesn't appear this is actually used/enforced
165 2013-05-29 08:44:37 <eps> anyone know how many MB the blockchain grows each day?
166 2013-05-29 09:07:54 <mrkent> anyone have experience with this? https://github.com/kangasbros/django-bitcoin
167 2013-05-29 09:48:23 <michagogo> Has 0.8.2 been tagged as final yet, or were there showstopper bugs?
168 2013-05-29 09:51:11 <kinlo> it's still not tagged as final
169 2013-05-29 09:51:26 <kinlo> so basicly it is still in testing phase
170 2013-05-29 09:53:51 <michagogo> kinlo: Ah, I see. I ask because about 16 hours ago, gavin said he wanted to tag for release barring any showstopper (I think that's the word he used) bugs in the next 12 hours
171 2013-05-29 09:54:09 <michagogo> And I wanted to know if I should boot into Ubuntu to build and sign
172 2013-05-29 09:54:43 <kinlo> I'm sure gavin will tell when the release is done
173 2013-05-29 09:59:52 <TheUni> sipa: for backlog: i have autotools building all including bitcoin-qt, without qmake. I'd be interested in getting your opinion before continuing, if you wouldn't mind
174 2013-05-29 10:00:43 <TheUni> there's still quite a bit of work left, but it'd be nice to get a nod before continuing down this path
175 2013-05-29 11:01:20 <jgarzik> mornin'
176 2013-05-29 11:19:45 <BlueMatt> ;;seen Goonie
177 2013-05-29 11:19:46 <gribble> Goonie was last seen in #bitcoin-dev 8 weeks, 1 day, 14 hours, 53 minutes, and 5 seconds ago: <Goonie> hopefully we will be soon paying in satoshis only. That's a nice name.
178 2013-05-29 11:19:47 <BlueMatt> ;;seen Goonie_
179 2013-05-29 11:19:47 <gribble> Goonie_ was last seen in #bitcoin-dev 1 week, 1 day, 13 hours, 39 minutes, and 9 seconds ago: <Goonie_> what's the plan for 0.8.2? will there be an additional rc2?
180 2013-05-29 11:27:10 <wallet43> ;;seen gribble
181 2013-05-29 11:27:39 <gribble> satoshinakamoto was last seen in #bitcoin-dev 11 weeks, 1 day, 11 hours, 7 minutes, and 33 seconds ago: <satoshinakamoto> I'm back to save the day
182 2013-05-29 11:27:39 <wallet43> ;;seen satoshinakamoto
183 2013-05-29 11:28:03 <gribble> I have not seen therealsatoshinakamoto.
184 2013-05-29 11:28:03 <wallet43> ;;seen therealsatoshinakamoto
185 2013-05-29 11:28:18 <BlueMatt> ;;slap wallet43
186 2013-05-29 11:28:20 <gribble> ACTION slaps wallet43 with a radioactive diadem
187 2013-05-29 11:28:39 <wallet43> autsch
188 2013-05-29 12:03:45 <jaake> hey guys I have a few questions that may sound fishy but I can assure you are not. about two years ago I locked myself out of one of my bitcoin wallets. at the time it was worth around 3500$ which was a major loss then but now obviously it seems worth my time to revisit any possible way to crack it open. Which is most likely still impossible...
189 2013-05-29 12:04:26 <BlueMatt> you mean encrypted + lost the password?
190 2013-05-29 12:04:30 <jaake> My questions are: where in the program is the encrypted key/hash
191 2013-05-29 12:04:33 <jaake> BlueMatt: yes
192 2013-05-29 12:04:34 <BlueMatt> seems we didnt have encryption then...
193 2013-05-29 12:04:46 <BlueMatt> hmm, well all you can do then is brute force
194 2013-05-29 12:04:49 <jaake> maybe 1.5 years ago? 0.3.1 i think?
195 2013-05-29 12:05:07 <BlueMatt> and given each try takes upwards of a few hundred ms, you better make that really damn targeted
196 2013-05-29 12:05:10 <jaake> BlueMatt: this is what I am prepared to do
197 2013-05-29 12:05:15 <BlueMatt> 0.4 is when encryption started
198 2013-05-29 12:05:22 <jaake> ahh 0.4.1 then
199 2013-05-29 12:05:49 <jaake> the encryption is 256 AES yea?
200 2013-05-29 12:05:55 <jaake> what is it specifically?
201 2013-05-29 12:05:59 <jaake> ecb?
202 2013-05-29 12:06:05 <Guest99340> there is a thread in the forums with some code to brute-force if you know approximately what your password was
203 2013-05-29 12:06:08 <BlueMatt> look at crypter.cpp
204 2013-05-29 12:06:12 <BlueMatt> ahh
205 2013-05-29 12:06:28 <BlueMatt> yea, you are gonna need to generate a personal word list that has what you think might have been in your password
206 2013-05-29 12:06:47 <jaake> there is no software like hashcat for 256 AES
207 2013-05-29 12:06:49 <jaake> ?
208 2013-05-29 12:06:59 <jaake> jtr?
209 2013-05-29 12:32:44 <nsh> jaake
210 2013-05-29 12:33:50 <nsh> there have been some articles recently about passport cracking techniques. in one i think a security 'professional' lost a reasonably good password to an encrypted hard disk and enlisted the aid of a cracker/researcher who helped him narrow the search space and ultimately recover it
211 2013-05-29 12:33:58 <nsh> trying to fish up the article
212 2013-05-29 12:34:54 <nsh> there's this, but it's not what i was thinking of: http://arstechnica.com/security/2013/03/how-i-became-a-password-cracker/
213 2013-05-29 12:36:40 <jaake> nsh: I think I just read that article
214 2013-05-29 12:36:58 <jaake> about a mac DMG in 256AES right?
215 2013-05-29 12:37:09 <jaake> he got some help with it
216 2013-05-29 12:38:33 <btcls> i got lost in chat
217 2013-05-29 12:38:42 <btcls> just wanted to let everyone know
218 2013-05-29 12:39:17 <jaake> nsh: the problem with mine is that it's 64^32 I can make that smaller by the things I know about the password but it was randomly generated. so it'll take years likely if it's possible at all. I need to calc the char space with the things I do know about the password to make sure it is even feasible first. I have ten lancelot mining boards that'll I'll probably retire soon and wanted to use them to try
219 2013-05-29 12:39:20 <jaake> and get this.
220 2013-05-29 12:39:26 <btcls> i am now calling "physical" money on my website "snail" money ...it is analgous to "snail mail" when it first started
221 2013-05-29 12:39:47 <btcls> fyi
222 2013-05-29 12:39:49 <btcls> poof
223 2013-05-29 12:40:04 <MC1984> wtf
224 2013-05-29 12:41:08 <nsh> jaake, tough situation :/
225 2013-05-29 12:41:12 <jaake> indeed
226 2013-05-29 12:41:54 <jaake> but I think i may be able to get at it with good software if I can trim the target down enough, at the very least I will learn a lot about encryption and information theory
227 2013-05-29 12:42:18 <jaake> and I may have to write frimware for those FPGA's too
228 2013-05-29 12:42:23 <jaake> firmware*
229 2013-05-29 12:43:37 <jaake> I was just wondering if anyone in here could tell me anything more specific about the way the client encrypts the priv keys.
230 2013-05-29 12:48:01 <BlueMatt> jaake: look at the code :p crypter.cpp iirc
231 2013-05-29 12:50:04 <jaake> will do. I'll probably end up hiring some people. let anyone with skills who may be interested know. if I have to end up writing the custom firmware for the FPGA's it'll be too much work for me on my own..
232 2013-05-29 12:52:42 <BlueMatt> how much money is in this wallet?
233 2013-05-29 12:52:47 <BlueMatt> (by today's standards)
234 2013-05-29 12:53:06 <jaake> uh 90k?
235 2013-05-29 12:53:12 <jaake> ish
236 2013-05-29 12:53:21 <BlueMatt> hmm, yea that may be worth hiring someone then...
237 2013-05-29 12:53:40 <jaake> i has wrote it off back then but now it warrants another look :)
238 2013-05-29 12:53:46 <jaake> had*
239 2013-05-29 12:54:15 <michagogo> jaake: Looking to crack a wallet?
240 2013-05-29 12:54:24 <jaake> indeed
241 2013-05-29 12:54:39 <BlueMatt> how long was the randomly generated password?
242 2013-05-29 12:55:24 <jgm> Another salutary lesson: make sure that you use weak passwords so that you can crack them when you lose them. When will people learn?
243 2013-05-29 12:55:38 <BlueMatt> heh
244 2013-05-29 12:56:02 <jaake> 32^64 or 32*[0-9][a-z][A-Z] but I do remember things about the password that will lessen it, things like there were not any four char that were the same IE 4444 or AAAA etc.
245 2013-05-29 12:56:10 <Ry4an> I just always use the same one, that way if I forget it there's only 1 to try. ;)
246 2013-05-29 12:56:22 <jaake> Ry4an: this was just a security mix up
247 2013-05-29 12:56:35 <jaake> I was running a lot of different wallets and I backed up the wrong one
248 2013-05-29 12:56:37 <iwilcox> jaake: So you didn't forget this password, because there's no damn way you remembered that much entropy.
249 2013-05-29 12:56:44 <jaake> indeed
250 2013-05-29 12:56:46 <Ry4an> jaake: I'm just riffing on jgm's comment, not making fun of your unfortunate situation
251 2013-05-29 12:57:01 <iwilcox> jaake: So where was it stored? Feasible to go after that instead?
252 2013-05-29 12:57:09 <jaake> Ry4an: oh don't worry, I have long ago finished shedding tears over this one
253 2013-05-29 12:57:10 <Ry4an> I did the same w/ a harddrive as a youngin' and there was much wailing and gnashing of teeth.
254 2013-05-29 12:57:28 <jaake> iwilcox: negative
255 2013-05-29 12:58:24 <jaake> this was a while ago and it was't worth (at the time) doing advanced hardware forensics to get the other wallet especially since I had been using the computer for 1+ month before I realized
256 2013-05-29 12:58:35 <Ry4an> jaake: if there's a header in encrypted wallets in addition to the private keys you could probably publish just enough of the encrypted file to know someone's got the right password w/o them getting the private key
257 2013-05-29 12:58:51 <Ry4an> then you could "crowd source" the bruteforcing and offer a bounty.
258 2013-05-29 12:58:59 <BlueMatt> jaake: you want to brute force a
259 2013-05-29 12:59:00 <jaake> Ry4an: that's why I am in here, to explore such options
260 2013-05-29 12:59:07 <jgm> jaake: you really need to cut down that search space. Were there any rules around the password such as total number of letters/numbers, consecutive letters/numbers, avoiding ambiguous characters? Anything like that would help
261 2013-05-29 12:59:12 <BlueMatt> n alphanum 32-char password???? hahahahahahahahahaha
262 2013-05-29 12:59:16 <BlueMatt> I dont care what hardware you have
263 2013-05-29 12:59:28 <BlueMatt> or that there are no quintuplets
264 2013-05-29 12:59:39 <iwilcox> ;;calc 32 ^ 64
265 2013-05-29 12:59:40 <gribble> Error: Something in there wasn't a valid number.
266 2013-05-29 12:59:43 <iwilcox> ;;calc 32 ** 64
267 2013-05-29 12:59:44 <gribble> 2135987035920910082395021706169552114602704522356652769947041607822219725780640550022962086936576
268 2013-05-29 12:59:49 <jaake> BlueMatt: I admitted when I first entered that this whole business was unlikely
269 2013-05-29 13:00:19 <jaake> however I can remember other things about the password that can further reduce the search space
270 2013-05-29 13:00:25 <iwilcox> Hardly.
271 2013-05-29 13:00:29 <kinlo> iwilcox: 64 ** 32 seems more correct if you want to calculate the number of iterations required for 32 letters of 64 possibilities
272 2013-05-29 13:00:50 <iwilcox> So it does.
273 2013-05-29 13:00:53 <jgm> Much better off just generating random keys and hoping to get lucky hitting someone else's wallet for the coin (not that I am advocating nor recommending such a course of action)
274 2013-05-29 13:01:24 <gribble> 6277101735386680763835789423207666416102355444464034512896
275 2013-05-29 13:01:24 <kinlo> ;;calc 64 **32
276 2013-05-29 13:01:25 <iwilcox> ;;calc (26 + 26 + 10) ** 32
277 2013-05-29 13:01:26 <gribble> 2272657884496751488845238209201680422446063209228378570752
278 2013-05-29 13:01:42 <kinlo> much smaller number :)
279 2013-05-29 13:01:58 <iwilcox> Yeah, jaake should be finished by lunchtime :)
280 2013-05-29 13:02:00 <BlueMatt> jaake: "unlikey" hahahhaa read http://www.schneier.com/blog/archives/2009/09/the_doghouse_cr.html or atleast the section that talks about thermodynamics
281 2013-05-29 13:02:00 <jgm> Relatively smaller number, anyway
282 2013-05-29 13:02:19 <jaake> what I really need to do is figure out how much I can limit the search space. and calculate the feasibility
283 2013-05-29 13:02:35 <jaake> BlueMatt: I have read that thank you
284 2013-05-29 13:03:04 <iwilcox> I'd say what you really need to do is either find a way to forensically analyse wherever you stored the password (?) or let it go.
285 2013-05-29 13:03:41 <jaake> iwilcox: my plan is to wait until quantum computing is fully realized :)
286 2013-05-29 13:03:57 <BlueMatt> that wont even help, sorry
287 2013-05-29 13:04:18 <BlueMatt> at least getting the password, it will help to get the privkeys, but...
288 2013-05-29 13:04:36 <iwilcox> I'm still fuzzy on how wallet backups had anything to do with the loss. If you have the encrypted wallet still, what you need is your password manager's storage. You haven't said what happened to that.
289 2013-05-29 13:04:36 <jgm> jaake: I'd put the wallet up for sale on Ebay. Let someone who can't do the math buy it from you for a decent amount of money
290 2013-05-29 13:04:57 <jaake> iwilcox: the password was changed
291 2013-05-29 13:05:16 <jaake> the password manager had the new password. the old wallet was backed up
292 2013-05-29 13:05:21 <BlueMatt> jaake: with 10x hardware that runs 2 orders of magnitude (!) faster than a cpu, you may be able to get 864000000 tries per DAY
293 2013-05-29 13:05:23 <BlueMatt> so...have fun
294 2013-05-29 13:05:25 <jaake> the new wallet was lost
295 2013-05-29 13:05:45 <iwilcox> Some password managers automatically save modified entries.
296 2013-05-29 13:06:02 <jgm> jaake: have you checked to see if the password manager keeps a history? Or if you used a provider which keeps backups?
297 2013-05-29 13:06:07 <jaake> iwilcox: no dice (lastpass)
298 2013-05-29 13:06:08 <iwilcox> As in, save the old when you set a new one.
299 2013-05-29 13:06:16 <jgm> jaake: lastpass keeps a full history
300 2013-05-29 13:06:24 <jaake> jgm: not in a secure note
301 2013-05-29 13:06:41 <jgm> You aren't helping yourself, you know :)
302 2013-05-29 13:06:44 <jaake> I know
303 2013-05-29 13:07:08 <jaake> as I have said I was jsut taking another look :) I will calc how low I can get the search space
304 2013-05-29 13:07:17 <jaake> and get back to you
305 2013-05-29 13:07:39 <jgm> Worth contacting lastpass and seeing if they have a backup they can restore for you? I'd be worried if they couldn't (if they would is another matter, but...)
306 2013-05-29 13:07:58 <jaake> I have already decided this is now just a challenge for fun. and to learn about encryption and information theory
307 2013-05-29 13:08:08 <jgm> Promise to give them some glowing quotes about how it saved you real money, they might do it for the publicity
308 2013-05-29 13:08:41 <jaake> jgm: lol, I doubt they keep backups of encrypted secure notes for over a year
309 2013-05-29 13:08:49 <jaake> but I guess it's worth a look
310 2013-05-29 13:09:02 <iwilcox> For $90000 they might find a dusty backup
311 2013-05-29 13:09:28 <jgm> jaake: I'd be surprised if they didn't. Definitely worth mailing them either way
312 2013-05-29 13:09:41 <jaake> the problem is that I don't think the old password ever got saved in there
313 2013-05-29 13:10:02 <iwilcox> Did you never actually use it to open the wallet? You'd have had to, to change the password, shirley?
314 2013-05-29 13:10:32 <jaake> since that was the switch to 32 * [0-9][A-Z][a-z][special]
315 2013-05-29 13:11:54 <jaake> i was new and foolish. and at the time it wasn't nearly worth that much :) you can all thank me for the increase in BTC worth though I guess!
316 2013-05-29 13:12:16 <Musk> lol
317 2013-05-29 13:14:05 <iwilcox> My opinion: "a challenge for fun. and to learn" definitely doesn't involve hiring people. Anyone who takes your hiring-money is either not really qualified to know they can't help, or is swindling you.
318 2013-05-29 13:18:35 <jaake> iwilcox: the hiring will only commence once I calculate that the search space is feasible. which it probably is not. but if it is not at least I get good at calculating search space and reducing it. and understanding the difference, and maybe designing an algorythm the probabilistically searches based on a model that i could build. like I said at this point i do not ever hope to reclaim them
319 2013-05-29 13:19:31 <jaake> iwilcox: and I would be hiring people to comsult me on an hourly basis not there cracking GPU clusters or anything
320 2013-05-29 13:19:38 <jaake> more like tutoring :)
321 2013-05-29 13:20:50 <jaake> their*
322 2013-05-29 13:24:50 <nsh> jaake, maybe you should just publicise an open competition to crack the wallet, promising a certain percentage bounty
323 2013-05-29 13:25:24 <nsh> though that would require some honour system i guess
324 2013-05-29 13:27:10 <jaake> not if I can get a hash or w/e
325 2013-05-29 13:27:39 <jaake> that'd be kind of cool though I imagine that nobody would even try until computer get much much faster
326 2013-05-29 13:28:11 <jaake> %s/hash/header/
327 2013-05-29 13:32:20 <iwilcox> Are the coins divided conveniently among the addresses in that wallet? You should still be able to tell if encryption then worked like encryption now, i.e. only the private keys are encrypted.
328 2013-05-29 13:33:33 <iwilcox> If there's an address with a UTXO with a suitable bounty, and you can devise an honour system, then letting the market decide is probably quite a neat way to do it.
329 2013-05-29 13:33:55 <iwilcox> (Since they'll quickly decide "no", which will give you all the info you need!)
330 2013-05-29 13:34:28 <jaake> iwilcox: lol yeah I think it's in 100 or 200 coins groups
331 2013-05-29 13:35:09 <jaake> i think it's something like 600 or 700 coins?
332 2013-05-29 13:37:06 <nsh> or you could announce that you have deflated the bitcoin supply by X% and make a compelling argument that you should become a permanent ward of the economy and have your lodging and board paid in perpetuity
333 2013-05-29 13:37:08 <jaake> iwilcox: I will see, it may be a fun way to meet some interesting people
334 2013-05-29 13:37:25 <jaake> nsh: ++
335 2013-05-29 13:37:33 <jaake> I should get tx priority without any fees
336 2013-05-29 13:37:36 <jaake> :P
337 2013-05-29 13:37:40 <nsh> :)
338 2013-05-29 13:39:12 <jaake> funny thing is that if I had not locked it up, i'd have spent that money long ago when it was worth 5 or 6 bucks
339 2013-05-29 13:40:01 <jaake> it's only horrific now becaue of the increase in value which is only applicable because I was forced into saving them in the first place
340 2013-05-29 13:41:01 <jaake> I'll do some more research and maybe I'll put up a site for orphaned wallets, that might be cool...
341 2013-05-29 13:41:10 <jaake> not really orphaned i guess
342 2013-05-29 13:41:13 <jaake> but w/e
343 2013-05-29 13:48:35 <sipa> warren: i no longer have tgat list public
344 2013-05-29 14:20:54 <kaniini> hi, was 32256 is the first block in the chain with a difficulty change?
345 2013-05-29 14:25:10 <iwilcox> Blocks have reward changes, not difficulty changes, AIUI.
346 2013-05-29 14:28:58 <wallet43> soon there will be more alternate cryptocurrencies than bitcoin blocks
347 2013-05-29 14:29:53 <sipa> iwilcox: uh yes they do, every 2016 blocks the difficulty is adjusted
348 2013-05-29 14:30:05 <sipa> well, difficulty is a derived unit; the target changes
349 2013-05-29 14:30:25 <Mad7Scientist> bitcoin-qt is still locked up
350 2013-05-29 14:30:33 <kaniini> indeed, 32256 mod 2016 is 0
351 2013-05-29 14:30:36 <Mad7Scientist> 1114MB resident memory used
352 2013-05-29 14:30:54 <Mad7Scientist> 2194MB virt
353 2013-05-29 14:31:03 <sipa> Mad7Scientist: define locked up?
354 2013-05-29 14:31:13 <kaniini> but, calculating difficulty for each block, from 0 to 32216
355 2013-05-29 14:31:13 <Mad7Scientist> 1 thread uses 100% CPU for a minute
356 2013-05-29 14:31:19 <Mad7Scientist> and 5 other threads spawn
357 2013-05-29 14:31:21 <kaniini> well, 32255 rather
358 2013-05-29 14:31:24 <Mad7Scientist> then they close and it frees up
359 2013-05-29 14:31:26 <Mad7Scientist> for a few seconds
360 2013-05-29 14:31:27 <kaniini> yields difficulty=1.0
361 2013-05-29 14:31:28 <Mad7Scientist> then again
362 2013-05-29 14:31:42 <sipa> Mad7Scientist: 0.8.2?
363 2013-05-29 14:31:46 <Mad7Scientist> the 100% cpu threads spawns
364 2013-05-29 14:31:47 <kaniini> then it goes to 1.18
365 2013-05-29 14:31:47 <Mad7Scientist> 0.8.1
366 2013-05-29 14:31:48 <kaniini> \\
367 2013-05-29 14:31:52 <kaniini> oops, lag
368 2013-05-29 14:32:04 <Mad7Scientist> I guess I have to upgrade
369 2013-05-29 14:32:18 <sipa> Mad7Scientist: try 0.8.2 please, it has significant memory usage improvements and also cpu usage improvements for GBT
370 2013-05-29 14:32:33 <kaniini> 2016 = 1.0, 4032 = 1.0, so on
371 2013-05-29 14:33:00 <sipa> kaniini: bitcoin.sipa.be :)
372 2013-05-29 14:33:13 <Mad7Scientist> there must be some DoS or some issue with the block chain
373 2013-05-29 14:33:20 <Mad7Scientist> because it has been working fine for a long time
374 2013-05-29 14:33:51 <kaniini> sipa: doesn't graph difficulty=
375 2013-05-29 14:33:52 <sipa> we haven't found the root cause of the suddenly increased GBT cpu usage
376 2013-05-29 14:33:58 <sipa> kaniini: it does
377 2013-05-29 14:33:58 <wallet43> sipa: is there csv for the data?
378 2013-05-29 14:34:14 <sipa> wallet43: eh, don't think so
379 2013-05-29 14:34:28 <kaniini> i only see compute throughput, and only from january 2012
380 2013-05-29 14:34:33 <wallet43> how do you draw the charts?
381 2013-05-29 14:34:46 <sipa> wallet43: gnuplot
382 2013-05-29 14:34:54 <kaniini> oh, i see.
383 2013-05-29 14:35:26 <Mad7Scientist> where is 0.8.2?
384 2013-05-29 14:35:30 <Mad7Scientist> I just see 0.8.1
385 2013-05-29 14:35:34 <sipa> kaniini: http://bitcoin.sipa.be/speed-ever-large.png red line
386 2013-05-29 14:35:44 <sipa> Mad7Scientist: not released yet, there is a rc3
387 2013-05-29 14:35:48 <kaniini> sipa: yep, i see now.
388 2013-05-29 14:35:51 <Mad7Scientist> sourceforge?
389 2013-05-29 14:35:56 <sipa> yes
390 2013-05-29 14:36:11 <sipa> it's announced on the forums and the mailing list i think
391 2013-05-29 14:36:19 <kaniini> sipa: that is basically what i was trying to compute, so, you have saved me some work ;)
392 2013-05-29 14:36:29 <sipa> oh
393 2013-05-29 14:37:12 <sipa> http://bitcoin.sipa.be/blocks.txt
394 2013-05-29 14:37:29 <sipa> that's the extracted input data from which the graphs are computed
395 2013-05-29 14:37:39 <wallet43> thx :)
396 2013-05-29 14:37:40 <sipa> it has block heights and difficulty
397 2013-05-29 14:38:15 <wallet43> whats the last
398 2013-05-29 14:38:19 <wallet43> numtx?
399 2013-05-29 14:38:47 <sipa> yes
400 2013-05-29 15:05:59 <Subo1978> sipa: when will the new bitcoind version released
401 2013-05-29 15:06:08 <sipa> when it is ready
402 2013-05-29 15:07:36 <Subo1978> sipa: this is ?
403 2013-05-29 15:08:10 <jgarzik> Subo1978, a spoon
404 2013-05-29 15:08:12 <sipa> i can't say when; it is likely very soon, but it depends on how many bugreports we see
405 2013-05-29 15:08:17 <jgarzik> no, no, a shoe.
406 2013-05-29 15:19:43 <gavinandresen> sipa jgarzik: I think "now" is a good time for 0.8.2, there weren't any showstopper bugs since yesterday, were there?
407 2013-05-29 15:20:35 <sipa> gavinandresen: i'm mildly concerned about the mutex errors at shutdown that keep popping up
408 2013-05-29 15:20:52 <gavinandresen> sipa: not show-stopper-serious, in my opinion
409 2013-05-29 15:20:57 <sipa> agree
410 2013-05-29 15:21:03 <jgarzik> gavinandresen, ack
411 2013-05-29 15:21:40 <gavinandresen> ok, I'm going to tag git HEAD which is one teeny-tiny little #include <stdarg.h> change from 0.8.2rc3
412 2013-05-29 15:21:57 <MC1984> anyone find out about my thing?
413 2013-05-29 15:22:00 <MC1984> GBT crash
414 2013-05-29 15:22:40 <gavinandresen> MC1984: what issue# ?"
415 2013-05-29 15:22:58 <sipa> #2705 seems harmless
416 2013-05-29 15:23:07 <MC1984> in rc3, issuing a GBT in the debug console crashes bitcoin hard
417 2013-05-29 15:23:16 <MC1984> in the QT gui
418 2013-05-29 15:23:42 <sipa> hmmz
419 2013-05-29 15:23:57 <MC1984> the thing i described a few days ago
420 2013-05-29 15:23:59 <gavinandresen> MC1984: file an issue, please. Doesn't sound like a show-stopper, though (why would you getblocktemplate in the console?)
421 2013-05-29 15:24:35 <MC1984> i dont, usually, but i read someone fixed the latency bug and i wanted to see
422 2013-05-29 15:24:48 <BlueMatt> gavinandresen: if its reproducible, any crash that we dont at least know the source of should be show-stopper
423 2013-05-29 15:25:00 <MC1984> i thought the crash might be related to the fix, so i thought someone should know
424 2013-05-29 15:25:19 <MC1984> i can reproduce it but someone else here couldnt
425 2013-05-29 15:25:23 <michagogo> MC1984: Is the command just `getblocktemplate`?
426 2013-05-29 15:25:29 <MC1984> yes
427 2013-05-29 15:25:31 <michagogo> I'll try it, just a sec
428 2013-05-29 15:25:43 <michagogo> (looks like I need to boot my node)
429 2013-05-29 15:25:50 <sipa> let me try to reproduce
430 2013-05-29 15:25:58 <MC1984> my system is winxp32
431 2013-05-29 15:26:02 <gavinandresen> getblocktemplate in the console works for me
432 2013-05-29 15:26:04 <michagogo> gavinandresen: Ping me when you tag it final, I'll reboot into Ubuntu
433 2013-05-29 15:26:04 <sipa> ah, no qt build env here
434 2013-05-29 15:26:20 <sipa> MC1984: how reproducible is it?
435 2013-05-29 15:26:32 <MC1984> i did it like 5 times in a row
436 2013-05-29 15:26:39 <sipa> MC1984: i vaguely remember asking you (or someone) to test something with an empty wallet
437 2013-05-29 15:26:40 <michagogo> MC1984: On freshly-booted nodes?
438 2013-05-29 15:26:44 <sipa> was that for this issue?
439 2013-05-29 15:26:58 <MC1984> yes you told me to try an empty wallet with it few days ago
440 2013-05-29 15:27:03 <MC1984> same result
441 2013-05-29 15:27:15 <MC1984> lemme try again
442 2013-05-29 15:27:34 <MC1984> actually ill reboot and try again
443 2013-05-29 15:28:40 <psychophoniac> hello everyone, can someone give me a link to something about the cryptographic background of bitcoin?
444 2013-05-29 15:28:48 <psychophoniac> i already read the paper by satoshi
445 2013-05-29 15:29:09 <BlueMatt> en.bitcoin.it/wiki/OP_CHECKSIG
446 2013-05-29 15:29:22 <sipa> http://en.wikipedia.org/wiki/Elliptic_Curve_DSA
447 2013-05-29 15:29:40 <jgarzik> psychophoniac, it's pretty much off-the-shelf crypto technologies
448 2013-05-29 15:29:50 <sipa> http://www.secg.org/download/aid-780/sec1-v2.pdf
449 2013-05-29 15:30:00 <sipa> except we're pretty much the only ones who use secp256k1
450 2013-05-29 15:30:26 <michagogo> Question: Do you guys use checkip.dyndns.org as a way for the client to find its own address?
451 2013-05-29 15:30:39 <kaniini> sipa: actually, i developed a SASL mechanism which uses secp256k1.
452 2013-05-29 15:30:48 <kaniini> sipa: http://github.com/atheme/ecdsatool
453 2013-05-29 15:31:08 <sipa> ha!
454 2013-05-29 15:31:41 <michagogo> I ask because of http://i.imgur.com/2hn3EVx.png
455 2013-05-29 15:32:16 <psychophoniac> nice, thank you guys. i have a lecture about cryptography at uni and today introduced my (retired) prof who loves that stuff to bitcoin.
456 2013-05-29 15:32:43 <gavinandresen> michagogo: grep checkip *.cpp <--- gets addrConnect = CService("91.198.22.70", 80); // checkip.dyndns.org
457 2013-05-29 15:32:48 <jgarzik> psychophoniac, ECDSA, SHA256 are the main ones
458 2013-05-29 15:32:59 <jgarzik> psychophoniac, the innovation (proof of work) came from hashcash
459 2013-05-29 15:33:02 <psychophoniac> ...can you choose the algo?
460 2013-05-29 15:33:06 <jgarzik> psychophoniac, no
461 2013-05-29 15:33:07 <sipa> no
462 2013-05-29 15:33:21 <sipa> there's also RIPEMD160 used for address hashes
463 2013-05-29 15:33:44 <MC1984> !blocks
464 2013-05-29 15:33:45 <gribble> 238555
465 2013-05-29 15:33:53 <MC1984> shi
466 2013-05-29 15:33:53 <psychophoniac> ah. learned something today.
467 2013-05-29 15:33:55 <MC1984> t
468 2013-05-29 15:34:20 <michagogo> Ah, virustotal comes up clean, but: BitDefender domain information
469 2013-05-29 15:34:20 <michagogo> The URL domain/host was seen to host badware at some point in time
470 2013-05-29 15:34:23 <psychophoniac> now let us read into that... thanks again :)
471 2013-05-29 15:35:03 <sipa> getblocktemplate crashing bitcoin-qt is reproducible for me
472 2013-05-29 15:35:31 <MC1984> oh its not just me
473 2013-05-29 15:35:57 <michagogo> I typed getblocktemplate into the console
474 2013-05-29 15:36:13 <michagogo> And it crashed. (rc3, win7x64)
475 2013-05-29 15:36:21 <sipa> gavinandresen: looks related to your reservekey fix
476 2013-05-29 15:36:35 <MC1984> babbys first bug report ^^
477 2013-05-29 15:36:45 <sipa> MC1984: next time, file an issue
478 2013-05-29 15:37:28 <MC1984> i didnt want to do that and waste someones time if it was just me, which is why i asked about it in here a few days ago
479 2013-05-29 15:39:14 <gavinandresen> sipa: still can't reproduce on my Mac, can you debug?
480 2013-05-29 15:40:17 <MC1984> in future though i will just file an issue if im fairly sure
481 2013-05-29 15:40:59 <michagogo> BTW, debug.log doesn't have anything in it that seems related
482 2013-05-29 15:41:02 <gavinandresen> oh??? I see it...
483 2013-05-29 15:41:08 <michagogo> 2013-05-29 17:34:05 CTxMemPool::accept() : accepted d78356857f7ec2cd33bc877d041f747aa0499a8627caa8e950bc52b8fafdd47f (poolsz 182)
484 2013-05-29 15:41:08 <michagogo> 2013-05-29 17:34:06 Flushed 14729 addresses to peers.dat 49ms
485 2013-05-29 15:41:13 <michagogo> And that's the end
486 2013-05-29 15:41:21 <gavinandresen> I can't reproduce because I'm running bitcoin-qt with -server=1
487 2013-05-29 15:41:36 <gavinandresen> ??? so the RPC threads are started, so the mining key is created....
488 2013-05-29 15:41:54 <Krellan> Curious, is IPv6 supported in official build? I have never seen it make an IPv6 connection, either inbound or outbound.
489 2013-05-29 15:42:03 <sipa> gavinandresen: yup, that's it
490 2013-05-29 15:42:10 <sipa> kaniini: it should be, yes
491 2013-05-29 15:46:37 <michagogo> Is this GBT fix going to mean an rc4?
492 2013-05-29 15:46:43 <michagogo> Or is it small enough for a final?
493 2013-05-29 15:46:57 <kaniini> sipa: unfortunately, key enrollment still needs to be tidied up, and then freenode needs to be sold on turning it on.
494 2013-05-29 15:47:30 <gavinandresen> michagogo: might be small enough to be release notes "KNOWN BUGS"
495 2013-05-29 15:47:32 <sipa> kaniini: ??
496 2013-05-29 15:47:41 <sipa> kaniini: oh, SASL
497 2013-05-29 15:47:51 <michagogo> Ah
498 2013-05-29 15:49:00 <gavinandresen> Bah, I hate deciding whether to live with a bug or add a last-minute "easy" fix???.
499 2013-05-29 15:49:36 <michagogo> gavinandresen: Personally, I'd just leave it if it's that minor
500 2013-05-29 15:49:53 <michagogo> Because you never know what may end up breaking
501 2013-05-29 15:50:14 <sipa> i don't see how it can be triggered except by the literal combination {getwork,getblocktemplate} + Bitcoin-Qt + server=0
502 2013-05-29 15:50:33 <gavinandresen> well, the easy fix is two lines of code in getwork / getblocktemplate: if (pMiningKey == NULL) pMiningKey = new CReserveKey(pWalletMain);
503 2013-05-29 15:50:35 <michagogo> BTW, I may have asked this before and forgotten, but when do you add new checkpoints?
504 2013-05-29 15:51:00 <gavinandresen> michagogo: new checkpoints approximately every-other-release
505 2013-05-29 15:51:20 <sipa> ;;blocks
506 2013-05-29 15:51:21 <gribble> 238555
507 2013-05-29 15:51:32 <sipa> hmm, it's been 13k blocks since the last checkpoint
508 2013-05-29 15:51:55 <jgarzik> we were talking about a post-fork checkpoint
509 2013-05-29 15:52:06 <MC1984> no fork yet
510 2013-05-29 15:52:08 <jgarzik> are we still not hard forked?
511 2013-05-29 15:52:10 <jgarzik> ok
512 2013-05-29 15:52:20 <nsh> wait, sorry, what's key enrolment and why does it require assent from freenode?
513 2013-05-29 15:52:21 <MC1984> luke is trying, i believe
514 2013-05-29 15:53:07 <sipa> jgarzik: indeed
515 2013-05-29 15:53:42 <sipa> 13k blocks is 1.5 month; seems not long ago enough
516 2013-05-29 15:53:51 <sipa> wait
517 2013-05-29 15:53:53 <sipa> 3 months?
518 2013-05-29 15:53:54 <michagogo> sipa: Not long enough?
519 2013-05-29 15:53:59 <sipa> for a new checkpoint
520 2013-05-29 15:54:05 <michagogo> ;;calc 24*60
521 2013-05-29 15:54:06 <gribble> 1440
522 2013-05-29 15:54:14 <michagogo> ;;calc 13000/1440
523 2013-05-29 15:54:15 <gribble> 9.02777777778
524 2013-05-29 15:54:28 <michagogo> That doesn't look right
525 2013-05-29 15:54:41 <gribble> 90.2777777778
526 2013-05-29 15:54:41 <sipa> ;;calc 13000*600/86400
527 2013-05-29 15:54:45 <sipa> 90 days
528 2013-05-29 15:55:09 <gavinandresen> MC1984: https://github.com/bitcoin/bitcoin/issues/2706
529 2013-05-29 15:55:09 <kaniini> sipa: if only there were a SASL mechanism that involved authenticating a user by paying me with bitcoins
530 2013-05-29 15:55:12 <kaniini> ;)
531 2013-05-29 15:55:19 <michagogo> Remind me where the checkpoints are coded?
532 2013-05-29 15:55:39 <nsh> 2013 so far is about 8.9 minutes per block on average i believe
533 2013-05-29 15:55:49 <sipa> michagogo: checkpoints.cpp :)
534 2013-05-29 15:56:25 <michagogo> sipa: Thanks
535 2013-05-29 15:56:48 <michagogo> ;;calc 225430-216116
536 2013-05-29 15:56:49 <gribble> 9314
537 2013-05-29 15:56:49 <MC1984> gavinandresen cool
538 2013-05-29 15:58:31 <michagogo> So last checkpoint was 9k interval, previous ones were 6k, 7k, 25k, 33k, 29k, 31k, 40k, and 22k
539 2013-05-29 15:58:39 <michagogo> (in reverse chronological order)
540 2013-05-29 15:59:05 <jgarzik> we occasionally reomve intermediate, more recent checkpoints
541 2013-05-29 15:59:09 <jgarzik> *remove
542 2013-05-29 15:59:12 <michagogo> Hmm?
543 2013-05-29 15:59:39 <michagogo> jgarzik: Why remove them?
544 2013-05-29 15:59:54 <MC1984> theres no real pattern to checkpoints besides "when it feels right" afaik
545 2013-05-29 16:00:08 <jgarzik> michagogo, kinda pointless as the middle hashes are guaranteed by later ones
546 2013-05-29 16:00:10 <MC1984> theres one that ends in 11 because its someones favourite number :>
547 2013-05-29 16:00:16 <michagogo> jgarzik: Though, why do you need anything more than the most recent?
548 2013-05-29 16:00:17 <jgarzik> michagogo, there is minor value
549 2013-05-29 16:00:17 <michagogo> Yeah
550 2013-05-29 16:00:39 <sipa> jgarzik: more frequent checkpoints gives better protection against DoS-attacking a node with orphan blocks during IBD
551 2013-05-29 16:00:42 <jgarzik> michagogo, the code does check height==hash at each checkpoint, so it helps to notice earlier a bad download
552 2013-05-29 16:00:58 <jgarzik> sipa, ^ indeed :)
553 2013-05-29 16:01:11 <sipa> (not because of the reason you gave)
554 2013-05-29 16:01:39 <michagogo> jgarzik: Ah, I see
555 2013-05-29 16:02:13 <michagogo> Personally, I think a checkpoint is worth adding
556 2013-05-29 16:02:17 <michagogo> But maybe that's just me
557 2013-05-29 16:02:43 <UukGoblin> fork
558 2013-05-29 16:02:50 <jgarzik> My personal preference is for a checkpoint to be no -younger- than 13k blocks
559 2013-05-29 16:02:57 <jgarzik> But other devs are more aggressive
560 2013-05-29 16:03:09 <michagogo> jgarzik: What do you mean?
561 2013-05-29 16:03:18 <nsh> kaniini, what is 'key enrollment' and how does it require freenode to turn it on?
562 2013-05-29 16:03:26 <michagogo> Ah, as in at least 13k blocks back?
563 2013-05-29 16:03:33 <jgarzik> michagogo, correct
564 2013-05-29 16:03:40 <jgarzik> 3 months
565 2013-05-29 16:03:49 <jgarzik> (144 * 90)
566 2013-05-29 16:03:58 <michagogo> How long ago was 225430 checkpointed?
567 2013-05-29 16:04:07 <michagogo> Oh, there's a history button
568 2013-05-29 16:04:46 <michagogo> Looks like that was added 2 months ago
569 2013-05-29 16:05:04 <gavinandresen> Pushed * [new tag] v0.8.2 -> v0.8.2
570 2013-05-29 16:05:12 <michagogo> OTOH, I guess you can say that was extenuating circumstances
571 2013-05-29 16:05:32 <michagogo> Since that was right after the chain fork and it was important to cement that in
572 2013-05-29 16:05:37 <gavinandresen> I'll document the debug-console-getblocktemplate bug in the release notes, we should implement a clean fix for 0.9
573 2013-05-29 16:06:38 <BlueMatt> aaaaannndd...merge window open :)
574 2013-05-29 16:06:40 <michagogo> gavinandresen: Okay, lemme get my Ubuntu drive
575 2013-05-29 16:07:03 <kaniini> nsh: i implemented an ECDSA authentication mechanism for services
576 2013-05-29 16:07:18 <kaniini> nsh: so, freenode in order to allow it, has to turn the module on etc :P
577 2013-05-29 16:07:39 <jgarzik> BlueMatt: :)
578 2013-05-29 16:09:21 <MC1984> what does the -server operator do again?
579 2013-05-29 16:09:27 <nsh> oh right. i would be hesitant to mix ircd services codebase with anything pertaining to actual real important money things, on account of irc code being pretty much the absolute favouite thing for hackers to attack, backdoor, DoS, etc.
580 2013-05-29 16:09:29 <sipa> it starts the RPC server
581 2013-05-29 16:09:30 <MC1984> allows you to issue RPC calls to QT right
582 2013-05-29 16:09:33 <MC1984> ok
583 2013-05-29 16:09:40 <nsh> but i don't know atheme's recent track record or anything, so maybe i'm just being paranoid
584 2013-05-29 16:10:42 <BlueMatt> jgarzik: I expect you to merge at least 5 pulls in the next 10 minutes
585 2013-05-29 16:10:52 <warren> sigh boost fail...
586 2013-05-29 16:10:58 <jgarzik> not until gitian is done
587 2013-05-29 16:11:05 <jgarzik> sigs match == merge window open :)
588 2013-05-29 16:11:07 <warren> need kill -9, but it will corrupt the wallet.dat
589 2013-05-29 16:11:15 <gavinandresen> Somebody please bump the version number to 0.8.2.99 before merge-fest??? (and set the "not a release" flag)
590 2013-05-29 16:11:17 <BlueMatt> awwww
591 2013-05-29 16:11:41 <gavinandresen> I'm gitian building, and working on the OSX builds.
592 2013-05-29 16:11:56 <BlueMatt> also, can we ensure we dont release with 2 sigs this time?
593 2013-05-29 16:12:15 <BlueMatt> (ie get the gitian-mandated 3 devs, or change our gitian-mandated threshold)
594 2013-05-29 16:12:47 <sipa> we may want to wait a *bit*, as often minor bugs show up very shortly after full release...
595 2013-05-29 16:13:02 <sipa> though that can be solved with a simply backfork fix of course
596 2013-05-29 16:13:04 <gavinandresen> BlueMatt: sure, I'm all for being more strict for final releases
597 2013-05-29 16:13:29 <gavinandresen> sipa still can't gitian-sign, though (right?)
598 2013-05-29 16:13:38 <BlueMatt> ACTION can, but not for a few hours
599 2013-05-29 16:13:52 <sipa> gavinandresen: indeed, not until saturday
600 2013-05-29 16:14:18 <gavinandresen> me, BlueMatt, Luke-Jr would be three
601 2013-05-29 16:14:46 <jgarzik> ditto here. not today, but RSN hopefully.
602 2013-05-29 16:15:01 <jgarzik> ACTION expected tagging to happen Thu/Fri honestly
603 2013-05-29 16:15:14 <gavinandresen> I'll be unavailable this weekend (funeral, my father-in-law died yesterday)
604 2013-05-29 16:15:47 <jgarzik> sorry to hear :(
605 2013-05-29 16:15:55 <denisx> ;(
606 2013-05-29 16:16:13 <petertodd> gavinandresen: sorry to hear that
607 2013-05-29 16:16:34 <sipa> gavinandresen: :(
608 2013-05-29 16:16:43 <gavinandresen> thanks
609 2013-05-29 16:18:17 <Joker_> Hello!
610 2013-05-29 16:18:56 <Joker_> I have problem with compile in QT5
611 2013-05-29 16:19:23 <sipa> That's expected, as the source isn't Qt5 compliant (yet).
612 2013-05-29 16:20:16 <michagogo> Okay, gitian's booting up lucid
613 2013-05-29 16:25:02 <Joker_> what version of QT's needed to build?
614 2013-05-29 16:25:31 <sipa> 4.8.3 is currently used, afaik
615 2013-05-29 16:25:39 <sipa> and likely preety much any 4.8 will work
616 2013-05-29 16:25:53 <Joker_> thanx
617 2013-05-29 16:25:54 <sipa> there's a pullreq to add Qt5 support, which will likely be merged soon
618 2013-05-29 16:30:07 <warren> Is the openssl from 2009 static linked in bitcoin a security risk?
619 2013-05-29 16:30:26 <gavinandresen> no
620 2013-05-29 16:30:52 <warren> the parts of openssl we use haven't had issues I guess
621 2013-05-29 16:31:17 <jgarzik> well there is RPC SSL. the other bits (ecdsa, sha) are pretty static.
622 2013-05-29 16:31:41 <jgarzik> RPC SSL from 2009-era code might have a vulnerability or two? but RPC itself requires a password and security, so no huge threat model.
623 2013-05-29 16:31:55 <warren> I see. thanks.
624 2013-05-29 16:32:37 <dansmith_btc> Hello, Is it possible to create a 2-of-3 tx without exposing all 3 private keys to a single party? Can Alice add her key, pass on to Bob who add a key and pass on to Carol?
625 2013-05-29 16:33:03 <jgarzik> dansmith_btc, sure.
626 2013-05-29 16:33:18 <michagogo> Linux done building, windows running now
627 2013-05-29 16:33:21 <jgarzik> dansmith_btc, pass around unsigned or partially signed transactions
628 2013-05-29 16:33:31 <dansmith_btc> jgarzik, great!
629 2013-05-29 16:33:46 <jgarzik> IMO we need better support for collecting/signing partially signed transactions right now. It is an out of band, manual process.
630 2013-05-29 16:33:49 <jgarzik> But yes, it works.
631 2013-05-29 16:35:53 <gavinandresen> I just pushed my 0.8.2 gitian sigs
632 2013-05-29 16:36:07 <michagogo> I will as soon as the win32 build finishes
633 2013-05-29 16:43:18 <michagogo> gavinandresen: Done