Username: Password:

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - bney

Pages: [1] 2
General Discussion / Re: Insufficient funds on sell
« on: January 27, 2021, 04:53:07 AM »
This may have to do with the error I noticed and dug into and posted above. Kraken is barfing on orders with more than 7 digits to the right of the decimal.
I have opened a ticket with their API  team as it shouldn't be giving an insufficient funds error but Gunbot might also want to limit the number of insignificant digits to 7 or less

General Discussion / Gunbot error on buy with Kraken
« on: January 27, 2021, 04:31:19 AM »
I seem to have found an annoying error in kraken which is preventing Gunbot from buying.

When gunbot attempts to place a buy order for .3781027650841647 eth, Kraken responds with an error 900 Insufficient funds.
I attempted this as a limit order manually and received the same error but it placed the order as well. See attached image.

If I place the same order but for .3781 eth, no error occurs and the order is placed.

While kraken shouldnt be giving that error, its confusing Gunbot. Gunbot should trim off the ridiculous number of insignificant digits. Kraken seems to like 7 or less to the right of the decimal.
While 4 to 5 digits may be significant in Bitcoin, it really isnt in any other coin

General Discussion / Can Gunbot be told to prestage a limit order?
« on: January 05, 2021, 10:06:04 PM »
I have seen a number of times when Gunbot has set a buy point and the price touches and then retreats from that price too quickly for Gunbot to notice and send an order. This happens on both buy and sell. This results in missed opportunities as you can see in the image below where the price went through the buy line then took off upwards. This is especially true in an active pair since gunbot only looks every 30 seconds or so

If Gunbot would simply set a limit order at the price that it has set for buy and/or sell then the exchange would take care of executing the actual order. Orders are easily cancelled prior to execution so I cannot see any technical reason to not do this. Its much sloppier to be sending in market orders as slippage will occur and orders are processed in fifo order so a market order is going to sit at the back of the line behind limit orders increasing slippage

General Discussion / Insufficient funds on sell
« on: January 04, 2021, 09:41:29 PM »
I had a trade today with a trailing stop. When Gunbot attempted to close the order with a sell it kept getting the error below. I manually closed the order on Kraken for good profit but the fact that I manually had to do it is concerning.

Technical Support & Development / Error on Kraken when attempting to sell
« on: January 24, 2020, 02:34:33 PM »
I was wondering why gunbot was not buying or selling as prices passed the sell and buy points.
Today I was watching and caught the following error.

At this point Gunbot is doing nothing useful so I am just manually trading.

I have adjusted mvtb and mvts and is makes no difference. I assume the mvtb and mvts values are setting the amount of the base currency to transact.

General Discussion / Re: Gunbot 16 blows error when attempting to trade.
« on: January 14, 2020, 04:23:24 PM »
I have no reseller. I bought Gunbot directly from Gunthy way back in version 3 days.

On the plus side I took your suggestion and disabled multiple base. That helped.
It still cannot perform a market order but it is able to generate its own orders now without falling over, so thanks for the advise

General Discussion / Re: Gunbot 16 blows error when attempting to trade.
« on: January 14, 2020, 01:44:33 AM »
Further information seems to indicate that its directly related to placing a market order.
Gunbot seems to want a price on a trade type that doesnt need or allow a price.

It would be nice if a developer would respond to this

General Discussion / Re: Gunbot 16 blows error when attempting to trade.
« on: January 13, 2020, 05:38:51 PM »
Gunbot just attempted to sell and blew the following error.
Something seems pretty broken

General Discussion / Re: Gunbot 16 blows error when attempting to trade.
« on: January 13, 2020, 05:01:21 PM »
Attempts to place a market order also blows an error.
It says the price argument is invalid. One doesnt have to put in a price on a market order.

If I place a limit order it works as I provide a price on a limit order.
I would have thought that Gunbot whould know the current price in order to put it into the market order

Image attached.

General Discussion / Gunbot 16 blows error when attempting to trade.
« on: January 12, 2020, 04:02:03 PM »
I am receiving the following when gunbot tries to sell dollars and buy bitcoin.
See attachment

