Topic: 【BOT】 🌟 C.A.T. Cryptocurrency Automatic Trader 🌟 (New Price List 04/2021) - page 80. (Read 531503 times)
August 09, 2017, 06:22:57 PM
what would be the current price for hitbtc? and is there a version to try on one of the free api exchanges before purchase?
August 09, 2017, 05:18:48 PM
In which order are Price Limit rules applied? Is it possible to give them a priority?
For example, if the first rules matches than CAT stops there, otherwise CAT processes the second rule and so on.
For example, I have a situation where I don't want the ping buy price to be lower than X, and also the ping buy price be higher then last pong sell price - x%. I want the first rules to have priority over the second.
For example, if the first rules matches than CAT stops there, otherwise CAT processes the second rule and so on.
For example, I have a situation where I don't want the ping buy price to be lower than X, and also the ping buy price be higher then last pong sell price - x%. I want the first rules to have priority over the second.
Limit conditions are in OR relationship.
Rule1 OR Rule2 OR Rule3......
OR is commutative, so you don't need to set a priority.
August 09, 2017, 05:12:56 PM
In which order are Price Limit rules applied? Is it possible to give them a priority?
For example, if the first rules matches than CAT stops there, otherwise CAT processes the second rule and so on.
For example, I have a situation where I don't want the ping buy price to be lower than X, and also the ping buy price be higher then last pong sell price - x%. I want the first rules to have priority over the second.
For example, if the first rules matches than CAT stops there, otherwise CAT processes the second rule and so on.
For example, I have a situation where I don't want the ping buy price to be lower than X, and also the ping buy price be higher then last pong sell price - x%. I want the first rules to have priority over the second.
August 08, 2017, 11:36:55 AM
I am lost.
I am getting too many zombies in both versions.
Where do I find the setting in 5.0 and 5.1?
What is the risk?
I am getting too many zombies in both versions.
Where do I find the setting in 5.0 and 5.1?
What is the risk?
yes that is the option, change the check in the first option, set "Currenct order qty vs previous qty"
Risk is (as i explained in my previous post) that there's an error on Exchange System and NO real trade occur (but order is no more returned by the api system, this is the anomaly).
So CAT will create a pong based on a trade that wasn't happens.
This is the risk. But i hope that, when order is not returned by Yobit is because a trade occurs AND the Api Call "MyTrade" is not updated.
August 08, 2017, 11:33:07 AM
I am lost.
I am getting too many zombies in both versions.
Where do I find the setting in 5.0 and 5.1?
What is the risk?
I am getting too many zombies in both versions.
Where do I find the setting in 5.0 and 5.1?
What is the risk?
August 08, 2017, 06:31:24 AM
Hi may i know whats the current price of this bot?
Hi, pm me with the list of API you wants to activate and i will calculate your final price
August 08, 2017, 06:30:06 AM
How do I avoid cat getting a zombie status on a market that conducted a trade?
I emailed you the log.
There is a 5.2? I switched to 5.0 from 5.1 as I didnt do anything else but restoring red markets all day long.
I emailed you the log.
There is a 5.2? I switched to 5.0 from 5.1 as I didnt do anything else but restoring red markets all day long.
firsr try to follow what i wrote here : https://bitcointalksearch.org/topic/m.20700013 let's see if it works.
It's important also that you understand what the problem is and why it's correct that CAT returns an error and eventually zombie status.
My solution could solve the problem, but it's risky.
August 08, 2017, 01:59:18 AM
Hi may i know whats the current price of this bot?
August 07, 2017, 11:25:06 PM
How do I avoid cat getting a zombie status on a market that conducted a trade?
I emailed you the log.
There is a 5.2? I switched to 5.0 from 5.1 as I didnt do anything else but restoring red markets all day long.
I emailed you the log.
There is a 5.2? I switched to 5.0 from 5.1 as I didnt do anything else but restoring red markets all day long.
August 07, 2017, 05:57:59 PM
@Su100
As i can see from the image you're trading on Yobit.
If you open one zombie log (i mean you open the txt file from CAT_5.2\CATSystem\YoBit\MarketLogs) and search for "****" String you will find all the (Managed) Error that occurs.
Errors written this way
***************
* ERROR *
***************
Are usually bad errors that comes from an unexpected behaviour from the exchange.
You will probably find that The Order is not more available on the exchange AND no trade is found.
Example :
You place an order SELL 100@X
CAT search for this order every lookup and search for trades over this order every lookup
If a trade is found then a pong is created.
If the sum of trades is = order Qty then the order if full close.
BUT what happens if
- Order is no more on the exchange
AND
- No Trade is found?
this is an anomaly on server side because when exchange works good you will have all the trades related to an order and when the order is no more available it means that a final trade occured.
There's a solution, but it's risky :
- Change the ADVANCED OPTION : Find Trades Using Current Order QTY VS Previous (DEfault on yobit is My Trades Api Call).
This way, CAT will works only using Order Current QTY VS Previous QTY and if this value changes then it will automatically consider a Trade event.
this is risky because when exchanges offer the API call "MyTrades" it should not happens that order is no more active but no trades happens.
So the risk is that no trade occurs on the exchange but you tell cat "consider the fact that order is no more available as a final trade".
This could avoid a lot of zombie status. Especially when exchange api system gives problems like this one.
Let me know if it works.
If you want just send me 2-3 zombie logs and i will verify what happens.
Thanks
As i can see from the image you're trading on Yobit.
If you open one zombie log (i mean you open the txt file from CAT_5.2\CATSystem\YoBit\MarketLogs) and search for "****" String you will find all the (Managed) Error that occurs.
Errors written this way
***************
* ERROR *
***************
Are usually bad errors that comes from an unexpected behaviour from the exchange.
You will probably find that The Order is not more available on the exchange AND no trade is found.
Example :
You place an order SELL 100@X
CAT search for this order every lookup and search for trades over this order every lookup
If a trade is found then a pong is created.
If the sum of trades is = order Qty then the order if full close.
BUT what happens if
- Order is no more on the exchange
AND
- No Trade is found?
this is an anomaly on server side because when exchange works good you will have all the trades related to an order and when the order is no more available it means that a final trade occured.
There's a solution, but it's risky :
- Change the ADVANCED OPTION : Find Trades Using Current Order QTY VS Previous (DEfault on yobit is My Trades Api Call).
This way, CAT will works only using Order Current QTY VS Previous QTY and if this value changes then it will automatically consider a Trade event.
this is risky because when exchanges offer the API call "MyTrades" it should not happens that order is no more active but no trades happens.
So the risk is that no trade occurs on the exchange but you tell cat "consider the fact that order is no more available as a final trade".
This could avoid a lot of zombie status. Especially when exchange api system gives problems like this one.
Let me know if it works.
If you want just send me 2-3 zombie logs and i will verify what happens.
Thanks
August 07, 2017, 04:48:53 PM
Quote
Why do you always have to come up with a new version which has more bugs than the old version?
Not true, i always fix problems and add features.
Quote
Please dont ask whats not working correctly, you know it all.
Well no, i don't know.
I know that during the latest month many exchanges got problems in API system because they are not able to manage the increasing call request.
Quote
Orders dont get correctly placed in the orderbook once a pong gets created (it only skip the e.g. 20% and then does not skip the orderbook), limiting the buy pool doesnt work ( i ended up trading with with over 0.1 BTC on a market althoug I have set to reuse 50% and started with 0.01 BTC (5.1), Polo doesnt load the whole orderbook (since ever), etc...
If you have problems you can send me logs and describe me which problem has occured.
As i remember i never received a log from you when there was a problem on CAT side. Usually it was a problem on Exchange side.
Show me a log where the buy/sell pool limit doesn't works, or when an order is not correctly placed.
Give me a list of all the problems and i will check one by one.
Quote
If such issues occurs in my company, I acknowledge the origins of problem and get a mechanism built to avoid negative interference from the third party to my products.
When problems occurs on the other side (Exchange) there are problems that could be managed and some others have zombie status as consequences.
Quote
In cat case that would be like delaying API calls etc.
there's an option to do that.
Quote
I hope this negative feedback enriches you
As i told you, if you have a problem i need logs and explanation about your problem.
Otherwise i won't be able to solve it.
First of all it's important to understand if the problem is :
- A Cat problem
- An exchange problem.
- An error from the user
Actually in my "TODO LIST" there's only 1 Error to FIX. So if you think CAT is full of problems i suggest you to explain me/show me this problems. Otherwise 5.2....5.3...5.X version will always have the problems you are talking about.
One last thing : If CAT doesn't fit your needs or you don't like it more, there's a rule in the Term of service that allows you to sell your copy.
It is your right to do that.
Thanks for your post.
August 07, 2017, 03:59:10 PM
I will try to re-set all those trades on old 5.0 this night.
Why do you always have to come up with a new version which has more bugs than the old version?
The only thing CAT does really cool is that it will create a buy order once coins gets sold and vice versa.
Babysitting the cat has always been a pain in the ass, but 5.1 with the markets getting zombie would require me to hire a new person to manage that.
Please dont ask whats not working correctly, you know it all.
Orders dont get correctly placed in the orderbook once a pong gets created (it only skip the e.g. 20% and then does not skip the orderbook), limiting the buy pool doesnt work ( i ended up trading with with over 0.1 BTC on a market althoug I have set to reuse 50% and started with 0.01 BTC (5.1), Polo doesnt load the whole orderbook (since ever), etc...
PS: Now, it is true you are always available for support, that is what I can confirm. However, isnt it more relaxing to have a cool product working rather than spend tons of hours solving things in a role of "customer service"? Which in many cases end up "Its not cat fault, its this or that, cat is fine". If such issues occurs in my company, I acknowledge the origins of problem and get a mechanism built to avoid negative interference from the third party to my products. In cat case that would be like delaying API calls etc.
You are like the government:) Invest the minimum effort needed to keep the things somewhat working so people are not bitching too much and pay taxes.
I hope this negative feedback enriches you
Why do you always have to come up with a new version which has more bugs than the old version?
The only thing CAT does really cool is that it will create a buy order once coins gets sold and vice versa.
Babysitting the cat has always been a pain in the ass, but 5.1 with the markets getting zombie would require me to hire a new person to manage that.
Please dont ask whats not working correctly, you know it all.
Orders dont get correctly placed in the orderbook once a pong gets created (it only skip the e.g. 20% and then does not skip the orderbook), limiting the buy pool doesnt work ( i ended up trading with with over 0.1 BTC on a market althoug I have set to reuse 50% and started with 0.01 BTC (5.1), Polo doesnt load the whole orderbook (since ever), etc...
PS: Now, it is true you are always available for support, that is what I can confirm. However, isnt it more relaxing to have a cool product working rather than spend tons of hours solving things in a role of "customer service"? Which in many cases end up "Its not cat fault, its this or that, cat is fine". If such issues occurs in my company, I acknowledge the origins of problem and get a mechanism built to avoid negative interference from the third party to my products. In cat case that would be like delaying API calls etc.
You are like the government:) Invest the minimum effort needed to keep the things somewhat working so people are not bitching too much and pay taxes.
I hope this negative feedback enriches you
August 07, 2017, 03:31:26 PM
I have been trying to use 5.1.
Almost every hour I get a market turned into red.
How do I solve the issue?
Almost every hour I get a market turned into red.
How do I solve the issue?
August 07, 2017, 11:38:59 AM
CAT 5.1 not allowing me to login in to poloniex, when i check the excahnge error log.. it see " ONE MORE STEP
Please complete the security check to proceed ". so polo is expecting me to solve captha and cat doesn't support it .. I am very much worried
Please complete the security check to proceed ". so polo is expecting me to solve captha and cat doesn't support it .. I am very much worried
No it's not "CAT doesn't support it"
It's "Poloniex must not return this error on API Side"
CAT is performing a Json Http Call to api system and api system must return a response.
Poloniex rarely returns (i don't know why, but i'm sure it's a problem on their side) an HTLM Page!!
I don't know how it's possible to manage that htlm page, get an image, solve the captha and send the result to poloniex. This is something not expected from the API system.
I suggest you to open a ticket and ask them how to solve this problem.
August 07, 2017, 11:26:06 AM
CAT 5.1 not allowing me to login in to poloniex, when i check the excahnge error log.. it see " ONE MORE STEP
Please complete the security check to proceed ". so polo is expecting me to solve captha and cat doesn't support it .. I am very much worried
Please complete the security check to proceed ". so polo is expecting me to solve captha and cat doesn't support it .. I am very much worried
August 07, 2017, 09:14:15 AM
Tomorrow i will launch the AUGUST OFFER
31 Days WITH BIG DISCOUNT Over a CAT Copy purchase
Stay tuned!!!
Hi! 31 Days WITH BIG DISCOUNT Over a CAT Copy purchase
Stay tuned!!!
Im sorry, but I cant find any info about AUGUST OFFER. Where is it ?
Tnx.
Hi, i still haven't found the time to write about that.
But if you write me a PM with the API you need i will calculate the discount price in real time
August 07, 2017, 09:13:10 AM
Tomorrow i will launch the AUGUST OFFER
31 Days WITH BIG DISCOUNT Over a CAT Copy purchase
Stay tuned!!!
Hi! 31 Days WITH BIG DISCOUNT Over a CAT Copy purchase
Stay tuned!!!
Im sorry, but I cant find any info about AUGUST OFFER. Where is it ?
Tnx.
August 06, 2017, 03:14:31 AM
For those who might be interested, CAT runs beautifully on a Raspberry Pi 3.
I have had it running for a couple of days with no issues.
I have had it running for a couple of days with no issues.
August 05, 2017, 12:44:48 PM
Hi Sanpey. A proposed feature for your ToDo list.
The combination of a Min Gain % and a Price Limit % for the next Ping seems to work fine in a pure sideways moving market, both for long and short positions. However, markets rarely move in a pure sideways direction, where all highs and lows are at aproximately the same price. It is much more frequent to have slightly higher highs and lows or slightly lower highs and lows, so that additional to the oscilation of the price there is a certain trending component in the price movement. This forces the user to constantly adjust parameters to stay in the market range because otherwise at the end you order gets outside the market with the risk of your Stop Loss rule being executed with a loss.
It would be great if you could add to the Price Limit rule generator an additional variable component, lets call it a Trending Factor, that would add (or substract) to the defined price limit % an additional % calculated by CAT based on the trending component of the price during the last ping-pong lifecycle (or the last X minutes).
Let's put an example. Let's imagine a certain market price is ranging from $100 to $110 during a number of price oscillation movements. I would set up a Ping buy order at $100 with a Min Gain of 10% (expecting to pong sell at $110) and a Price Limit rule like "Never BUY OVER Your Last PONG SELL Price - 10%" ensuring the next Ping buy would be executed again at $100 (in real world things are not that easy, but this is just an example).
Lets imagine that after a certain number of successfull cycles the price trends up and starts ranging from $105 to $115. If CAT detects such a change in price range, where both highs and lows have moved up by 5%, it could modify the Price Limit rule by adding the same amount (5%) to the % limit and the next ping buy would execute at $105 instead of $100, which would have never be executed in the new status of the market. The same applies if the market is trending down to range from $95 to $105. In this case the 5% would be substracted from the Price Limit %, so that the new ping buy would execute at $95, not at $100.
The trick is, of course, how to calculate the Trending Factor. I know exchanges do not provide long term historical price data, but all APIs have a command to retrieve the market history containing the price in the last N trades. Why not use this data to identify a trend a exploit this information? It could probably be enough to determine the maximum and minimum prices in the Market History and compare them with the values read during the last ping creation.
At the end the idea is to implement a certain self-adjusting mechanism that would enable you to stay in markets prices for a longer time.
A similar approach could be taken with the Min Gain %, where it could self-adjust to the spread between supports and resistances, but this is probably a bit more complex to implement.
The combination of a Min Gain % and a Price Limit % for the next Ping seems to work fine in a pure sideways moving market, both for long and short positions. However, markets rarely move in a pure sideways direction, where all highs and lows are at aproximately the same price. It is much more frequent to have slightly higher highs and lows or slightly lower highs and lows, so that additional to the oscilation of the price there is a certain trending component in the price movement. This forces the user to constantly adjust parameters to stay in the market range because otherwise at the end you order gets outside the market with the risk of your Stop Loss rule being executed with a loss.
It would be great if you could add to the Price Limit rule generator an additional variable component, lets call it a Trending Factor, that would add (or substract) to the defined price limit % an additional % calculated by CAT based on the trending component of the price during the last ping-pong lifecycle (or the last X minutes).
Let's put an example. Let's imagine a certain market price is ranging from $100 to $110 during a number of price oscillation movements. I would set up a Ping buy order at $100 with a Min Gain of 10% (expecting to pong sell at $110) and a Price Limit rule like "Never BUY OVER Your Last PONG SELL Price - 10%" ensuring the next Ping buy would be executed again at $100 (in real world things are not that easy, but this is just an example).
Lets imagine that after a certain number of successfull cycles the price trends up and starts ranging from $105 to $115. If CAT detects such a change in price range, where both highs and lows have moved up by 5%, it could modify the Price Limit rule by adding the same amount (5%) to the % limit and the next ping buy would execute at $105 instead of $100, which would have never be executed in the new status of the market. The same applies if the market is trending down to range from $95 to $105. In this case the 5% would be substracted from the Price Limit %, so that the new ping buy would execute at $95, not at $100.
The trick is, of course, how to calculate the Trending Factor. I know exchanges do not provide long term historical price data, but all APIs have a command to retrieve the market history containing the price in the last N trades. Why not use this data to identify a trend a exploit this information? It could probably be enough to determine the maximum and minimum prices in the Market History and compare them with the values read during the last ping creation.
At the end the idea is to implement a certain self-adjusting mechanism that would enable you to stay in markets prices for a longer time.
A similar approach could be taken with the Min Gain %, where it could self-adjust to the spread between supports and resistances, but this is probably a bit more complex to implement.
I think this is what I was trying to reach with my previous question.
It would be a really nice addition.
August 05, 2017, 07:34:59 AM
Hi Sampey, I tried to send you a PM but not sure if it went through to you?
*EDIT* Ok see they did go through, sorry for sending 2 messages, thought first one did not go through
*EDIT* Ok see they did go through, sorry for sending 2 messages, thought first one did not go through
Jump to: