1 2013-12-09 00:23:01 <TYDIRocks> Hey gmaxwell, you there?
  2 2013-12-09 00:23:55 <gmaxwell> TYDIRocks: maybe but your problems can be answered by people other than me!
  3 2013-12-09 00:24:12 <gmaxwell> 
ACTION is reminded as to why you don't feed stray cats :)

  4 2013-12-09 00:24:20 <TYDIRocks> gmaxwell, haha true sorry
  5 2013-12-09 00:25:20 <TYDIRocks> To anyone, it seems that I have around .4-.5 BTC missing from blockchain.info than on the wallet on my machine (I imported keys to blockchain). I'mn 8 weeks behind currently while syncing, but once I am synced up what should I do? Should I send all my coins to 1 address in the wallet?
  6 2013-12-09 00:25:57 <gmaxwell> TYDIRocks: yes that would probably fix that, by consolidating whatever keys bc.i isn't aware of.
  7 2013-12-09 00:26:26 <TYDIRocks> Okay thank you. This is awesome to know I have a hidden stash of this amount of btc! :D
  8 2013-12-09 00:27:23 <Luke-Jr> TYDIRocks: you probably shouldn't be messing with ECDSA keys
  9 2013-12-09 00:27:43 <omniden> TYDIRocks: Might be worth reading https://en.bitcoin.it/wiki/Change if you're not familiar with change addresses and how they will result in different balances reported on blockchain.info vs in your wallet.
 10 2013-12-09 00:27:44 <TYDIRocks> Luke-Jr, what do you mean?
 11 2013-12-09 00:27:51 <gmaxwell> Luke-Jr: he imported a bitcoin-qt wallet into bc.i and it sounds like it didn't get all the keys.
 12 2013-12-09 00:28:09 <Luke-Jr> gmaxwell: does bc.i have a B-Qt wallet importer?
 13 2013-12-09 00:28:14 <gmaxwell> Luke-Jr: it does.
 14 2013-12-09 00:28:18 <Luke-Jr> weird
 15 2013-12-09 00:28:21 <gmaxwell> Luke-Jr: its server side.
 16 2013-12-09 00:28:27 <Luke-Jr> lol >_<
 17 2013-12-09 00:28:36 <gmaxwell> Luke-Jr: of course, it doesn't tell users that…
 18 2013-12-09 00:29:03 <Luke-Jr> we really need some kind of certification for sane wallet implementations
 19 2013-12-09 00:29:11 <Luke-Jr> (which sadly would have to exclude Electrum now)
 20 2013-12-09 00:29:48 <TYDIRocks> omniden, oh right I remember reading how it does that, that completely slipped my mind that may have happened. Pretty sure I imported my wallet while it was having problems though, so I would think bc.i would put thos addresses with my login if it used it. Guess not
 21 2013-12-09 00:31:17 <hno> TYDIRocks, and you really needed to reuse your old addresses instead of just sending a transaction with all coins to the new wallet?
 22 2013-12-09 00:31:41 <TYDIRocks> hnc, who said anything about a new wallet?
 23 2013-12-09 00:31:46 <TYDIRocks> hnc, same wallet, 2 locations
 24 2013-12-09 00:31:50 <Luke-Jr> TYDIRocks: that won't work
 25 2013-12-09 00:32:03 <Luke-Jr> TYDIRocks: Bitcoin-Qt is always revising its wallet file
 26 2013-12-09 00:32:15 <Luke-Jr> it cannot be shared
 27 2013-12-09 00:32:32 <TYDIRocks> Okay fine sorry, same private keys, different wallets
 28 2013-12-09 00:32:36 <TYDIRocks> right?
 29 2013-12-09 00:32:38 <Luke-Jr> no
 30 2013-12-09 00:32:44 <Luke-Jr> don't mess with ECDSA keys.
 31 2013-12-09 00:32:48 <Luke-Jr> that's wallet internals
 32 2013-12-09 00:32:55 <hno> TYDIRocks, see link omniden sent you above..
 33 2013-12-09 00:33:01 <TYDIRocks> I am
 34 2013-12-09 00:33:40 <Luke-Jr> messing with ECDSA keys directly is asking to lose bitcoins
 35 2013-12-09 00:34:10 <hno> Bottom line, blockchain.info wallet != your qt wallet. Different wallets, now both claim to have some of the same coins.
 36 2013-12-09 00:34:26 <Luke-Jr> hno: will the fixed firmware be out soon, or do I really need to figure out a workaround to put in BFGMiner long-term?
 37 2013-12-09 00:34:47 <Luke-Jr> hno: re i2c issue in KnCMiner units
 38 2013-12-09 00:35:17 <TYDIRocks> Okay I see now. Question though. Since I've only used the blockchain.info, would that mean there could be coins on bc.i that I don't have in my bitcoin-qt?
 39 2013-12-09 00:35:29 <Luke-Jr> TYDIRocks: could be
 40 2013-12-09 00:35:39 <hno> Luke-Jr, good question. Have been on another project for most of last week. The workaround (as I told you before) is to delay a little bit between i2c transactions.
 41 2013-12-09 00:35:57 <gmaxwell> TYDIRocks: yea, if you've been running your wallet in multiple places you can end up like that..
 42 2013-12-09 00:36:05 <Luke-Jr> hno: right, I just don't want to put it in the mainline codebase if it's going to be fixed in a week
 43 2013-12-09 00:36:05 <TYDIRocks> Interesting. So would the best way to go about this is make a new wallet and send the funds of both wallets to that new wallet?
 44 2013-12-09 00:36:32 <gmaxwell> where there are coins in each not in the other. The way to fix that is to go to one, send all it can see to another wallet. then wait until it confirms and both wallets see it, and if there is any coin left over in the other wallet, them move it.
 45 2013-12-09 00:36:33 <Luke-Jr> TYDIRocks: probably the safest
 46 2013-12-09 00:36:40 <hno> Luke-Jr, understood. I'll discuss the matter with the rest of the team tomorrow.
 47 2013-12-09 00:37:10 <TYDIRocks> Hmm, not sure if I want to do what gmaxwell said or just make a fresh wallet
 48 2013-12-09 00:37:32 <TYDIRocks> I think I'll just make a fresh wallet
 49 2013-12-09 00:37:47 <hno> TYDIRocks, doesn't matter really. If you empty one wallet into another both updates..
 50 2013-12-09 00:37:51 <TYDIRocks> Probably the safest in case my blockchain somehow gets comprimised
 51 2013-12-09 00:38:20 <TYDIRocks> hmc, I meant security wise but yeah
 52 2013-12-09 00:38:45 <Belxjander> Luke-Jr: how about a reference wallet implimentation as a library?
 53 2013-12-09 00:38:47 <hno> TYDIRocks, all keys that had any value should get spent by that transaction.
 54 2013-12-09 00:39:01 <Luke-Jr> Belxjander: doesn't exist at this time, afaik
 55 2013-12-09 00:39:11 <gmaxwell> the reason to use a third wallet for the cleanup is to get yourself into a totally non-mixed up state.
 56 2013-12-09 00:39:44 <hno> agreed.
 57 2013-12-09 00:40:19 <TYDIRocks> yes I think that's best haha
 58 2013-12-09 00:41:09 <hno> just don't delete any of the wallets.. archive them somewhere when done.
 59 2013-12-09 00:41:45 <Belxjander> 
