1 2013-06-18 04:04:42 <kuzetsa> I discovered Vm0wd2QyU purely by accident.., and I'm not the first. Now I find myself wondering if base58 has a similar fixed point or not --> http://fmota.eu/blog/base64-fixed-point.html
  2 2013-06-18 05:25:36 <TradeFortress> It looks like I have fallen victim to a successful double spend attack.
  3 2013-06-18 05:26:03 <TradeFortress> Where can I see reorgs?
  4 2013-06-18 05:28:13 <sturles> blockchain.info
  5 2013-06-18 05:29:32 <TradeFortress> OK, so what happened was that getbalance("account", 0) [for visual purposes] was returning the correct amount
  6 2013-06-18 05:29:39 <TradeFortress> I credit balances when it reaches 3 confirmations.
  7 2013-06-18 05:30:10 <TradeFortress> But soon, getbalance("account", 0) becomes 0.0001 even through I haven't moved or sent anything.
  8 2013-06-18 05:32:37 <sturles> Did you save the txid?
  9 2013-06-18 05:32:43 <sipa> that seems strange
 10 2013-06-18 05:33:03 <sipa> what does listtransactions say?
 11 2013-06-18 05:33:24 <TradeFortress> Yes, the txid for the 0.19 one was https://blockchain.info/tx/6ced43ac22064b47ad145c8f257fadeebad8b0a0c1b4b997baf1bf11e05d3dca
 12 2013-06-18 05:37:42 <sturles> This was included in block 242106 and spent in block 242123.
 13 2013-06-18 05:37:47 <sturles> Check listtransactions-
 14 2013-06-18 05:38:34 <TradeFortress> In listtransactions, I see the tx, along with a 0.001 one to another address belonging to this account.
 15 2013-06-18 05:39:02 <TradeFortress> My PHP code the executed and has swept the funds to main, and is supposed to have credited the user with 0.19 BTC. However, that wasnt credited.
 16 2013-06-18 05:40:37 <TradeFortress> Nothing in error logs.
 17 2013-06-18 05:41:00 <sturles> Sounds like a bug in your code.  Nothing like a double spend.
 18 2013-06-18 05:41:06 <sturles> The coins are there.
 19 2013-06-18 05:42:14 <TradeFortress> Mind taking a quick look at my PHP code? http://pastebin.com/7F4ZbwtM
 20 2013-06-18 05:46:59 <TradeFortress> I would really apperciate it if you could take a look and tell me if there is a fault with the code.
 21 2013-06-18 05:55:15 <sturles> Perhaps something went wrong with your sql queries?  I don't know how you would notice that in your logs.
 22 2013-06-18 06:00:35 <melvster> kuzetsa: the fixed point in base64 is easy to see because 64 is a factor of 128, since 128 and 29 are coprime, it's more difficult to tell if there's a fixed point in bitcoin's base58 encoding, I suspect there is not
 23 2013-06-18 06:04:53 <warren> https://forum.litecoin.net/index.php?topic=4471.msg32120#msg32120  let me know if you think I'm too harsh.
 24 2013-06-18 06:04:56 <warren> oops
 25 2013-06-18 06:05:02 <warren> wrong channel, sorry =(
 26 2013-06-18 06:05:30 <warren> that was a serious blunder of pasting
 27 2013-06-18 06:51:03 <Nothing4You> putting "testnet=1" in ~/.bitcoin/bitcoin.conf on mac should get bitcoin-qt launching in testnet mode, right?
 28 2013-06-18 06:53:18 <BlueMatt> in theory, yes
 29 2013-06-18 06:54:35 <Nothing4You> friend of mine, using a mac, tried putting that in his bitcoin.conf. he's using v0.8.2-beta. after second launch or so he says there were additional lines, e.g. one saying "{\\fonttbl\\f0\\fmodern\\fcharset0 Courier;}"
 30 2013-06-18 06:54:44 <Nothing4You> and help ??? debug ??? testnet isn't checked
 31 2013-06-18 06:55:19 <BlueMatt> did he file a bug report?
 32 2013-06-18 06:55:47 <kinlo> eh
 33 2013-06-18 06:55:49 <Nothing4You> no, we were currently trying to figure out whether it's a bug or not
 34 2013-06-18 06:55:56 <Nothing4You> maybe it's just user misconfiguration
 35 2013-06-18 06:55:57 <kinlo> that sounds like your friend editing the config file with wordpad
 36 2013-06-18 06:56:02 <kinlo> and saving it as rtf
 37 2013-06-18 06:56:10 <kinlo> can you tell him to use notepad?
 38 2013-06-18 06:56:14 <BlueMatt> oh, you mean in the file
 39 2013-06-18 06:56:16 <BlueMatt> yea, thats rtf
 40 2013-06-18 06:56:19 <Nothing4You> oh
 41 2013-06-18 06:56:25 <Nothing4You> i couldn't believe someone would do that
 42 2013-06-18 06:56:33 <Nothing4You> i'll tell him to use a text editor
 43 2013-06-18 06:56:41 <Nothing4You> that is a plain text editor
 44 2013-06-18 06:57:08 <BlueMatt> hes probably using Text Edit, which is right, but its not default to save in plain text anymore
 45 2013-06-18 06:57:18 <BlueMatt> so you have to make sure you save it right in the save dialog/prefs editor
 46 2013-06-18 06:57:25 <Nothing4You> can you suggest a free text editor for mac?
 47 2013-06-18 06:57:34 <Nothing4You> i know i've used smultron in the past, i'm not sure it's free anymore
 48 2013-06-18 06:57:38 <BlueMatt> if you're just editing bitcoin.conf, Text Edit is fine
 49 2013-06-18 06:57:42 <BlueMatt> otherwise, no idea
 50 2013-06-18 06:57:55 <Nothing4You> kk
 51 2013-06-18 07:06:19 <Luke-Jr> side note: I'm not sure bitcoin.conf is loaded early enough for testnet flag, considering testnet uses a different conf file normall
 52 2013-06-18 07:07:57 <sipa> works fine here, both bitcoind and bitcoin-qt
 53 2013-06-18 07:08:27 <Luke-Jr> sipa: does it reload the bitcoin.conf for testnet? O.o
 54 2013-06-18 07:08:39 <sipa> no
 55 2013-06-18 07:08:49 <sipa> not afaik
 56 2013-06-18 07:22:54 <kinlo> Luke-Jr: there is no different config file for testnet
 57 2013-06-18 07:23:57 <sipa> if you use -testnet on the command line, ~/.bitcoin/testnet3/bitcoin.conf is used, afaik
 58 2013-06-18 07:24:34 <sipa> while if you test testnet=1 in ~/.bitcoin/bitcoin.conf, that file itself is used
 59 2013-06-18 07:30:52 <kinlo> ic
 60 2013-06-18 07:34:02 <TD[gone]> nick TD
 61 2013-06-18 07:34:11 <BlueMatt> missing something?
 62 2013-06-18 07:34:19 <TD> for some reason some guy is always camping on my nick
 63 2013-06-18 07:34:21 <TD> irritating
 64 2013-06-18 07:34:40 <BlueMatt> it is a two letter nick on freenode...
 65 2013-06-18 07:35:00 <Nothing4You> TD: maybe /msg nickserv set enforce on?
 66 2013-06-18 07:35:40 <TD> is that a command? i don't see any reference to it in nickserv help
 67 2013-06-18 07:36:17 <BlueMatt> its there somewhere
 68 2013-06-18 07:36:33 <BlueMatt> (it makes you auth within X secs of switching to the nick)
 69 2013-06-18 07:36:44 <BlueMatt> (why you always see jgarzik as GuestXXXX)
 70 2013-06-18 07:37:06 <Nothing4You> TD: see /msg nickserv help set
 71 2013-06-18 07:37:08 <TD> that seems no easier than just ghosting the other guy every time :)
 72 2013-06-18 07:37:23 <BlueMatt> set your irc client to auto-auth
 73 2013-06-18 07:37:25 <Nothing4You> TD: it will release the nick automatically
 74 2013-06-18 07:37:33 <Nothing4You> set your client to auth via sasl
 75 2013-06-18 07:37:59 <Nothing4You> you might want to upgrade to http://hexchat.org
 76 2013-06-18 07:38:01 <Nothing4You> it has builtin sasl
 77 2013-06-18 07:38:05 <TD> ok
 78 2013-06-18 07:38:06 <Nothing4You> for xchat you need a script
 79 2013-06-18 07:38:06 <TD> thanks
 80 2013-06-18 07:38:14 <BlueMatt> every client has builtin sasl at this point (or at least a plugin for it)
 81 2013-06-18 07:38:41 <Nothing4You> TD: see the ppa: https://launchpad.net/~gwendal-lebihan-dev/+archive/hexchat-stable
 82 2013-06-18 07:38:43 <sipa> netcat doesn't!
 83 2013-06-18 07:38:48 <Nothing4You> telnet also doesn't
 84 2013-06-18 07:38:58 <BlueMatt> or use a bouncer that handles that for you and then just auth to the bouncer
 85 2013-06-18 07:39:02 <Nothing4You> ^
 86 2013-06-18 10:47:52 <jgarzik> mornin'
 87 2013-06-18 10:48:17 <Anduckk> gm!
 88 2013-06-18 10:49:07 <handle> night!
 89 2013-06-18 10:49:21 <sipa> 'fternoon
 90 2013-06-18 10:53:18 <BlueMatt> good afternoon
 91 2013-06-18 11:11:30 <handle> evening
 92 2013-06-18 11:50:04 <jgarzik> TD, sipa: does subsidy halving interval need to be a variable, for regtest mode?
 93 2013-06-18 11:50:48 <TD> BlueMatt has tests that require that, so yes, i think so
 94 2013-06-18 11:51:39 <sipa> you can argue that regtest mode should be chosen at compile time instead of at runtime, but meh, this is more flexible and easier
 95 2013-06-18 11:52:49 <sipa> oh, mainParams is static, so the Params() function can't be inlined itself
 96 2013-06-18 11:53:01 <sipa> not like you'd notice at runtime
 97 2013-06-18 11:53:58 <jgarzik> ok
 98 2013-06-18 12:00:51 <TD> sipa: for app development it's nice to be able to switch back and forth with the same binary
 99 2013-06-18 12:12:44 <cheesecake299> I am trying to get multi sig to work, How do i list the info on the multi-sig transaction? http://pastebay.com/1241334
