--- Day changed Wed Apr 05 2017
00:04 -!- juscamarena [~justin@47.148.176.74] has quit [Remote host closed the connection]     
00:05 -!- juscamarena [~justin@47.148.176.74] has joined #joinmarket     
00:26 -!- waxwing [~waxwing@185.65.134.77] has quit [Ping timeout: 268 seconds]     
00:37 -!- waxwing [~waxwing@185.65.134.77] has joined #joinmarket     
03:26 -!- waxwing [~waxwing@185.65.134.77] has quit [Ping timeout: 268 seconds]     
03:41 -!- waxwing [~waxwing@62.205.214.125] has joined #joinmarket     
03:50 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Ping timeout: 264 seconds]     
03:59 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #joinmarket     
04:00 -!- MaxSan [~one@185.104.184.43] has joined #joinmarket     
04:02 -!- MaxSan [~one@185.104.184.43] has quit [Client Quit]     
05:19 -!- King_Rex [~King_Rex@unaffiliated/king-rex/x-3258444] has joined #joinmarket     
05:38 -!- jm-lover [5ef2de6e@gateway/web/freenode/ip.94.242.222.110] has joined #joinmarket     
05:38 < jm-lover> hello guys
05:38 < jm-lover> i am trying to make a join for the last 72 hours but none of the bots ever responded
05:39 < jm-lover> join amount is about 3 btc
05:39 < jm-lover> are there liquidity issues?
05:39 < jm-lover> i never had any problem before with amount up to 0.5 btc
05:39 -!- ananteris [~user@unaffiliated/ananteris] has quit [Remote host closed the connection]     
05:39 < jm-lover> it now says to me [TimeoutThrea] [ERROR]  ERROR not enough liquidity in the orderbook, exiting
05:42 < adlai> that's odd
05:44 < adlai> jm-lover: according to http://joinmarket.io/ there are several bots at this size, does your taker see them?
05:44 < waxwing> yeah that is odd, i agree
05:45 < waxwing> https://joinmarket.me/ob/ back up as of a minute ago, VPS really giving me troubles for some reason. keeps going down.
05:45 < jm-lover> i will not try to queue and see all orderbook
05:45 < waxwing> maybe some IRC problem? no log messages complaining about connecting or something?
05:46 < waxwing> i noticed some troubles connecting to Cgan yesterday, or the day before.
05:46 < jm-lover> i get "connecting to host agora.anarplex.net14716"
05:46 < jm-lover> then Connected to IRC and joined channel on agora-irc
05:47 < jm-lover> then i see suggested makers and hit yes
05:47 < jm-lover> and at this point it stops every time "Connected to IRC and joined channel on agora-irc"
05:47 < jm-lover> sorry, on this "waiting for all replies.. timeout=45"
05:48 < jm-lover> after timeout is says
05:48 < jm-lover> timeout thread woken by timeout, makers didnt respond. nonresponding makers...Too few makers responded to complete, trying again.
05:49 < jm-lover> if i hit YES again it goes in the same say and if I hit now it says: ERROR not enough liquidity in the orderbook, exiting. Shutting down all connections
05:49 < waxwing> jm-lover: did you change any config variables? are you using latest release, or latest on develop branch, also after that we might need to look at a scrubbed log.
05:50 < jm-lover> i changed log to allow only one server agora.anarplex.net
05:51 < jm-lover> version,,,trying to find
05:52 < waxwing> jm-lover: ok; you didn't change the taker_utxo_age etc settings at the bottom of the config?
05:53 < waxwing> hmm we should have a version message for the scripts. there is a version variable but it's not specific. did you download the release, or from master, in the last 3-4 months? or perhaps using develop branch?
05:53 < waxwing> (this stuff is just for background info
05:54 < jm-lover> there is no any version trace neither in readme`s nor in scripts initializations. i downloaded form github 2 months ago
05:54 < waxwing> ok it's fine then.
05:54 < waxwing> so my Q about config above? ^  that's important, it can cause spurious failures if you change those settings.
05:55 < jm-lover> one second
05:55 < waxwing> if it's not that, i'm leaning towards IRC level weirdness, but in that case would def need you to run scrub-log.py and pastebin a log.
05:56 < waxwing> for example, want to see if you're receiving !pubkey messages from counterparties.
05:56 < jm-lover> taker_utxo_age has never been changed, the age is okay ... 5++
05:57 < waxwing> good, that one's crossed off the list then.
05:57 < jm-lover> i only updated taker_utxo_retries when I exhausted all attempts. but the behaviour is abssolutley the same
05:57 < jm-lover> i guess it cannot be a problem
05:57 < waxwing> oh you changed that? that can cause problems, yes.
05:58 < waxwing> basically, you have used utxo U 3 times, but your code now allows you to try a 4th. but the counterparties do not allow it, they just ignore you.
05:58 < jm-lover> yes i changed. but as I said all first 6 attempts (2 utxos) gave the same results
05:58 < waxwing> i see. well but that complicates the scenario. can you find the log file of the first 6 (any of them) before you changed it?
05:59 < jm-lover> no sorry. i can resend to a new mixdepth and retry 
05:59 < waxwing> and scrub that and pastebin it.
05:59 < waxwing> yes that's a decent option.
05:59 < waxwing> also, are you sweeping?
05:59 < jm-lover> no     
06:00 < waxwing> ok, good, then it's less likely to go wrong.
06:00 < waxwing> try with N ~5 at least (makes it very unlikely to get blocked if N is high, or should do)
06:00 < jm-lover> can you explain a little bit what does it mean "scrub that and pastebin it" ?
06:01 < waxwing> jm-lover: see in the logs/ directory there's a script scrub-log.py , you run it with the log name as the first argument.
06:01 < waxwing> then it removes all private data like amounts and txids
06:01 < jm-lover> ah ok
06:02 < jm-lover> i will need btw to wait 5 confirmation when moving betweem mixdepths?
06:02 < waxwing> yes if you want to use the new utxos for commitments (and in this case, you do)
06:02 < waxwing> and reset the config var ofc
06:03 < waxwing> you can also add external commitments if you want. but more hassle of course.
06:11 < jm-lover> waitinf for confirmations. will get back here later, thanks so much for the support
06:12 -!- jm-lover [5ef2de6e@gateway/web/freenode/ip.94.242.222.110] has quit [Quit: Page closed]     
06:27 -!- Cory [~Cory@unaffiliated/cory] has quit [Ping timeout: 240 seconds]     
06:32 -!- Pasha [~Cory@unaffiliated/cory] has joined #joinmarket     
06:35 -!- Pasha is now known as Cory     
07:01 -!- MaxSan [~one@185.104.184.43] has joined #joinmarket     
08:44 < MaxSan> hmmm
08:44 < MaxSan> this doesnt support ummm
08:44 < MaxSan> multiple outputs yet does it?
08:44 < MaxSan> on a sendpayment.py command
09:52 -!- Giszmo [~leo@pc-240-13-215-201.cm.vtr.net] has joined #joinmarket     
10:16 < waxwing> MaxSan: no, it doesn't.
10:19 < MaxSan> also... is there any issue using multisg addressses when sending out coins?
10:20 < MaxSan> waxwing:  ^^
10:20 < waxwing> MaxSan: sure, unfortunately there is; if you are the only multisig output, it flags yours as special. yieldgenerators use p2pkh only.
10:21 < waxwing> there was a vague intent to move everything to p2sh, but it fits most naturally with moving to segwit.
10:21 < MaxSan> yeah was thinking this earlier when looking at numbers
10:21 < MaxSan> so joins will all be on segwit addresses?
10:22 < MaxSan> I would love it if you and belcher could compile and a sign a UASF build with BIP148
10:22 < MaxSan> That would be great
10:22 < MaxSan> afaik you dont work on core but you make a product that is well used and both have major props for your work an the money that rests on it
10:23 < waxwing> one way the move could happen is a new offertype !swrel/absoffer and then those txs are p2sh only (p2sh/p2wpkh, that's how i worked up the preliminary trial last year, that's the most logical way)
10:23 < waxwing> MaxSan: i was looking at it today/yesterday; i built and started running it, but i dunno it seems like they're still talking about details. i'm not the expert, i guess i'll follow the lead of others on that.
10:24 < MaxSan> i cant get it to build
10:24 < MaxSan> im happyt for the 1st august flag day
10:24 < waxwing> can you build bitcoin normally?
10:24 < MaxSan> got some compile issues with something
10:24 < MaxSan> cant mind now
10:24 < waxwing> it isn't meaningfully different. but anyway, i don't see a point in rushing forwards on that right now.
10:25 < MaxSan> might take another look tonight
10:25 < waxwing> users shouldn't have to build random patches anyway. have to be cautious.
10:25 < MaxSan> very true
10:26 < MaxSan> I just feel if its seen in the wild.. more people are likely to go for this generally
10:30 < waxwing> MaxSan: try the uasf channel on bitcoin core slack. same discussion being had there on and off.
10:30 < waxwing> (you can connect via irc, i do)
10:39 < MaxSan> oh, how?
10:39 < MaxSan> what is the room
10:40 < waxwing> it's something like: bitcoincore.slack.com, get invite, register, then go to their help page and it tells you the irc server/port and you generate an initial password.
10:41 < waxwing> and yeah channel uasf is the one i meant
10:41 < waxwing> port is 6667 *but* use ssl
12:41 -!- xc0der [sid219441@gateway/web/irccloud.com/x-okobxsfpejvpexgt] has quit []     
13:04 -!- wumpus [~quassel@pdpc/supporter/professional/wumpus] has quit [Quit: No Ping reply in 180 seconds.]     
13:06 -!- wumpus [~quassel@pdpc/supporter/professional/wumpus] has joined #joinmarket     
13:11 -!- takamatsu [~takamatsu@unaffiliated/takamatsu] has quit [Quit: (┛◉Д◉)┛┻━┻]     
15:32 -!- MaxSan [~one@185.104.184.43] has quit [Quit: Leaving.]     
16:23 -!- K1NGREX [~King_Rex@unaffiliated/king-rex/x-3258444] has joined #joinmarket     
16:25 -!- King_Rex [~King_Rex@unaffiliated/king-rex/x-3258444] has quit [Ping timeout: 240 seconds]     
16:56 -!- K1773R [~K1773R@unaffiliated/k1773r] has quit [Ping timeout: 264 seconds]     
17:14 -!- cbits [~cbits@2607:f380:a61:650:2901:d2ee:c675:e83e] has joined #joinmarket     
17:15 < belcher_> pgp the head of bitfinex just joined the UASF channel on slack...
17:16 < belcher_> agreed that someone releasing binaries are not the right way to do it, UASF has to happen with a lot of the economy agreeing to do it
17:17 < belcher_> so instead, try to get people in your local group involved, if you trade with exchanges, otc traders, marketplaces, etc talk to them about UASF and ask if they would enforce it if everybody else enforced it
17:17 < belcher_> thats the hard part, writing and compiling the code is trivial in comparison
17:45 -!- cbits [~cbits@2607:f380:a61:650:2901:d2ee:c675:e83e] has quit [Ping timeout: 246 seconds]     
17:52 -!- cbits [~cbits@2607:f380:a61:650:4063:141d:863c:f7fe] has joined #joinmarket     
18:02 -!- cbits_ [~cbits@2607:f380:a61:650:9c67:a897:6e8c:89b7] has joined #joinmarket     
18:06 -!- cbits [~cbits@2607:f380:a61:650:4063:141d:863c:f7fe] has quit [Ping timeout: 246 seconds]     
18:24 -!- cbits_ [~cbits@2607:f380:a61:650:9c67:a897:6e8c:89b7] has quit [Read error: Connection reset by peer]     
18:24 -!- cbits [~cbits@2607:f380:a61:650:9c67:a897:6e8c:89b7] has joined #joinmarket     
18:33 -!- Giszmo [~leo@pc-240-13-215-201.cm.vtr.net] has quit [Quit: Leaving.]     
19:14 -!- cbits [~cbits@2607:f380:a61:650:9c67:a897:6e8c:89b7] has quit [Ping timeout: 246 seconds]     
20:26 -!- K1NGREX [~King_Rex@unaffiliated/king-rex/x-3258444] has quit [Remote host closed the connection]     
22:57 -!- juscamarena [~justin@47.148.176.74] has quit [Remote host closed the connection]     
22:58 -!- cbits [~cbits@47.148.176.74] has joined #joinmarket     
23:04 -!- juscamarena [~justin@47.148.176.74] has joined #joinmarket     
23:48 -!- cbits_ [~cbits@47.148.176.74] has joined #joinmarket     
23:49 -!- juscamarena [~justin@47.148.176.74] has quit [Ping timeout: 260 seconds]     
23:49 -!- cbits [~cbits@47.148.176.74] has quit [Ping timeout: 240 seconds]     
23:49 -!- juscamarena [~justin@47.148.176.74] has joined #joinmarket     
23:52 -!- cbits [~cbits@47.148.176.74] has joined #joinmarket     
23:55 -!- cbits_ [~cbits@47.148.176.74] has quit [Ping timeout: 256 seconds]     
23:59 -!- K1773R [~K1773R@unaffiliated/k1773r] has joined #joinmarket