--- Day changed Sun Oct 02 2016 00:41 -!- fqtw [~me@x4db10b1f.dyn.telefonica.de] has joined #joinmarket 00:44 -!- fqtw_ [~me@x4db02e6a.dyn.telefonica.de] has quit [Ping timeout: 264 seconds] 00:45 -!- fqtw_ [~me@x4db10b1f.dyn.telefonica.de] has joined #joinmarket 00:45 -!- fqtw__ [~me@x4db02e6a.dyn.telefonica.de] has quit [Ping timeout: 265 seconds] 01:05 -!- fqtw__ [~me@x590dbcd3.dyn.telefonica.de] has joined #joinmarket 01:05 -!- pigeons [~pigeons@94.242.209.214] has quit [Ping timeout: 243 seconds] 01:05 -!- pigeons [~pigeons@94.242.209.214] has joined #joinmarket 01:06 -!- pigeons is now known as Guest54199 01:08 -!- fqtw_ [~me@x4db10b1f.dyn.telefonica.de] has quit [Ping timeout: 272 seconds] 01:08 -!- fqtw [~me@x4db10b1f.dyn.telefonica.de] has quit [Ping timeout: 264 seconds] 01:09 -!- fqtw [~me@x590dbcd3.dyn.telefonica.de] has joined #joinmarket 02:56 -!- errorstill [2e1c3590@gateway/web/freenode/ip.46.28.53.144] has joined #joinmarket 02:57 < errorstill> dear dev guys, v0.2.1 still failing to send occasionally from either --rpcwallet and wallet.json 02:57 < errorstill> gives error and forces me to use lower version 0.1.X 02:58 < errorstill> the new mixing method works sometimes but i feel like almost 80% fail rates out of all attempts 02:58 < errorstill> please fix this issue qq 02:58 < errorstill> thank you 02:58 -!- errorstill [2e1c3590@gateway/web/freenode/ip.46.28.53.144] has quit [Client Quit] 02:59 < adlai> well that's a useless error report 02:59 < adlai> "doctor, it hurts!" "where?" "in the place, when i do the thing" 03:11 -!- DeathShadow--666 [~IDSE@S0106a0f3c1139365.vc.shawcable.net] has quit [Quit: You've met with a terrible fate, haven't you?] 03:12 < waxwing> and .. he's gone :) 03:32 -!- DeathShadow--666 [~IDSE@S0106a0f3c1139365.vc.shawcable.net] has joined #joinmarket 03:53 < waxwing> he needs to check commitments_debug.txt when it fails to see why commitments could not be created. also run from develop branch latest, not master, for the 2nd bugfix for --rpcwallet (although that only comes up if the transaction was going to fail anyway). 03:53 < waxwing> i suspect part of the problem is that the help message telling you to read commitments_debug.txt can get lost in the terminal scrollback due to the message channel threads shutting down. 03:54 < waxwing> which is a bit crappy, but there we are. 04:54 -!- fqtw__ [~me@x590dbcd3.dyn.telefonica.de] has quit [Quit: Leaving] 05:39 -!- molz [~molly@unaffiliated/molly] has quit [Write error: Connection reset by peer] 05:39 -!- molz [~molly@unaffiliated/molly] has joined #joinmarket 06:18 -!- coins123 [~coins123@unaffiliated/coins123] has joined #joinmarket 06:52 -!- coins123 [~coins123@unaffiliated/coins123] has quit [Ping timeout: 248 seconds] 07:06 -!- twokun [~two@46.19.137.116] has joined #joinmarket 07:23 -!- Giszmo [~leo@pc-40-227-45-190.cm.vtr.net] has quit [Ping timeout: 248 seconds] 07:35 -!- Giszmo [~leo@pc-40-227-45-190.cm.vtr.net] has joined #joinmarket 07:41 -!- Guest54199 is now known as pigeons 07:43 -!- molz [~molly@unaffiliated/molly] has quit [Ping timeout: 252 seconds] 07:47 -!- Giszmo [~leo@pc-40-227-45-190.cm.vtr.net] has quit [Ping timeout: 265 seconds] 07:52 -!- Giszmo [~leo@pc-40-227-45-190.cm.vtr.net] has joined #joinmarket 07:57 -!- coins123 [~coins123@unaffiliated/coins123] has joined #joinmarket 07:57 -!- moli [~molly@unaffiliated/molly] has joined #joinmarket 08:00 -!- Giszmo [~leo@pc-40-227-45-190.cm.vtr.net] has quit [Read error: No route to host] 08:00 -!- Giszmo [~leo@pc-40-227-45-190.cm.vtr.net] has joined #joinmarket 08:45 -!- moli [~molly@unaffiliated/molly] has quit [Read error: Connection reset by peer] 08:45 -!- moli [~molly@unaffiliated/molly] has joined #joinmarket 08:52 -!- molz [~molly@unaffiliated/molly] has joined #joinmarket 08:55 -!- moli [~molly@unaffiliated/molly] has quit [Ping timeout: 248 seconds] 08:56 -!- molz [~molly@unaffiliated/molly] has quit [Client Quit] 08:56 -!- molz [~molly@unaffiliated/molly] has joined #joinmarket 09:31 -!- twokun [~two@46.19.137.116] has quit [Ping timeout: 272 seconds] 10:04 -!- fqtw_ [~me@x590dcc0a.dyn.telefonica.de] has joined #joinmarket 10:07 -!- fqtw [~me@x590dbcd3.dyn.telefonica.de] has quit [Ping timeout: 272 seconds] 10:09 -!- megaddin [aladdin@gateway/shell/fnordserver.eu/x-fcskkvwyuhpsdhsu] has joined #joinmarket 10:15 -!- fqtw [~me@x590d037b.dyn.telefonica.de] has joined #joinmarket 10:18 -!- fqtw_ [~me@x590dcc0a.dyn.telefonica.de] has quit [Ping timeout: 265 seconds] 10:51 -!- fqtw_ [~me@x4db25f70.dyn.telefonica.de] has joined #joinmarket 10:55 -!- fqtw [~me@x590d037b.dyn.telefonica.de] has quit [Ping timeout: 265 seconds] 10:56 -!- NoJoke [~ImCool@176.123.26.59] has quit [Changing host] 10:56 -!- NoJoke [~ImCool@unaffiliated/thisiszenified] has joined #joinmarket 11:18 -!- fqtw [~me@x590c3084.dyn.telefonica.de] has joined #joinmarket 11:20 -!- fqtw_ [~me@x4db25f70.dyn.telefonica.de] has quit [Ping timeout: 244 seconds] 11:33 -!- fqtw_ [~me@x4db12961.dyn.telefonica.de] has joined #joinmarket 11:37 -!- fqtw [~me@x590c3084.dyn.telefonica.de] has quit [Ping timeout: 264 seconds] 11:55 -!- megaddin [aladdin@gateway/shell/fnordserver.eu/x-fcskkvwyuhpsdhsu] has quit [Quit: https://fnordserver.eu] 11:58 -!- moli [~molly@unaffiliated/molly] has joined #joinmarket 12:00 -!- molz [~molly@unaffiliated/molly] has quit [Ping timeout: 252 seconds] 12:11 -!- fqtw [~me@x4db12961.dyn.telefonica.de] has joined #joinmarket 12:13 -!- fqtw_ [~me@x4db12961.dyn.telefonica.de] has quit [Ping timeout: 264 seconds] 12:27 -!- twokun [~two@46.19.137.116] has joined #joinmarket 12:35 -!- fqtw_ [~me@x4db12961.dyn.telefonica.de] has joined #joinmarket 12:39 -!- fqtw [~me@x4db12961.dyn.telefonica.de] has quit [Ping timeout: 265 seconds] 15:36 -!- grubles [~grubles@unaffiliated/grubles] has joined #joinmarket 15:48 -!- brand0 [brand0@lol.bxroberts.org] has quit [Ping timeout: 244 seconds] 17:29 -!- twokun [~two@46.19.137.116] has quit [Quit: Leaving.] 17:32 -!- brand0 [brand0@lol.bxroberts.org] has joined #joinmarket 19:05 < grubles> i'm getting a Cannot construct transaction, failed to generate commitment, shutting down. when using sendpayment.py 19:05 < grubles> which i've never seen before 19:19 -!- fqtw_ [~me@x4db12961.dyn.telefonica.de] has quit [Read error: Connection reset by peer] 19:20 -!- fqtw_ [~me@x4db24225.dyn.telefonica.de] has joined #joinmarket 21:44 -!- coins123 [~coins123@unaffiliated/coins123] has quit [Ping timeout: 265 seconds] 21:54 < nkuttler> grubles: trying to spend unconfirmed outputs 21:55 < nkuttler> < waxwing> nkuttler: no need really ; what this shows me is (what should be obvious), that just "can't generate commitment" is no good as a user experience. need to tell the user what the exact situation is: what utxos were tried and why they didn't pass the conditions required. 21:55 < nkuttler> < 5 confirms old, it would tell you that and suggest either (a) wait a while or (b) use add-utxo.py to add an external utxo for commitment. 21:55 < nkuttler> < waxwing> i guess i didn't already do it because it's a bit of a hassle to construct an explanation: you have to show the user all utxos that were tried, first in the transaction, then in the wallet, then external ones if they exist 21:55 < nkuttler> < waxwing> and for each, explain why they were not acceptable. i think i'll put it in a log file, it'll be too much on screen i think (in some cases) 22:04 < grubles> hm they're confirmed though 22:04 < grubles> 35 confirms 22:14 < grubles> 1: Utxos that passed age and size limits, but have been used too many times 22:14 < grubles> it falls under that ^ i suppose 22:44 -!- fqtw_ [~me@x4db24225.dyn.telefonica.de] has quit [Read error: No route to host] 22:44 < gmaxwell> any idea how your utxo ended up overused? 22:45 -!- fqtw_ [~me@x4db24225.dyn.telefonica.de] has joined #joinmarket 22:47 < grubles> i think i first tried sendpayment.py and the tx did not complete 22:50 < grubles> otherwise i have no idea 22:51 < gmaxwell> I was of the belief that it would tolerate up to N reuses where N is some small number like 5. 22:51 < grubles> yeah i think it does 22:52 < grubles> that's what commitments_debug.txt says 22:52 < grubles> wait...no it doesn't 23:05 < grubles> guess i'll try add-utxo.py 23:11 < waxwing> grubles: so it falls under "used too many times" in commitments_debug.txt? 23:11 < grubles> yeah 23:11 < waxwing> but you don't think you tried a transaction 3 times? 23:12 < grubles> no i tried a ton of times 23:13 < grubles> this is a brand new joinmarket wallet too 23:13 < waxwing> ok, makes sense then. what kind of errors were you getting first few times you tried it? 23:13 < grubles> the same one complaining about commitment 23:13 < grubles> "Cannot construct transaction, failed to generate commitment, shutting down. Please read commitments_debug.txt for some information on why this is, and what can be done to remedy it. 23:13 < grubles> " 23:14 < waxwing> if you were getting that in all cases, then it never actually used up any commitments, so that would be weird. 23:16 < waxwing> it would be common to get that when first funding a wallet, simply because < 5 blocks age 23:16 < waxwing> but i don't know why you would get "utxos already used" for a brand new wallet, unless you had at least sent requests into the joinmarket pit (at least 3 times) 23:16 < waxwing> and you will get a lot more than 3 chances if you follow the advice here: https://github.com/JoinMarket-Org/joinmarket/wiki/Sourcing-commitments-for-joins#fund-your-wallet-with-multiple-utxos 23:17 < waxwing> i tried to make a big deal of directing people to read the bolded parts in that doc when we "switched",but it's not good enough, i bet people sometimes don't follow the links to that page and read the bold parts even. 23:18 < waxwing> but, sidetrack, at the moment i can't see how you're getting "used up" if you never sent a request. 23:24 < waxwing> grubles: so did you ever send a request into the pit before you got "used too many times"? 23:24 < grubles> i believe so 23:24 < grubles> i just used sendpayment.py 23:25 < grubles> nothing else 23:25 < waxwing> right, i.e. completely new wallet, completely new addresses 23:26 < waxwing> i have an idea 23:29 < waxwing> grubles: i think it's my error, like this: you tried say 3 times before 5 blocks, and it ended up getting recorded in your commitments.json file even though it was not "used", it was only "tried". 23:30 < grubles> yeah that might be the case 23:30 < waxwing> i guess we could prove it like this: if you have not yet actually sent a request into the pit, just empty the commitments.json file and try again 23:30 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood] 23:30 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #joinmarket 23:30 < grubles> hm ok 23:30 < waxwing> i just looked at the code, i *think* i did this and it's a pretty dreadful mistake :( 23:31 < waxwing> looking more positively, fixing this bug will make it less likely to not work 23:31 < grubles> well at least we found the bug! 23:31 < waxwing> but, it's early here, i'll have to check again in a little while 23:32 < waxwing> grubles: wait, don't delete that file though 23:32 < waxwing> i forgot you might already have stuff in there for other wallets 23:33 < waxwing> just back it up 23:34 < grubles> ok one sec 23:34 < grubles> i restarted -qt with -rescan to see if that helped at all 23:35 < waxwing> yeah i'll be back later, i'd mv cmttools/commitments.json to *.bak then just retry with exact same wallet, i'd bet it'd work then. 23:35 < grubles> ok ill try that 23:35 < grubles> will report back 23:40 -!- coins123 [~coins123@unaffiliated/coins123] has joined #joinmarket