1 2014-09-11 02:50:40 <warren> wumpus: sipa: ping
  2 2014-09-11 08:20:58 <wumpus>  warren: pong?
  3 2014-09-11 08:24:03 <sipa> warren: pang?
  4 2014-09-11 08:31:04 <wumpus> why is markets.blockchain.info connecting to my node every 5 seconds, doing nothing but immediately disconnect again
  5 2014-09-11 08:32:33 <wumpus> I can't think of any reason why this would be useful...
  6 2014-09-11 08:47:47 <arowser> I guess they try to check if your node is online, but 5 seconds is too short.
  7 2014-09-11 08:47:55 <warren> wumpus: sipa: sorry about that, I thought I found a problem in one of the recent patches but gmaxwell corrected me
  8 2014-09-11 08:49:21 <wumpus> arowser: but why would they care if my node is online? and indeed, why with such small granularity?
  9 2014-09-11 08:50:39 <wumpus> anyhow I'll just contact them
 10 2014-09-11 08:51:29 <wumpus> 
ACTION is close to adding a measure to automatically bans nodes that reconnect too fast

 11 2014-09-11 08:51:56 <warren> wumpus: that's easy with iptables
 12 2014-09-11 08:52:14 <warren> iptables can also prevent too many connections from the same IP or subnet
 13 2014-09-11 08:53:45 <wumpus> sure, that'd be possible, but I think hammering a node with repeated connections is misbehavior (and something the real client would never do), even though it's not directly harmful
 14 2014-09-11 08:54:49 <warren> agreed
 15 2014-09-11 09:05:19 <wumpus> ResendWalletTransactions()'s logic is a bit twisted; it looks at, and sorts *all* wallet transactions older than 5 hours, and only just before actually relaying each transaction it checks if the transaction is unconfirmed
 16 2014-09-11 09:06:46 <wumpus> meh, only one of the many things that make the wallet slow with lots of transactions
 17 2014-09-11 09:07:55 <arowser> wumpus: Just guss, and what's the blockchain.info ip, I want try to check it on my node.
 18 2014-09-11 09:08:28 <wumpus> arowser: I gave the hostname, you can easily look up the ip :p
 19 2014-09-11 09:10:37 <arowser> wumpus: The site looks like behind cloudflare CDN, how to get it's realy IP?
 20 2014-09-11 09:11:14 <wumpus> sigh, okay it's 209.105.246.182
 21 2014-09-11 09:11:41 <arowser> wumpus:thanks
 22 2014-09-11 09:18:57 <arowser> wumpus: The ip(209.105.246.182) seems not run a active node, I search the history on three site http://btcnodes.org/search?keyword=209.105.246.182 https://getaddr.bitnodes.io/nodes/?q=209.105.246.182 https://blockchain.info/ip-address/209.105.246.182, but no any result, and I can't find it on my three active node's debug.log, so its just connect your node by tcp, and not send any msg like "ver"?
 23 2014-09-11 09:19:24 <wumpus> it does do the version handshake
 24 2014-09-11 09:21:46 <arowser> so its just a tcp connect, then close it immediately?
 25 2014-09-11 09:26:23 <wumpus> no, it connects, it does sends its version, it receives my version, I send a verack, sometimes even a ping, then it disconnects...
 26 2014-09-11 09:26:59 <wumpus> identifies as /BitCoinJ:0.12SNAPSHOT/Satoshi:0.2.0/: version 70001
 27 2014-09-11 09:27:39 <arowser> wumpus: its wired
 28 2014-09-11 09:27:54 <wumpus> ?
 29 2014-09-11 09:30:07 <arowser> wumpus: my node not received it, it just for you
 30 2014-09-11 09:31:14 <wumpus> I doubt that, but I guess it's a subset
 31 2014-09-11 09:39:08 <wumpus> seeing from the sequence of their source port numbers they're connecting to 150-200 nodes every time
 32 2014-09-11 09:42:32 <wumpus> hah, must have been a software bug, they stopped hammering and open a normal connection dialogue now
 33 2014-09-11 09:59:52 <inian> Hi I have set up a local regtest network and I would like to set up a mining pool as well on my local network to simulate some experiments.
 34 2014-09-11 10:00:29 <inian> any place where I can get started on setting up a private mining pool which my nodes can connect to?
 35 2014-09-11 10:01:28 <wumpus> it may be better to use a testnet-in-a-box setup instead of regtest if you want to simulate a mining pool, as regtest doesn't require mining
 36 2014-09-11 10:02:41 <inian> The testnet-in-a-box is not related to the testnet network right?
 37 2014-09-11 10:03:25 <wumpus> well - it's a testnet, but limited to your own nodes, unlike the regtest network it does have a variable difficulty
 38 2014-09-11 10:03:49 <inian> How do I simulate the mining environment using that?
 39 2014-09-11 10:04:06 <wumpus> make your miners connect to one of the nodes?
 40 2014-09-11 10:04:34 <inian> Sorry, I meant a mining-pool environment
 41 2014-09-11 10:04:37 <inian> not solo mining
 42 2014-09-11 10:05:34 <inian> I looked online and could not find an open-source implementation of a mining pool for bitcoin which is currently being maintained
 43 2014-09-11 10:12:56 <sturles> eloipool?
 44 2014-09-11 10:13:09 <wumpus> not sure one exists; the open source preference is P2Pool
 45 2014-09-11 10:17:01 <inian> @sturles I will try eloipool..thanks!
 46 2014-09-11 10:17:47 <inian> @wumpus yes P2Pool looks cool but I need a centralised mine pool for my simulation!
 47 2014-09-11 12:02:50 <b-itcoinssg> hearn:Hey Mike, really enjoyed your talk on lighthouse and SIGHASH_ANYONECANPAY!
 48 2014-09-11 12:15:03 <hearn> b-itcoinssg: thanks!
 49 2014-09-11 12:18:54 <b-itcoinssg> hearn: no prob. Is there, in your opinion, another promising untapped function of the Bitcoin protocol that holds promise, but don't have the time to work on?
 50 2014-09-11 12:19:08 <hearn> have you read the contracts page?
 51 2014-09-11 12:19:48 <hearn> https://bitcoin.org/en/developer-guide#contracts
 52 2014-09-11 12:21:03 <b-itcoinssg> not in detail, but, will do if you recommend it
 53 2014-09-11 12:26:19 <hearn> b-itcoinssg: it's docs intended for developers about other features. you can do micropayments, multi-party payments, payments conditional on various other things. quite a lot of interesting potential. there's a talk i gave in 2012 about this too.
 54 2014-09-11 12:26:36 <hearn> b-itcoinssg: so if you prefer videos then you could watch that: https://www.youtube.com/watch?v=mD4L7xDNCmA
 55 2014-09-11 12:29:01 <b-itcoinssg> hearn: excellent! That sounds interesting enough to pursue. I've watched that video, but I'm gonna regurgitate again.
 56 2014-09-11 12:30:56 <hearn> oh ok. well if you watched it already ...
 57 2014-09-11 12:31:31 <b-itcoinssg> I'm downloading it, I'm gonna watch it again.
 58 2014-09-11 12:33:42 <b-itcoinssg> If for some reason in the future, the hashing algorithm had to be replaced, e.g. let's say for security purposes. Would the transition be intractable or fairly smooth. I realize the there would have to be some sort of intervention where the network dictates that proof-of-work is now such and such. But would there have to changed made retrospectively, like
 59 2014-09-11 12:33:43 <b-itcoinssg> address generation etc.?
 60 2014-09-11 13:25:55 <wumpus> I intend to tag 0.9.3rc2 soon; anything missing? https://github.com/bitcoin/bitcoin/commits/0.9.3   @theuni any mac-related build/code signing changes that still have to go in?
 61 2014-09-11 13:27:34 <hearn> b-itcoinssg: if sha256 broke unexpectedly it's hard to imagine any workable transition that wasn't chaos. however there is no history of hash functions breaking over night
 62 2014-09-11 13:27:44 <hearn> b-itcoinssg: they tend to get weaker with time. and humanity got better at designing them with time too
 63 2014-09-11 13:27:50 <hearn> sha256 is widely considered to be extremely strong
 64 2014-09-11 13:31:46 <b-itcoinssg> hearn: I couldn't disagree with any of what you just said. Sometimes I like to play devil's advocate just in the spirit of exploring territories in the hopes of making fringes, ex-fringes.
 65 2014-09-11 13:47:08 <jgarzik> Holy shit.  The Bnak of England just emailed me personally.  Drawing my attention to a quarterly bulletin, that discusses digital currencies.
 66 2014-09-11 13:47:10 <jgarzik> *Bank
 67 2014-09-11 13:47:21 <jgarzik> I bet a few other comm members got the same email
 68 2014-09-11 13:49:42 <hearn> i didn't, but i did get an email from a journo asking me what i thought of it
 69 2014-09-11 13:49:45 <hearn> guess i should read it too
 70 2014-09-11 13:51:42 <hearn> jgarzik: this is the bulletin that only mentions bitcoin once?
 71 2014-09-11 13:51:58 <hearn> does not seem very significant
 72 2014-09-11 13:53:29 <jgarzik> http://www.bankofengland.co.uk/publications/Documents/quarterlybulletin/2014/qb14q3digitalcurrenciesbitcoin2.pdf
 73 2014-09-11 13:53:43 <jgarzik> Just started reading.  Still getting over the shock of a direct email from BoE to me.
 74 2014-09-11 13:54:53 <jgarzik> Companion article, "how digital currencies work" http://www.bankofengland.co.uk/publications/Documents/quarterlybulletin/2014/qb14q3digitalcurrenciesbitcoin1.pdf
 75 2014-09-11 13:54:56 <b-itcoinssg> jgarzik: to me that just indicates that they're doing they're due dilligence to contact the experts, isn't that what we hope they would do?
 76 2014-09-11 13:55:36 <jgarzik> b-itcoinssg, ideally
 77 2014-09-11 13:55:43 <jgarzik> b-itcoinssg, it also means bitcoin is growing up
 78 2014-09-11 13:55:53 <b-itcoinssg> :-)
 79 2014-09-11 14:03:07 <hearn> jgarzik: ah ha
 80 2014-09-11 14:03:14 <hearn> jgarzik: well BoE is just an organisation like any other :)
 81 2014-09-11 14:03:56 <hearn> oh i see
 82 2014-09-11 14:25:12 <gavinandresen> jgarzik: BoE emailed me, too. Most interesting piece of spam I’ve received in a while....
 83 2014-09-11 14:25:39 <b-itcoinssg> lol
 84 2014-09-11 14:28:27 <jgarzik> The backgrounder is actually quite good, and goes into bitcoin in some depth.
 85 2014-09-11 14:28:52 <jgarzik> It covers proof-of-work, orphan blocks, and other details.
 86 2014-09-11 14:54:22 <amaclin> does not cover bitcoin risks: centralization, forking...
 87 2014-09-11 15:02:33 <wumpus> would be funny if BoE saw centralization as a risk
 88 2014-09-11 15:05:11 <hearn> wumpus: they do!
 89 2014-09-11 15:05:17 <hearn> they talk about the risk of miner centralisation and monopoly
 90 2014-09-11 15:05:26 <hearn> they have quite a sophisticated analysis and argument about miner economy and fees
 91 2014-09-11 15:05:59 <hearn> although they seemed to suggest they think the hardware arms race will never end. not sure i followed that part.
 92 2014-09-11 15:06:55 <Luke-Jr> hearn: if the price keeps going up, it subsidises more hardware
 93 2014-09-11 15:07:17 <hearn> yeah but their argument was based on that
 94 2014-09-11 15:07:48 <Luke-Jr> was or wasn't?
 95 2014-09-11 15:07:57 <hearn> oops wasn't
 96 2014-09-11 15:10:35 <MiningBuddy> im looking for a proxy type of setup to modify hashrate output to multiple sources, something similar to the 3 way mining you can do in cgminer but need more control if anything like that already exists?
 97 2014-09-11 15:20:23 <ajweiss> i'm not sure if i agree with their choice to plot hashrate against "address count"
 98 2014-09-11 15:21:24 <paveljanik> Do we still need MEMPOOL_GD_VERSION constant?
 99 2014-09-11 15:33:07 <jgarzik> got BoE to fix an error
