- Put negative gains in red and/or bold
- Add filters to the markets list. For example, I want to select markets with volume > 100btc, >200 24h buy trades, >300 24h sell trades and spread >10%
Topic: 【BOT】 🌟 C.A.T. Cryptocurrency Automatic Trader 🌟 (New Price List 04/2021) - page 20. (Read 531500 times)
August 19, 2018, 05:31:08 AM
Feature requests:
August 16, 2018, 01:43:54 PM
I was using this for quite a while and am having the below 2 issues. Any suggestions on these?
1. Orders get stuck, either Ping or Pong and just never get filled which leads to no trades etc.
2. Any settings I can use to ensure that my balance doesn't go down, like some type of stop loss? my balance always seems to go down and not up
1. Orders get stuck, either Ping or Pong and just never get filled which leads to no trades etc.
2. Any settings I can use to ensure that my balance doesn't go down, like some type of stop loss? my balance always seems to go down and not up
August 14, 2018, 05:41:00 AM
Hi Sampey, sent you a pm for Auto Update Suspended on 20th July. Can you check?
you're ok in the active users list
https://freiexchange.com/market/BTI/BTC
api update soon... sorry for delays
Would you stop one day to spam this topic with this nonsense reply?
August 13, 2018, 02:50:09 PM
Hi Sampey, sent you a pm for Auto Update Suspended on 20th July. Can you check?
you're ok in the active users list
https://freiexchange.com/market/BTI/BTC
api update soon... sorry for delays
August 10, 2018, 12:34:38 PM
Hi Guys,
I´m using the bot for around a year. It runs quite stable and fine. What I´m asking myself now is how to optimize my trades.
When I start with a pair it runs good for a couple of days but the more time goes by, the less trades are made.So from time to time I need to restart the tradingpairs. Quite unsatisfying. I don´t blame the bot for this, but my bad knowledge how to use and optimize the bot.
I´m looking for help from succesfull users, that can help me to perform better, than right now.
Would be awesome hearing from you.
Greetings + happy weekend
drflax
I´m using the bot for around a year. It runs quite stable and fine. What I´m asking myself now is how to optimize my trades.
When I start with a pair it runs good for a couple of days but the more time goes by, the less trades are made.So from time to time I need to restart the tradingpairs. Quite unsatisfying. I don´t blame the bot for this, but my bad knowledge how to use and optimize the bot.
I´m looking for help from succesfull users, that can help me to perform better, than right now.
Would be awesome hearing from you.
Greetings + happy weekend
drflax
August 04, 2018, 02:29:10 AM
On 1 market my order is constantly recreated, but with an different amount. There are a lot of buyers @0.00000147, so I will never buy.
How can I prevent this?
How can I prevent this?
Code:
2018-08-04 07:17:34| PPA : Lookup 116 Start. Update Market Orders,My Orders,My Trades. Personal/Market Stats are the same as Previous Lookup
2018-08-04 07:17:34| Dynamic-PING(CAT-71d5/4455829) BUY [email protected] Current 6090 | Check For Recalculation
2018-08-04 07:17:34| PPC(REC-BUY-PI) : Check Limit Rule PING-PONG LIMIT (Adequate:true) - Never BUY OVER Your Last SELL Price - 1% VS Calculated Price 0.00000149 Comparing Value : 0.00000147 Limit Applied! Price is Adequate to 0.0000014751
2018-08-04 07:17:34| PPC(REC-BUY-PI) : New Order Data Last Check Ok, With Roundings :
Warning : Rounded Price : 0.0000014751 -> 0.00000147
2018-08-04 07:17:34| Dynamic-PING(CAT-71d5/4455829) BUY [email protected] Current 6090 | Recalculation Success, New Values : [email protected]
2018-08-04 07:17:34| Dynamic-PING(CAT-71d5/4455829) BUY [email protected] Current 6090 Delete Reason : Recreation
2018-08-04 07:17:34| API : Dynamic-PING(CAT-71d5/4455829) BUY [email protected] Current 6090 Deleted
2018-08-04 07:17:39| OCR : Try To Create new Order (Auto) PING : BUY [email protected] (Dynamic)
2018-08-04 07:17:41| PPA : Order Successfully Added to OrderList Dynamic-PING(CAT-71d5/4455881) BUY [email protected] Current 6068
2018-08-04 07:17:42| PPO : Dynamic-PING(CAT-71d5/4455881) BUY [email protected] Current 6068 Order Synch Call(Attempt 1) - Synch Successful! Order Status Changed from ToSynch To Active
2018-08-04 07:18:23| PPA : Lookup 117 Start. Update Market Orders,My Orders,My Trades. First Markets Checks Are Ok.
Current Personal Last Prices : S:0.00000149 S_PI:N/A S_PO:0.00000149 B:0.00000147 B_PI:0.00000147 B_PO:N/A Best Market Prices : S:0.00000148/B:0.00000147
Current Orders/Trades : 1 Ping, 0 Pong, 0 Trades From Ping, 0 Orders To Restore, Pool Values : Buy 0.00000000/Sell 525.00000000
2018-08-04 07:19:04| PPA : Lookup 118 Start. Update Market Orders,My Orders,My Trades. First Markets Checks Are Ok.
Current Personal Last Prices : S:0.00000149 S_PI:N/A S_PO:0.00000149 B:0.00000147 B_PI:0.00000147 B_PO:N/A Best Market Prices : S:0.00000149/B:0.00000148
Current Orders/Trades : 1 Ping, 0 Pong, 0 Trades From Ping, 0 Orders To Restore, Pool Values : Buy 0.00000000/Sell 525.00000000
2018-08-04 07:19:45| PPA : Lookup 119 Start. Update Market Orders,My Orders,My Trades. Personal/Market Stats are the same as Previous Lookup
2018-08-04 07:19:45| Dynamic-PING(CAT-71d5/4455881) BUY [email protected] Current 6068 | Check For Recalculation
2018-08-04 07:19:45| PPC(REC-BUY-PI) : Check Limit Rule PING-PONG LIMIT (Adequate:true) - Never BUY OVER Your Last SELL Price - 1% VS Calculated Price 0.00000149 Comparing Value : 0.00000147 Limit Applied! Price is Adequate to 0.0000014751
2018-08-04 07:19:45| PPC(REC-BUY-PI) : New Order Data Last Check Ok, With Roundings :
Warning : Rounded Price : 0.0000014751 -> 0.00000147
2018-08-04 07:19:45| Dynamic-PING(CAT-71d5/4455881) BUY [email protected] Current 6068 | Recalculation Success, New Values : [email protected]
2018-08-04 07:19:45| Dynamic-PING(CAT-71d5/4455881) BUY [email protected] Current 6068 Delete Reason : Recreation
2018-08-04 07:19:45| API : Dynamic-PING(CAT-71d5/4455881) BUY [email protected] Current 6068 Deleted
2018-08-04 07:19:50| OCR : Try To Create new Order (Auto) PING : BUY [email protected] (Dynamic)
2018-08-04 07:19:51| PPA : Order Successfully Added to OrderList Dynamic-PING(CAT-71d5/4456019) BUY [email protected] Current 6047
2018-08-04 07:19:52| PPO : Dynamic-PING(CAT-71d5/4456019) BUY [email protected] Current 6047 Order Synch Call(Attempt 1) - Synch Successful! Order Status Changed from ToSynch To Active
2018-08-04 07:17:34| Dynamic-PING(CAT-71d5/4455829) BUY [email protected] Current 6090 | Check For Recalculation
2018-08-04 07:17:34| PPC(REC-BUY-PI) : Check Limit Rule PING-PONG LIMIT (Adequate:true) - Never BUY OVER Your Last SELL Price - 1% VS Calculated Price 0.00000149 Comparing Value : 0.00000147 Limit Applied! Price is Adequate to 0.0000014751
2018-08-04 07:17:34| PPC(REC-BUY-PI) : New Order Data Last Check Ok, With Roundings :
Warning : Rounded Price : 0.0000014751 -> 0.00000147
2018-08-04 07:17:34| Dynamic-PING(CAT-71d5/4455829) BUY [email protected] Current 6090 | Recalculation Success, New Values : [email protected]
2018-08-04 07:17:34| Dynamic-PING(CAT-71d5/4455829) BUY [email protected] Current 6090 Delete Reason : Recreation
2018-08-04 07:17:34| API : Dynamic-PING(CAT-71d5/4455829) BUY [email protected] Current 6090 Deleted
2018-08-04 07:17:39| OCR : Try To Create new Order (Auto) PING : BUY [email protected] (Dynamic)
2018-08-04 07:17:41| PPA : Order Successfully Added to OrderList Dynamic-PING(CAT-71d5/4455881) BUY [email protected] Current 6068
2018-08-04 07:17:42| PPO : Dynamic-PING(CAT-71d5/4455881) BUY [email protected] Current 6068 Order Synch Call(Attempt 1) - Synch Successful! Order Status Changed from ToSynch To Active
2018-08-04 07:18:23| PPA : Lookup 117 Start. Update Market Orders,My Orders,My Trades. First Markets Checks Are Ok.
Current Personal Last Prices : S:0.00000149 S_PI:N/A S_PO:0.00000149 B:0.00000147 B_PI:0.00000147 B_PO:N/A Best Market Prices : S:0.00000148/B:0.00000147
Current Orders/Trades : 1 Ping, 0 Pong, 0 Trades From Ping, 0 Orders To Restore, Pool Values : Buy 0.00000000/Sell 525.00000000
2018-08-04 07:19:04| PPA : Lookup 118 Start. Update Market Orders,My Orders,My Trades. First Markets Checks Are Ok.
Current Personal Last Prices : S:0.00000149 S_PI:N/A S_PO:0.00000149 B:0.00000147 B_PI:0.00000147 B_PO:N/A Best Market Prices : S:0.00000149/B:0.00000148
Current Orders/Trades : 1 Ping, 0 Pong, 0 Trades From Ping, 0 Orders To Restore, Pool Values : Buy 0.00000000/Sell 525.00000000
2018-08-04 07:19:45| PPA : Lookup 119 Start. Update Market Orders,My Orders,My Trades. Personal/Market Stats are the same as Previous Lookup
2018-08-04 07:19:45| Dynamic-PING(CAT-71d5/4455881) BUY [email protected] Current 6068 | Check For Recalculation
2018-08-04 07:19:45| PPC(REC-BUY-PI) : Check Limit Rule PING-PONG LIMIT (Adequate:true) - Never BUY OVER Your Last SELL Price - 1% VS Calculated Price 0.00000149 Comparing Value : 0.00000147 Limit Applied! Price is Adequate to 0.0000014751
2018-08-04 07:19:45| PPC(REC-BUY-PI) : New Order Data Last Check Ok, With Roundings :
Warning : Rounded Price : 0.0000014751 -> 0.00000147
2018-08-04 07:19:45| Dynamic-PING(CAT-71d5/4455881) BUY [email protected] Current 6068 | Recalculation Success, New Values : [email protected]
2018-08-04 07:19:45| Dynamic-PING(CAT-71d5/4455881) BUY [email protected] Current 6068 Delete Reason : Recreation
2018-08-04 07:19:45| API : Dynamic-PING(CAT-71d5/4455881) BUY [email protected] Current 6068 Deleted
2018-08-04 07:19:50| OCR : Try To Create new Order (Auto) PING : BUY [email protected] (Dynamic)
2018-08-04 07:19:51| PPA : Order Successfully Added to OrderList Dynamic-PING(CAT-71d5/4456019) BUY [email protected] Current 6047
2018-08-04 07:19:52| PPO : Dynamic-PING(CAT-71d5/4456019) BUY [email protected] Current 6047 Order Synch Call(Attempt 1) - Synch Successful! Order Status Changed from ToSynch To Active
August 03, 2018, 06:40:29 PM
Hi Sampey, sent you a pm for Auto Update Suspended on 20th July. Can you check?
you're ok in the active users list
August 03, 2018, 02:42:08 AM
Hi Sampey, sent you a pm for Auto Update Suspended on 20th July. Can you check?
August 02, 2018, 02:25:03 AM
Hi,
Can I ask what method of API CAT uses to access Poloniex?
Its just that they have a notice up saying that v1 of their API will obsoleted on 25th September, dose this mean that CAT will cease to function after that date?
Below is their notification is worded:
"Friendly reminder to those using our v1 push API. Please switch to our v2 push API by September 25, 2018 as v1 will be obsolete on that day. Read our API documentation here (https://poloniex.com/support/api).Posted by The Poloniex Team at 2018-07-30 21:25:48"
Thanks.
Crypt
Can I ask what method of API CAT uses to access Poloniex?
Its just that they have a notice up saying that v1 of their API will obsoleted on 25th September, dose this mean that CAT will cease to function after that date?
Below is their notification is worded:
"Friendly reminder to those using our v1 push API. Please switch to our v2 push API by September 25, 2018 as v1 will be obsolete on that day. Read our API documentation here (https://poloniex.com/support/api).Posted by The Poloniex Team at 2018-07-30 21:25:48"
Thanks.
Crypt
CAT doesn't use PUSH Api. PUSH is something sent by the server to you, like a push notification on your phone.
CAT use REST API. It's CAT that asks for data.
Ah! Okay, thanks Sampey
August 01, 2018, 03:59:24 PM
Hi,
Can I ask what method of API CAT uses to access Poloniex?
Its just that they have a notice up saying that v1 of their API will obsoleted on 25th September, dose this mean that CAT will cease to function after that date?
Below is their notification is worded:
"Friendly reminder to those using our v1 push API. Please switch to our v2 push API by September 25, 2018 as v1 will be obsolete on that day. Read our API documentation here (https://poloniex.com/support/api).Posted by The Poloniex Team at 2018-07-30 21:25:48"
Thanks.
Crypt
Can I ask what method of API CAT uses to access Poloniex?
Its just that they have a notice up saying that v1 of their API will obsoleted on 25th September, dose this mean that CAT will cease to function after that date?
Below is their notification is worded:
"Friendly reminder to those using our v1 push API. Please switch to our v2 push API by September 25, 2018 as v1 will be obsolete on that day. Read our API documentation here (https://poloniex.com/support/api).Posted by The Poloniex Team at 2018-07-30 21:25:48"
Thanks.
Crypt
CAT doesn't use PUSH Api. PUSH is something sent by the server to you, like a push notification on your phone.
CAT use REST API. It's CAT that asks for data.
August 01, 2018, 02:05:54 PM
Hi,
Can I ask what method of API CAT uses to access Poloniex?
Its just that they have a notice up saying that v1 of their API will obsoleted on 25th September, dose this mean that CAT will cease to function after that date?
Below is their notification is worded:
"Friendly reminder to those using our v1 push API. Please switch to our v2 push API by September 25, 2018 as v1 will be obsolete on that day. Read our API documentation here (https://poloniex.com/support/api).Posted by The Poloniex Team at 2018-07-30 21:25:48"
Thanks.
Crypt
Can I ask what method of API CAT uses to access Poloniex?
Its just that they have a notice up saying that v1 of their API will obsoleted on 25th September, dose this mean that CAT will cease to function after that date?
Below is their notification is worded:
"Friendly reminder to those using our v1 push API. Please switch to our v2 push API by September 25, 2018 as v1 will be obsolete on that day. Read our API documentation here (https://poloniex.com/support/api).Posted by The Poloniex Team at 2018-07-30 21:25:48"
Thanks.
Crypt
July 31, 2018, 04:09:03 PM
Decimal places usually are a contraints given by the exchange, and it's not something you can choose.
Sorry, I meant it is better to place an order for eg. 0.214254 then 0.2?
you should always consider the rule
0.2XXXXX -> 0.2
0.1XXXXX -> 0.1
then it's up to you what you prefer.
July 31, 2018, 04:06:09 PM
Decimal places usually are a contraints given by the exchange, and it's not something you can choose.
Sorry, I meant it is better to place an order for eg. 0.214254 then 0.2?
July 31, 2018, 04:03:06 PM
So it is better to use more decimals?
And also the fees for Kraken displayed in CAT don't match with the fees in my Kraken account page 0.25/0.25 vs. 0.16/.026. See https://www.kraken.com/help/fees
And also the fees for Kraken displayed in CAT don't match with the fees in my Kraken account page 0.25/0.25 vs. 0.16/.026. See https://www.kraken.com/help/fees
Decimal places usually are a contraints given by the exchange, and it's not something you can choose.
Fee displayed by CAT are only an "info", but fees calculated are correct and directly obtained by the API CALL.
FROM KRAKEN DOCUMENTATION :
Get open positions
URL: https://api.kraken.com/0/private/OpenPositions
Input:
txid = comma delimited list of transaction ids to restrict output to
docalcs = whether or not to include profit/loss calculations (optional. default = false)
Result: associative array of open position info
ordertxid = order responsible for execution of trade
pair = asset pair
time = unix timestamp of trade
type = type of order used to open position (buy/sell)
ordertype = order type used to open position
cost = opening cost of position (quote currency unless viqc set in oflags)
fee = opening fee of position (quote currency)
vol = position volume (base currency unless viqc set in oflags)
vol_closed = position volume closed (base currency unless viqc set in oflags)
margin = initial margin (quote currency)
value = current value of remaining position (if docalcs requested. quote currency)
net = unrealized profit/loss of remaining position (if docalcs requested. quote currency, quote currency scale)
misc = comma delimited list of miscellaneous info
oflags = comma delimited list of order flags
viqc = volume in quote currency
July 31, 2018, 03:56:50 PM
So it is better to use more decimals?
And also the fees for Kraken displayed in CAT don't match with the fees in my Kraken account page 0.25/0.25 vs. 0.16/.026. See https://www.kraken.com/help/fees
And also the fees for Kraken displayed in CAT don't match with the fees in my Kraken account page 0.25/0.25 vs. 0.16/.026. See https://www.kraken.com/help/fees
July 31, 2018, 03:44:03 PM
Actually CAT always round down because many customers were not happy with the "classic" round (from 0,0 to 0,4 > 0 from 0,5 to 0,9 -> 1)
Your case is the "extreme" case where the round down mode is not good : usually exchanges allows at least 3-4 decimal places, so round it's not very important.
Your case is the "extreme" case where the round down mode is not good : usually exchanges allows at least 3-4 decimal places, so round it's not very important.
July 31, 2018, 03:38:10 PM
I don't understand this:
Or
In my opinion >=5 should round up, and <5 should round down.
The first example was from an 0.2 quantity and the second from 0.1. In the first example it sold 0.2 and wants to buy back 0.1. That won't make any gain.
Is there anybody who can clarify this for me?
Code:
2018-07-31 19:11:53| PPC(NO-SELL-PO) : New Order Data Last Check Ok, With Roundings :
Warning : Rounded Quantity : 0.19967800 -> 0.1
Or
Code:
2018-07-31 19:53:23| PPC(NO-SELL-PO) : New Order Data Last Check Ok, With Roundings :
Warning : Rounded Quantity : 0.09983900 -> 0.0
Warning : Set Quantity to Min Quantity : 0.0 -> 0.1
In my opinion >=5 should round up, and <5 should round down.
The first example was from an 0.2 quantity and the second from 0.1. In the first example it sold 0.2 and wants to buy back 0.1. That won't make any gain.
Is there anybody who can clarify this for me?
July 29, 2018, 12:18:28 PM
Bitfinex
Announcements > API Update - September 1st, 2018 7 月 29, 2018
Starting from September 1st, 2018, 00:00 UTC, Bitfinex will be implementing a series of changes to the way we manage WebSocket connections to our APIs.
As of September 1st, every WebSocket connection will have a limit of 50 subscriptions to market data feed channels (tickers, book, candles, trades, ...). We kindly ask all users to adapt their application setup accordingly to split subscriptions to channels on more WebSocket.
As an example, if you subscribe to all tickers, books, candles, trades channels on a single WebSocket connection, you'll receive
error:10305 (https://docs.bitfinex.com/v2/docs/ws-general#section-error-codes)
to notify the quota if the current socket is full. For users, this means handling multiple streams, or running multiple instances and spreading them over different pairs.
Implementing this API change results in quicker connections for all our API users, meaning quicker data feeds and optimised trading strategies.
For a full overview of the Bitfinex API documentation, refer to the following page:
docs.bitfinex.com/docs
. For issues, please contact
[email protected]
with
[API Update September 2018]
as the email subject.
Does this mean that he is going to delete the API KEY?
wtf... again
Announcements > API Update - September 1st, 2018 7 月 29, 2018
Starting from September 1st, 2018, 00:00 UTC, Bitfinex will be implementing a series of changes to the way we manage WebSocket connections to our APIs.
As of September 1st, every WebSocket connection will have a limit of 50 subscriptions to market data feed channels (tickers, book, candles, trades, ...). We kindly ask all users to adapt their application setup accordingly to split subscriptions to channels on more WebSocket.
As an example, if you subscribe to all tickers, books, candles, trades channels on a single WebSocket connection, you'll receive
error:10305 (https://docs.bitfinex.com/v2/docs/ws-general#section-error-codes)
to notify the quota if the current socket is full. For users, this means handling multiple streams, or running multiple instances and spreading them over different pairs.
Implementing this API change results in quicker connections for all our API users, meaning quicker data feeds and optimised trading strategies.
For a full overview of the Bitfinex API documentation, refer to the following page:
docs.bitfinex.com/docs
. For issues, please contact
[email protected]
with
[API Update September 2018]
as the email subject.
Does this mean that he is going to delete the API KEY?
wtf... again
CAT doesn't use websocket API.
July 29, 2018, 08:31:20 AM
Bitfinex
Announcements > API Update - September 1st, 2018 7 月 29, 2018
Starting from September 1st, 2018, 00:00 UTC, Bitfinex will be implementing a series of changes to the way we manage WebSocket connections to our APIs.
As of September 1st, every WebSocket connection will have a limit of 50 subscriptions to market data feed channels (tickers, book, candles, trades, ...). We kindly ask all users to adapt their application setup accordingly to split subscriptions to channels on more WebSocket.
As an example, if you subscribe to all tickers, books, candles, trades channels on a single WebSocket connection, you'll receive
error:10305 (https://docs.bitfinex.com/v2/docs/ws-general#section-error-codes)
to notify the quota if the current socket is full. For users, this means handling multiple streams, or running multiple instances and spreading them over different pairs.
Implementing this API change results in quicker connections for all our API users, meaning quicker data feeds and optimised trading strategies.
For a full overview of the Bitfinex API documentation, refer to the following page:
docs.bitfinex.com/docs
. For issues, please contact
[email protected]
with
[API Update September 2018]
as the email subject.
Does this mean that he is going to delete the API KEY?
wtf... again
Announcements > API Update - September 1st, 2018 7 月 29, 2018
Starting from September 1st, 2018, 00:00 UTC, Bitfinex will be implementing a series of changes to the way we manage WebSocket connections to our APIs.
As of September 1st, every WebSocket connection will have a limit of 50 subscriptions to market data feed channels (tickers, book, candles, trades, ...). We kindly ask all users to adapt their application setup accordingly to split subscriptions to channels on more WebSocket.
As an example, if you subscribe to all tickers, books, candles, trades channels on a single WebSocket connection, you'll receive
error:10305 (https://docs.bitfinex.com/v2/docs/ws-general#section-error-codes)
to notify the quota if the current socket is full. For users, this means handling multiple streams, or running multiple instances and spreading them over different pairs.
Implementing this API change results in quicker connections for all our API users, meaning quicker data feeds and optimised trading strategies.
For a full overview of the Bitfinex API documentation, refer to the following page:
docs.bitfinex.com/docs
. For issues, please contact
[email protected]
with
[API Update September 2018]
as the email subject.
Does this mean that he is going to delete the API KEY?
wtf... again
July 26, 2018, 06:41:21 AM
Is there a Russian FAQ? Or thread here?
Jump to: