1 2014-04-19 01:57:15 <wallet42> https://blockchain.info/de/tx-index/42766264 wtf output script?
 2 2014-04-19 01:58:42 <owowo> try: https://blockchain.info/en/tx-index/42766264 ;)
 3 2014-04-19 02:00:38 <owowo> what kind of wallet are you using? Bitcoin-qt or blockchain wallet?
 4 2014-04-19 02:01:04 <wallet42> right now?
 5 2014-04-19 02:01:08 <owowo> *blockchain.info
 6 2014-04-19 02:01:27 <owowo> yes, the wallet you made the tx with
 7 2014-04-19 02:01:43 <wallet42> none, im analyzing the blockchain for strange output types
 8 2014-04-19 02:02:20 <owowo> ah, ok, then it could be just a blockchain.info issue
 9 2014-04-19 02:02:51 <wallet42> no its acually a compicated script
10 2014-04-19 02:04:17 <wallet42> OP_DUP OP_HASH160 [0-9a-f]{40} OP_EQUALVERIFY OP_CHECKSIG
11 2014-04-19 02:04:35 <wallet42> is for normal bitcoin addresses
12 2014-04-19 02:04:52 <wallet42> this is quite compicated and it got solved
13 2014-04-19 02:05:12 <saizai> would any of you be interested in commenting on our draft comments on the fec bitcoin AO drafts?
14 2014-04-19 02:05:22 <wallet42> i wonder who put it there, why, and how did it pass isStandardTx()
15 2014-04-19 02:08:38 <maaku> saizai: link?
16 2014-04-19 02:08:49 <saizai> via pm
17 2014-04-19 02:18:57 <saizai> maaku: have you read the draft AOs?
18 2014-04-19 02:19:25 <saizai> http://saos.fec.gov/aodocs/201402.pdf http://saos.fec.gov/aodocs/201402_1.pdf
19 2014-04-19 03:59:16 <saizai> anywho, bbl
20 2014-04-19 06:02:20 <gmaxwell> ::sigh:: https://github.com/bitcoin/bitcoin/issues/4069  "As the file was automatically quarantined and deleted (I can't change SAV default settings), that crashed bitcoind and corrupted the bitcoin DB"
21 2014-04-19 06:21:48 <midnightmagic> :-/
22 2014-04-19 06:22:52 <DiabloD3> midnightmagic: probs?
23 2014-04-19 06:23:08 <DiabloD3> [02:02:28] <gmaxwell> ::sigh:: https://github.com/bitcoin/bitcoin/issues/4069  "As the file was automatically quarantined and deleted (I can't change SAV default settings), that crashed bitcoind and corrupted the bitcoin DB"
24 2014-04-19 06:23:16 <DiabloD3> gmaxwell: yet another reason why to never use windows
25 2014-04-19 06:23:31 <DiabloD3> no other OS has the scamware genre known as anti-viruses
26 2014-04-19 06:24:21 <midnightmagic> DiabloD3: anti-virus morons writing shitty software that assumes their users are complete idiots who just play in Word all day long
27 2014-04-19 06:24:39 <DiabloD3> if they use windows... uh... arent they?
28 2014-04-19 06:35:43 <warren> wumpus: ping
29 2014-04-19 06:37:09 <wumpus> pong
30 2014-04-19 06:38:19 <warren> wumpus: for the roadmap, how many weeks do we want in there now?
31 2014-04-19 06:38:39 <warren> wumpus: and sorry, what was the command to regenerate the english strings again?
32 2014-04-19 06:40:40 <wumpus> warren: see doc/translation-process.md
33 2014-04-19 06:40:59 <wumpus> warren: btw, 0.9.2 macosx builds would also be a good time to start using gitian
34 2014-04-19 06:41:40 <warren> wumpus: I'll try to get that working in nightly builds
35 2014-04-19 06:41:52 <warren> so, weeks?
36 2014-04-19 06:41:57 <wumpus> warren: that would be wonderful
37 2014-04-19 06:42:07 <wumpus> warren: I just woke up, don't ask me difficult questions :p
38 2014-04-19 06:42:27 <warren> wumpus: 1^0?
39 2014-04-19 06:42:54 <wumpus> warren: in any case I'd suggest that we leave at least a month between the moment of announcing 0.9.2 and the planned release
40 2014-04-19 06:43:00 <warren> ok
41 2014-04-19 06:43:36 <wumpus> and let's make some public announcement about those plans today (even if it's just "we plan to do a 0.9.2 from master in a month")
42 2014-04-19 06:44:18 <warren> we have all the prereqs in place now for a detailed announcement
43 2014-04-19 06:44:39 <wumpus> that's fine with me, but it seems to be dragging along, I don't want details of wording the announcement to delay the work :p
44 2014-04-19 06:44:56 <warren> the work would be affected be the announcement?
45 2014-04-19 06:49:51 <Chief_Panda> warren, unless you regulate
46 2014-04-19 06:50:09 <warren> That was odd.
47 2014-04-19 08:01:31 <warren> Could folks please test UPNP with the nightly builds on both Linux and Windows?  It seems to inconsistently work for me depending on which wireless router is used.  Please report Windows or Linux and the model of your wireless router.
48 2014-04-19 08:01:46 <warren> https://bitcointalk.org/index.php?topic=571414
49 2014-04-19 09:58:06 <shesek> I found a cool way to make phishing harder on websites that takes payments from users on a regular basis - embed a unique per-user identicon into the qr code, so that the user can visually verify he got the qr from the right server
50 2014-04-19 10:27:41 <jaakkos> shesek: what if you brute force similar-looking identicons?
51 2014-04-19 11:38:59 <rnicoll> Morning all; trying to sync Bitcoin 0.9 on a new OS install, and I've got it up to about a year ago from bootstrapping old .dat files I had kicking around. However, now it's switched to the network, it keeps stalling, and I see lots of orphan blocks in the debug.log. Restarting client fixes the problem for a while but it does recur. Waiting 10 minutes seems to clear the problem, as if client was restarted, but again
52 2014-04-19 11:38:59 <rnicoll> recurs. Would looking at the DoS code be a reasonable place to start diagnosing this?
53 2014-04-19 11:41:24 <sipa> no
54 2014-04-19 11:42:05 <sipa> the block fetching algorithm is very hacky, and gets easily confused when multiple peers announce blocks
55 2014-04-19 11:42:43 <sipa> it often stalls because of that, more if you are validating slowly
56 2014-04-19 11:42:56 <sipa> and it picks up again when a new block is announced
57 2014-04-19 11:43:34 <rnicoll> great, will see if we can make any improvements there, thanks
58 2014-04-19 11:43:53 <sipa> i've been working on replacing that system for almost a year
59 2014-04-19 11:44:04 <sipa> well, that's not true
60 2014-04-19 11:44:15 <sipa> but we want the client to function in a different way
61 2014-04-19 11:44:35 <sipa> where it first validates headers, and then downloads the blovks
62 2014-04-19 11:44:43 <sipa> instead of everything at once
63 2014-04-19 11:45:06 <rnicoll> 
ACTION nods "I saw the stuff about getting blocks from more than a single node, as well. Is it going to be better to just keep restarting the client and wait for the whole thing to be replaced?"

64 2014-04-19 11:45:49 <sipa> bootstrap.dat avoids this problem
65 2014-04-19 11:46:04 <sipa> as does connecting to just a single fast peer (-connect=ip)
66 2014-04-19 11:46:20 <sipa> also, help with testing patches is always welcome