--- Day changed Tue Mar 05 2019 01:17 -!- v_unimportant_pe [~user@45.74.60.136] has quit [Read error: Connection reset by peer] 01:17 -!- v_unimportant_pe [~user@45.74.60.132] has joined #joinmarket 01:27 -!- user_ [~user@45.74.60.131] has joined #joinmarket 01:27 -!- v_unimportant_pe [~user@45.74.60.132] has quit [Read error: Connection reset by peer] 01:34 -!- user_ [~user@45.74.60.131] has quit [Remote host closed the connection] 01:35 -!- user_ [~user@45.74.60.131] has joined #joinmarket 02:49 -!- devachandra [~devachand@vmi179228.contaboserver.net] has joined #joinmarket 02:51 < devachandra> hi! i'm trying to act as a market maker for couple of days, but not having any deals. is there any way to view orderbook, so i can see how i'm positioned comparing to other makers? 03:08 < belcher> devachandra run the ob-watcher script which allows you to see the orderbook 03:09 -!- devachandra [~devachand@vmi179228.contaboserver.net] has quit [Ping timeout: 245 seconds] 03:12 -!- devachandra [~devachand@vmi179228.contaboserver.net] has joined #joinmarket 03:25 < Sentineo> hm there is such script?, good to know :P 06:06 -!- undeath [~undeath@hashcat/team/undeath] has joined #joinmarket 06:36 < belcher> it should be more documented i guess 06:58 < devachandra> looks like i missed something during irc disconnect 07:03 -!- belcher_ [~user@unaffiliated/belcher] has quit [Ping timeout: 255 seconds] 07:14 < belcher> nope * devachandra has quit (Ping timeout: 245 seconds) * devachandra (~devachand@vmi179228.contaboserver.net) has joined 07:29 < belcher> https://en.bitcoin.it/wiki/JoinMarket#Orderbook_watcher 07:37 -!- belcher_ [~user@unaffiliated/belcher] has joined #joinmarket 07:50 < devachandra> thx 07:50 < devachandra> yeah this single line doesn't help much 07:51 < devachandra> have to dig more 08:15 < devachandra> got it working 08:15 < devachandra> it's a script scripts/obwatch/ob-watcher.py 08:16 < devachandra> for it to work i had to put joinmarket.cfg up to the root directory of joinmarket-clientserver 08:16 < devachandra> and put orderbook.html from obwatch directory up to scripts directory 08:44 < waxwing> devachandra, you should run it from within the obwatch directory, then it'll take the config from the directory up (expected that you'd have that already from running scripts) 08:44 < waxwing> sorry that wasn't obvious 08:45 < waxwing> also sorry that nobody ever got round to the job of putting configuration in ~/.joinmarket, much saner that way. 09:11 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 09:11 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #joinmarket 09:20 < waxwing> undeath, i don't think it stops the reactor does it? it stops the protocol factory and presumably the protocol instance. if it stopped the reactor then the script would quit but it hangs. 09:21 < undeath> oh, possible 09:21 < waxwing> (talking about pre-236 of course) 09:21 < waxwing> functionally, though, yes, things shut down. this is a bit like the other open PR, in that i'm really not exactly sure what we want. 09:22 < undeath> belcher does have some valid concerns 09:23 < belcher> which concerns? 09:23 < waxwing> we're talking about #236 09:23 < undeath> the ones you voiced in #236 09:24 < undeath> generic exception handler 09:24 < belcher> oh yes 09:24 < waxwing> yeah it's pretty clear what we certainly do want: preventing crashes or corruption from external input. you could even argue for the added generic exception handling to *force* a shutdown, rather than prevent it. 09:25 < waxwing> at the moment you get an effective shutdown (protocol instances shut off) but it's messy and the error message isn't helpful to the user. 09:25 < undeath> yeah, or somehow signal to the daemon that things went wrong and it should reset its state 09:27 < waxwing> you're right that the maker is intended to be stateless, but an uncaught exception should probably shut stuff off, for conservatism's sake. 09:28 < undeath> idk, an exception that is handled properly isn't bad 09:28 < waxwing> it's true we have the atomicity of coinjoin on our side, so it's not really possible to lose money except in a small area of program logic. it won't happen because of network messups etc. like it can in other more advanced protocols. 09:31 < undeath> allowing makers to crash means we are very vulnerable against someone evil who can mount a very cheap sybil attack 09:31 < undeath> crashing all legit makers in the market would be a matter of seconds 09:33 < waxwing> undeath, yes. that's the other side of the argument, i'm just not sure it wins. i guess the heart of the question is: is it possible to cause some kind of internal consistency by triggering an exception in one protocol instance? i guess not, but ... 09:33 < waxwing> hang on, don't think i mean protocol instance. txs in parallel. 11:25 -!- undeath [~undeath@hashcat/team/undeath] has quit [Quit: WeeChat 2.3] 16:03 -!- deafboy [quasselcor@cicolina.org] has quit [Remote host closed the connection] 16:05 -!- deafboy [quasselcor@cicolina.org] has joined #joinmarket 16:29 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has quit [Remote host closed the connection] 17:08 -!- AgoraRelay [~jmrelayfn@p5DE4AEDA.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds] 17:25 -!- AgoraRelay [~jmrelayfn@p5DE4AD15.dip0.t-ipconnect.de] has joined #joinmarket 17:29 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has joined #joinmarket 19:42 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #joinmarket 23:34 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 240 seconds]