1 2014-01-09 01:15:26 <netg> /
  2 2014-01-09 01:52:38 <tiyoT> about bitcoin mining, my understanding that the miners basically verifying transactions in the blockchain. when they are done with one block (~10min) they will be rewarded 25 btc by bitcoin protocol.
  3 2014-01-09 01:53:41 <Belxjander> tiyoT: that is true... but it is also based on the fastest hashing "miner" being the "winner" of the BTC "prize"... as only 1 miner is able to "win"
  4 2014-01-09 01:53:47 <tiyoT> 1. when block is discovered, the one who found the block will be rewarded the bitcoin
  5 2014-01-09 01:53:51 <Belxjander> and the "win" is the "longest chain" generated
  6 2014-01-09 01:54:48 <tiyoT> i dont get what does "when the block found" part. because the miners are verifying all the transactions in block A, which block found does it mean?
  7 2014-01-09 02:16:19 <TheLordOfTime> is there a command line option that I can use to speed up indexing the blocks?
  8 2014-01-09 02:16:30 <TheLordOfTime> indexing / downloading*
  9 2014-01-09 02:16:41 <phantomcircuit> TheLordOfTime, download bootstrap.dat using the torrent
 10 2014-01-09 02:16:52 <TheLordOfTime> phantomcircuit: any way to speed up indexing though?
 11 2014-01-09 02:16:55 <shesek> if there was one, why would it be an option and not always turned on?
 12 2014-01-09 02:17:14 <TheLordOfTime> good question, however if there's any secret tricks, I'd be happy to know them :/
 13 2014-01-09 02:17:19 <phantomcircuit> TheLordOfTime, increase -dbcache
 14 2014-01-09 02:17:20 <gmaxwell> TheLordOfTime -dbcache=2000
 15 2014-01-09 02:17:40 <phantomcircuit> although my measurements dont show it making that big of a difference
 16 2014-01-09 02:17:45 <TheLordOfTime> phantomcircuit: gmaxwell: thanks.
 17 2014-01-09 02:18:00 <gmaxwell> and it's not on by default becuause it uses a lot of ram. :P  (well the default is 25... you can see improvements up to perhaps 1000-2000 megs, beyond that nah)
 18 2014-01-09 02:18:02 <phantomcircuit> it only takes about 20 minutes now to reindex
 19 2014-01-09 02:18:02 <shesek> heh, and apparently there's one :)
 20 2014-01-09 02:18:26 <gmaxwell> it's not a huge improvement unless you have a slow disk.
 21 2014-01-09 02:18:48 <phantomcircuit> TheLordOfTime, how much ram do you have total?
 22 2014-01-09 02:19:37 <TheLordOfTime> phantomcircuit: 8GB minus whatever isn't usable, so 7.67 GB RAM
 23 2014-01-09 02:19:49 <TheLordOfTime> plus ~7.5GB swap
 24 2014-01-09 06:04:16 <justanotheruser> Is there a bitcoin script assembler, or do I need to type to opcodes and all that myself?
 25 2014-01-09 06:08:05 <gmaxwell> justanotheruser: the opcode hex takes less typing than the names in all cases. :P
 26 2014-01-09 06:08:07 <justanotheruser> s/do I need to type to opcodes and all that myself/do I need to convert to opcodes to hex myself?
 27 2014-01-09 06:08:11 <gmaxwell> justanotheruser: no assembler that I'm aware of.
 28 2014-01-09 06:08:25 <justanotheruser> *the opcode
 29 2014-01-09 06:08:32 <justanotheruser> wow I'm bad at typing right now
 30 2014-01-09 06:08:42 <gmaxwell> besides, how else will you reconize the opcodes in hex when looking at them unless you type them some. Want my flashcard deck?
 31 2014-01-09 06:08:45 <justanotheruser> gmaxwell: is there a bitcoin scipt tool that is better than bitcoind
 32 2014-01-09 06:08:55 <gmaxwell> no.
 33 2014-01-09 06:09:12 <gmaxwell> (bitcoind has decodescript so at least you can manually inspect your hand-assembly)
 34 2014-01-09 06:09:33 <justanotheruser> gmaxwell: well if there was an assembler I wouldn't have to look at them in hex because I could just open them up in the assembler :P
 35 2014-01-09 06:13:02 <justanotheruser> gmaxwell: what does decode script do? Evaluate it? Turn it into assembly? Something else?
 36 2014-01-09 06:13:13 <uiop> 
