1 2014-03-19 00:15:25 <BlueMatt> michagogo|cloud: its not released yet?
2 2014-03-19 00:39:14 <ripper234> Hello guys,
3 2014-03-19 00:39:28 <ripper234> I need a bitcoind expert for an urgent security matter
4 2014-03-19 00:39:40 <ripper234> bitcoind rpc to be exact
5 2014-03-19 00:40:13 <ripper234> Would appreciate your help ... I'm on Skype with the same nick.
6 2014-03-19 00:40:36 <ripper234> Connecting to this IRC via webchat, so I won't see/hear notifications unless I have the tab open.
7 2014-03-19 00:42:05 <gmaxwell> The nature of your issue is a bit vague.
8 2014-03-19 00:43:17 <gmaxwell> If you believe there is a security related software in the bitcoin protocol or a popular implementation please email bitcoin-security@lists.sourceforge.net or if its very serious send gpg encrypted email to the developers of the application in question.
9 2014-03-19 00:49:51 <amiller> jgarzik, your seed node has been displaying the same 15 ip addresses for basically the last week if not longer
10 2014-03-19 00:50:12 <amiller> $ host bitseed.xf2.or
11 2014-03-19 00:50:16 <amiller> g
12 2014-03-19 00:51:44 <gmaxwell> thats what it does, thats also why its last in the list.
13 2014-03-19 00:52:06 <amiller> oh.
14 2014-03-19 00:52:39 <amiller> okay carry on then. i thought it used to behave differently
15 2014-03-19 00:52:43 <amiller> thanks
16 2014-03-19 00:53:39 <ripper234> Let me clarify:
17 2014-03-19 00:53:43 <ripper234> This is not a problem with Bitcoin at all.
18 2014-03-19 00:53:55 <ripper234> It is a problem with a specific Mastercoin wallet, and the way it uses bitcoind.
19 2014-03-19 00:54:12 <ripper234> We have it figured out, I just need a quick pair of eyes to review a commit.
20 2014-03-19 00:54:16 <Luke-Jr> amiller: that particular seed is a DNS server with a static list
21 2014-03-19 00:54:40 <ripper234> I know Mastercoin isn't popular in some circles.
22 2014-03-19 00:55:01 <amiller> Luke-Jr, iirc it used to be a DNS server with a much larger static text file it sampled randomly from
23 2014-03-19 00:55:11 <amiller> Luke-Jr, which is a lot different than showing exactly the same 15 all the time
24 2014-03-19 00:55:46 <ripper234> But we're all crypto-geeks ultimately working for the same goals, and I believe we should help each others.
25 2014-03-19 00:55:51 <ripper234> So I'll stop trolling here.
26 2014-03-19 00:56:25 <ripper234> Just wanted to explain the situation, and politely ask that if someone does have a spare 10 minutes, they contact me (gtalk / email at ron.gross@gmail.com or preferably skype)
27 2014-03-19 00:56:28 <ripper234> Thanks!
28 2014-03-19 00:59:02 <Diablo-D3> gmaxwell: http://www.acm.org/news/featured/awards/turing-award-2013
29 2014-03-19 01:02:48 <Luke-Jr> ripper234: usually we consider non-bitcoin stuff off-topic here even if we are glad to help in other channels/forums
30 2014-03-19 01:02:57 <Luke-Jr> just fwiw
31 2014-03-19 01:08:06 <melik> hi everyone; can anyone tell me what is wrong with this tx: e411dbebd2f7d64dafeef9b14b5c59ec60c36779d43f850e5e347abee1e1a455
32 2014-03-19 01:36:34 <jgarzik> amiller, I replied to that days ago; I guess the reply got lost
33 2014-03-19 01:36:39 <jgarzik> amiller, It is a static list
34 2014-03-19 01:37:03 <jgarzik> though it sounds like dnspark finally got dynamic DNS API, so I should revisit that
35 2014-03-19 01:37:39 <jgarzik> ACTION is not opposed to dynamic lists -- just did not want to reuse the same seeder code and algorithm as everyone else, and the same single-system setup as everyone else. This is at least DDoS protected.
36 2014-03-19 01:37:50 <jgarzik> Though it is fair to question the value of DDoS-protected stale data ;p
37 2014-03-19 01:39:00 <amiller> jgarzik, even a static list doesn't have to be only 15 elements i don't think
38 2014-03-19 01:39:09 <amiller> other seeds return more results
39 2014-03-19 01:39:28 <jgarzik> amiller, yes. Trade-offs are unavoidable when using someone else's system
40 2014-03-19 01:39:39 <amiller> ok :)
41 2014-03-19 01:39:47 <amiller> and sorry for asking again, i def. didn't see hte reply earlier
42 2014-03-19 01:40:00 <jgarzik> amiller, hopefully their dynamic API either (a) permits more entries or at least (b) permits frequent updates
43 2014-03-19 02:51:47 <miseria> "nada es facil, caemos en cosas que no entendemos, nos golpean, parecen imposibles pero hay que incistir hasta lograr el opjetivo" bienvenidos: http://castroruben.com *temo_a_un_ser_sin_rival*
44 2014-03-19 03:18:35 <Ghaleon_> importprivkey it only takes a private key and adds it to the wallet. but how do you add it to the wallet address? how do you even know what the amount it?
45 2014-03-19 03:19:47 <Ghaleon_> so we need the amount that was added by importpriv key
46 2014-03-19 03:19:58 <Ghaleon_> is there anyway to get this? from the privacy itself? sips format?
47 2014-03-19 03:20:09 <Luke-Jr> Ghaleon_: you shouldn't be using importprivkey
48 2014-03-19 03:20:38 <Ghaleon_> ok, but how do we allow our wallet users to use arms? the arms give them private keys to scan right?
49 2014-03-19 03:20:50 <Luke-Jr> arms?
50 2014-03-19 03:21:12 <Luke-Jr> uh, if you're importing a private key someone has given you, consider your wallet compromised..
51 2014-03-19 03:21:19 <Ghaleon_> ATM's
52 2014-03-19 03:21:30 <Luke-Jr> no, they shouldn't be anyhow
53 2014-03-19 03:21:35 <Luke-Jr> any ATM that gives you a private key is broken
54 2014-03-19 03:21:56 <Luke-Jr> you display a payment address to the ATM and it sends you bitcoins..
55 2014-03-19 03:22:40 <Ghaleon_> ahh ok
56 2014-03-19 03:23:11 <Luke-Jr> it's safe to *sweep* a private key, but Bitcoin Core does not support that at all yet
57 2014-03-19 03:31:39 <etotheipi_> gpg: Signature made Mon 09 Dec 2013 04:14:17 PM EST using RSA key ID 7BF6E212; gpg: Can't check signature: public key not found
58 2014-03-19 03:32:02 <etotheipi_> *whose
59 2014-03-19 03:32:02 <etotheipi_> who's public key is that?
60 2014-03-19 03:32:32 <etotheipi_> that's on the SHA256SUMS.asc file on the bitcoin.org download page
61 2014-03-19 03:46:50 <pigeons> etotheipi_: gavin's code signing key
62 2014-03-19 03:47:24 <etotheipi_> I have a different key for gavin
63 2014-03-19 03:47:31 <etotheipi_> did he change it?
64 2014-03-19 03:48:55 <pigeons> dunno, the signatures on 7BF6E212 look good to me
65 2014-03-19 04:28:29 <etotheipi_> did gavin really make two new 1024-bit PGP keys at the beginning of this year?
66 2014-03-19 04:28:44 <etotheipi_> seems suspicious
67 2014-03-19 04:31:23 <fload> Is python-jsonrpc the best way for a beginner to start playing with transactions? I am looking at using it in conjunction with blockchains api...
68 2014-03-19 05:02:53 <richcollins> Is there a Bitcoin script repl that I can use to test scripts?
69 2014-03-19 05:04:06 <richcollins> want to check a scriptsig
70 2014-03-19 05:04:55 <Luke-Jr> not really
71 2014-03-19 05:06:02 <richcollins> I'm using bitcoinj -- I suppose there is probably a way to execute a script using it
72 2014-03-19 05:06:28 <richcollins> Luke-Jr: Have you heard of any tools that make it easy to debug a scriptSig?
73 2014-03-19 05:07:01 <richcollins> or a transaction as a whole?
74 2014-03-19 05:07:11 <Luke-Jr> no
75 2014-03-19 05:07:12 <richcollins> Testnet doesn't appear to be relaying my tx
76 2014-03-19 05:07:26 <richcollins> and peers disconnect when I send it so I guess I'm doing something wrong
77 2014-03-19 05:44:47 <michagogo> cloud|BlueMatt: it's tagged, though, and for the Ubuntu PPA you don't use the gbuilt release binaries...
78 2014-03-19 06:19:55 <petertodd> etotheipi_: anyone can make a key...
79 2014-03-19 06:35:12 <Rawdawg> anyone here interested in doing a bit of security work?
80 2014-03-19 06:35:34 <Rawdawg> just attempting to poke holes in a site then telling me what to do to fix said holes
81 2014-03-19 06:38:40 <kadoban> Rawdawg: maybe. you paying?
82 2014-03-19 06:39:09 <Rawdawg> depends on how much something like that is worth
83 2014-03-19 06:39:37 <Rawdawg> if its too much i can wait till tomorrow when my freind that does it for a living comes back online :P
84 2014-03-19 06:39:52 <Rawdawg> but if you would be interested in doing it for say, 500 digitalcoins?
85 2014-03-19 06:40:02 <Rawdawg> I could swing that
86 2014-03-19 06:40:26 <kadoban> i have no idea what that is...bitcoins seem more appropriate? i'll take less than 500 ;)
87 2014-03-19 06:40:57 <Rawdawg> hahaha i would hope so :P
88 2014-03-19 06:47:45 <venzen> Rawdawg: i'll do it for half of whatever kadoban asks - but then again, my security knowedge is only half as good as his ;)
89 2014-03-19 06:47:58 <Rawdawg> haha
90 2014-03-19 06:47:59 <kadoban> ;)
91 2014-03-19 06:48:13 <Rawdawg> well i can only afford 500 dgc at this point
92 2014-03-19 06:48:21 <Rawdawg> which is about 0.04 btc
93 2014-03-19 06:49:59 <venzen> only joking - i have enough on my plate today...
94 2014-03-19 06:50:15 <Rawdawg> lol its cool
95 2014-03-19 06:50:29 <Rawdawg> i have a freind thats gonna do it
96 2014-03-19 06:54:29 <disident> Hello small question, how do people to do to fix the first 3 characters of their addresses ?
97 2014-03-19 06:54:57 <paveljanik> disident: google for vanitygen
98 2014-03-19 06:55:03 <maxplm> I'm no dev but I have not found a conclusive answer: with a 2-of-2 P2SH TX, would it be possible to create and store the 2 key pairs on 2 devices, exchange pub keys, create 2-of-2 address and fund it, then craft a TX on 1st device, send half-signed TX to 2nd device, sign and broadcast?
99 2014-03-19 06:55:06 <disident> paveljanik: cheers
100 2014-03-19 06:55:22 <disident> paveljanik: could it be done on the server side ?
101 2014-03-19 06:55:57 <paveljanik> sure
102 2014-03-19 06:56:05 <disident> that won't be to slow ?
103 2014-03-19 06:56:26 <paveljanik> first 3 chars: no.
104 2014-03-19 06:57:14 <paveljanik> opencl:/tmp/1/vanitygen # time ./oclvanitygen 123
105 2014-03-19 06:57:15 <paveljanik> Address: 1235SRWiU7hw4UStCxJCDk6hNPW769RKoG
106 2014-03-19 06:57:15 <paveljanik> Difficulty: 1353
107 2014-03-19 06:57:15 <paveljanik> Pattern: 123
108 2014-03-19 06:57:15 <paveljanik> WARNING: Built with OpenSSL 0.9.8j-fips 07 Jan 2009
109 2014-03-19 06:57:15 <paveljanik> WARNING: Use OpenSSL 1.0.0d+ for best performance
110 2014-03-19 06:57:17 <paveljanik> Privkey: 5JMRyeTPUJd4ERJicmcKTpuyoX6p7qxeATJ4bbhu4azkuYCqmdP
111 2014-03-19 06:57:19 <paveljanik> real
112 2014-03-19 06:57:21 <paveljanik> user
113 2014-03-19 06:57:23 <paveljanik> sys
114 2014-03-19 06:57:25 <paveljanik> opencl:/tmp/1/vanitygen #
115 2014-03-19 06:57:54 <paveljanik> but well, this is better discuss in #bitcoin as this is not related to Bitcoin Core.
116 2014-03-19 06:58:40 <disident> :)
117 2014-03-19 06:58:55 <disident> thank you
118 2014-03-19 06:59:06 <maxplm> to add to my question: in my head it seems as if this would make it possible for securely storing bitcoin, with no device holding all necessary keys at the same time
119 2014-03-19 07:02:24 <Luke-Jr> maxplm: yes
120 2014-03-19 07:02:30 <Luke-Jr> maxplm: that's why P2SH was created
121 2014-03-19 07:02:49 <Luke-Jr> maxplm: now the trick is to remember you can only use an address once.. so you need to throw HD wallets into the loop ;)
122 2014-03-19 07:03:51 <draradech> {
123 2014-03-19 07:03:51 <draradech> }
124 2014-03-19 07:03:51 <draradech> gsens_offset_min = 12;
125 2014-03-19 07:03:51 <draradech> if(Abs_dummy34 == 0)
126 2014-03-19 07:04:03 <draradech> arf, sorry
127 2014-03-19 07:05:35 <Luke-Jr> unnecessary braces are annoying
128 2014-03-19 07:06:24 <draradech> goto fail?
129 2014-03-19 07:11:44 <maxplm> Luke-Jr: thank you! yeah of course throw in HD and a 3rd key pair for backup.
130 2014-03-19 07:53:35 <michagogo> cloud|9:02:39 <Luke-Jr> maxplm: that's why P2SH was created
131 2014-03-19 07:53:55 <michagogo> cloud|..actually, that's why checkmultisig was created
132 2014-03-19 07:54:53 <michagogo> cloud|P2SH was created to allow software to use addresses to pay to arbitrary scripts without knowing or caring what they are
133 2014-03-19 10:23:08 <xdotcommer> Would best practice be to check RPC for incoming transactions / confirmations for thousands of wallets or to store blockchain locally and analyze it?
134 2014-03-19 10:23:52 <xdotcommer> Neither seems very elegant
135 2014-03-19 10:42:02 <SamsonOnian> https://pay.reddit.com/r/Bitcoin/comments/20spyb/bitcoin_core_version_090_is_ready_featuring_the/
136 2014-03-19 11:38:18 <topynate> meta: bitcoinstats' parsing is broken. all of michagogo|cloud's messages are read as having 'michago' as the username and 'cloud|' as part of the message
137 2014-03-19 11:39:10 <michagogo> cloud|topynate: Yeah, I've noticed that
138 2014-03-19 11:39:23 <michagogo> cloud|A couple other bots have broken on my |, too :-P
139 2014-03-19 12:05:28 <tiago> michagogo|cloud, hey, I got the make-clean-vm to work but now when I try to compile anything I get "Checking if target is up" for a while and then it crashes with "ssh: connect to host localhost port 2223: Connection refused".
140 2014-03-19 12:06:07 <michagogo> cloud|tiago: did you export USE_LXC=1?
141 2014-03-19 12:06:14 <michagogo> cloud|It shouldn't be using SSH
142 2014-03-19 12:07:02 <tiago> heh, I didn't. thanks
143 2014-03-19 12:07:16 <michagogo> cloud|tiago: Didn't it warn you that kvm isn't loaded?
144 2014-03-19 12:07:29 <tiago> nope
145 2014-03-19 12:07:41 <michagogo> cloud|Interesting
146 2014-03-19 12:18:31 <tiago> michagogo|cloud, sorry to bother you so much with this, but now... http://pastebin.com/raw.php?i=iRvk7U2K
147 2014-03-19 12:19:02 <michagogo> cloud|qcow2?
148 2014-03-19 12:19:06 <michagogo> cloud|LXC doesn't use qcow2
149 2014-03-19 12:19:26 <tiago> that's what it created
150 2014-03-19 12:19:31 <tiago> make-basevm
151 2014-03-19 12:19:35 <michagogo> cloud|Can you give me an `ls` of your gitian-builder dir?
152 2014-03-19 12:19:40 <tiago> *make-base-vm
153 2014-03-19 12:20:13 <lawlll> why is git so popular these days?
154 2014-03-19 12:20:19 <lawlll> what wrong with good old cvs?
155 2014-03-19 12:20:32 <tiago> base-precise-amd64 base-precise-i386 bin COPYING etc libexec README.md share target-precise-i386.qcow2 var
156 2014-03-19 12:20:32 <tiago> base-precise-amd64.qcow2 base-precise-i386.qcow2 build doc inputs LICENSE result target-bin Vagrantfile
157 2014-03-19 12:20:50 <michagogo> cloud|Here's what happens: make-base-vm creates base-suite-arch.qcow2, which is the KVM machine, and then extracts it for LXC, creating another file called base-suite-arch
158 2014-03-19 12:21:20 <tiago> yep, it's there
159 2014-03-19 12:21:22 <michagogo> cloud|tiago: delete target-precise-i386.qcow2
160 2014-03-19 12:21:28 <michagogo> cloud|make sure that USE_LXC=1
161 2014-03-19 12:21:37 <michagogo> cloud|and then try a gbuild
162 2014-03-19 12:21:41 <tiago> ok
163 2014-03-19 12:24:34 <tiago> http://pastebin.com/raw.php?i=qD5U7PzR
164 2014-03-19 12:24:56 <michagogo> cloud|Oh, that
165 2014-03-19 12:25:10 <michagogo> cloud|See the bottom of gitian-builder's readme
166 2014-03-19 12:25:37 <michagogo> cloud|(I forgot about that because I just put those two commands in whatever the file is that gets run on boot)
167 2014-03-19 12:26:06 <michagogo> cloud|(/etc/init.d, I think)
168 2014-03-19 12:26:21 <michagogo> cloud|(or maybe rc.local, actually)
169 2014-03-19 12:26:46 <tiago> oh
170 2014-03-19 12:26:50 <michagogo> cloud|Yeah, I just put `brctl addbr br0` and `ifconfig br0 10.0.2.2/24 up` in rc.local
171 2014-03-19 12:28:08 <xdotcommer> Is best way way to use bitcoind walletnotify/listtransactions to watch 100K+ addresses for incoming transactions and confirmations or to use parse blockchain into db and then use it
172 2014-03-19 12:29:06 <tiago> there we go! thanks michagogo|cloud
173 2014-03-19 12:29:15 <michagogo> cloud|Great :-)
174 2014-03-19 12:29:22 <michagogo> cloud|You're welcome.
175 2014-03-19 12:55:18 <michagogo> cloud|...so yeah, someone leaked the 0.9.0 downloads on reddit :-(
176 2014-03-19 12:55:29 <michagogo> cloud|I hope it wasn't my fault... :-/
177 2014-03-19 12:56:51 <gavinandresen_> nah, it is my fault for uploading the binaries before we had 3 gitian signers.
178 2014-03-19 12:57:14 <gavinandresen_> But we have three now, so all is good.
179 2014-03-19 12:57:23 <venzen> michagogo|cloud: what, the fact that they've been tagged on Git?
180 2014-03-19 12:57:35 <michagogo> cloud|venzen: No, the binaries
181 2014-03-19 12:57:59 <venzen> tsk tsk, anything to get votes on Reddit, eh?
182 2014-03-19 12:58:26 <hearn> fireworks! parties! 0.9 is out! :)
183 2014-03-19 12:58:36 <michagogo> cloud|venzen: see logs from 19:45 UTC last night
184 2014-03-19 12:58:58 <venzen> michagogo|cloud: i'll check em :)
185 2014-03-19 13:00:07 <venzen> gavinandresen_: i guess a new release is newsworthy, but isn't this a TAG ?
186 2014-03-19 13:00:27 <michagogo> cloud|venzen: Hmm? v0.9.0 was tagged, and then we did builds
187 2014-03-19 13:01:16 <aschildbach_> Question about gitian, is there a script that automatically matches all checksums from the bitcoin-build.assert files and verifies the GPG signatures?
188 2014-03-19 13:01:26 <michagogo> cloud|aschildbach_: I think so
189 2014-03-19 13:01:33 <michagogo> cloud|ACTION isn't sure where it is, though
190 2014-03-19 13:01:49 <aschildbach_> I think so, too (-:
191 2014-03-19 13:02:05 <michagogo> cloud|BTW, the Windows setup release binary won't match the gitian sigs
192 2014-03-19 13:02:21 <aschildbach_> why?
193 2014-03-19 13:02:44 <michagogo> cloud|Because gavinandresen_ codesigns it
194 2014-03-19 13:03:18 <warren> so you can only verify it after it's installed =)
195 2014-03-19 13:03:28 <michagogo> cloud|So when users run it, it shows up as being published by "The Bitcoin Foundation Inc."
196 2014-03-19 13:03:52 <aschildbach_> I see. Why do I even try to reproduce the Windows build (its in the instructions)?
197 2014-03-19 13:04:03 <gavinandresen_> I think theoretically you could extract the bitcoin-qt.exe from the setup.exe and make sure its checksum matches the gitian-built .exe ...
198 2014-03-19 13:04:18 <michagogo> cloud|gavinandresen_: Yeah, you can
199 2014-03-19 13:04:34 <michagogo> cloud|aschildbach_: The only files affected are the installers
200 2014-03-19 13:04:46 <gavinandresen_> But also, theoretically, the setup.exe could do something malicious and not actually install that .exe
201 2014-03-19 13:04:50 <aschildbach_> Ok, anyway. Where is the check script? gavinandresen_, do you know?
202 2014-03-19 13:04:59 <gavinandresen_> check script?
203 2014-03-19 13:05:11 <michagogo> cloud|The binaries in the .zip are still verifyable, as are the binaries within the setup.exe
204 2014-03-19 13:05:20 <michagogo> cloud|Which you could take apart, I believe
205 2014-03-19 13:05:26 <michagogo> cloud|aschildbach_: https://github.com/devrandom/gitian-builder/blob/master/bin/gverify might be it
206 2014-03-19 13:05:27 <aschildbach_> Yeah. "Question about gitian, is there a script that automatically matches all checksums from the bitcoin-build.assert files and verifies the GPG signatures?"
207 2014-03-19 13:06:00 <jouke> michagogo|cloud: could you guide me trough a gitian setup?
208 2014-03-19 13:06:08 <gavinandresen_> yes, the gitian gverify. Or there is contrib/verifysvbinaries in our source tree (which needs to be updated since we're moving away from sourceforge)
209 2014-03-19 13:06:11 <jouke> (again)
210 2014-03-19 13:06:14 <michagogo> cloud|jouke: What's your host system?
211 2014-03-19 13:06:22 <gavinandresen_> err contrib/verifysfbinaries
212 2014-03-19 13:06:31 <jouke> michagogo|cloud: ubuntu
213 2014-03-19 13:06:48 <michagogo> cloud|Is it Ubuntu 64-bit, running on a machine with hardware virtualization?
214 2014-03-19 13:06:53 <tiago> why does gitian require apache?
215 2014-03-19 13:07:44 <jouke> 64bit and yes
216 2014-03-19 13:08:07 <michagogo> cloud|jouke: Great, so you can build in KVM
217 2014-03-19 13:08:26 <michagogo> cloud|jouke: make a directory for the while gitian thing
218 2014-03-19 13:08:48 <michagogo> cloud|In there, you'll want to clone https://github.com/bitcoin/bitcoin and https://github.com/devrandom/gitian-builder
219 2014-03-19 13:09:28 <tiago> michagogo|cloud, is there any advantage to kvm over lxc?
220 2014-03-19 13:09:31 <michagogo> cloud|Also, if you want to submit gitian signatures for Bitcoin Core, fork https://github.com/bitcoin/gitian.sigs and clone your fork in that directory
221 2014-03-19 13:09:49 <michagogo> cloud|tiago: In general, I've found it tends to work more smoothly
222 2014-03-19 13:10:01 <tiago> I see
223 2014-03-19 13:10:52 <michagogo> cloud|jouke: Then, follow the readme file in the gitian-builder repo
224 2014-03-19 13:11:14 <michagogo> cloud|But when you run the two make-base-vm commands, add "--suite precise" to each of them
225 2014-03-19 13:11:50 <michagogo> cloud|Once gitian is working and the sanity check section of the gitian readme works, follow doc/release-process.md in the bitcoin source tree
226 2014-03-19 13:12:03 <michagogo> cloud|If you have any problems, just ask in here
227 2014-03-19 13:14:43 <aschildbach_> michagogo: what's your keyid?
228 2014-03-19 13:15:09 <michagogo> cloud|gavinandresen_: gverify and the verifysfbinaries do two different things, though
229 2014-03-19 13:15:37 <michagogo> cloud|aschildbach_: it's in the bitcoin repo
230 2014-03-19 13:15:49 <michagogo> cloud|In contrib/gitian-downloaded
231 2014-03-19 13:16:02 <michagogo> cloud|s/d$/r/
232 2014-03-19 13:16:10 <jouke> do I nead apache?
233 2014-03-19 13:16:51 <michagogo> cloud|jouke: I don't actually know exactly why it calls for that in the doc or what it uses it got
234 2014-03-19 13:16:55 <michagogo> cloud|For*
235 2014-03-19 13:17:32 <michagogo> cloud|Maybe you need it, maybe not -- if you want you could try leaving it out, and seeing if it works
236 2014-03-19 13:17:58 <aschildbach_> michagogo|cloud: how is it called? I see a few keys there, but not yours.
237 2014-03-19 13:18:05 <michagogo> cloud|But if it's listed as a requirement, I'd guess it's probably a requirement
238 2014-03-19 13:18:15 <michagogo> cloud|aschildbach_: oh, really?
239 2014-03-19 13:18:28 <gavinandresen_> michagogo|cloud jouke : my memory if fuzzy, but it might be you need apt-cacher + apache + squid to save re-downloading packages again and again when you're using gitian
240 2014-03-19 13:18:46 <michagogo> cloud|I'll take a look
241 2014-03-19 13:18:47 <aschildbach_> I'm looking in the bitcoin.org root directory.
242 2014-03-19 13:18:57 <michagogo> cloud|aschildbach_: oh, no, not there
243 2014-03-19 13:19:06 <michagogo> cloud|In the bitcoin git repo
244 2014-03-19 13:19:22 <michagogo> cloud|contrib/gitian-downloader
245 2014-03-19 13:19:56 <michagogo> cloud|gavinandresen_: I know that's what apt-cacher does, but where does Apache come in?
246 2014-03-19 13:19:59 <aschildbach_> Ah I see. Should I put my key there, too?
247 2014-03-19 13:20:23 <skinnkavaj> Isn't gavinandresen supposed to announce this https://bitcointalk.org/index.php?topic=522014 ?
248 2014-03-19 13:22:24 <wumpus> skinnkavaj: he usually does, although I announced 0.8.6
249 2014-03-19 13:22:32 <gavinandresen_> skinnkavaj: I'm happy to delegate the announcement to .. whoever ...
250 2014-03-19 13:22:36 <wumpus> skinnkavaj: in any case it's genuine
251 2014-03-19 13:22:58 <gavinandresen_> And I'd rather people not blindly trust announcements just because they look like they come from me
252 2014-03-19 13:23:45 <wumpus> though generally the announcements for releases are in Bitcoin Discussion, not Development
253 2014-03-19 13:24:12 <gavinandresen_> wumpus: I'm going to post an announcement to bitcoin-development
254 2014-03-19 13:24:24 <michagogo> cloud|Has the site been updated yet?
255 2014-03-19 13:24:43 <wumpus> I'll ask the mods to move it and sticky it
256 2014-03-19 13:24:46 <gavinandresen_> michagogo|cloud: bitcoin.org ? Not yet, want to submit a pull request?
257 2014-03-19 13:25:16 <michagogo> cloud|gavinandresen_: I will if nobody else has when I get back to my computer
258 2014-03-19 13:25:34 <michagogo> cloud|Once that's done, the channel topics should also be updates
259 2014-03-19 13:25:38 <jouke> michagogo|cloud: is make-base-vm supposed to take a while?
260 2014-03-19 13:25:44 <michagogo> cloud|Yes
261 2014-03-19 13:26:06 <michagogo> cloud|You're installing Ubuntu onto a new VM
262 2014-03-19 13:26:39 <jouke> maybe I shold have actually read the script :x
263 2014-03-19 13:27:08 <gavinandresen_> wumpus: Do you think I should upload binaries to sourceforge also, or just put a README there that says "Go to bitcoin.org/bin to get binaries" ?
264 2014-03-19 13:27:50 <michagogo> cloud|gavinandresen_: personally I'd say the latter, except that rc3 is there
265 2014-03-19 13:27:57 <wumpus> gavinandresen_: I'm divided on that... on one hand, having the download available on all sourceforge's mirrors increases availability
266 2014-03-19 13:28:10 <wumpus> gavinandresen_: on the other hand, it'd be nice to stop using sourceforge
267 2014-03-19 13:28:13 <michagogo> cloud|And also what wumpus said
268 2014-03-19 13:28:24 <jgarzik> doh :(
269 2014-03-19 13:28:26 <wumpus> gavinandresen_: and michagogo|cloud has a good point
270 2014-03-19 13:28:31 <jgarzik> Missed the window for an OP_RETURN release note :(
271 2014-03-19 13:28:32 <jouke> ah, looking at the script you need a webserver to host the packages, as it includes a local apt-mirror
272 2014-03-19 13:28:39 <jgarzik> ACTION kicks himself
273 2014-03-19 13:28:45 <wumpus> jgarzik: doh
274 2014-03-19 13:28:49 <michagogo> cloud|jouke: ah, that'll do it
275 2014-03-19 13:29:15 <jgarzik> gavinandresen_, having binaries in multiple places is annoying
276 2014-03-19 13:29:19 <jgarzik> gavinandresen_, just deprecate SF
277 2014-03-19 13:29:59 <michagogo> cloud|Does bitcoin.org have mirrors, btw?
278 2014-03-19 13:30:20 <wumpus> michagogo|cloud: nope
279 2014-03-19 13:30:37 <wumpus> though it's trivial to create one (just clone the github)
280 2014-03-19 13:30:44 <tiago> why isn't github used for the binary hosting, instead of sourceforge?
281 2014-03-19 13:31:03 <wumpus> tiago: seems sourceforge won't be used for binary hosting anymore
282 2014-03-19 13:31:12 <michagogo> cloud| Github hasn't always done binary hosting
283 2014-03-19 13:31:19 <tiago> I know, but it does now
284 2014-03-19 13:31:35 <wumpus> now a dedicated server will be used for it
285 2014-03-19 13:31:53 <venzen> tiago: i don't think Github has the minerals to handle the traffic - and Sourceforge is the traditional repo with the mirrors...
286 2014-03-19 13:32:04 <michagogo> cloud|Well, I guess the decision was made to switch to bitcoin.org before the decision was made to switch to Github Releases
287 2014-03-19 13:33:18 <venzen> i'm reading the forum announcement at https://bitcointalk.org/index.php?topic=522014 and it says 0.9 is a RC for a major version... is this correct or is that remnant wording referring to rc3?
288 2014-03-19 13:33:30 <michagogo> cloud|Remnant
289 2014-03-19 13:33:39 <venzen> ok
290 2014-03-19 13:34:02 <venzen> tx, michagogo|cloud
291 2014-03-19 13:34:08 <michagogo> cloud|No
292 2014-03-19 13:34:12 <michagogo> cloud|Np*
293 2014-03-19 13:34:12 <wumpus> where do you see that?
294 2014-03-19 13:34:40 <wumpus> ah I see it now
295 2014-03-19 13:34:49 <wumpus> that was just copy/pasted I suppose :)
296 2014-03-19 13:35:40 <michagogo> cloud|ACTION wonders if anyone remembered to take the RC out of doc/r-n.md before the tag
297 2014-03-19 13:35:51 <wumpus> of course not michagogo|cloud
298 2014-03-19 13:36:03 <michagogo> cloud|:-/
299 2014-03-19 13:36:42 <jgarzik> venzen, That's what happens when someone else takes it upon themselves to post the release announcement without talking to anybody
300 2014-03-19 13:36:48 <wumpus> from the experience I'm not really convinced that git is a good place to maintain (pre-final) release notes
301 2014-03-19 13:37:08 <michagogo> cloud|wumpus: yeah, same here
302 2014-03-19 13:37:26 <wumpus> though I don't know a good alternative either
303 2014-03-19 13:37:58 <wumpus> jgarzik: nah, final was already tagged with that release announcement in it
304 2014-03-19 13:38:23 <gavinandresen_> jgarzik: RE: OP_RETURN release note: easy to update the README.txt at the download siteâ¦.
305 2014-03-19 13:39:00 <gavinandresen_> (I'm not OCD enough to care that the README.txt with the downloads doesn't match the tagged README.md)
306 2014-03-19 13:39:17 <wumpus> documents have much more 'last minute change' potential than code
307 2014-03-19 13:40:07 <gavinandresen_> mmm. after-the-last-minute changes sometimes, too. Which is fine with me.
308 2014-03-19 13:40:09 <wumpus> me neither, especially in case of minor, trivial mistakes
309 2014-03-19 13:41:10 <venzen> jgarzik: lucky it's a minor wording issue, but these things can end in tears, so communication and process should be honored, hey? who is user: rme by the way? anyone here? or someone who is sanctioned to make such an announcement?
310 2014-03-19 13:41:42 <michagogo> cloud|Idk
311 2014-03-19 13:41:58 <michagogo> cloud|But the reddit announcement also came from someone random
312 2014-03-19 13:42:02 <wumpus> lol, 'sanctioned'
313 2014-03-19 13:42:03 <jgarzik> venzen, Answering your questions in order: hey! don't know. no. no.
314 2014-03-19 13:42:16 <michagogo> cloud|(In fact, a new account...)
315 2014-03-19 13:42:27 <wumpus> venzen: everyone does what they can to help, I suppose, there is nothing sanctioned or official
316 2014-03-19 13:43:56 <venzen> wumpus: understood... and that's great but communications are critical - a loose tongue can do much harm
317 2014-03-19 13:44:12 <venzen> anyhoo - no biggie
318 2014-03-19 13:44:49 <gavinandresen_> https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.9.0/ is just a README.txt And default download for SourceForge is just that README.txt (wouldn't be surprised if that breaks something somewhere, but that's OK)
319 2014-03-19 13:45:12 <wumpus> venzen: that's always the risk in a distributed project, though it shouldn't be able to do much harm: don't just believe everything you read, and if someone posts a fake release it's signalled and deleted soon enough
320 2014-03-19 13:45:55 <gavinandresen_> venzen: If you'd like to Officially Sanction things, you can be the Official Sanction Official.
321 2014-03-19 13:46:00 <wumpus> hehe
322 2014-03-19 13:46:31 <gavinandresen_> ACTION has some issues with Authority
323 2014-03-19 13:47:22 <michagogo> cloud|gavinandresen_: did you remove rc3 from sf?
324 2014-03-19 13:47:39 <gavinandresen_> michagogo|cloud: yes, deleted the test/ directory
325 2014-03-19 13:47:50 <michagogo> cloud|Okay, cool
326 2014-03-19 13:47:52 <venzen> wumpus: true what you say. i think most people are aware that i write articles, so for me it's always about considering whether a piece of information is news - or tattle-tale - or sensation, and it's respect for this workgroup that requires that information going out is sanctioned
327 2014-03-19 13:48:02 <wumpus> Authority creates centralized risk
328 2014-03-19 13:48:22 <venzen> wumpus: but sure - controlling information distribution and leaks is impossible
329 2014-03-19 13:48:38 <venzen> indeed
330 2014-03-19 13:48:49 <michagogo> cloud|On a semirelated note: it's awesome to see so many new gbuilders
331 2014-03-19 13:48:52 <wumpus> venzen: especially if you're trying to be more open
332 2014-03-19 13:49:03 <wumpus> michagogo|cloud: yes! that's very nice
333 2014-03-19 13:49:13 <michagogo> cloud|Or at least people getting help with gbuilding... Hopefully they'll all come through
334 2014-03-19 13:49:47 <Guest62255> I'd be more scared if people posted links to their home made 9.0 bins rather than just bitcoin.org/bin/
335 2014-03-19 13:50:39 <gavinandresen_> wumpus: Jinyoung is asking about writing a blog entry for the 0.9 release⦠can I twist your arm and convince you to do that?
336 2014-03-19 13:50:54 <wumpus> Guest62255: but it shouldn't be the URI that makes it trustworthy, but the fact that it's gitian built thus verified by multiple independent pepole
337 2014-03-19 13:51:04 <wumpus> gavinandresen_: ah yes I still need to do that
338 2014-03-19 13:52:48 <jgarzik> gavinandresen_, wumpus: If wumpus doesn't want to do it, I can take that. If wumpus does it, please let me insert a quick note about OP_RETURN.
339 2014-03-19 13:55:42 <wumpus> jgarzik: well if I do it I'll mostly write about GUI changes, you're welcome to add something about OP_RETURN of course
340 2014-03-19 13:57:10 <venzen> michagogo|cloud: as you mentioned: apt-cacher has its own webserver so I am also interested why the Apache dependecy for gitian?
341 2014-03-19 13:57:31 <wumpus> apache dependency? I don't think that's necessary
342 2014-03-19 13:58:22 <jgarzik> wumpus, tnx
343 2014-03-19 13:58:35 <gavinandresen_> venzen: devrandom is Mr. Gitian, he might know. Or just leave it out and see if anything breaks....
344 2014-03-19 13:58:52 <michagogo> cloud|venzen: I think jouke answered? Read up.
345 2014-03-19 13:59:58 <michagogo> cloud|Hm, it'd be cool if gitian could automatically detect and install dependencies the way RVM does
346 2014-03-19 14:02:15 <venzen> michagogo|cloud: hmm, gavinandresen_ answered (from memory): you need apt-cacher + apache + squid to save re-downloading packages
347 2014-03-19 14:02:49 <venzen> nevermind... i'm not dealing with that issue now anyway...
348 2014-03-19 14:02:53 <wumpus> so apt-cacher requires apache and squid?
349 2014-03-19 14:03:51 <wumpus> sounds a bit overkill for a local caching store, but heh if it works
350 2014-03-19 14:04:47 <michagogo> cloud|wumpus: venzen: read what jouke said
351 2014-03-19 14:09:46 <venzen> 20:28 < jouke> ah, looking at the script you need a webserver to host the packages, as it includes a local apt-mirror
352 2014-03-19 14:11:23 <venzen> michagogo|cloud: you mean that? I'm still weirded out, because apt-cacher does that with little effort :)
353 2014-03-19 14:11:34 <michagogo> cloud|venzen: like I said, idk
354 2014-03-19 14:12:59 <venzen> hehe, let's leave it for another day, because i don't want to know at the moment... :)
355 2014-03-19 14:13:26 <jgarzik> wumpus, will have that OP_RETURN bit written in ~15 min, after current meeting ends
356 2014-03-19 14:14:52 <michagogo> cloud|But I don't think squid is used anywhere in gitian, as far as I can tell
357 2014-03-19 14:21:32 <gavinandresen_> saivann: I committed bitcoin.org/_releases/2014-03-19-v0.9.0.md --- keeping my fingers crossed I didn't accidently break bitcoin.org ....
358 2014-03-19 14:34:16 <sturles> Bitcoin Core is still Bitcoin-Qt on https://bitcoin.org/en/choose-your-wallet and https://bitcoin.org/en/download
359 2014-03-19 14:37:31 <gavinandresen_> sturles: "patches welcome" github.com/bitcoin/bitcoin.org/
360 2014-03-19 14:39:07 <jgarzik> gavinandresen_, wumpus, sipa, gmaxwell: comments, RE OP_RETURN: http://0bin.net/paste/jI07rSW7BrQd9Gpg#f1ntGuNArR6xqTRoxf5kiHrUafx4mWwH8GMXBU16dJw=
361 2014-03-19 14:39:28 <jgarzik> Generally trying to convey a "do that elsewhere" message.
362 2014-03-19 14:39:41 <jgarzik> Comments welcome...
363 2014-03-19 14:39:48 <wumpus> let's see
364 2014-03-19 14:40:26 <wumpus> agreed
365 2014-03-19 14:42:12 <gavinandresen_> jgarzik: "remains an idea to be discouraged" is awfully passive⦠how about "Storing arbitrary data in the blockchain is still a bad idea; it is less costly and far more efficient to store non-currency data elsewhere."
366 2014-03-19 14:42:21 <jgarzik> gavinandresen_, +1
367 2014-03-19 14:42:41 <jgarzik> gavinandresen_, what file in git do I edit, adding this note? I am happy to word it more strongly!
368 2014-03-19 14:42:44 <jgarzik> README.md?
369 2014-03-19 14:42:54 <gavinandresen_> jgarzik: yes, README.md
370 2014-03-19 14:43:10 <gavinandresen_> jgarzik: while you are editing, can you tweak the first paragraph so it doesn't say this is a release candidate ?
371 2014-03-19 14:43:17 <jgarzik> will do
372 2014-03-19 14:43:33 <gavinandresen_> bug fixes."
373 2014-03-19 14:43:33 <gavinandresen_> jgarzik: should just say "This is a new major version that brings both new features and
374 2014-03-19 14:49:16 <BCB> is there a diff for rc9 and 0.9?
375 2014-03-19 14:49:28 <wumpus> is the note about rc2 windows binaries not being signed still in there?
376 2014-03-19 14:49:44 <wumpus> just saw "NOTE: Release candidate 2 Windows binaries are not code-signed" in the forum topic
377 2014-03-19 14:49:52 <jgarzik> gavinandresen_, hum...
378 2014-03-19 14:49:53 <wumpus> to be clear, final binaries *are* signed
379 2014-03-19 14:50:27 <jgarzik> gavinandresen_, are you talking about 0.9.0 branch or master? I only see 0.9.0rc1 string in doc/README.md and then some boring setup instructions.
380 2014-03-19 14:50:40 <jgarzik> gavinandresen_, no first paragraph talking about release candidates?
381 2014-03-19 14:50:56 <jgarzik> and master seems to have a blank release-notes.md
382 2014-03-19 14:50:58 <wumpus> jgarzik: AFAIK he doesn't mean the README.md in the bitcoin repo
383 2014-03-19 14:51:11 <jgarzik> ah ok, on SF
384 2014-03-19 14:51:18 <jgarzik> repo needs a fix too
385 2014-03-19 14:51:21 <wumpus> jgarzik: in git it's in doc/release-notes.md ,but it's too late to change those
386 2014-03-19 14:51:29 <gavinandresen_> jgarzik: start with https://bitcoin.org/bin/0.9.0/README.txt ....
387 2014-03-19 14:52:07 <gavinandresen_> Checking that into the 0.9.0 branch as doc/release_notes.md is probably a good idea. Or master/doc/ ⦠uh, wherever we put previous-release-release-notes....
388 2014-03-19 14:52:08 <wumpus> the bitcoin.org site git
389 2014-03-19 14:52:54 <wumpus> gavinandresen_: right, the final version of the final release notes for 0.9.0 should be added to master/doc/release-notes/*.md... let's wait until we have all last-minute changes in first :)
390 2014-03-19 14:53:21 <wumpus> that's for historical reference
391 2014-03-19 14:53:46 <jgarzik> gavinandresen_, master:doc/release-notes-0.9.0.md
392 2014-03-19 14:54:49 <michagogo> cloud|Are we keeping all the old stuff on SF? Will it be copied/moved over to bitcoin.org/bin, or will that just be for new releases going forward?
393 2014-03-19 14:54:58 <jgarzik> migrating away from SF
394 2014-03-19 14:55:08 <gavinandresen_> jgarzik: ACK. I can upload to bitcoin.org when they're done; I'm working on documenting everything in the dev team's private repository so any of us can do that in the future.
395 2014-03-19 14:55:45 <wumpus> I vote for keeping the old stuff on SF, seems unnecessary to move all the old versions to bitcoin.org as well
396 2014-03-19 14:56:27 <wumpus> woei
397 2014-03-19 14:56:30 <jgarzik> ok
398 2014-03-19 14:57:17 <jgarzik> gavinandresen_, bitcoin.org.git seems to be already updated in _releases/2014-03-19-v0.9.0.md with "this is a new major version"
399 2014-03-19 14:57:36 <jgarzik> gavinandresen_, I don't see a bin/0.9.0/README.txt in the git repo
400 2014-03-19 14:58:03 <michagogo> cloud|Hey, why is choose-your-wallet still using the gold logo for Bitcoin Core? o_O
401 2014-03-19 14:58:10 <gavinandresen_> jgarzik: everything in bin/ is not in the git repo, it is uploaded manually
402 2014-03-19 14:58:26 <gavinandresen_> jgarzik: (using ssh/scp)
403 2014-03-19 14:58:36 <michagogo> cloud|My downloads folder suggests that was phased out with 0.8.2
404 2014-03-19 14:58:45 <jgarzik> gavinandresen_, ahhhh! So I need to get my head completely out of git. Sorry.
405 2014-03-19 14:59:55 <drizztbsd> hi, where is bitcoin-qt.desktop in bitcoin 0.9.0?
406 2014-03-19 15:03:34 <jgarzik> gavinandresen_, wumpus: OK, updated text: http://yyz.us/bitcoin/README.txt
407 2014-03-19 15:03:56 <wumpus> drizztbsd: should be in the same place as before
408 2014-03-19 15:04:01 <drizztbsd> no
409 2014-03-19 15:04:13 <drizztbsd> it was in contrib/debian/bitcoin-qt.desktop
410 2014-03-19 15:04:22 <wumpus> it's still there
411 2014-03-19 15:04:31 <drizztbsd> drizzt@liara bitcoin % find /var/lib/archbuild/extra-x86_64/drizzt/build/bitcoin/src/bitcoin-0.9.0-linux/ -name \*.desktop
412 2014-03-19 15:04:32 <drizztbsd> drizzt@liara bitcoin %
413 2014-03-19 15:04:32 <gavinandresen_> jgarzik: OP_RETURN is pretty obscure, I think that section should come after "Rebranding to Bitcoin Core"
414 2014-03-19 15:04:48 <drizztbsd> wumpus: retry, you will be more lucky
415 2014-03-19 15:05:17 <wumpus> drizztbsd: maybe it doesn't get packaged in the tarball somehow
416 2014-03-19 15:05:21 <wumpus> drizztbsd: why didn't you notice in the rcs?
417 2014-03-19 15:05:29 <jgarzik> gavinandresen_, disagree -- it's been subject of several articles in the press
418 2014-03-19 15:05:42 <drizztbsd> wumpus: why is not packaged anymore? :P
419 2014-03-19 15:05:43 <jgarzik> gavinandresen_, well, "OP_RETURN" is obscure, but the data issue isn't
420 2014-03-19 15:05:59 <wumpus> drizztbsd: no clue
421 2014-03-19 15:06:07 <jgarzik> gavinandresen_, so I really wanted high placement. Feel free to use your own judgement... no objection to further edits.
422 2014-03-19 15:06:48 <wumpus> right, the data issue attracts a lot of flak and trolling, it's good to place it near the top
423 2014-03-19 15:07:30 <drizztbsd> ok, I will package using the git tag for this version
424 2014-03-19 15:07:53 <wumpus> drizztbsd: I suggest creating a github issue for it, along with other files you're missing in the tarball, if any
425 2014-03-19 15:08:12 <wumpus> drizztbsd: if you had checked the rcs then it could have been solved for final
426 2014-03-19 15:09:41 <michagogo> cloud|I'm looking at the source for the download page on the site
427 2014-03-19 15:10:14 <michagogo> cloud|Am I reading correctly that the big download button is always the win32 installer regardless of platform?
428 2014-03-19 15:13:53 <venzen> wumpus jgarzik : as per your good advice not to believe everything one reads, is it correct that the tx fee for network relay has been reduced to 0.01 mBTC ?
429 2014-03-19 15:14:32 <jgarzik> venzen, I respectfully decline to think in mBTC
430 2014-03-19 15:15:01 <venzen> hehe, ok, and the 0.9.0 wallet by default suggests 0.0001 BTC?
431 2014-03-19 15:15:49 <nezZario> 0.00001
432 2014-03-19 15:15:58 <nezZario> i think
433 2014-03-19 15:16:13 <drizztbsd> wumpus: if I fix it do you release a 0.9.1? :P
434 2014-03-19 15:16:28 <devrandom> venzen: not aware of apache dep... where do you see it?
435 2014-03-19 15:16:29 <wumpus> venzen: wallet has not been changed, but relay fee has been cut by 10
436 2014-03-19 15:16:56 <jgarzik> drizztbsd, there will inevitably be a 0.9.1
437 2014-03-19 15:17:07 <nezZario> does anyone keep tabs on #tx/sec ?
438 2014-03-19 15:17:22 <jgarzik> drizztbsd, BTW, standard bug fix policy is upstream-first (master first), unless the fix only applies to 0.9.0 and not to master
439 2014-03-19 15:17:33 <wumpus> drizztbsd: sure :p no problem including build system changes in stable releases
440 2014-03-19 15:18:42 <michagogo> cloud|Looking at https://github.com/bitcoin/bitcoin.org/edit/master/_templates/download.html, am I reading correctly that the big download button is always the win32 installer regardless of platform?
441 2014-03-19 15:19:16 <michagogo> cloud|Oh, nvm -- I see the script at the bottom now
442 2014-03-19 15:21:11 <wumpus> it probably defaults to windows, as most big-green-button-clickers are bound to be windows users :)
443 2014-03-19 15:21:33 <michagogo> cloud|I unfortunately don't know web coding (HTML nor Javascript)... the download page needs to be updated to reflect the fact that we do win32 and win64 builds now
444 2014-03-19 15:23:24 <michagogo> cloud|wumpus: It technically defaults to Windows, but there's a block of javascript at the bottom that looks for Mac and Linux in the useragent and switches the button to either the Mac DMG or... uh... the Ubuntu PPA?
445 2014-03-19 15:23:28 <michagogo> cloud|o_O
446 2014-03-19 15:26:17 <wumpus> hmm for windows it would be good if it suggested the 64-bit version by default and offer the 32-bit one as fallback, at least if it's not possible to determine 32/64 from the user agent, I have no clue :)
447 2014-03-19 15:27:14 <drizztbsd> it should be possibile on major browsers
448 2014-03-19 15:27:50 <michagogo> cloud|My useragent string is Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.154 Safari/537.36
449 2014-03-19 15:27:57 <drizztbsd> "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:25.0) Gecko/20100101 Firefox/25.0" "Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1667.0 Safari/537.36"
450 2014-03-19 15:28:03 <michagogo> cloud|WOW64 is the 64-bit identifier
451 2014-03-19 15:28:13 <drizztbsd> x64
452 2014-03-19 15:28:22 <drizztbsd> for some windows/browsers
453 2014-03-19 15:28:31 <michagogo> cloud|I'd check for either Win64 or WOW64
454 2014-03-19 15:28:54 <Luke-Jr> michagogo|cloud: I think WOW64 is the 32-bit-on-64-bit identifier
455 2014-03-19 15:29:06 <michagogo> cloud|Luke-Jr: Yeah, I think you're right
456 2014-03-19 15:29:16 <drizztbsd> WOW!
457 2014-03-19 15:29:23 <Luke-Jr> drizztbsd: Windows-on-Windows
458 2014-03-19 15:29:28 <Luke-Jr> it's the MS WINE
459 2014-03-19 15:29:36 <drizztbsd> like crap-on-crap
460 2014-03-19 15:30:08 <michagogo> cloud|I think Chrome is only available as 32-bit for Windows atm
461 2014-03-19 15:30:35 <drizztbsd> maybe firefox too
462 2014-03-19 15:31:01 <michagogo> cloud|But yeah, I think what should be done is to add the Windows 64-bit download to the page, change the javascript to detect it
463 2014-03-19 15:31:26 <michagogo> cloud|And also maybe add text to the big download button indicating what it will download...
464 2014-03-19 15:31:52 <michagogo> cloud|Unfortunately I don't have the knowledge to be able to do it, or I'd make the changes and PR
465 2014-03-19 15:32:35 <michagogo> cloud|(also, do we want to stick with the Windows 7 logo, or upgrade to the Windows 8 logo?
466 2014-03-19 15:32:37 <michagogo> cloud|)
467 2014-03-19 15:32:50 <drizztbsd> windows (9)8 logo!
468 2014-03-19 15:33:22 <wumpus> bitcoin for workgroups
469 2014-03-19 15:33:35 <drizztbsd> 16 bit bitcoin release :)
470 2014-03-19 15:39:14 <drizztbsd> should we keed berkeley db for a long time? :)
471 2014-03-19 15:39:16 <drizztbsd> keep*
472 2014-03-19 15:41:17 <wumpus> if so I do suggest that you keep it under low temparature to avoid bitrot
473 2014-03-19 15:44:00 <venzen> wumpus: bitrot sounds awful - sure hope neither i nor my hardware ever contract that..
474 2014-03-19 15:50:54 <topynate> i prefer 1E-5 BTC - saves counting the zeros
475 2014-03-19 15:52:23 <wumpus> counting zeros (before the decimal) is a solved problem by grouping numbers per three in localized number formatting
476 2014-03-19 15:53:34 <jgarzik> wumpus, RE blog post, I'm writing up a very terse list of "what's new" that might be helpful to you. Finished in ~15 in
477 2014-03-19 15:53:36 <jgarzik> *min
478 2014-03-19 15:55:32 <wumpus> ok, I'm a lot slower in that
479 2014-03-19 15:55:37 <venzen> jgarzik: do you mind if i look at that for public dissemination? I've been using the forum notes and they're not accurate in every instance.
480 2014-03-19 15:55:57 <venzen> when you're done of course
481 2014-03-19 15:57:49 <wumpus> jgarzik: it's also fine if you write the generale release blog article, I'm working on a blog post that highlights a few GUI changes (payment requests, rebranding to bitcoin core, new receive workflow, coin control), but this is the first time I'm fighting with Wordpress etc so I'm not sure when it will be finished
482 2014-03-19 15:59:14 <jgarzik> wumpus, I'd be happy to. These notes will help.
483 2014-03-19 16:01:11 <venzen> correction: the Bitcointalk forum thread we looked at before copied the new features from https://bitcoin.org/bin/0.9.0/README.txt, so they are correct
484 2014-03-19 16:19:23 <venzen> however, the document https://bitcoin.org/bin/0.9.0/README.txt still refers to 0.9.0 as an RC in line 5
485 2014-03-19 16:19:34 <jgarzik> gavinandresen, wumpus, sipa, gmaxwell: This is intended as a "highlights of the release" list, not an exhaustive list, to be used as notes when talking with reporters: http://yyz.us/bitcoin/soundbites.txt
486 2014-03-19 16:19:36 <jgarzik> venzen, ^
487 2014-03-19 16:19:43 <jgarzik> venzen, Yes, that doc will get fixed in an hour or so.
488 2014-03-19 16:20:07 <venzen> jgarzik: thanks for the link, i'm checking
489 2014-03-19 16:23:18 <jcorgan> jgarzik: very minor nit, might say "decrease minimum relay fee" instead of "drop minimum relay fee"
490 2014-03-19 16:24:27 <jgarzik> jcorgan, it's notes to myself. I know what I'm talking about ;p
491 2014-03-19 16:24:30 <jgarzik> I hope!
492 2014-03-19 16:24:38 <Imbue> hello; i have found what appears to be an inconsistency in the comments in serialize.h
493 2014-03-19 16:25:42 <Imbue> i think it's a typo but my brain is asleep right now
494 2014-03-19 16:25:54 <Imbue> Very small ... 16512-2113663: 3 bytes
495 2014-03-19 16:25:58 <Imbue> 16511: [0x80 0xFF 0x7F]
496 2014-03-19 16:26:21 <Imbue> this seems incompatible
497 2014-03-19 16:26:26 <sipa> ha!
498 2014-03-19 16:26:44 <Imbue> i am trying to use these values to unit test and.. lol.
499 2014-03-19 16:27:49 <sipa> please do!
500 2014-03-19 16:31:00 <Imbue> i believe the code itself is fine, simply that these 'commented values' are bunk
501 2014-03-19 16:31:14 <Imbue> my cpp knowledge is lacking
502 2014-03-19 16:38:10 <michagogo> cloud|Well, I certainly hope the code itself is fine!
503 2014-03-19 16:38:18 <Imbue> indeed!
504 2014-03-19 16:39:11 <Luke-Jr> at least one known security regression
505 2014-03-19 16:40:27 <michagogo> cloud|jouke, tiago: how's the gitian thing coming along?
506 2014-03-19 16:57:25 <olalonde> is there an RPC command to know how many bitcoin an address "controls" at a given date/block height?
507 2014-03-19 16:58:41 <flammit> short answer: no.
508 2014-03-19 17:00:47 <Luke-Jr> olalonde: addresses don't control bitcoins, ECDSA keypairs and wallets do :P
509 2014-03-19 17:05:02 <olalonde> Luke-Jr: godâ¦
510 2014-03-19 17:05:08 <olalonde> Luke-Jr: you will never give up :P
511 2014-03-19 17:05:40 <Luke-Jr> olalonde: nope, so stop trying to do stupid things? :P
512 2014-03-19 17:06:53 <olalonde> you are welcome to suggest alternatives https://github.com/olalonde/bitcoin-asset-proof/issues :)
513 2014-03-19 17:08:11 <Luke-Jr> what kind of commit message is "uhh" ? :P
514 2014-03-19 17:08:12 <jouke> michagogo|cloud: had to go away for a bit, but it is unable to download the packages from the mirror
515 2014-03-19 17:08:47 <Luke-Jr> "The assets proof is done by signing an identifier with all private keys in a Bitcoin wallet." <-- that's a TON of private keys! :O
516 2014-03-19 17:09:45 <olalonde> Luke-Jr: yes⦠although some exchanges re-use same keys for cold storage⦠the objective would be to support HD wallets so only one signature is required
517 2014-03-19 17:10:01 <Luke-Jr> olalonde: signmessage only proves you *receive* on an address, not that you own or control funds for the pubkey which the address is created from
518 2014-03-19 17:10:13 <gribble> http://xkcd.com/1296/
519 2014-03-19 17:10:13 <michagogo> cloud|Luke-Jr: ,,(google --lucky xkcd commit messages)
520 2014-03-19 17:10:28 <jouke> michagogo|cloud: but the host is running some other webservices as well.
521 2014-03-19 17:10:46 <michagogo> cloud|jouke: What system is the host on?
522 2014-03-19 17:10:53 <Luke-Jr> olalonde: you need to be using ECDSA keys (or HD seeds) and some custom signature format here..
523 2014-03-19 17:10:55 <jouke> ubuntu
524 2014-03-19 17:11:02 <michagogo> cloud|jouke: which version?
525 2014-03-19 17:11:10 <jouke> euh
526 2014-03-19 17:11:19 <Luke-Jr> olalonde: actually, s/ECDSA keys/scriptSigs/; not all assets might be held by a ECDSA signature!