General Discussion / Re: US trader looking for new exhange
« on: October 22, 2019, 04:58:48 PM »
Not polo anymore. It just got sold and is dumping all US customers. Total betrayal of those of us who have been with them for years.

General Discussion / Gunbot should be trading ?
« on: September 10, 2019, 08:38:42 PM »
Based on the attached image, The buy price is 10,180 and the current price is below that. I would think that Gunbot should have done a buy, but it doesnt, it just sits there watching price go up and down. I have set this up according to 'The way Gunther runs it" so I would think it was set up correctly. I am however still trying to figure out the best combination of settings.

Any thoughts or feedback would be welcome

Where is the page storing its working copy of the file. It seems like after the first time, its not possible to import the current file and any modifications I subsequently make manually to it.
It also seems to be duplicating the pairs that I am trading

Running the new software, it suddenly started spitting out the following error.

Error on strategy BB for BTC_XMR on poloniex while getting ema2 -\ Error: undefined is not a function

Not sure if its still going to trade or not. It also looks like the program has restarted itself a couple times.

The bot already has in its little mind a sell price after a buy. If it were to set an order to sell at that price then polo would take care of the trade in the event the bot misses a quick spike. Either way it pushes the sell action onto polo which is fine.

Currently the bot checks every so often to see if the price has reached the buy or sell threshold. If the bot is only checking every couple minutes, it will miss an event that happens during that time. I just had the bot miss the opportunity to sell a coin when a single candle spiked above the sell threshold. The problem was that the price didnt stay up there long enough for Gunbot to notice. If the Gunbot had placed a standing sell order at the sell price, at the time it did the buy, POLO would have executed it regardless of whether the bot is checking or not.

In answer to your question regarding which nix flavor, Im using ubuntu.
I used the following installation script to install the Gunbot and the other things it depends on, specifically node.

Technical Support & Development / Re: Preventing 422 Errors
« on: July 02, 2017, 05:32:49 PM »
It seems that the push approach to updates might also allow the bot to respond faster to short spikes or drops in price which seem to be missed with the poling every couple minutes method. It could then be basically interrupt driven to buy or sell in shorter windows.

Digital ocean doesn't appear to have windows available. They have various nix flavors.

|BTC_DASH |     amount: '0.59106958',
0|BTC_DASH |     total: '0.01388416',
0|BTC_DASH |     fee: '0.00150000',
0|BTC_DASH |     orderNumber: '23128579293',
0|BTC_DASH |     type: 'sell',
0|BTC_DASH |     category: 'exchange' } ]
0|BTC_DASH | Unhandled rejection Error: Bad server answer
0|BTC_DASH |     at Object.console./snapshot/Users/Enrico/Desktop/xBot_v2.9.3/poloniex.js.module.exports.Market.getLastBuyRate.poloniex.returnTradeHistory [as callback] (evalmachine.<anonymous>:0:0)
0|BTC_DASH |     at /snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/async/dist/async.js:2243:31
0|BTC_DASH |     at /snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/async/dist/async.js:906:16
0|BTC_DASH |     at Request._callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/plnx/lib/index.js:138:7)
0|BTC_DASH |     at Request.self.callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:188:22)
0|BTC_DASH |     at emitTwo (events.js:106:13)
0|BTC_DASH |     at Request.emit (events.js:192:7)
0|BTC_DASH |     at Request.<anonymous> (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:1171:10)
0|BTC_DASH |     at emitOne (events.js:96:13)
0|BTC_DASH |     at Request.emit (events.js:189:7)
0|BTC_DASH |     at IncomingMessage.<anonymous> (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:1091:12)
0|BTC_DASH |     at Object.onceWrapper (events.js:291:19)
0|BTC_DASH |     at emitNone (events.js:91:20)
0|BTC_DASH |     at IncomingMessage.emit (events.js:186:7)
0|BTC_DASH |     at endReadableNT (_stream_readable.js:974:12)
0|BTC_DASH |     at _combinedTickCallback (internal/process/next_tick.js:74:11)
0|BTC_DASH |     at process._tickCallback (internal/process/next_tick.js:98:9)
0|BTC_DASH | +
0|BTC_DASH | +
0|BTC_DASH | +

Pages: [1] 2