ACTION has "mirrored" two wallets into each other

 60 2013-12-09 00:41:54 <TYDIRocks> Yeah. So would the best course of action be copy my current wallet, delete it in the dir so a new one is made, get that public address, copy that and put the old one in to send the coins?
 61 2013-12-09 00:42:56 <hno> I think there is a bitcoin-qt command line flag for specifying wallet, but not sure it actually works..
 62 2013-12-09 00:43:14 <Luke-Jr> hno: it's not in any release
 63 2013-12-09 00:43:35 <hno> Luke-Jr, only in master?
 64 2013-12-09 00:43:40 <Luke-Jr> right
 65 2013-12-09 00:50:40 <TYDIRocks> So should I do my idea then?
 66 2013-12-09 00:57:16 <hno> TYDIRocks, yes, and after transaction confirmed also from the blockchain wallet.
 67 2013-12-09 00:57:34 <hno> just make sure you have it backed up proper first.
 68 2013-12-09 00:57:43 <TYDIRocks> Yup will do, thanks for the help
 69 2013-12-09 01:20:10 <sunspotbtc> yay, for the first time, bitcoind completed and I've now got an active node running - 15G space consumed by the database, logging, etc.
 70 2013-12-09 01:20:56 <sunspotbtc> just thought I'd share success since you guys probaly get a lot more failure reports :)
 71 2013-12-09 01:21:15 <gmaxwell> sunspotbtc: indeed! thanks!
 72 2013-12-09 01:24:07 <gmaxwell> sipa: a mental note for future wallet formats:  ISTM that when we do a "Backup" we should be exporting in a slightly different form where all the data is actually encrypted.  E.g. by having all the wallet data encrypted, with a seperate key for the 'public data' which is stored in the operating wallet, and when you do a backup it just omits that key in the backup.
 73 2013-12-09 01:24:29 <warren> wumpus: ping
 74 2013-12-09 01:24:31 <gmaxwell> (and when you load such a wallet it first converts it to the operating form by asking for the encryption key to decrypt the operating key)
 75 2013-12-09 01:27:23 <hno> gmaxwell, what do you mean by "a seperate key for the 'public data' which is stored in the operating walle"t?
 76 2013-12-09 01:27:28 <Belxjander> gmaxwell: to me it all reads as "WalletID, "rootkey", crtypto-block(public key section), cryptoblock(opt-privkey-set)
 77 2013-12-09 01:28:13 <Belxjander> where rootkey is a generator input to apply with a user-entered password for any crypto logic
 78 2013-12-09 01:28:34 <Belxjander> WalletID being the "UserID for the wallet converned
 79 2013-12-09 01:29:00 <gmaxwell> Belxjander: that general kind of thing.
 80 2013-12-09 01:30:25 <gmaxwell> hno: I'm finding myself repeating the same words. Current bitcoin-qt wallets do not encrypt the "public data", public keys transaction metadata, etc— for good reason: if its encrypted you'd have to type the encryption key at startup and keep it in memory constantly... which is not compatible with minimizing the risk of exposure of the key.
 81 2013-12-09 01:30:44 <hno> yes, I am well aware of this.
 82 2013-12-09 01:30:46 <gmaxwell> hno: I'm suggesting that while this is a good tradeoff for operating wallets, it's not a necessary one for backups.
 83 2013-12-09 01:31:04 <hno> agreed so far.
 84 2013-12-09 01:31:29 <gmaxwell> So if, instead, the public data was also encrypted, but the key for that encryption was kept on the node (perhaps even in a seperate file) but also in the wallet encrypted with the wallet passphrase, then that key could be omitted in backups.
 85 2013-12-09 01:31:44 <gmaxwell> so when you restore a backup you'd need to provide the spending key— but just once.
 86 2013-12-09 01:32:45 <hno> Ok, so the operating key is stored twice in both encrypted and plan form, but only envrypted form backed up.
 87 2013-12-09 01:33:18 <hno> makes sense.
 88 2013-12-09 01:34:24 <hno> make it the default wallet.dat format even, with operating key in bitcoin.conf or similar.
 89 2013-12-09 01:34:32 <hno> the plain copy.
 90 2013-12-09 01:35:24 <hno> or better a separate file. bitcoin.conf also have backup value.
 91 2013-12-09 01:39:14 <gmaxwell> hno: yea, we can't do this in wallet.dat today... but in a future format we should.
 92 2013-12-09 02:07:49 <amiller> ugh, even pynode really wants to keep a whole blockchain for itself
 93 2013-12-09 02:08:10 <amiller> i wish i had an easy way to get different nodes on my machine to share the same storage
 94 2013-12-09 02:25:19 <amiller> well, now i think i should make an SPV mode variant of pynode
 95 2013-12-09 02:25:48 <nsh> i think i should make brownies
 96 2013-12-09 03:14:06 <maaku> amiller: switch to a shared database?
 97 2013-12-09 03:47:15 <copumpkin> tcatm: you around?
 98 2013-12-09 03:53:32 <Eneerge> any of you good with batch? If you're taking a reference variable into a function, is there anyway to read the value of that variable within the function after it's been set. EG: set %~1=whatever .... how would I access %~1% while still inside of the function? ..... set %~1=whatever & echo %~1 <--- only echos out the name of the variable. I tried %~1% and %%~1%, etc
 99 2013-12-09 03:53:58 <andytoshi> just use cygwin :}