ACTION puts script (dis)assembler on his todo-if-have-free-time list

 37 2014-01-09 06:13:59 <justanotheruser> uiop: please let me beta test it if you make it
 38 2014-01-09 06:14:09 <uiop> justanotheruser: will do
 39 2014-01-09 06:16:06 <justanotheruser> I don't see decodescript in https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list
 40 2014-01-09 06:19:58 <warren> anyone have testnet coins?  the faucets seem to be busted now.
 41 2014-01-09 06:20:04 <justanotheruser> warren: address?
 42 2014-01-09 06:21:02 <warren> justanotheruser: mhzEDASM25bAu2HM2JRdeMWq8JsJQnZojv  please.  send a few tx.
 43 2014-01-09 06:21:52 <justanotheruser> warren: please chose 2 values, one the number of tx (1-25), two the sum out the transactions (1-8)
 44 2014-01-09 06:22:45 <warren> justanotheruser: just send anything
 45 2014-01-09 06:23:08 <justanotheruser> okay, I'll send a few tx summing to 2 testcoins
 46 2014-01-09 06:24:43 <justanotheruser> f0ea29ef351610dcd3090d1545f47668ac34e38c070b0caedf0086b2aac721ba 6597db4c7338a0a277c803bd586a8c9ec24ee5ca88cf80fa0d40fb5bb9ce4d97 9713cdec8051b2a71b1faf6558c86c9a16ea1801bac86cc212cee809f976bb29 1f76c2d3504c22053a694a0865336b4a3195ed6b57d48bcc12f74337997c4301
 47 2014-01-09 06:25:31 <warren> justanotheruser: thank you
 48 2014-01-09 06:25:45 <justanotheruser> np
 49 2014-01-09 06:27:12 <gmaxwell> justanotheruser: http://0bin.net/paste/It+bT30JWs-cPx8u#0oAYOHNXLIOhP0Q7zVyRuFSCf8p3GG1G5bBsxr7WtA0=
 50 2014-01-09 06:29:17 <michagogo> cloud|08:08:02 <gmaxwell> justanotheruser: the opcode hex takes less typing than the names in all cases. :P
 51 2014-01-09 06:29:23 <michagogo> cloud|Only if you include OP_
 52 2014-01-09 06:29:31 <justanotheruser> gmaxwell: I am running version 80600 and my bitcoind doensn't have that
 53 2014-01-09 06:29:47 <michagogo> cloud|justanotheruser: yeah, it's in git
 54 2014-01-09 06:29:56 <michagogo> cloud|0.8.6 doesn't have it
 55 2014-01-09 06:30:22 <justanotheruser> michagogo|cloud: well for some opcodes like op_0 it takes less time
 56 2014-01-09 06:30:41 <justanotheruser> but for NUMEQUALVERIFY it takes more time than the hex
 57 2014-01-09 06:31:07 <justanotheruser> michagogo|cloud: is it a 0.8.6 fork, or a different version fork
 58 2014-01-09 06:32:48 <michagogo> cloud|justanotheruser: Git master builds on 0.8.2
 59 2014-01-09 06:32:58 <michagogo> cloud|That's what will be 0.9
 60 2014-01-09 06:33:45 <justanotheruser> michagogo|cloud: Will this be in 0.9 or what does that last statement you made mean?
 61 2014-01-09 06:33:58 <michagogo> cloud|decodescript is in Git master.
 62 2014-01-09 06:34:14 <michagogo> cloud|The last release that git master has in its history is 0.8.2.
 63 2014-01-09 06:34:28 <michagogo> cloud|0.9 will be taken from git master.
 64 2014-01-09 06:34:30 <justanotheruser> michagogo|cloud: does encodescript exist
 65 2014-01-09 06:34:41 <michagogo> cloud|I don't know
 66 2014-01-09 06:34:51 <justanotheruser> Probably not if you didn't make it :)
 67 2014-01-09 06:35:42 <justanotheruser> Any idea on .9 release date?
 68 2014-01-09 06:36:09 <shesek> warren, the testnet faucet on mojocoin moved here: http://faucet.xeno-genesis.com/
 69 2014-01-09 06:37:12 <shesek> it seems to work fine
 70 2014-01-09 06:38:19 <shesek> the one on appspot seems to work too, but has some serious delays until the coins are sent
 71 2014-01-09 06:46:47 <wyager> I'm glad people are finally getting frenetic about pool centralization. I mean, this is like the 3rd time, but every time we get a little closer to not needing to worry about a 51% attack wrought by carelessness
 72 2014-01-09 08:02:20 <allanlw> is there a nice place I can get a list of the types of transactions forwarded by standard bitcoin nodes?
 73 2014-01-09 08:02:52 <allanlw> i.e. the subset of all valid transactions that will be accepted by the network
 74 2014-01-09 08:05:51 <warren> shesek: thanks
 75 2014-01-09 08:08:25 <shesek> warren, you welcome
 76 2014-01-09 08:08:43 <shesek> I wonder why they let the old domain expire and didn't setup a 301... I had to email them to find out the new URL
 77 2014-01-09 08:10:09 <shesek> allanlw, I don't know if it counts as nice, but https://github.com/bitcoin/bitcoin/blob/master/src/script.cpp#L1197
 78 2014-01-09 08:12:07 <allanlw> shesek: thanks
 79 2014-01-09 08:12:08 <shesek> basically its pay-to-pubkey, pay-to-pubkey-hash, multisig, p2sh and OP_RETURN (on git only)
 80 2014-01-09 08:12:45 <allanlw> shesek: is the rejection of others mostly a hardening thing?
 81 2014-01-09 08:14:14 <allanlw> also I assume OP_SMALLINTERGER is made somewhere else from separate pushes?
 82 2014-01-09 08:14:26 <allanlw> aka it's a pseudo op?
 83 2014-01-09 08:17:22 <swulf--> If anyone's interested, I just put up http://bip32.org/
 84 2014-01-09 08:17:24 <deanclkclk> ok apologies for coming here but, I've run out of luck on the #bitcoin. I am trying to  run my bitcoind as a daemon. From my command land I specify -> bitcoind -daemon -conf="path" -datadir="path"
 85 2014-01-09 08:17:34 <deanclkclk> whenever I run it..the command freezes
 86 2014-01-09 08:18:07 <deanclkclk> it's running from the background because I can use my web app to send json rpc commands to it but, not from the command line. It freezes and I can't type a command
 87 2014-01-09 08:18:50 <shesek> swulf--, that looks pretty cool
 88 2014-01-09 08:18:57 <shesek> how about deriving from a master public key?
 89 2014-01-09 08:19:07 <swulf--> shesek: it works - just copy in a master public key
 90 2014-01-09 08:19:40 <shesek> oh, awesome :) perhaps you should make that clearer in the interface
 91 2014-01-09 08:20:02 <swulf--> shesek: you can get the associated master public key from the current private one by setting the key derivation to "Info: m" and copying the "derived public key" (even tho its not actually derived)
 92 2014-01-09 08:20:15 <jcorgan> swulf: i suggest swapping i and k in your terminology
 93 2014-01-09 08:20:25 <shesek> allanlw, yes, afaik its mostly due to security concerns and possible unknown attacker vectors
 94 2014-01-09 08:20:27 <swulf--> jcorgan: really? I was going with the terminology used in the bIP
 95 2014-01-09 08:21:04 <jcorgan> the "index" used in the bip is i
 96 2014-01-09 08:21:25 <swulf--> jcorgan: true. there is no separate value for k, either.
 97 2014-01-09 08:21:40 <swulf--> m/i'/0  is fixed with 0 being the only child index
 98 2014-01-09 08:21:43 <jcorgan> k is a not specified, but seems to be the common way to refer to the account
 99 2014-01-09 08:21:48 <deanclkclk> can anyone help me?
