austinyearlykim/wolf

Repurchase again for the next trade?

Closed this issue · 11 comments

hpduong commented

Thanks for a great script to build on! The script executes properly when I initially run it - it purchases within my set budget, and then after a time it makes the proper sell when an opportunity arises.

But, it never makes another buy after that to repeat the process.
It just continues on with:

Watching watchlist... Orders in watchlist:  0
Consumed queue. Orders in queue: 0

Am I doing something wrong? How can I get it to repurchase again for the next trade?

Thanks!

austinyearlykim commented

Hi @hpduong

Can you do me the hugest of favors and try to see if this continues to happen throughout your day/week and report back here? I'm having trouble seeing why Wolf wouldn't repopulate the queue after a successful sell.

Here is the line that is in charge of purchasing a position again:
https://github.com/austinyearlykim/wolf/blob/master/modules/Wolf.js#L95

Thanks!

hpduong commented
  • 🎉1
austinyearlykim commented

That's so sick! But just to clarify- please restart Wolf if it seems to get stuck as if there's nothing in the watchlist because that means the Wolf cycle is indefinitely stopped. 👍

  • 👍1
hpduong commented

I've run it for ~ 2 days it never repopulated. I just had to stop it and restart it to add to watchlist again.
Longest time it's run on it's own after executing a sell has been ~9 hours with no repurchase.

It looks like it just automatically purchases on a Limit Buy when it's started at any price, so I would expect it to do that again right after a Limit Sell and the Watchlist is empty.

Will look over the code more carefully, too.

Orbitalz-eth commented

Any info on when this bug will be fixed?

austinyearlykim commented

Hi @BatmanPDX,

I am currently working on W.O.L.F locally on my end night-by-night. ETA on this is a little sporadic as these last two weeks, I have been extra busy at work. All it'll take is one full day to test and release, i'm just waiting for that day to show up.

Thanks

Orbitalz-eth commented

Thanks for letting us know.

austinyearlykim commented

@hpduong

I do not have this bug as of v3.4.0.
Please do a git pull on master branch and git reset --hard origin/master.
I did a fresh install of W.O.L.F and used these .env variables:

`
BINANCE_API_KEY=asdfasdfasdfasdf
BINANCE_API_SECRET=asdfasasdfasdfasdf
BUDGET=0.02
PROFIT_PERCENTAGE=.15
TARGET_ASSET=ADA
BASE_ASSET=ETH

#this is a bit complex please view README.md for more info; pick one. not both.
STOP_LOSS_PERCENTAGE=false
STOP_LIMIT_PERCENTAGE=false

#this is a bit complex please view README.md for more info
PROFIT_LOCK_PERCENTAGE=false

#if true, gains will get compounded into the following trade
COMPOUND=false

`

and W.O.L.F purchases, sells, and repurchases just fine....

can you check and see if maybe you overlooked the logs incorrectly? that's my fault for them being a little spammy, i'm going to be tidying them up in the next release.

if you are still running into this issue post here your .env variables!

DONT POST YOUR BINANCE KEYS
DONT POST YOUR BINANCE KEYS
DONT POST YOUR BINANCE KEYS

austinyearlykim commented

I am going to close this issue as this seems to be fixed in the latest releases. Please re-open a ticket with your .env if it continues to happen!

DONT POST YOUR BINANCE KEYS
DONT POST YOUR BINANCE KEYS
DONT POST YOUR BINANCE KEYS
DONT POST YOUR BINANCE KEYS
DONT POST YOUR BINANCE KEYS
DONT POST YOUR BINANCE KEYS
DONT POST YOUR BINANCE KEYS
DONT POST YOUR BINANCE KEYS
DONT POST YOUR BINANCE KEYS

austinyearlykim commented

Nevermind, this is definitely still happening. Will investigate tonight. Seems like the MIN_NOTIONAL error is the culprit. Might be a rounding issue, but raising your BUDGET should be a quick remedy.

austinyearlykim commented

closing this issue as MIN_NOTIONAL error filter from binance is a user & binance problem. Please view #45 for help getting past this error :) W.O.L.F will translate binance errors into a more human readable format in a later version <3