100 2013-12-09 03:55:54 <clan_> hi, i wrote some code to create transactions. but i am not sure if the transaction is valid. how can i do the testing? or can i post the raw transaction here?
101 2013-12-09 04:00:17 <phantomcircuit> clan_, decoderawtransactions
102 2013-12-09 04:00:19 <phantomcircuit> clan_, decoderawtransaction
103 2013-12-09 04:12:26 <clan_> is there any bitcoind rpc server for testnet?
104 2013-12-09 04:15:49 <gribble> jgarzik was last seen in #bitcoin-dev 3 days, 12 hours, 35 minutes, and 46 seconds ago: <jgarzik> http://www.reddit.com/r/Bitcoin/comments/1s5hzl/my_human_translation_of_the_china_regulation/
105 2013-12-09 04:15:49 <phantomcircuit> ;;seen jgarzik
106 2013-12-09 04:40:40 <weex> is anyone aware of an abe that's running for bitcoin right now?
107 2013-12-09 04:50:03 <lechuga> abe?
108 2013-12-09 04:50:37 <weex> https://github.com/bitcoin-abe/bitcoin-abe it's "a block explorer"
109 2013-12-09 04:51:03 <weex> has this stat called % Coin Days Destroyed that I'm fond of
110 2013-12-09 04:51:23 <weex> guess it's back to the spreadsheet to calc that
111 2013-12-09 05:17:00 <BlueMattBot> Project Bitcoin build #499: FAILURE in 42 min: http://jenkins.bluematt.me/job/Bitcoin/499/
112 2013-12-09 05:22:29 <phantomcircuit> BlueMatt, looks like a jenkins failure rather than a real build failure
113 2013-12-09 05:22:37 <phantomcircuit> make[2]: *** [check-local] Killed
114 2013-12-09 06:23:41 <amiller> jaldskjf i take it no one is using pynode for much of anything
115 2013-12-09 06:23:57 <amiller> it seems to crash around block 218000, but i fixed it.
116 2013-12-09 06:30:11 <Plarkplark_> What is an estimate what a full normal (public ip) 8333 node generates a month?
117 2013-12-09 06:30:19 <Plarkplark_> (traffic)
118 2013-12-09 06:43:26 <Plarkplark_> also: If running a node on private addr. space - is port-forwarding 8333 enough for it to participate as a full node?
119 2013-12-09 07:28:13 <maaku> Plarkplark_: yes
120 2013-12-09 07:32:19 <go1111111> im trying to build bitcoin-qt for the first time. when i run 'configure', should everything be a 'yes'? I get several 'no's such as "checking for the pthreads library -lpthreads... no"
121 2013-12-09 07:37:49 <wumpus> go1111111: most "no"'s are not a problem and simply worked around. it's just "measuring" your system to build an bitcoin executable for it
122 2013-12-09 07:38:20 <wumpus> if there is a problem is will give a warning of even error out
123 2013-12-09 07:38:47 <go1111111> cool, thanks.
124 2013-12-09 07:45:27 <Plarkplark_> Version 80500 getting InvalidChainFound a lot and getinfo is stuck on "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
125 2013-12-09 07:45:48 <Plarkplark_> stuck on block 128969
126 2013-12-09 07:47:53 <Plarkplark_> debian wheezy, precompiled 64 bit bins.
127 2013-12-09 07:48:08 <Plarkplark_> did a -par=1 no help
128 2013-12-09 08:14:40 <Plarkplark_> exit
129 2013-12-09 08:14:46 <selocc> hello, im looking for a way to see all the IPs participiating in the bitcoin network
130 2013-12-09 08:15:07 <selocc> it seems that it was possible through addr.dat but now that is obsolete is there a new way
131 2013-12-09 08:18:51 <BlueMattBot> Project Bitcoin build #500: FIXED in 44 min: http://jenkins.bluematt.me/job/Bitcoin/500/
132 2013-12-09 08:18:51 <BlueMattBot> Yippie, build fixed!
133 2013-12-09 08:47:35 <maaku> selocc: peers.dat
134 2013-12-09 08:47:40 <maaku> it's still there
135 2013-12-09 08:47:55 <maaku> you may also be interested in the dns seeder
136 2013-12-09 08:48:07 <selocc> what tools should I use in order to read it
137 2013-12-09 08:49:16 <maaku> you'll have to write your own
138 2013-12-09 08:50:42 <selocc> alright. I guess Ill be looking into dns seeder thanks a bunch
139 2013-12-09 08:52:07 <ThomasZ> how does one build bitcoin on Windows since the qmake buildsystem removal from master?
140 2013-12-09 08:52:49 <sipa> the same as other platforms
141 2013-12-09 08:53:00 <ThomasZ> other platforms don't have visual studio ;)
142 2013-12-09 08:53:21 <sipa> bitcoin built in visual studio? :o
143 2013-12-09 08:53:46 <sipa> autogen.sh && ./configure && make
144 2013-12-09 08:53:59 <ThomasZ> we are talking about Windows...
145 2013-12-09 08:54:01 <lclc> I think on Windows it's called nmake?
146 2013-12-09 08:54:05 <ThomasZ> those are unix tools
147 2013-12-09 08:54:08 <sipa> in msys