100 2014-01-09 08:21:53 <swulf--> aight
101 2014-01-09 08:21:59 <swulf--> I'll swap k and i
102 2014-01-09 08:22:08 <jcorgan> so you'd have m/k'/0/i and m/k'/1/i
103 2014-01-09 08:22:36 <jcorgan> but nicely done anyway
104 2014-01-09 08:24:05 <allanlw> shesek: is there also a list of standard scriptSigs?
105 2014-01-09 08:24:35 <allanlw> shesek: I know C++ I just can't find anything in the source very well
106 2014-01-09 08:25:16 <jcorgan> swulf--: also, the bip recommends using two different chains for addresses you'll give out vs. addresses used internally, like change addresses
107 2014-01-09 08:25:22 <justanotheruser>  deanclkclk you could try https://bitcointalk.org/index.php?board=4.0
108 2014-01-09 08:25:36 <swulf--> jcorgan: right - the internal/external accounts (both available in the key derivation dropdown)
109 2014-01-09 08:25:38 <deanclkclk> ok thx
110 2014-01-09 08:26:10 <jcorgan> oh, didn't see that.
111 2014-01-09 08:26:37 <swulf--> i just pushed the i/k swap, a refrehs in ~5 mins should fix that
112 2014-01-09 08:27:55 <jcorgan> i'm working in parallel on a command line version of the same thing
113 2014-01-09 08:30:28 <jcorgan> also, the "key derivation" choice names are not informative.  the bip itself uses poor terminology for these, too.
114 2014-01-09 08:30:53 <jcorgan> but I nor apparently anyone else has been able to come up with anything better
115 2014-01-09 08:33:21 <swulf--> jcorgan: I thought this too :)
116 2014-01-09 08:33:24 <jcorgan> how are you getting from passphrase to the extended key
117 2014-01-09 08:36:03 <swulf--> first hash to produce 256-bit, then use the hash in the algorithm described in the bip
118 2014-01-09 08:36:13 <swulf--> using the sha512-hmac
119 2014-01-09 08:36:35 <jcorgan> i'd strongly discourage you from asking users to provide a passphrase as a source of entropy for this
120 2014-01-09 08:36:52 <Diablo-D3> well, unless you key stretch it
121 2014-01-09 08:37:00 <jcorgan> exactly
122 2014-01-09 08:37:24 <Diablo-D3> like, 1m rounds of sha512 pbkdf2
123 2014-01-09 08:37:40 <swulf--> jcorgan: well, brainwallet.org suffers from the same lack-of-entropy
124 2014-01-09 08:37:57 <jcorgan> yes, and brainwallet.org has been the source of many painful loss of bitcoin events
125 2014-01-09 08:38:14 <swulf--> indeed it has
126 2014-01-09 08:38:27 <shesek> its also a good idea to encourage users to include personal information in the passphrase, like a username, email, full name, government i.d., etc
127 2014-01-09 08:38:44 <shesek> I like what vbuterin is doing - he separated it into two separate fields, one for username and one for password
128 2014-01-09 08:38:44 <swulf--> jcorgon: doesn't mean that this particular way to derive the key can't be useful, though
129 2014-01-09 08:38:55 <shesek> using it like that makes brainwallets much safer
130 2014-01-09 08:38:58 <swulf--> shesek: interesting. got a link?
131 2014-01-09 08:39:28 <shesek> I saw this in his multisig.info project, he also talked about it in reddit
132 2014-01-09 08:39:45 <shesek> see his response here: http://www.reddit.com/r/Bitcoin/comments/1ucw7p/multisiginfo_a_simple_multisig_interface/cegu57l
133 2014-01-09 08:41:00 <shesek> its not really any different from the users putting the username into the passphrase field, but it forces them to do it which is good
134 2014-01-09 08:41:16 <swulf--> shesek: interesting - http://ms-brainwallet.org/ is my site, doing a very similar thing
135 2014-01-09 08:41:42 <shesek> yeah, I saw it on that same thread
136 2014-01-09 08:41:46 <shesek> gave you a beer too :)
137 2014-01-09 08:41:54 <swulf--> oh.. indeed. that was you:)
138 2014-01-09 08:43:09 <jcorgan> swulf--: SHA256(passphrase) as a source of entropy is valid, for people who understand what entropy is, but i'd really rather you go with a key stretching approach
139 2014-01-09 08:43:28 <swulf--> jcorgan: OK - what's a decent key stretching approach?
140 2014-01-09 08:43:40 <shesek> <Diablo-D3> like, 1m rounds of sha512 pbkdf2
141 2014-01-09 08:43:45 <jcorgan> google pbkdf2
142 2014-01-09 08:43:45 <shesek> sounds reasonable
143 2014-01-09 08:43:54 <swulf--> hmm
144 2014-01-09 08:44:06 <swulf--> the goal is to beat brute-force I guess
145 2014-01-09 08:44:11 <shesek> do it in a web worker tho with a progress bar or something, otherwise it'll choke the browser
146 2014-01-09 08:44:33 <Diablo-D3> pbkdf2 does x = 0; loop(x times) { x = x ^ hashalgo(input) }
147 2014-01-09 08:45:52 <Diablo-D3> er
148 2014-01-09 08:45:54 <Diablo-D3> I wrote that wrong
149 2014-01-09 08:46:02 <allanlw> other options are scrypt and bcrypt
150 2014-01-09 08:46:35 <swulf--> all right, sounds good enough. i'll try and get something cool done tonight
151 2014-01-09 08:46:44 <Diablo-D3> wikipedia lists it correctly anyways
152 2014-01-09 08:46:57 <Diablo-D3> allanlw: bcrypt isnt an option
153 2014-01-09 08:47:09 <Diablo-D3> and scrypt is the only useful replacement for pbkdf2+sha512
154 2014-01-09 08:47:12 <jcorgan> swulf--: please take our feedback in a positive way--i'm really happy to see someone doing this
155 2014-01-09 08:47:24 <Diablo-D3> and you have to learn how to use scrypt
156 2014-01-09 08:47:31 <Diablo-D3> dont make the mistake ltc did
157 2014-01-09 08:47:43 <shesek> definitely, its great to see somebody finally doing this
158 2014-01-09 08:47:51 <Diablo-D3> yeah, its good someone is doing this
159 2014-01-09 08:47:54 <Diablo-D3> just make sure you do it rightr
160 2014-01-09 08:48:19 <allanlw> Diablo-D3: why isn't bcrypt an option?
161 2014-01-09 08:48:24 <Diablo-D3> allanlw: not secure enough
162 2014-01-09 08:48:25 <shesek> I was actually planning to do something similar myself, but ended up doing a multisig implementation that's optimized for a third party arbitration
163 2014-01-09 08:48:58 <shesek> great to see someone else taking the initiative
164 2014-01-09 08:49:14 <shesek> I got to go, running late to a meeting
165 2014-01-09 08:49:16 <Diablo-D3> allanlw: its basically key stretched blowfish
166 2014-01-09 08:49:19 <allanlw> Diablo-D3: from what I've read they have similar amounts of security
167 2014-01-09 08:49:22 <shesek> good luck!
168 2014-01-09 08:49:30 <Diablo-D3> blowfish has not been sufficiently proven imo
169 2014-01-09 08:50:01 <Diablo-D3> and to be fair, neither has scrypt or sha3
170 2014-01-09 08:50:14 <Diablo-D3> which is why I went straight for the largest sha2 and key stretch that
171 2014-01-09 08:50:46 <allanlw> Diablo-D3: fair, although even if you used bcrypt it's not exactly the weak point in this whole scheme
172 2014-01-09 08:50:55 <Diablo-D3> yeah probably
173 2014-01-09 08:51:00 <Diablo-D3> but you want at least 20 years of security
174 2014-01-09 08:51:10 <allanlw> I mean what with doing this in javascript in a web page, etc
175 2014-01-09 08:51:19 <allanlw> Diablo-D3: sure, yeah okay, I'll agree with that
176 2014-01-09 08:51:20 <Diablo-D3> yeah, javascript cant be trusted here
177 2014-01-09 08:51:24 <jcorgan> swulf--: also, read bip0038 for ideas in this area, though that bip is likely to be superceded by something else
178 2014-01-09 08:51:41 <Diablo-D3> what you'd also want is an offline program in very simple C that is, say, command line
179 2014-01-09 08:52:04 <allanlw> I'm kind of surprised there isn't an accepted bip for this
180 2014-01-09 08:52:06 <Diablo-D3> just in case the website is compromised you can still do shit
181 2014-01-09 08:52:15 <Diablo-D3> allanlw: the problem is kinda difficult
182 2014-01-09 08:52:51 <Diablo-D3> and there are people in here who also would say pbkdf2 + sha512 isnt secure enough
183 2014-01-09 08:55:23 <allanlw> I mean the primative choices here are kind of meaningless
184 2014-01-09 08:55:34 <allanlw> this is all very similar to the GGM construction
185 2014-01-09 08:55:49 <allanlw> and you probably want algorithmic agility anyway
186 2014-01-09 08:57:11 <allanlw> (by GGM I mean Goldreich-Goldwasser-Micali : https://crypto.stanford.edu/pbc/notes/crypto/ggm.xhtml)
187 2014-01-09 08:57:35 <allanlw> just a thought
188 2014-01-09 10:45:31 <cr3pe> hi
189 2014-01-09 10:47:16 <kiddouk> hi
190 2014-01-09 11:01:54 <warren> sipa: whatever the issue is, when networking fails here, GUI remains responsive, and hours later I see a great many "CLOSE_WAIT" state connections in netstat -a on Windows 7.
191 2014-01-09 11:02:03 <warren> sipa: suggesting some kind of resource leak
192 2014-01-09 12:49:56 <warren> sipa: confirmed, bitcoin master gets stuck
193 2014-01-09 12:50:03 <warren> sipa: same symptoms
194 2014-01-09 12:50:28 <warren> I guess I can be blamed for causing this bug.
195 2014-01-09 12:52:44 <swulf--> jcorgan: no worries... I'm not taking any offense to any of the suggestions here. They're all wise ones:)
196 2014-01-09 13:44:13 <netg> /
197 2014-01-09 14:44:03 <Diablo-D3> https://twitter.com/chris__martin/status/420992421673988096
198 2014-01-09 16:26:40 <t7> the whole doge thing got outa hand about 6 months ago
199 2014-01-09 16:27:03 <Diablo-D3> and never stopped being out of hand
200 2014-01-09 16:27:15 <brisque> t7: it's an interesting social comment that people keep repeating it.
201 2014-01-09 16:29:35 <t7> it makes me sad
202 2014-01-09 16:30:14 <t7> i dont know why that meme irks me so much
203 2014-01-09 16:30:18 <brisque> it's the low mental barrier of entry I think. it requires no thought to strip grammar and follow the pattern.
204 2014-01-09 16:30:19 <t7> i can deal with most others
205 2014-01-09 16:30:31 <t7> ah maybe
206 2014-01-09 16:30:46 <t7> or maybe its just too mainstream and im a hipster deep down
207 2014-01-09 17:32:13 <wallet42> i think doge is quite an interesting phenomen
208 2014-01-09 17:32:45 <wallet42> also if keeping this in mind https://www.facebook.com/notes/facebook-data-science/the-evolution-of-memes-on-facebook/10151988334203859
209 2014-01-09 17:33:57 <wallet42> its sure that it wont be there forever
210 2014-01-09 17:34:58 <wallet42> and just like watching old pictures of people wearing clothes or hairstyles that were "trendy" 20 years ago
211 2014-01-09 17:35:49 <wallet42> ppl will feel embarrased after the trend has passed
212 2014-01-09 19:25:31 <lechuga__> is any1 aware of anything similar to -printblock but will work with any arbitrarily passed hex encoded block field?
213 2014-01-09 19:25:50 <lechuga__> such that i could dump a CTransaction or just a single CTxIn etc
214 2014-01-09 19:27:54 <sipa> lechuga__: fetchtx.info
215 2014-01-09 19:29:29 <lechuga__> eh i was more looking for something to dump the datastructure and not a real txn on the network
216 2014-01-09 19:29:40 <sipa> it works for arbitrary transactions
217 2014-01-09 19:29:42 <lechuga__> like any arbitrarily serialized field
218 2014-01-09 19:29:59 <sipa> first fetch one, click raw transaction, and edit the field
219 2014-01-09 19:31:05 <andytoshi> lechuga__: you need to know which data structure you are dealing with, as they are not tagged, then it's a fairly straightforward programming task to do the decoding..
220 2014-01-09 19:31:21 <lechuga__> hah perfect
221 2014-01-09 19:31:30 <lechuga__> sipa: thanks!
222 2014-01-09 19:31:38 <andytoshi> there is the 'decoderawtransaction' RPC which does what you want for transactions
223 2014-01-09 19:31:40 <andytoshi> fwiw
224 2014-01-09 19:31:48 <lechuga__> ah is that all fetchtx is using?
225 2014-01-09 19:31:55 <sipa> no
226 2014-01-09 19:32:16 <sipa> fetchtx.info gives quite a bit more ifnormation, and nicelier structured
227 2014-01-09 19:32:28 <sipa> (it actually shows you how it maps to bytes)
228 2014-01-09 19:32:44 <lechuga__> it is rather nice, k
229 2014-01-09 19:56:07 <wallet42> ah very nice fetchtx
230 2014-01-09 19:56:21 <wallet42> kudos to dev
231 2014-01-09 20:52:54 <Happzz> what did 0.8.6 fix?
232 2014-01-09 21:02:59 <sipa> https://github.com/bitcoin/bitcoin/blob/03a7d673876dc8fbae876290b455c02b0cac80bd/doc/release-notes.md
233 2014-01-09 21:04:40 <tiyoT> quick question, is there a software/api/protocol exist out there that can trigger something when particular btc address (eg our own) receive payment. Eg, tell my website backend to add +100gil to User1 when my btc address receive 0.1 btc.
234 2014-01-09 21:09:06 <upb> website backend really means php script?
235 2014-01-09 23:39:50 <sipa> ;;calc [diff]*2**48/65535
236 2014-01-09 23:39:51 <gribble> Error: invalid syntax (<string>, line 1)
237 2014-01-09 23:39:53 <sipa> ;;diff
238 2014-01-09 23:39:54 <gribble> 1.4184813952626355E9
239 2014-01-09 23:40:22 <gribble> 62.4016986633
240 2014-01-09 23:40:22 <sipa> ;;calc log(1.41848*10**9*2**32)/log(2)
241 2014-01-09 23:40:47 <sipa> ;;nethash
242 2014-01-09 23:40:48 <gribble> 13825207.9898