-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Arby improving suggestions #16
Comments
if there is no real removal/creation then it should be:
|
For now it is uncontrollable container that starts order placing when see balance in the channel. |
Good idea, but I would rather let xud ctl take care of that: warn & educate user before starting. Offer a command to stop it etc. |
|
Marked above as done, it has its own P1 issue and will be done asap: #17 |
I think we should tackle this one in course of this issue next:
|
Arby is in alpha state now and looks unfinished. So, here you can offer any improvement for discussion.
if invalid creds are passed to arby, status command should contain message about that, also logs of arby should contain error about bad creds and maybe container should finish work with another exit code (not 0).
Add info rder that was sent to binance + also i want to see info about binance fill.
Maybe it would be better to do not print same price twice or move printing all prices to lower debug level.
bestBid and bestAsk monitoring looks like more correct solution then last trade monitoring.
Current behavior can be destructive if price will move significantly after binance order placement, if I understood correctly. OpenDex update was stopped by placed but not filled order, so xud node will contain orders with tasty prices.
Orders should be canceled if Arby completes its work (for example, because of empty channel of shutting down by user)
arby is using
replace_order_id
when issuing new orders, right? I am confused by local xud/arby logs sayingremoved order
and creating new orders, but but there were no remova p2p packets. In that case, I'd remove this arby log statement since it's confusing:[OpenDEX] trace: Removed all open orders for ETH/BTC
The text was updated successfully, but these errors were encountered: