[TLLP Bug] Order Match True

Nagalim 2015-07-24 17:57:48 UTC #1

Are other pools having issues with this? I know I have ordermatch set to true, but my bot still gets hung up when an order is placed outside my spread.

woolly_sammoth 2015-07-25 20:23:06 UTC #2

I’ve not seen this myself. I just never have sufficient funds to clear any blocking order.
I’ll take a look though and see if anything obvious occurs to me.

Nagalim 2015-07-25 22:38:37 UTC #3

Yah, on Bter people will put up a very small order and then the btc price moves and suddenly that order is outside my spread. My bot then gets hung up on tiny little orders, like $0.05.

masterOfDisaster 2015-07-28 06:44:59 UTC #4

Haven’t experience that. So I can’t give you details (bad news).
But this might be related to something else I’d like to report (good news!).
I’ve switched all my TLLP bot operations to https://github.com/Nagalim/nu-pool/archive/master.zip
I let my TLLP bots run unattended and only check once in a while since I realized that the automatic reset works great.

# Sets time (in hours) between bot resets. [bug fixer]
restime = 1.00

So I might simply not have recognized the bugs related to order matches. I can dig the logs, though. What am I looking for? What string in the log is significant for this bug?

Nagalim 2015-07-28 12:21:14 UTC #5

Something like “match found at”. However, you won’t find them on the cny not, they come about when the btc price changes such that a third party order that was on the books is now outside the spread.

My issue is that I keep reading the code and I can’t see why it wouldn’t work. Anyway, with an active market this shouldn’t even be a problem, so I’ll keep an eye on it but we shouldn’t spend too much attention on it.

woolly_sammoth 2015-07-28 12:26:49 UTC #6

I had a brief look at this last night. I think it’s not getting picked up because it is the last of three conditions in an if/elif/elif block.
I think that one of the previous conditions is always getting triggered before the check to see if oderMatch is true.
moving the orderMatch check to be the first condition should fix that without impacting any of the other checks when orderMatch is false.
Hope that makes sense. I have a few more edits to sort out and then will be pushing the code to github so you can grab it from there.

masterOfDisaster 2015-07-28 13:50:44 UTC #7

I grep’ed all (nupond NBT/CNY) logs for “match” and didn’t have any match
The logs only reach back 10 days, because I deleted the old ones.

“matching order at” would be the string to search for.
I’ve found matches in the logs of the nupond BTC/NBT pair.
I tried that TLLP pool only for a short time and stopped, because there already was too much liquidity in this pair:

 grep -i "decreasing tier 1" /home/pi/nupondBTC/unix/nupond/logs/1437244769.log
2015/07/18-20:40:50 INFO: decreasing tier 1 bid limit of btc on bter from 250.00000000 to 125.00000000
2015/07/18-20:41:49 INFO: decreasing tier 1 bid limit of btc on bter from 125.00000000 to 63.67924528
2015/07/18-20:42:49 INFO: decreasing tier 1 bid limit of btc on bter from 63.67924528 to 54.27619377
2015/07/18-20:43:48 INFO: decreasing tier 1 bid limit of btc on bter from 54.27619377 to 48.84857439
2015/07/18-20:44:51 INFO: decreasing tier 1 bid limit of btc on bter from 48.84857439 to 43.96371695
2015/07/18-21:08:32 INFO: decreasing tier 1 bid limit of btc on bter from 52.96371695 to 34.44562283
2015/07/18-21:09:32 INFO: decreasing tier 1 bid limit of btc on bter from 34.44562282 to 26.10307271
2015/07/18-21:10:32 INFO: decreasing tier 1 bid limit of btc on bter from 26.10307270 to 21.16744922
2015/07/18-21:11:32 INFO: decreasing tier 1 bid limit of btc on bter from 21.16744921 to 17.86276860
2015/07/18-21:12:32 INFO: decreasing tier 1 bid limit of btc on bter from 17.86276859 to 15.48036581
2015/07/18-21:15:32 INFO: decreasing tier 1 bid limit of btc on bter from 15.48036581 to 13.67502156
2015/07/18-21:16:32 INFO: decreasing tier 1 bid limit of btc on bter from 13.67502156 to 12.25656172
2015/07/18-21:17:32 INFO: decreasing tier 1 bid limit of btc on bter from 12.25656171 to 11.03090554
2015/07/18-21:18:32 INFO: decreasing tier 1 bid limit of btc on bter from 11.03090553 to 9.92781498
2015/07/18-21:20:33 INFO: decreasing tier 1 bid limit of btc on bter from 11.03090553 to 9.92781498
2015/07/18-21:21:32 INFO: decreasing tier 1 bid limit of btc on bter from 9.92781497 to 8.93503347
2015/07/18-21:22:32 INFO: decreasing tier 1 bid limit of btc on bter from 8.93503347 to 8.04153012

If there might be helpful information in the logs, I would be glad to share them with you.
I’ll gladly upload it, if you provide me with a place, where I have SFTP/SCP access or can try to send it via PM.
Pasting it here in the thread would clog it up.

With the new nupond conditions, I might try BTC/NBT again