1 2013-06-25 00:59:28 <Luke-Jr> anyone recall why there's no transactions/remove mutation in BIP 23? :/
2 2013-06-25 01:33:54 <random_cat> where are BIPs?
3 2013-06-25 01:45:06 <Luke-Jr> random_cat: https://en.bitcoin.it/wiki/BIP
4 2013-06-25 02:17:54 <Luke-Jr> petertodd: thoughts? http://gitorious.org/bitcoin/libblkmaker/commit/e7d36757ef0532b94350c6691edf41d9d5877eb6/diffs/1e44b127ba61db2e83387cc7741385d4393f2e5b
5 2013-06-25 07:19:35 <TradeFortress> 5 BTC bounty if you help me patch bitcoind so I can call "getaddresstransactions" that lists transactions of any address.
6 2013-06-25 07:21:15 <swulf--> It wouldn't be too hard to code that up, but the problem is that you have to scan the entire blockchain for each call...
7 2013-06-25 07:22:14 <swulf--> Or build a new database that maps address->transactions, which (I think) would double the hd space requirements.
8 2013-06-25 07:22:47 <TradeFortress> swulf--, I can do that..
9 2013-06-25 07:22:55 <swulf--> which?
10 2013-06-25 07:22:58 <TradeFortress> except I know about zero C-- :/
11 2013-06-25 07:23:15 <TradeFortress> Which is why I'll pay you 5 BTC if you get me a patch that I can just query json-rpc.
12 2013-06-25 07:23:32 <swulf--> Hmmm.
13 2013-06-25 07:24:58 <lianj> TradeFortress: the question comes up often, i think the summary is that bitcoind isn't the tool to add this feature, you have to write something ontop. its not just double the disk space, more like 10 times.
14 2013-06-25 07:25:35 <swulf--> lianj: why 10x? A table of addresses, a table of transactions, and a 1-to-many mapping..
15 2013-06-25 07:26:13 <lianj> sites like blockexplorer or blockchain.info have build such a db for themself, they all use a seperate (unrelated to bitcoind) db for it.
16 2013-06-25 07:26:33 <Scrat> TradeFortress: https://github.com/jtobey/bitcoin-abe
17 2013-06-25 07:26:35 <lianj> swulf--: you need a table of outputs and inputs too
18 2013-06-25 07:27:08 <swulf--> linaj: which are just addresses, technically. you could include in the 1-to-many mapping whether the connection is to an input, an output, and the input/output index.
19 2013-06-25 07:27:22 <TradeFortress> Scrat, hmm, that's nice. does it scale?
20 2013-06-25 07:27:37 <swulf--> bitcoin-abe is in use in a lot of production sites
21 2013-06-25 07:27:42 <lianj> TradeFortress: with sqlite no. with postgres yes-ish
22 2013-06-25 07:28:15 <Scrat> sure, it reduces the problem to an properly indexed SQL query
23 2013-06-25 07:28:26 <Scrat> or multiple ones with JOINs
24 2013-06-25 07:28:27 <swulf--> right
25 2013-06-25 07:28:28 <sipa> TradeFortress: i've implemented a getaddresstransactions before
26 2013-06-25 07:28:32 <sipa> TradeFortress: maybe i still have the code
27 2013-06-25 07:28:42 <sipa> but i didn't like it enough to pullrequest it
28 2013-06-25 07:28:54 <TradeFortress> sipa, if you can dig that out and it works on latest with okay performance, I'll tip you 5 btc.
29 2013-06-25 07:29:10 <sipa> actually, i hate it... i don't think people should build infrastructure that depends on such a huge index to index
30 2013-06-25 07:29:16 <sipa> but they probably will anyway
31 2013-06-25 07:29:34 <Habbie> if it scales with postgres but not with sqlite it's likely that the problem is "default sqlite settings"
32 2013-06-25 07:29:54 <TradeFortress> okay. well this is actually for an offchain payments system. I'd like to include a block explorer in it, so people don't have to exit the site.
33 2013-06-25 07:30:10 <Scrat> I bet it's the other way around. default postgres settings suck for big DBs
34 2013-06-25 07:30:16 <sipa> if it's offchain, why do you need to observe the chain...?
35 2013-06-25 07:31:51 <TradeFortress> sipa, cause people might still want to see. it doesn't take much effort to make a block explorer using the rpc calls, but you can't lookup by address
36 2013-06-25 07:32:42 <sipa> TradeFortress: https://github.com/realazthat/overblock
37 2013-06-25 07:32:46 <sipa> RPC-based block explorer
38 2013-06-25 07:33:29 <sipa> TradeFortress: i still have the patch, but i'll need to rebase it
39 2013-06-25 07:33:31 <TradeFortress> sipa, no lookup by address which is what I need. I already have TX, blocks, etc.
40 2013-06-25 07:33:53 <sipa> i'll see if i find some time this evening
41 2013-06-25 07:36:40 <TD> TradeFortress: how does your service work?
42 2013-06-25 07:38:08 <TradeFortress> TD: deposit coins in > [wait for it to confirm] > send offchain to other inputs.io users > withdrawal to blockchain
43 2013-06-25 07:38:27 <TD> and why would someone use it?
44 2013-06-25 07:39:15 <TradeFortress> because it's easy (user side & developer to integrate), because it works with my services, and because it's much more secure
45 2013-06-25 07:40:41 <TD> how is it more secure?
46 2013-06-25 07:41:08 <TD> i ask because such services have a long track record of either getting hacked, being run by scammers, or both
47 2013-06-25 07:41:39 <TradeFortress> right, this is defintely a good point. online wallet services do require you to trust the operator. this includes blockchain.info
48 2013-06-25 07:42:01 <sipa> especially when they offer a blockexplorer
49 2013-06-25 07:42:06 <TradeFortress> your browser will happily run whatever JS the server feeds.
50 2013-06-25 07:42:20 <TD> there is also the question of whether you will be regulated as a bank
51 2013-06-25 07:42:22 <sipa> you may try to have your blockexplorer show that a transaction from you did confirm already, while you didn't send it at all :)
52 2013-06-25 07:42:46 <TradeFortress> tell me you check the source code every time you opened your "My Wallet".
53 2013-06-25 07:43:10 <TradeFortress> because if you haven't checked once, you could be compromised. your passphrase could have been stored and sent.
54 2013-06-25 07:43:19 <sipa> TradeFortress: you're preaching to the choir
55 2013-06-25 07:43:31 <TradeFortress> I guess :P
56 2013-06-25 07:44:19 <TradeFortress> Inputs.io is different on the server side. our bitcoin server is seperate from our web server, you never send your password to the server
57 2013-06-25 07:44:36 <sipa> so?
58 2013-06-25 07:45:00 <sipa> (i mean, that's good security practice, but not a reason why people should trust you)
59 2013-06-25 07:45:00 <TradeFortress> we don't pretend that we can't take your coins.
60 2013-06-25 07:45:09 <sipa> ha, i like that :D
61 2013-06-25 07:45:26 <TradeFortress> I've run coinlenders for 3 months now I think
62 2013-06-25 07:45:55 <TradeFortress> and I've ran an investment fund in BTC for half a year, with transparent accounts :)
63 2013-06-25 07:47:28 <TradeFortress> because the bitcoin sending is server side, inputs.io can make use of additional security measures, such as requesting an email confirmation if you're signing in from a different location or useragent.
64 2013-06-25 07:47:54 <TradeFortress> and login rate limits, which makes brute forcing impractical
65 2013-06-25 07:49:27 <TradeFortress> key point is, I'm not incompetent when it comes to web security, with real world experience in handling 5 digit coin sums and never been hacked.
66 2013-06-25 07:50:14 <TD> unfortunately, i would not trust anyone at this point to hold my coins. running a bitcoin bank is simply unlike any other kind of web app. normal best practices are insufficient.
67 2013-06-25 07:50:31 <TD> if you try this, you WILL get hacked or smacked by your local regulators, or both
68 2013-06-25 07:50:43 <TD> so i would recommend finding an alternative business plan.
69 2013-06-25 07:51:58 <TradeFortress> TD, there are different crowds of users, and Inputs.io is not for the "i <3 github" crowd.
70 2013-06-25 07:52:28 <TradeFortress> Inputs.io still has advanced features like messaging signing (in a single format, no fumbling over whitespaces or where it begins or whatever)
71 2013-06-25 07:53:08 <TradeFortress> But a web wallet *does* offer many benefits. Such as 2 factor auth, access it from anywhere (mobile, tablet, TV, whatever), cloud addressbook, and there's the off chain aspect.
72 2013-06-25 07:53:34 <BlueMatt> is the 2-factor bitcoin multisig, or shitty login 2-factor?
73 2013-06-25 07:54:30 <TD> sure, there can be some benefits, but you're comparing features you haven't written yet to the currently existing code for client side wallets. 2-factor auth helps users avoid losing their passwords, it doesn't stop you getting hacked. and the goal is that we can have 2-factor auth on the client side too, via devices like the trezor.
74 2013-06-25 07:54:30 <TradeFortress> login 2fa but multisig / escrow are in the pipeline
75 2013-06-25 07:54:55 <TradeFortress> TD, it kinda does when the bulk of coins are in cold storage held by many different people in a multisig address, no?
76 2013-06-25 07:55:20 <TD> no. cold storage is not a panacea. you still have to service withdrawal requests from userse
77 2013-06-25 07:55:26 <TD> and how do you know such a request is legitimate?
78 2013-06-25 07:55:45 <TD> cold storage can help avoid a 100% instant game-over scenario, but individual users can still get hacked
79 2013-06-25 07:56:11 <TD> and even then, your cold storage has to be secure as well. as the amounts of money stored go up, the types of attacks you might have to deal with go up as well
80 2013-06-25 07:56:30 <TD> e.g. breakins to your offices or facilities, kidnapping or bribery or blackmail of your staff.
81 2013-06-25 07:56:51 <TradeFortress> I'm not denying that this is easy and there are many challenges in regards to security
82 2013-06-25 07:56:54 <TD> really, there's just no amount of money you could pay me to run a bitcoin bank. all the features can be reimplemented with client side wallets, and you avoid painting a massive target on your back
83 2013-06-25 07:57:16 <TradeFortress> users can get hacked, but their wallet.dat could also be stolen.
84 2013-06-25 07:57:44 <TradeFortress> with a keylogger that makes your encryption useless
85 2013-06-25 07:57:51 <BlueMatt> trezor
86 2013-06-25 07:58:18 <TradeFortress> that's not a client side wallet.
87 2013-06-25 07:58:31 <TD> it plugs into my client? how is it not a client side wallet?
88 2013-06-25 07:59:19 <TradeFortress> You need to buy it, good luck convincing someone who is new to bitcoin to do that
89 2013-06-25 08:00:52 <TradeFortress> like I said, people who are paranoid (which is a good thing) probably won't use Inputs.io except for maybe a small amount. like a float you keep on an exchange.
90 2013-06-25 08:01:53 <TradeFortress> but there are people who's willing to use a hosted solution with benefits. I know, because CL requires people to trust me and people use coinlenders.
91 2013-06-25 08:06:23 <TD> sipa: it's not really a duplicate, is it? the latter pull req involves some git changes too
92 2013-06-25 08:07:47 <sipa> TD: hmm?
93 2013-06-25 08:07:56 <TD> sipa: updating leveldb
94 2013-06-25 08:07:59 <sipa> yes
95 2013-06-25 08:08:24 <TD> sipa: changing the version seems to be a different thing to changing how it's integrated with git. though i am not sure what the benefits are of the subtree stuff
96 2013-06-25 08:08:53 <sipa> the subtree stuff is already merged in a previous commit
97 2013-06-25 08:09:14 <sipa> TD: the idea is being able to maintain a separate repo/branch to maintain our leveldb branch, and be able to easily sync from that
98 2013-06-25 08:09:51 <TD> it seems like it's still possible to edit the code and create an ordinary pull request for it though. that's confusing.
99 2013-06-25 08:10:00 <TD> ACTION isn't sure he likes the idea of git magic in this
100 2013-06-25 08:10:26 <TD> why is this complexity worth it? there wasn't anything wrong with the previous approach
101 2013-06-25 08:10:31 <sipa> there is no magic really - it's just automatically finding changes in one repo and applying them to a subdir of the other
102 2013-06-25 08:10:56 <sipa> well, that's why i've asked for opinions about it on vinnie's pullreq
103 2013-06-25 08:11:06 <sipa> and i'd rather know how we want to deal with this first
104 2013-06-25 08:11:26 <TradeFortress> LOL @ No LTC support, do people actually come here and ask about ltc?
105 2013-06-25 08:11:33 <TD> the pull request looks identical, just with an auto-generated commit message
106 2013-06-25 08:11:40 <sipa> TD: yes
107 2013-06-25 08:11:55 <TD> ok. now i see why you close mine as a duplicate :)
108 2013-06-25 08:11:56 <sipa> but i want to know whether we want a bitcoin/leveldb.git repo for example
109 2013-06-25 08:12:24 <sipa> i'd like that - i find it pretty ugly that we maintain a leveldb branch whose authorative source is a subdir of our repository
110 2013-06-25 08:13:10 <TD> ACTION shrugs
111 2013-06-25 08:13:15 <TD> it's simple and robust. there's a lot to be said for that.
112 2013-06-25 08:13:56 <sipa> well, that's the nice thing about git-subtree: you don't need to care or even know about it if you only want to build
113 2013-06-25 08:16:19 <TD> fair enough
114 2013-06-25 11:08:31 <Vinnie_win> sup
115 2013-06-25 11:51:47 <jgarzik> mornin'
116 2013-06-25 11:51:50 <gavinandresen> mornin
117 2013-06-25 11:52:09 <gavinandresen> ??? my first semi-normal work morning in a few weeks....
118 2013-06-25 11:52:47 <jgarzik> ACTION performs his morning VirtualBox clock kick, on OSX (suspend + resume yields outdated clock inside Linux VM)
119 2013-06-25 11:55:11 <TD> it's gavinandresen ! he has returned to us !
120 2013-06-25 11:55:48 <gavinandresen> ??? got a brain transplant from the NSA when I was down in DC, though....
121 2013-06-25 11:56:29 <jgarzik> gavinandresen, that means you're now supersmart and massively parallel? Good, I've got some pull reqs for you to review
122 2013-06-25 11:56:30 <jgarzik> ACTION runs
123 2013-06-25 11:57:08 <TD> it means we don't have to CC him on threads anymore
124 2013-06-25 11:57:10 <TD> he knows already
125 2013-06-25 11:57:34 <gavinandresen> BEHOLD, GAVIN THE OMNISCIENT!
126 2013-06-25 11:57:35 <gjs278> time is always off for me too
127 2013-06-25 11:57:40 <gjs278> but it usually jumps up right away
128 2013-06-25 12:11:18 <tgs3> gavinandresen was the one that was sent to FBI back in goold old days?
129 2013-06-25 12:11:30 <tgs3> did they propose anything in diection of PRISM >_> ?
130 2013-06-25 12:18:08 <jgarzik> http://www.coindesk.com/bitcoin-network-recovering-from-ddos-attack/
131 2013-06-25 12:18:32 <jgarzik> Sigh. That's what I get for being vague.
132 2013-06-25 12:19:06 <TD> press cycle!
133 2013-06-25 12:19:52 <sipa> gavinandresen: ACK on 0.8.3 with strip-tx-before-relay + 2789
134 2013-06-25 12:21:02 <gmaxwell> I've been running 0.8.2 with strip before relay plus 2789 for ~two days on my laptop, fwiw.
135 2013-06-25 12:23:14 <gavinandresen> gmaxwell: I'll consider that another ACK then
136 2013-06-25 12:26:20 <jgarzik> gavinandresen, ACK what sipa just siad
137 2013-06-25 12:26:22 <jgarzik> *said
138 2013-06-25 12:27:17 <gmaxwell> Yes, ACK on that.
139 2013-06-25 12:29:46 <Mr_Cloud> curl --user loluser:pass --data-binary "{\\"method\\": \\"gettransaction\\"}" http://127.0.0.1:8332/ <<
140 2013-06-25 12:29:58 <Mr_Cloud> What comes after gettransaction?
141 2013-06-25 12:30:18 <Mr_Cloud> <txid> << Do I need the funky brackets?
142 2013-06-25 12:30:35 <sipa> no
143 2013-06-25 12:31:14 <Mr_Cloud> 'Cause if I write \\"gettransaction 023y9ahdf9asghf7893wg\\" then it doesn't like it
144 2013-06-25 12:31:23 <TD> you need txindex
145 2013-06-25 12:31:30 <sipa> and you need to pass it as an argument
146 2013-06-25 12:31:34 <sipa> not as the name of the method
147 2013-06-25 12:31:53 <Mr_Cloud> Ah ok
148 2013-06-25 12:32:06 <Mr_Cloud> So gettransaction is the name of the command only
149 2013-06-25 12:32:14 <Mr_Cloud> And the txid should be separate
150 2013-06-25 12:34:20 <gavinandresen> sipa jgarzik gmaxwell : pushed https://github.com/bitcoin/bitcoin/commits/0.8.3 -- look reasonalbe ?
151 2013-06-25 12:35:01 <jgarzik> gavinandresen, ACK
152 2013-06-25 12:35:01 <sipa> gavinandresen: 2013-06-20 14:43:50 Dropping 1500005 bytes of tx before relay!!!
153 2013-06-25 12:35:06 <sipa> that was the last on mainnet
154 2013-06-25 12:35:14 <sipa> gavinandresen: ACK
155 2013-06-25 12:35:36 <gavinandresen> cool, I'll push a v0.8.3 tag and start gitian building
156 2013-06-25 12:35:59 <gmaxwell> sounds good to me.
157 2013-06-25 12:36:21 <warren> i'll do a gitian build
158 2013-06-25 12:37:14 <gavinandresen> * [new tag] v0.8.3 -> v0.8.3
159 2013-06-25 12:37:15 <jgarzik> ACTION needs to dedicate a day to getting gitian going
160 2013-06-25 12:37:24 <jgarzik> gavinandresen, oh
161 2013-06-25 12:37:30 <jgarzik> gavinandresen, please push DOS fix to HEAD
162 2013-06-25 12:37:39 <jgarzik> gavinandresen, can't have a fix on a branch, and not in HEAD ;p
163 2013-06-25 12:37:56 <sivu> i'll update server to 0.8.3
164 2013-06-25 12:38:05 <jgarzik> er, master, I mean
165 2013-06-25 12:38:46 <gavinandresen> jgarzik: ok, I'll cherry-pick and push to master
166 2013-06-25 12:39:05 <jgarzik> gavinandresen, tnx
167 2013-06-25 12:42:41 <sivu> why the compile commandline has -fno-stack-protector -fstack-protector-all
168 2013-06-25 12:43:18 <gmaxwell> sivu: because ubuntu patches the compilter to -fstack-protector and just adding -fstack-protector-all didn't work right, IIRC.
169 2013-06-25 12:43:45 <jgarzik_> ACTION kicks freenode
170 2013-06-25 12:43:52 <jgarzik_> dammit bitmessage, please become a better-IRC
171 2013-06-25 12:43:57 <sivu> gmaxwell: sounds like ubuntu allright
172 2013-06-25 12:45:32 <michagogo_> Wow, 0.8.3 already?
173 2013-06-25 12:50:22 <michagogo> Is the 0.8.3 final? If so, I'll reboot into Ubuntu and build
174 2013-06-25 12:50:52 <warren> sounds like they're doing gitian builds to verify determinism.
175 2013-06-25 12:50:54 <warren> i'm buliding to help
176 2013-06-25 12:54:31 <jgarzik_> warren, what the heck is a "supernode" in litecoin?
177 2013-06-25 12:54:45 <warren> jgarzik: we had a unique problem and that was our dumb temporary solution
178 2013-06-25 12:57:22 <Mr_Cloud> Oh mang, so close
179 2013-06-25 12:57:25 <Mr_Cloud> Yet so far!
180 2013-06-25 12:58:36 <Mr_Cloud> Guys, what am I doing wrong?
181 2013-06-25 12:58:37 <Mr_Cloud> curl --user lol:hai --data-binary "{\\"method\\": \\"gettransaction\\", \\"txid\\":\\"5ahdfauhfu9adh00etc\\" --url http://127.0.0.1:8332/
182 2013-06-25 12:58:38 <Mr_Cloud> curl: no URL specified!
183 2013-06-25 12:58:38 <Mr_Cloud> curl: try 'curl --help' or 'curl --manual' for more information
184 2013-06-25 12:59:49 <imd23> hi there
185 2013-06-25 12:59:51 <michagogo> Mr_Cloud: I don't think you need --url
186 2013-06-25 12:59:52 <sipa> Mr_Cloud: you're missing a closing bracket
187 2013-06-25 12:59:56 <imd23> how is everyone going?
188 2013-06-25 12:59:56 <michagogo> And that
189 2013-06-25 13:00:03 <sipa> Mr_Cloud: and look up the specification for JSON-RPC, please
190 2013-06-25 13:00:06 <michagogo> Mr_Cloud: AFAIK the last argument is taken as the URL
191 2013-06-25 13:00:23 <imd23> I was wondering if anyone did a preformance /througput test of bitcoind ?
192 2013-06-25 13:01:06 <Mr_Cloud> Hory shet, I am too! Thanks sipa and michagogo
193 2013-06-25 13:01:19 <imd23> I am developing a new service and need to implement a roboust core for transactions and queries, is bitcoind fast enought to take this task?
194 2013-06-25 13:01:28 <Mr_Cloud> And sipa, I did look at the documentation. Only I'm having trouble interpreting it
195 2013-06-25 13:01:37 <Mr_Cloud> Which is why I'm asking for syntax help on here
196 2013-06-25 13:01:46 <Mr_Cloud> (I wish I was better at this lol)
197 2013-06-25 13:02:11 <michagogo> imd23: What exactly are you planning to do with bitcoind?
198 2013-06-25 13:02:21 <sipa> Mr_Cloud: please read the documentation instead of trying to guess and then complaining here that it doesn't work
199 2013-06-25 13:04:58 <warren> gavinandresen: gmaxwell: http://pastebin.com/YJ8CpXUH gitian sha256sums
200 2013-06-25 13:05:03 <Mr_Cloud> sipa: My trouble seems to be interpreting the documentation, as I've never worked with curl before. It's obvious that the level of programming present in this channel is way beyond me, so perhaps there is a more beginner-friendly channel where people can ask questions?
201 2013-06-25 13:06:24 <michagogo> warren: Why not just fork and PR gitian.sigs?
202 2013-06-25 13:06:50 <warren> michagogo: hm? I didn't look into how that works yet.
203 2013-06-25 13:07:47 <sipa> Mr_Cloud: not curl's documentation - JSON-RPC
204 2013-06-25 13:07:54 <michagogo> warren: See https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md
205 2013-06-25 13:08:13 <michagogo> warren: the "perform gitian builds" section
206 2013-06-25 13:08:46 <michagogo> Once you build, use gsign to create files describing the build input and output along with signatures
207 2013-06-25 13:09:05 <warren> michagogo: don't I have to be one of the signers in there?
208 2013-06-25 13:09:08 <warren> I'm not
209 2013-06-25 13:09:21 <michagogo> warren: That's why you fork the repo on github
210 2013-06-25 13:09:36 <michagogo> Clone your fork, commit to it, push, PR
211 2013-06-25 13:09:49 <warren> that goes to master?
212 2013-06-25 13:10:16 <michagogo> Assuming the PR gets merged, yes
213 2013-06-25 13:10:25 <michagogo> (that's the only branch)
214 2013-06-25 13:10:48 <warren> michagogo: I'll get involved with that in the next round ... for now I need to apparently fix this in the silly clone coin
215 2013-06-25 13:10:49 <Mr_Cloud> What I mean sipa is that I'm not familiar with implementing Bitcoin-qt's API using curl. Which is why I'm here. Trying to learn.
216 2013-06-25 13:14:46 <michagogo> Okay, going to gitian build now
217 2013-06-25 13:21:57 <gavinandresen> pushed 0.8.3 gitian sigs (linux build matches warren's)
218 2013-06-25 13:22:15 <warren> fedora gitian =)
219 2013-06-25 13:23:50 <Mad7Scientist> <Mad7Scientist> I already have most of the blocks from the 0.7 database
220 2013-06-25 13:23:50 <Mad7Scientist> <Mad7Scientist> Why is bitcoin-qt 0.8.2 downloading the blocks over the Internet
221 2013-06-25 13:24:04 <MC1984> its not
222 2013-06-25 13:24:09 <TheXev> Mad7Scientist: database conversion?
223 2013-06-25 13:24:29 <Mad7Scientist> It's rebuilding after a database corruption
224 2013-06-25 13:24:34 <Mad7Scientist> started at 233 weeks behind
225 2013-06-25 13:24:44 <Mad7Scientist> It asked if I want to reindex
226 2013-06-25 13:24:46 <Mad7Scientist> and I said yes
227 2013-06-25 13:24:55 <sipa> then it should reuse the blocks you have on disk
228 2013-06-25 13:24:55 <TheXev> yeah, i had that happen.. it basically deleted the pre-0.8 database (it was a good thing, in the long run)
229 2013-06-25 13:25:00 <Mad7Scientist> It's downloading 500KB/sec
230 2013-06-25 13:25:13 <sipa> well perhaps there's a corruption in the actual blocks file
231 2013-06-25 13:25:14 <TheXev> well, i nuked my block chain, i kept having random db problems.
232 2013-06-25 13:25:20 <Mad7Scientist> but the pre 0.8 database shouldn't be corrupted since it was not being used
233 2013-06-25 13:25:40 <Mad7Scientist> during the power failure
234 2013-06-25 13:25:55 <sipa> if it's reindexing, the old 0.8 database isn't being used
235 2013-06-25 13:26:03 <sipa> it's just rebuilding it from the blocks on disk
236 2013-06-25 13:26:09 <Mad7Scientist> old 0.7 you mean
237 2013-06-25 13:26:22 <sipa> both
238 2013-06-25 13:26:36 <sipa> and if a block on disk is corrupted, it loses a sync and will download from network after that point
239 2013-06-25 13:26:40 <Mad7Scientist> I want to clear out the 0.8 database and rebuild from 0.7 and then download what is remaining
240 2013-06-25 13:26:50 <Mad7Scientist> I think it ignored the 0.7 database
241 2013-06-25 13:27:13 <sipa> do you have ~/.bitcoin/blk*.dat files?
242 2013-06-25 13:27:13 <TheXev> imo, its best to nuke the old DBs and clean slate. I increased my maxconnections to 30 in bitcoin.conf and got resynced from scratch rather quickly. I haven't had any reindexing issues since I clean slated under 0.8+
243 2013-06-25 13:27:17 <Mad7Scientist> yes
244 2013-06-25 13:27:24 <Mad7Scientist> they are 2GB each
245 2013-06-25 13:27:35 <sipa> do you also have ~/.bitcoin/blocks/blk*.dat ?
246 2013-06-25 13:27:56 <TD> incidentally, my bitcoin corrupted its leveldb last night
247 2013-06-25 13:28:03 <TD> on my laptop .... it didn't come back after an OS update
248 2013-06-25 13:28:05 <TD> :(
249 2013-06-25 13:28:12 <TD> i couldn't see any evidence of a sudden shutdown though
250 2013-06-25 13:28:26 <TheXev> yeah, i just had all kinds of issues with a mixed database.
251 2013-06-25 13:28:27 <TD> and the hardware is pretty new
252 2013-06-25 13:28:33 <Mad7Scientist> yes blk*.dat and rev*.dat
253 2013-06-25 13:28:45 <TheXev> but since i did a clean 0.8 database, its all been good and stable.
254 2013-06-25 13:29:33 <Mad7Scientist> I shut down bitcoin-qt
255 2013-06-25 13:29:38 <Mad7Scientist> how do I tell it to rebuild from 0.7?
256 2013-06-25 13:29:58 <Mad7Scientist> delete the files?
257 2013-06-25 13:29:59 <TheXev> i went into my appdata folder and cleaned house, and backed up the wallet.dat
258 2013-06-25 13:30:44 <TheXev> and then just reinitialized my wallet with an empty appdata folder (windows)
259 2013-06-25 13:31:16 <sipa> TD: :(
260 2013-06-25 13:31:20 <sipa> TD: bah
261 2013-06-25 13:31:34 <sipa> Mad7Scientist: 0.8 always uses blocks/blk*, 0.7 always uses blk*
262 2013-06-25 13:31:46 <Mad7Scientist> can I delete ~/.bitcoin/blocks/
263 2013-06-25 13:31:54 <TD> sipa: yeah. i have no clue what can be causing that. but what i might try is setting up a cron job to tell it to re-verify recent data every day
264 2013-06-25 13:31:57 <sipa> Mad7Scientist: if you run 0.8, and no blocks/ exists, it will hardlink the 0.7 files into it, and rebuild from those
265 2013-06-25 13:32:09 <Mad7Scientist> ok
266 2013-06-25 13:32:11 <TD> as i suspect there may have been an issue introduced at some random point in the past, and the corruption only gets detected when i restart bitcoin-qt (which is rare)
267 2013-06-25 13:32:16 <TD> i also wonder if laptop sleeping is able to affect it
268 2013-06-25 13:32:24 <Mad7Scientist> now it found a corrupted 0.8 and then started downloading what was missing from the Internet
269 2013-06-25 13:32:34 <Mad7Scientist> instead of from 0.7
270 2013-06-25 13:32:55 <Mad7Scientist> what would deleting blocks/index do?
271 2013-06-25 13:33:12 <Mad7Scientist> I guess that would ruin it
272 2013-06-25 13:33:32 <Mad7Scientist> there are so many files in blocks/ and only the most recent one must be corrupted
273 2013-06-25 13:33:41 <Mad7Scientist> why would the older ones be corrupted?
274 2013-06-25 13:34:48 <Mad7Scientist> 19M Jun 25 10:28 rev00000.dat
275 2013-06-25 13:34:57 <Mad7Scientist> Jun 22 11:00 rev00016.dat
276 2013-06-25 13:35:01 <TheXev> I don't know what was causing the db issues I had. I just clean slated and its been good ever since. It was much simpler then trying save any of my pre-existing data. :/
277 2013-06-25 13:35:11 <Mad7Scientist> the block 0000 has newer modification time than the last block
278 2013-06-25 13:35:26 <Mad7Scientist> it must be hopeless then
279 2013-06-25 13:35:30 <Mad7Scientist> if it isn't writing them in order
280 2013-06-25 13:35:58 <Mad7Scientist> deleting .bitcoin/blocks
281 2013-06-25 13:38:10 <Mad7Scientist> now it is updating very fast
282 2013-06-25 13:41:20 <gavinandresen> TD: OSX laptop? Are you running FileVault?
283 2013-06-25 13:41:45 <TD> no. i don't believe so.
284 2013-06-25 13:41:55 <TD> it's a regular macbook pro with minimal changes, ssd
285 2013-06-25 13:43:26 <gavinandresen> TD: ok, that matches other reports of "random leveldb corruption on OSX" then
286 2013-06-25 13:43:47 <TD> i strongly suspect there's something weird going on with laptop sleeps. i keep bitcoin-qt running all the time.
287 2013-06-25 13:44:04 <TD> and OS X 10.8+ does weird things where it wakes up in a kind of partial-wake mode at night to do syncing and things
288 2013-06-25 13:45:26 <gavinandresen> I haven't had any problems on my 10.8 desktop, but it never sleeps (not that one data point means much)
289 2013-06-25 13:51:52 <michagogo> Okay, gitian's running
290 2013-06-25 13:52:11 <michagogo> "Running build script (log in var/build.log)" for linux i386 atm
291 2013-06-25 13:57:01 <michagogo> Building now for linux x64
292 2013-06-25 13:57:14 <michagogo> s/x/amd/
293 2013-06-25 14:12:52 <imd23> hey
294 2013-06-25 14:12:54 <imd23> guys
295 2013-06-25 14:13:08 <imd23> has anyone have idea about the performance of bitcoind as a server for a service?
296 2013-06-25 14:13:24 <imd23> I need to implement bit coin a startup
297 2013-06-25 14:13:47 <sipa> that will really depend on what kind of service
298 2013-06-25 14:14:30 <imd23> mmm??? not a exchange but related to the amount of transactions
299 2013-06-25 14:14:41 <imd23> I mean, I know I will need more than 1 server, of course,
300 2013-06-25 14:14:54 <helo> imd23: i think for most business-scale uses, bitcoind is not enough
301 2013-06-25 14:15:04 <imd23> ok.
302 2013-06-25 14:15:10 <imd23> any alternative?
303 2013-06-25 14:15:20 <gmaxwell> helo: please don't give irresponsible answers.
304 2013-06-25 14:15:36 <gmaxwell> imd23 has not even remotely suggested the sort of thing he's actually trying to do.
305 2013-06-25 14:15:48 <helo> this is true.
306 2013-06-25 14:15:57 <handle> i think for most james bond-scale uses, the world is not enough
307 2013-06-25 14:16:02 <imd23> I mean, kind of a exchange, is a new way of transferring btc???
308 2013-06-25 14:16:15 <helo> i was going to suggest that bitcoind should be involved as a signaling mechanism to the rest of his infrastructure
309 2013-06-25 14:16:20 <imd23> it's new concept, so if it works and works well, everyone could use it.
310 2013-06-25 14:16:34 <helo> but relying on bitcoind to handle accounts and balances, etc., is usually not[D the way to go.
311 2013-06-25 14:16:35 <imd23> the critical part is transactions and verifications.
312 2013-06-25 14:17:01 <imd23> helo: how many transactions are you talking about 10 or 1000?
313 2013-06-25 14:17:32 <imd23> I mean??? if the product works I will rent 50 servers, obviously, but to start small I will be using a few.
314 2013-06-25 14:17:58 <gmaxwell> It's still not clear what imd23 wants bitcoind to do.
315 2013-06-25 14:18:00 <imd23> I just need to know if it's not prepared to any kind of medium load, or ir can be kind of tolerant
316 2013-06-25 14:18:01 <helo> bitcoind can handle 10 transactions just fine. i still don't think that most people would want to use it to generate financial statements
317 2013-06-25 14:18:10 <helo> (or 1000)
318 2013-06-25 14:18:28 <imd23> bitocoind as a roc server for the startup-app logic.
319 2013-06-25 14:18:29 <gmaxwell> helo: he hasn't made any suggestion that he's planning on using bitcoind as a wallet.
320 2013-06-25 14:18:47 <helo> imd23: it all depends on what exactly you're doing. everyone's requirements are different.
321 2013-06-25 14:18:51 <imd23> it will serve as the code network connector.
322 2013-06-25 14:18:54 <imd23> no, the wallet will be offline
323 2013-06-25 14:19:07 <helo> imd23: so how will you know your balances?
324 2013-06-25 14:19:28 <imd23> the app will pass the private key each time it's needed, and will be cached
325 2013-06-25 14:19:56 <helo> imd23: from the topic, "Tell us what you're trying to do, not how you think you need to do it."
326 2013-06-25 14:20:03 <sipa> how will you detect incoming payments?
327 2013-06-25 14:20:22 <imd23> but this will be managed by our backend, not the bitcoind itself. I need it to be a bit coin network gateway.
328 2013-06-25 14:20:25 <michagogo> Erm, can someone help me out with something? https://github.com/Michagogo/gitian.sigs/commits/master
329 2013-06-25 14:20:25 <michagogo> Where did commits a84fc... and cd0e8... come from?
330 2013-06-25 14:20:45 <imd23> I can't talk a lot, so far, but if we think of MtGox for my problem it's the same
331 2013-06-25 14:20:48 <imd23> kinda
332 2013-06-25 14:21:24 <imd23> imagine, mtgox has to generate keys, receive btc, and withdraw..
333 2013-06-25 14:21:49 <imd23> that 3 key things, can I use bitcoind as my core bitcoint network talker?
334 2013-06-25 14:21:53 <imd23> (gateway)
335 2013-06-25 14:22:48 <sipa> imd23: to talk to the network sure, but you will either use bitcoind' wallet implementation or your own
336 2013-06-25 14:23:48 <pigeons> i've been here long enough to be able to handle this one. "What are you trying to do?"
337 2013-06-25 14:23:48 <sipa> imd23: you can't ask bitcoind to tell you when a transaction has happened, unless you manage your wallet by bitcoind
338 2013-06-25 14:25:21 <gmaxwell> pigeons: Sipa tried that already. :P
339 2013-06-25 14:25:36 <imd23> Imagine , my idea needs in 1 minute to tell bitcoind to do 1000 transactions, with 1000 differents privs key and addreses, in and out.
340 2013-06-25 14:25:36 <imd23> the store of the priv and pub keys will be handled by our app, not bitcoind
341 2013-06-25 14:25:36 <imd23> will it resist 1000 in 1 minute?
342 2013-06-25 14:26:01 <imd23> I know this is so relative to a lot of things like the server cpu, , etc.. but in general.
343 2013-06-25 14:26:02 <gmaxwell> Doesn't even make sense.
344 2013-06-25 14:26:13 <gmaxwell> The Bitcoin network can't handle transaction volumes that high.
345 2013-06-25 14:26:14 <imd23> haha, imagine an exchange, for my purposes is the same??? :)
346 2013-06-25 14:26:15 <imd23> imagine we need to create a new exchange.
347 2013-06-25 14:26:25 <imd23> ok. how does mtgox do it?
348 2013-06-25 14:26:31 <gmaxwell> imd23: have you ever actually used bitcoin?
349 2013-06-25 14:26:37 <imd23> yeah
350 2013-06-25 14:26:40 <gmaxwell> The bitcoin software does not implement an exchange.
351 2013-06-25 14:26:43 <michagogo> Anyone?
352 2013-06-25 14:26:49 <sipa> imd23: mtgox has their own bitcoin implementation, pretty much from scratch
353 2013-06-25 14:26:57 <imd23> spia: thanks!
354 2013-06-25 14:27:10 <michagogo> I want to PR my 0.8.3 sigs, but I don't know what those commits are
355 2013-06-25 14:27:18 <gmaxwell> michagogo: they're merge commits created by git where you pulled.
356 2013-06-25 14:27:28 <imd23> I mean, my product is not like an exchange, more like an scrow..
357 2013-06-25 14:27:32 <imd23> *escrow
358 2013-06-25 14:27:47 <michagogo> gmaxwell: Why do they exist?
359 2013-06-25 14:28:27 <imd23> it doesn't really matter what it is. I just need a server to transfer the btcs from one address to another, I don't get the difference between if the address is us or other person??? at my question I see it is the same.
360 2013-06-25 14:28:29 <gmaxwell> michagogo: your history diverged from the master repository you were pulling from, and so when you updated it git made those merge commits in order to make your repositories agree.
361 2013-06-25 14:28:44 <michagogo> Er, how could it have diverged? o_O
362 2013-06-25 14:28:47 <sipa> imd23: bitcoin transactions are _NOT_ from address to address
363 2013-06-25 14:28:53 <imd23> p2p
364 2013-06-25 14:29:07 <sipa> imd23: transaction manipulate coins, and you need the actual coins in order to send them
365 2013-06-25 14:29:22 <imd23> yeah, I know.
366 2013-06-25 14:29:31 <imd23> but they have a private key, doesn't it?
367 2013-06-25 14:30:21 <michagogo> gmaxwell: Pretty sure all I've done is git pull && git fetch upstream && git merge upstream/master && git push
368 2013-06-25 14:30:55 <gmaxwell> michagogo: presumably because you previously committed to your tree.
369 2013-06-25 14:31:25 <michagogo> AFAIK I haven't comitted anything that I didn't push and PR...
370 2013-06-25 14:31:30 <michagogo> +m
371 2013-06-25 14:31:38 <gmaxwell> michagogo: e.g. pull, commit, then upstream merges other stuff, then yours (or merges yours non-fast forward, or doesn't merge you at all) .. then latter you pull again and you end up with a merge.
372 2013-06-25 14:31:54 <michagogo> gmaxwell: Is it okay to PR with those weird commits?
373 2013-06-25 14:31:56 <sipa> imd23: just a private key is not enough to spend coins
374 2013-06-25 14:31:59 <gmaxwell> michagogo: absolutely.
375 2013-06-25 14:32:18 <sipa> imd23: you need to know the actual transactions (and their outputs) which credited the address corresponding to the key
376 2013-06-25 14:32:20 <imd23> sipa: i don't want to bother you more, may be if you have a like that explains this better
377 2013-06-25 14:32:32 <michagogo> gmaxwell: Done.
378 2013-06-25 14:32:59 <imd23> sipa: you mean the whole chain of transactions?
379 2013-06-25 14:33:06 <sipa> imd23: no, read what i said
380 2013-06-25 14:33:11 <michagogo> .w gavinandresen
381 2013-06-25 14:33:12 <michagogo> oops
382 2013-06-25 14:33:49 <gmaxwell> michagogo: Thanks! In any case, basically you will end up with merges unless your history is exactly the same 1:1 so any difference in the commit ordering around your past pull requests will create those things. If it bothers you, you can always reset your repository to match exactly before adding a new commit.
383 2013-06-25 14:34:31 <imd23> sipa: ok, I am missing something. Let's say you have 1 btc and you want to send it to me. what information do you need to create the transaction? (behind the scenes)
384 2013-06-25 14:34:49 <michagogo> gmaxwell: I don't really mind, it's more a matter of "will the bitcoin devs be upset that I added 3 extra commits to their repo"
385 2013-06-25 14:35:03 <michagogo> Er, more like "will they let me add 3 extra commits to their repo"
386 2013-06-25 14:35:05 <sipa> imd23: the txid and vout index which credited me
387 2013-06-25 14:35:25 <sipa> imd23: and the private key of the address it was sent to
388 2013-06-25 14:35:40 <gmaxwell> michagogo: github should have let you open a pull on just the commit.
389 2013-06-25 14:35:52 <imd23> sipa: ok, I am searching about txid and vout
390 2013-06-25 14:35:55 <michagogo> gmaxwell: Hmm? How?
391 2013-06-25 14:36:13 <michagogo> I clicked the green button and that's what it gave me
392 2013-06-25 14:37:38 <sipa> imd23: https://en.bitcoin.it/wiki/Change
393 2013-06-25 14:37:40 <sipa> imd23: read that first
394 2013-06-25 14:37:53 <sipa> imd23: it's not an answer to your question, but it may teach you something about the internals
395 2013-06-25 14:37:57 <imd23> sipa: ok, you are very kind thanks
396 2013-06-25 14:42:52 <michagogo> gmaxwell: I think I fixed it
397 2013-06-25 14:44:32 <michagogo> I moved my sigs out of my local copy, deleted my local copy, cloned bitcoin's version, added bitcoin's version as upstream and deleted it as origin, added my fork as origin, moved my sigs back in and committed, then `git push --force`
398 2013-06-25 14:47:05 <sipa> michagogo: next time, do a 'git pull' before adding your commits
399 2013-06-25 14:47:11 <michagogo> sipa: I did
400 2013-06-25 14:47:53 <michagogo> (well, I did a `git pull && git fetch upstream && git merge upstream/master && git push`)
401 2013-06-25 14:48:18 <sipa> michagogo: _before_ adding commits
402 2013-06-25 14:48:20 <sipa> not after
403 2013-06-25 14:48:27 <sipa> you do the push afterwards
404 2013-06-25 14:48:38 <michagogo> sipa: That was the first thing I did
405 2013-06-25 14:48:42 <michagogo> Before I gitian-built
406 2013-06-25 14:48:43 <sipa> ah, ok
407 2013-06-25 14:48:54 <michagogo> gavinandresen: When you see this, I've gitian-built 0.8.3 and our outputs do appear to match: https://github.com/bitcoin/gitian.sigs/pull/8
408 2013-06-25 14:48:54 <sipa> well then someone was very simultaneous with you
409 2013-06-25 14:49:14 <michagogo> sipa: Hmm?
410 2013-06-25 14:49:25 <michagogo> gavin's sigs were already in when I did that
411 2013-06-25 14:49:43 <michagogo> Hmm, looks like I make up 50% of PRs on gitian.sigs
412 2013-06-25 14:50:34 <sipa> yeah, most others push directly
413 2013-06-25 14:50:40 <sipa> but don't feel bad abput that!
414 2013-06-25 14:50:59 <michagogo> sipa: Lol, I know
415 2013-06-25 14:51:05 <michagogo> :-P
416 2013-06-25 14:53:34 <Luke-Jr> my win32 matches gavin's
417 2013-06-25 14:54:00 <michagogo> As does mine
418 2013-06-25 14:55:05 <michagogo> Anyone want to double-check that I did everything corrently in https://github.com/bitcoin/gitian.sigs/pull/8 before I reboot to windows and put away my Ubuntu disk?
419 2013-06-25 14:57:05 <sipa> michagogo: looks good
420 2013-06-25 14:57:11 <sipa> i haven't verified the match though
421 2013-06-25 14:58:52 <Luke-Jr> what is the status of how public the 0.8.3 fix is?
422 2013-06-25 14:59:40 <sipa> it was discussed here already, afaik
423 2013-06-25 14:59:49 <sipa> well, maybe not that explicitly
424 2013-06-25 15:00:10 <gmaxwell> We're not attempting to shelter it, though walking people through exploiting it might be unwise.
425 2013-06-25 15:00:49 <gmaxwell> I'm actually surprised that there hasn't been more problems due to it yet.
426 2013-06-25 15:00:50 <Luke-Jr> ok; somehow someone PM'd me with the impression that only low memory nodes are at risk; I guess I can clarify that at least
427 2013-06-25 15:01:24 <gmaxwell> Ah. yes, no. all nodes are at risk.
428 2013-06-25 15:01:47 <gmaxwell> Luke-Jr: any idea where they got that idea?
429 2013-06-25 15:02:00 <handle> wouldn't that only affect people if someone threw a bunch of money at it?
430 2013-06-25 15:02:12 <handle> and only did so before a block showed up, or am I misunderstanding this
431 2013-06-25 15:02:14 <Luke-Jr> gmaxwell: I'll ask.
432 2013-06-25 15:02:35 <Luke-Jr> does anyone know the exact math to figure out the RAM/bandwidth relationship?
433 2013-06-25 15:03:05 <gmaxwell> handle: no. I have no clue what you're talking about but not this.
434 2013-06-25 15:03:27 <handle> ah, disregard that then
435 2013-06-25 15:03:45 <handle> maybe I misunderstand what the problem is
436 2013-06-25 15:03:49 <handle> s/maybe/i definitely/
437 2013-06-25 15:04:22 <Ferroh> "i definitely I misunderstand" then?
438 2013-06-25 15:04:23 <Ferroh> :)
439 2013-06-25 15:04:27 <michagogo> What exactly is the .3 fix?
440 2013-06-25 15:04:51 <thrasher`> truncates malicious tx's
441 2013-06-25 15:04:54 <handle> oops, lol Ferroh
442 2013-06-25 15:05:42 <thrasher`> and by malicious I mean oversized ones
443 2013-06-25 15:06:15 <michagogo> sipa: I just double-checked and both bitcoin-build.assert files have identical out_manifests
444 2013-06-25 15:06:19 <Luke-Jr> gmaxwell: https://github.com/bitcoin/bitcoin/commit/c40a5aaaf484855a4350fd702e8e72fd21a68155
445 2013-06-25 15:06:59 <gmaxwell> hah. Okay. Well. So long as you define low to mean finite.
446 2013-06-25 15:07:11 <michagogo> What was the bug?
447 2013-06-25 15:07:53 <thrasher`> no check on TX string length I assume?
448 2013-06-25 15:07:54 <gmaxwell> michagogo: transactions can have extra data stuck onto the end of them. This size is not what the normal fee rules check against, and the transactions get stored in memory.
449 2013-06-25 15:08:32 <jgarzik> back
450 2013-06-25 15:08:37 <jgarzik> how goes the 0.8.3 builds?
451 2013-06-25 15:08:43 <michagogo> Transactions or transaction messages?
452 2013-06-25 15:08:47 <gmaxwell> So someone can exhaust nodes memory by feeding them bloated transactions. There are some complications that make it a little harder to exploit than it sounds.
453 2013-06-25 15:08:49 <michagogo> jgarzik: I seem to match gavin
454 2013-06-25 15:09:23 <michagogo> jgarzik: I've PR'd: https://github.com/bitcoin/gitian.sigs/pull/8
455 2013-06-25 15:09:31 <gmaxwell> michagogo: The messages, not the transactions themselves really. But the data gets relayed.
456 2013-06-25 15:09:38 <jgarzik> gmaxwell, especially now with a few patched nodes deployed
457 2013-06-25 15:09:40 <michagogo> Ah, I see.
458 2013-06-25 15:11:29 <Luke-Jr> 0.8.3 sigs pushed
459 2013-06-25 15:13:24 <Luke-Jr> that makes 3
460 2013-06-25 15:13:43 <upb> ??????
461 2013-06-25 15:15:27 <Scrat> upb: that's debatable
462 2013-06-25 15:16:13 <upb> no it's not!
463 2013-06-25 15:16:40 <handle> ??
464 2013-06-25 15:16:55 <handle> ??????
465 2013-06-25 15:17:11 <handle> i have no idea what i am saying
466 2013-06-25 15:17:13 <Luke-Jr> ACTION wonders if this right-to-left stuff is on-topic
467 2013-06-25 15:17:29 <handle> that's racist :(
468 2013-06-25 15:17:49 <handle> also I just realized this is bitcoin-dev
469 2013-06-25 15:17:50 <handle> my bad
470 2013-06-25 15:17:59 <Luke-Jr> http://luke.dashjr.org/tmp/screenshots/snapshot104.png
471 2013-06-25 15:18:09 <Luke-Jr> ACTION kicks 404
472 2013-06-25 15:18:42 <upb> http://luke.dashjr.org/tmp/screenshots/snapshot103.png <- are those the lightbearing rays of licufer?:P
473 2013-06-25 15:19:04 <Luke-Jr> 404 fixed
474 2013-06-25 15:19:41 <handle> heh, interesting
475 2013-06-25 15:19:44 <upb> what are those blue lines?
476 2013-06-25 15:20:03 <Luke-Jr> upb: markers
477 2013-06-25 15:20:13 <Luke-Jr> "where I've read up to"
478 2013-06-25 15:20:16 <upb> and mine was hzb not just one letter so the client doesnt display it correctly
479 2013-06-25 15:20:22 <upb> ah
480 2013-06-25 15:40:03 <gavinandresen> All righty, binaries uploaded to https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.3/
481 2013-06-25 15:42:23 <imd23> hi people, who is kind enough to give me the best link explanation about how transactions works?
482 2013-06-25 15:42:25 <imd23> thanks
483 2013-06-25 15:43:21 <Luke-Jr> imd23: bitcoin.pdf
484 2013-06-25 15:43:40 <imd23> Luke-Js: didn't work :p
485 2013-06-25 15:43:51 <imd23> Luke-Jr: didn't work :p
486 2013-06-25 15:43:51 <Luke-Jr> imd23: it's linked off bitcoin.org
487 2013-06-25 15:44:09 <imd23> i know, I read it already, I mean, I need a little bit lighter :)
488 2013-06-25 15:44:27 <imd23> but it has been a time I don't read it so I will give it a try again
489 2013-06-25 15:44:39 <imd23> any other link apart of the wiki?
490 2013-06-25 15:44:47 <imd23> a video, a conf talk, a blog post?
491 2013-06-25 15:45:50 <helo> imd23: #bitcoin
492 2013-06-25 15:46:32 <imd23> ok.
493 2013-06-25 15:47:16 <gavinandresen> imd23: try http://omegataupodcast.net/2011/03/59-bitcoin-a-digital-decentralized-currency/
494 2013-06-25 15:47:29 <imd23> thanks
495 2013-06-25 15:49:39 <helo> imd23: what i meant was "i'll be happy to answer any questions you have about how bitcoin transactions work in #bitcoin". not just trying to get you to go away ;)
496 2013-06-25 15:50:10 <imd23> helo: oh ok, :) no prob
497 2013-06-25 15:53:47 <jgarzik> gavinandresen, awesome (0.8.3)
498 2013-06-25 15:55:45 <bloke> is 0.8.3 officially the stable release yet?
499 2013-06-25 15:56:24 <jgarzik> bloke, yes, as of a few minutes ago :) gavinandresen hasn't even gotten to the announce yet ;p
500 2013-06-25 15:57:01 <bloke> all good :)
501 2013-06-25 16:01:20 <gavinandresen> ??? sent email to the bitcoin-development mailing list...
502 2013-06-25 16:02:39 <petertodd> gmaxwell: only nodes with less memory than incoming-bandwidth * 15 minutes are at risk - mostly that's VPS's and similar in practice
503 2013-06-25 16:04:41 <gavinandresen> ??? thread on bitcointalk ??? https://bitcointalk.org/index.php?topic=242848
504 2013-06-25 16:08:16 <saivann> gavinandresen : Will update bitcoin.org in the next minutes
505 2013-06-25 16:10:04 <gavinandresen> saivann: thanks!
506 2013-06-25 16:10:10 <gavinandresen> I updated links on the wiki homepage
507 2013-06-25 16:15:36 <jgarzik> reddit link: http://www.reddit.com/r/Bitcoin/comments/1h1vch/bitcoinqt_bitcoind_version_083_released/