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 - zicots

Pages: [1] 2
What's the proper format for TV alerts for gunthy futures exchange?  Like this, to open a short on ETH using USDT base?


Or is it something else?  I get an error with that format, attached.  thank you!

Bump?  Kucoin is a listed supported exchange, and tradingview alerts is advertised as supported.  I imagine I'm doing something incorrect here, but everything is basic preset settings with tradingview alerts for buy.  It works for some pairs fine, such as USDT-ETH or USDT-BTC, sometimes USDT-LTC works.. but other pairs don't work at all.

Is there anybody I can ask for help or even like pay money for help?  At this point my reseller is puzzled, and I'd just like to be able to use features that are advertised.  thanks!

Hey there,

I am having an issue with tradingview alerts for kucoin spot orders.  I asked my reseller and they looked over everything and have no idea why it isn't working properly as it is setup right.

Has anyone seen these, and can resolve?  If not, can it please be forwarded to the development team?  Kucoin is a supported exchange, and tradingview is an advertised feature for supported exchanges.  I just really want to get this to work and figure it out, thanks for all help.

These attached pictures are the errors being displayed when Gunbot recieves a tradingview signal and fails to buy.  It fails for every pair, giving the same error every time.

Resolved this, but have another problem.

ByBit won't work for some reason, can someone look over this please and try and see what the error says and how to fix it?  It gets the order, but then has an error afterwards.  Please help :).

Beginners & Help / Re: long and short syntax for Bybit
« on: December 29, 2021, 02:31:25 AM »
The syntax is like this:

to open a USDT-BTC long perp futures


for a short


Hello, just as the title says.  I want to trade perpetual futures pairs through Okex in gunbot.  I have gunbot all setup with the okex5 API key, it's set to swaps, but when I go to enter a trading pair, the only ones it brings up are their futures (weeklies, monthlies, quarterlys etc).

It says in the wiki its possible to trade perpetual futures pairs through Okex on gunbot.  Is there a resource that shows the syntax for typing in the pairs that you want to use?


See below.

General Discussion / Re: KuCoin Futures/Margin Support?
« on: December 20, 2021, 11:23:04 PM »
Not yet.

Any upcoming news, or reason as to why it hasn't been supported yet?  I know KuCoin is only growing in it's usage levels and userbase.

By the way this was finally solved.

The cause for this error was because the min vol to buy and min vol to sell settings were set to the same integer.  Once they were changed to different integers/values, the problem ceased entirely.

Beginners & Help / Where to See Results of StepGrid style Strategies?
« on: November 14, 2021, 11:47:11 PM »
Just as the topic says, anywhere to see Results of StepGrid style Strategies or the most profitable strategies people share?  I've got a pretty good one setup between BB/RSI confirming indicator I've fined tuned for a compounding 1% trading style, but I would love to employ multiple strategies.  Thanks yall!

Technical Support & Development / Re: KuCoin cant connect !
« on: November 07, 2021, 07:50:24 PM »
Yeah your API pass phrase is separate from your KuCoin login password, maybe you entered your login password?

Check the API page and it will show you your API pass phrase.

General Discussion / Re: KuCoin Futures/Margin Support?
« on: November 07, 2021, 04:24:36 AM »
Is there any plans to support KuCoin Futures or margins one day?  I'd love to be able to use Kucoin futures if thats at all possible.

Yes, it's something that is being worked on and it should be ready soon.

Hey Aitor,

Any news on the update of Kucoin Futures being supported :)?

General Discussion / Re: US trader looking for new exhange
« on: August 15, 2021, 09:52:51 PM »
KuCoin 100% of the way.  You can even use their 3x leveraged tokens without liquidation risks to do futures on the same way a normal token would work, buy low sell high, even with the shorts.  its just the way the tokens function over there. cant do futures fully currently before kucoin futures is supported, which is in the works apparently.  They have every token I want to buy, and like 75% at least if not more of the top 100 CMC.

General Discussion / Re: KuCoin Futures/Margin Support?
« on: August 15, 2021, 09:50:28 PM »
Is there any plans to support KuCoin Futures or margins one day?  I'd love to be able to use Kucoin futures if thats at all possible.

Yes, it's something that is being worked on and it should be ready soon.

YAY!!!!!  This literally reinforces so much my decision to have upgraded my gunbot license, once this comes out, it will have been money well spent.  Any estimates at this point?  Thank you!!!!!

General Discussion / KuCoin Futures/Margin Support?
« on: June 07, 2021, 03:55:55 AM »
Is there any plans to support KuCoin Futures or margins one day?  I'd love to be able to use Kucoin futures if thats at all possible.

I know they have their own API key, but can you already do futures with that on Kucoin?  Thanks for all answers!


Fixed, had to add the API and exchange to edit license tab.  Doh!

Hello all, so I just upgraded to PRO so I can run three exchanges.  I have been currently running KuCoin spot trading with great success.  Now I want to add BinanceFutures as another exchange.  The only problem is after adding the exchange and creating a pair to use it, when I save changes the entire system crashes and the Terminal readout gives me this error "Invalid License for Binance - Please Contact Support! Error Message in Terminal".  This doesn't make any sense as the terminal shows I have PRO, and heck, even STANDARD can run futures.  I tried adding plain old Binance, and I get the exact same error.  My license will not allow me to connect to Binance. 

Yes, I have contacted my reseller, and they're amazing at helping, but they are searching for an answer as they don't understand why my license is giving this error, when it shouldn't.  So we are trying to utilize all resources possible.  I appreciate all help.

The attached image is the error for BinanceUS, but BinanceFutures gives the exact same error, just reading BinanceFutures instead of BinanceUS obviously.

The bug you are describing happens in v22.0
Fixed on v22.0.1 beta. If you don't have access to it, send me a PM and I will point you.

PM'ed.  I tried download v22.0.1 and have it running.  It doesn't seem to fix the problem with the trades that aren't being followed that were in progress before running it and upgrading, but hopefully any new trade it starts it has no issue with.

Technical Support & Development / Re: Kucoin error
« on: May 26, 2021, 06:00:15 PM »
Yes do a fresh install of v22, and set it up from scratch based on your old strategies and pairs.  The earlier version had an error for KuCoin that everyone ran into that was solved via v22.

For those TypeError you are having, are you using one of the HFT alpha's?  Because I get the same error trying to use the new alphas in Unix environments and nothing works trying to debug it.  Stick with v22 from the github for now.

Thank you.  We are in contact, he's super smart and incredibly helpful, but we still can't figure it out.  What I've found is that I believe the core is having an issue.  The active trades that aren't being followed anymore are giving all NO readouts in the core where it can DCA, buy, sell, etc.  The active trades that are being followed have YES in those readouts where it should.

See how in the screenshot, the DOGE-BTC pair has a YES where it could possibly DCA?  The active pairs that are suddenly not followed, are giving all NO in that section.  So perhaps this is a core issue?  It tends to happen when I "Save Changes" and change a paramater such as DCA buydown (changing it from 4% to 2%) triggered a few pairs to be unfollowed once the changes were saved.  As well, sometimes they just randomly get unfollowed as they are status checked by the core (aka when the Terminal checks the pair and sees what it can do).  So maybe it's  a loss of connection between the core and pairs?

Pages: [1] 2