100 2014-09-11 15:33:29 <jgarzik> They refer to "longest chain of blocks" when it is total PoW
101 2014-09-11 15:39:56 <Luke-Jr> jgarzik: so it's a work-in-progress?
102 2014-09-11 15:40:37 <jgarzik> Luke-Jr, everything is a work in progress :)
103 2014-09-11 15:40:57 <jgarzik> Luke-Jr, It is going to the printers for hardcopy, but the online PDF can still be updated if other errors are found.
104 2014-09-11 15:41:13 <Luke-Jr> i c
105 2014-09-11 15:43:00 <Luke-Jr> bleh, they mislabel stale blocks as "orphaned blocks"
106 2014-09-11 15:44:09 <Luke-Jr> jgarzik: how do you even contact them?
107 2014-09-11 15:45:44 <jgarzik> Luke-Jr, (question just for clarification)   so blocks on a weak chain are officially "stale blocks"?  That is the name people use?
108 2014-09-11 15:46:54 <Luke-Jr> jgarzik: "orphaned blocks" is not a rare misterm, but properly speaking refers to blocks for which no parent block is known; the misuse of "orphaned blocks" seems to come from the orphaned *generation transaction* in bitcoind
109 2014-09-11 15:47:39 <jgarzik> Luke-Jr,  that did not directly address the question...
110 2014-09-11 15:47:56 <Luke-Jr> jgarzik: I'm not aware of any "official" term, but "stale blocks" is common and well-understood
111 2014-09-11 15:55:47 <Luke-Jr> hard to answer a question about "official" when there is no such thing ;)
112 2014-09-11 16:00:06 <JackH> jgarzik:
113 2014-09-11 19:33:32 <kdomanski> sipa: AFK or present?
114 2014-09-11 20:09:35 <robertjw> I had an 'out of disk space' event yesterday and after clearing the space issue and restarting bitcoind I'm now getting "PANIC: fatal region error detected; run recovery" in db.log.  What's the safest way to recover from this?
115 2014-09-11 20:58:34 <Strider_> hello
116 2014-09-11 21:00:39 <Strider_> I am trying to use the blockchain.info RPC API
117 2014-09-11 21:00:46 <Strider_> This is the response I am getting: http://nobanchan.com/btctest/index.php
118 2014-09-11 21:01:16 <Strider_> what did I do wrong? I am using the bitcoin.inc wrapper linked to in thier API documentation, and using the constructor the way they show
119 2014-09-11 21:02:49 <Strider_> since you're all away, i will be lurking
120 2014-09-11 21:11:17 <michagogo> robertjw: what version of bitcoind, on what system?
121 2014-09-11 21:11:28 <Strider_> ..
122 2014-09-11 21:11:48 <robertjw> bitcoin-0.9.1 on Fedora 20
123 2014-09-11 21:12:24 <robertjw> it looks like wallet.dat is corrupted, and my best alternative might be to regenerate it somehow
124 2014-09-11 21:13:00 <michagogo> robertjw: hm. Db.log would suggest it's the wallet, yeah.
125 2014-09-11 21:13:10 <michagogo> Do you have backups?
126 2014-09-11 21:13:10 <robertjw> I have recorded my private key, and am now looking for a way to inject that private key into a freshly generated wallet.dat
127 2014-09-11 21:13:36 <helo> robertjw: did you ever send any transactions, or only receive to a single address?
128 2014-09-11 21:13:41 <michagogo> robertjw: unless you've only ever received once and never sent, there is more than one private key
129 2014-09-11 21:14:06 <robertjw> I have received multiple times, but never sent
130 2014-09-11 21:14:15 <michagogo> robertjw: first thing, back up what you have now ASAP
131 2014-09-11 21:14:22 <robertjw> already done
132 2014-09-11 21:14:37 <michagogo> Do you have pre-corruption backups?
133 2014-09-11 21:14:43 <robertjw> no
134 2014-09-11 21:15:02 <michagogo> Do you have the privkey for each address you received to?
135 2014-09-11 21:16:13 <robertjw> I have recorded one private key (when wallet.dat was first generated) and I have a record of all public keys which were used to receive
136 2014-09-11 21:16:32 <michagogo> robertjw: each address has it's own private key
137 2014-09-11 21:16:38 <robertjw> dang
138 2014-09-11 21:16:45 <michagogo> You need the key for each and every address you received to
139 2014-09-11 21:17:16 <michagogo> Unfortunately, I know nothing about BDB and I can't give you any advice on recovering your wallet
140 2014-09-11 21:17:31 <michagogo> (Or any idea whether it's even possible)
141 2014-09-11 21:17:46 <mr_burdell> Strider_: I think your password is in plaintext
142 2014-09-11 21:18:01 <Strider_> it is in plaintext,
143 2014-09-11 21:18:05 <robertjw> Then I'm stuck.  I'm looking at the source now to see if I might be able to manually hexedit the file to find the keys
144 2014-09-11 21:18:12 <Strider_> the API docs show me to do it as follows:
145 2014-09-11 21:18:38 <mr_burdell> wallet id and password encoded with base64?
146 2014-09-11 21:18:53 <Strider_> 
147 2014-09-11 21:18:53 <Strider_> 
148 2014-09-11 21:18:53 <Strider_> 
149 2014-09-11 21:18:53 <Strider_> 
150 2014-09-11 21:18:53 <Strider_> 
151 2014-09-11 21:18:53 <Strider_> 
152 2014-09-11 21:18:53 <Strider_> function getConnection() {
153 2014-09-11 21:18:54 <Strider_> 
154 2014-09-11 21:18:54 <Strider_> 
155 2014-09-11 21:18:55 <Strider_> 
156 2014-09-11 21:18:55 <Strider_> 
157 2014-09-11 21:18:56 <Strider_> }
158 2014-09-11 21:19:02 <Strider_> this is what I thought i was supposed to do
159 2014-09-11 21:19:12 <mr_burdell> well, I hope you don't have funds in that wallet
160 2014-09-11 21:19:25 <robertjw> 0.8 BTC
161 2014-09-11 21:19:45 <robertjw> Enough for me to spend some time to sort this out
162 2014-09-11 21:20:03 <Apocalyptic> why don't people backup wallets is beyond me...
163 2014-09-11 21:20:18 <Strider_> then from there, you take your connection to perform the methods from the BitcoinClient object. ex: $btc->getinfo();
164 2014-09-11 21:20:32 <Strider_> but, as you see, the getinfo() method is giving me that garbage response
165 2014-09-11 21:22:30 <mr_burdell> looks like it's encoded as gzip and then it decodes it as "page ok"
166 2014-09-11 21:23:11 <Strider_> um,
167 2014-09-11 21:23:16 <Strider_> lol i see that, i just have no idea why
168 2014-09-11 21:23:20 <Strider_> i mean, im using the stock stuff
169 2014-09-11 21:23:36 <michagogo> Strider_: do you have any funds in that wallet?
170 2014-09-11 21:23:51 <phantomcircuit> Strider_, whatever you're doing
171 2014-09-11 21:23:51 <robertjw> 0.8 BTC
172 2014-09-11 21:23:53 <phantomcircuit> stahp
173 2014-09-11 21:23:58 <Strider_> no sir. this is brand new stuff.
174 2014-09-11 21:24:07 <michagogo> The http log you posted includes the wallet identifier and password in base64
175 2014-09-11 21:24:09 <Strider_> zero finds.
176 2014-09-11 21:24:21 <michagogo> You'll want to change wallets immediately.
177 2014-09-11 21:24:29 <phantomcircuit> michagogo, plz2notencourage
178 2014-09-11 21:24:41 <Strider_> ill change it, but since theres nothing in it i might as well sort the problem out first
179 2014-09-11 21:24:48 <michagogo> phantomcircuit: hm? There are no funds.
180 2014-09-11 21:25:49 <phantomcircuit> michagogo, this is wildly offtopic
181 2014-09-11 21:39:00 <Strider_> Yeah. no idea what the problem is.