100 2013-06-18 12:16:17 <jgarzik> cheesecake299, what do you mean by 'list the info'?  What info do you need?
101 2013-06-18 12:16:55 <cheesecake299> balance, if it's been signed
102 2013-06-18 12:17:22 <jgarzik> cheesecake299, listtransactions and getinfo RPC calls should give that
103 2013-06-18 12:17:38 <jgarzik> cheesecake299, signrawtransaction also tells you if its completely signed
104 2013-06-18 12:19:27 <cheesecake299> partially signed? I want to program a web interface for mutli-sigs to simplify the process
105 2013-06-18 12:20:06 <sydna> somewhat related, has anyone ever made a curses interface for bitcoind?
106 2013-06-18 12:24:29 <TD> cheesecake299: afaik blockchain.info already has done that
107 2013-06-18 12:25:08 <jgarzik> Yep, https://blockchain.info/wallet/escrow
108 2013-06-18 12:25:40 <cheesecake299> jgarzik getbalance says 0 :/
109 2013-06-18 12:26:36 <jgarzik> cheesecake299, are the transactions confirmed yet?
110 2013-06-18 12:28:07 <cheesecake299> how do i find out?
111 2013-06-18 12:28:53 <cheesecake299> not showing up on http://blockexplorer.com/testnet/address/mpxs2zxpPpQspCjQo1QfQ2afvQMtSoHaG5
112 2013-06-18 12:29:04 <boonies4u> I'm wondering what happens if you install a full node on a HD of limited capacity and it reaches the point that it can't download further blocks
113 2013-06-18 12:29:42 <boonies4u> I'm certainly not facing this concern, but i'm curious
114 2013-06-18 12:31:10 <cheesecake299> jgarzik when i do listreceivedbyaddress 1 true it does not even show it's left the wallet
115 2013-06-18 12:32:07 <cheesecake299> it did return 0de20f9934343b25cdd9c4bf654a9922603a5e17eda14a3475000461eafc04a8 though
116 2013-06-18 12:32:24 <sipa> jgarzik, cheesecake299: multisig transactions are not assumed to be 'to' you, unless you have all relevant keys in your wallet
117 2013-06-18 12:32:52 <cheesecake299> so how do i fund it?
118 2013-06-18 12:33:05 <sipa> you need to find the outputs to it in another way, which is very clumsy
119 2013-06-18 12:33:22 <sipa> we need something like having them in listtransactions but not counted in balanc eor something
120 2013-06-18 12:33:36 <sipa> or it can be integrated with watch-only addresses
121 2013-06-18 12:35:47 <sipa> boonies4u: if you run out of disk space, and bitcoin detects this, it exits
122 2013-06-18 12:36:00 <cheesecake299> sipa please could you write a simple example of creating/funding/signing/spending a multi sig? I am really confused
123 2013-06-18 12:36:01 <boonies4u> ah thanks :3
124 2013-06-18 12:36:20 <sipa> cheesecake299: it is not simple
125 2013-06-18 12:36:36 <sipa> cheesecake299: gmaxwell has an example somewhere
126 2013-06-18 12:36:47 <sipa> but the parts to make it easy don't exist yet, afaik
127 2013-06-18 12:40:33 <cheesecake299> sipa https://gist.github.com/gavinandresen/3966071/raw/1f6cfa4208bc82ee5039876b4f065a705ce64df7/TwoOfThree.sh ?
128 2013-06-18 12:41:32 <sipa> cheesecake299: yes, but that completely bypasses the problem of detecting incoming payments
129 2013-06-18 12:42:01 <sipa> which currently doesn't exist in bitcoind
130 2013-06-18 12:42:53 <cheesecake299> okay, i just got to wait  a few hrs before my transaction is processed by testnet?
131 2013-06-18 12:43:36 <sipa> eh, no, you need a way to know incoming payments on multisig addresses
132 2013-06-18 12:44:20 <sipa> confirmations have nothing to do with it
133 2013-06-18 12:44:45 <cheesecake299> ah so at the moment there is no way to know if a mult-sig address is funded?
134 2013-06-18 12:45:14 <sipa> only if you own all keys involved
135 2013-06-18 12:45:27 <sipa> which isn't actually useful at all
136 2013-06-18 12:45:35 <cheesecake299> inlcuding the public and private or just pub?
137 2013-06-18 12:45:49 <sipa> own == you have the private key
138 2013-06-18 12:46:04 <cheesecake299> :/ so can't really use it then
139 2013-06-18 12:46:31 <sipa> the nice solution imho would be watch-only wallets
140 2013-06-18 12:46:39 <sipa> which was implemented already, but outdated now
141 2013-06-18 12:46:44 <TD> cheesecake299: what are you *actually* trying to do
142 2013-06-18 12:47:02 <TD> cheesecake299: multi-sig transactions are not, by themselves, a feature
143 2013-06-18 12:47:08 <cheesecake299> use multi-sig as an escrow
144 2013-06-18 12:47:08 <TD> cheesecake299: they are something you use to build other features
145 2013-06-18 12:47:13 <TD> what does "escrow" mean?
146 2013-06-18 12:47:27 <cheesecake299> keep coins in the multi-sig
147 2013-06-18 12:47:32 <TD> that's circular
148 2013-06-18 12:47:36 <TD> think higher level
149 2013-06-18 12:47:39 <TD> what end user problem are you trying to solve
150 2013-06-18 12:47:45 <cheesecake299> trust
151 2013-06-18 12:47:52 <TD> trust in what sense? dispute mediation? security against viruses?
152 2013-06-18 12:47:53 <cheesecake299> so the user only needs to privide a pub key
153 2013-06-18 12:48:32 <cheesecake299> minimize the access to coins if service was hacked, as only when the multi-sig is signed it can be spent
154 2013-06-18 12:49:01 <sipa> so you want to create an e-wallet site where the held coins are co-owned by the user?
155 2013-06-18 12:49:09 <cheesecake299> an escrow site
156 2013-06-18 12:49:21 <sipa> or you want to facilitate payments to untrusted receivers?
157 2013-06-18 12:49:22 <TD> if what service was hacked? a web service? an exchange?
158 2013-06-18 12:49:52 <cheesecake299> sipa facilitate payments to untrusted receivers?
159 2013-06-18 12:50:14 <sipa> cheesecake299: please explain what exact problem you're solving
160 2013-06-18 12:50:30 <sipa> you're just listing arbitrary features you're using, or very high-level terms
161 2013-06-18 12:51:49 <cheesecake299> sure, so buyer gives an unused public address, and so does the seller, then the escow agent adds his public key
162 2013-06-18 12:52:17 <sipa> and then returns 2-of-3 multisig address?
163 2013-06-18 12:52:19 <cheesecake299> then the buyer funds the multi-sig, and once the goods arrive both paries sign the transactoin
164 2013-06-18 12:52:32 <cheesecake299> and then the funds are relased
165 2013-06-18 12:52:35 <sipa> ok
166 2013-06-18 12:52:48 <sipa> so yes, your problem will be detecting payments to the multisig address
167 2013-06-18 12:53:02 <sipa> that's something bitcoind can't do today
168 2013-06-18 12:53:18 <Scrat> what is the plan with including multisig into bitcoin-qt?
169 2013-06-18 12:53:20 <TD> cheesecake299: so, this one? https://en.bitcoin.it/wiki/Contracts#Example_2:_Escrow_and_dispute_mediation
170 2013-06-18 12:53:23 <Jouke> does anyone knom if there is an easy way to calculate the public key of a raw private key through openssl? And with raw private key, I mean non DER-encoded (because when I use dumpprivkey it isn't der-encoded right?)
171 2013-06-18 12:53:26 <TD> cheesecake299: it's really best to call that dispute mediation
172 2013-06-18 12:53:30 <TD> cheesecake299: "escrow" can mean other things
173 2013-06-18 12:53:55 <TD> Jouke: you mean the command line tool or with the c api?
174 2013-06-18 12:53:59 <cheesecake299> thanks TD will be more specific next time didnt know :)
175 2013-06-18 12:54:05 <Jouke> command line
176 2013-06-18 12:54:10 <TD> cheesecake299: for something like dispute mediation, that's a big project and it involves more than just a website and a few RPC calls to bitcoind.
177 2013-06-18 12:54:30 <TD> cheesecake299: for instance, the wallet apps have to know how to represent disputed transactions in the GUI, the merchants have to communicate to the users which mediator to use, etc
178 2013-06-18 12:54:47 <TD> cheesecake299: if you implement that, you'll be doing it either in c++, java (for multibit/android wallet), or both
179 2013-06-18 12:54:52 <TD> not via JSON-RPC and a web app
180 2013-06-18 12:58:32 <Jouke> TD: or does openssl only accept DER or PEM encoded input?
181 2013-06-18 12:58:58 <TD> not sure. i expect only der/pem
182 2013-06-18 12:59:44 <sipa> Jouke: "just the secret parameter as 32 bytes" is not really a standard format
183 2013-06-18 12:59:56 <sipa> so i expect openssl to only accept DER encoded private keys indeed