zhamp
Newbie
Offline
Activity: 44
Merit: 0
|
|
July 18, 2018, 02:59:09 PM |
|
No changes in CAT Tos. I didn't send the broadcast message because version is Beta. So i wrote "Anyone who wants to try the 5.2 BETA PM ME".
I've PM you the link
May be you look over my question Does CAT also support OKEX or just OKCOIN? Not sure if I should ask here or PM you.
|
|
|
|
Sampey (OP)
Legendary
Offline
Activity: 2632
Merit: 1040
|
|
July 18, 2018, 03:01:04 PM |
|
No changes in CAT Tos. I didn't send the broadcast message because version is Beta. So i wrote "Anyone who wants to try the 5.2 BETA PM ME".
I've PM you the link
May be you look over my question Does CAT also support OKEX or just OKCOIN? Not sure if I should ask here or PM you. Actually only OKCOIN
|
|
|
|
zhamp
Newbie
Offline
Activity: 44
Merit: 0
|
|
July 18, 2018, 03:35:15 PM |
|
No changes in CAT Tos. I didn't send the broadcast message because version is Beta. So i wrote "Anyone who wants to try the 5.2 BETA PM ME".
I've PM you the link
May be you look over my question Does CAT also support OKEX or just OKCOIN? Not sure if I should ask here or PM you. Actually only OKCOIN Thank you.
|
|
|
|
RonMank
|
|
July 18, 2018, 03:46:46 PM |
|
So what are the legal and technical formalities I have to be aware to get a licence for CAT? As I see that some are selling their licence for 0.5 BTC, the first postings says 0.9BTC and in the German Altcoin forum it is announced with 0.8BTC.
|
|
|
|
Sampey (OP)
Legendary
Offline
Activity: 2632
Merit: 1040
|
|
July 18, 2018, 03:49:50 PM |
|
So what are the legal and technical formalities I have to be aware to get a licence for CAT? As I see that some are selling their licence for 0.5 BTC, the first postings says 0.9BTC and in the German Altcoin forum it is announced with 0.8BTC.
0.8??? Maybe 5 years ago. Current CAT Prices are here : https://bitcointalk.org/index.php?topic=507103.msg5590877#msg5590877Core license costs 0.065 BTC Then there's a price for any api you wants to get, from FREE to 0.015 BTC
|
|
|
|
Guruclef
Member
Offline
Activity: 97
Merit: 10
|
|
July 19, 2018, 05:07:02 PM |
|
Hi Sampey, I have a question regarding the interface for C.A.T.
It seems to me that c.a.t. cannot be navigated using only the keyboard; am I right? I ask because I was thinking of automating some operations I do frequently on CAT via scripts, so I can do them easily without much input from my part. But it seems the mouse is needed.
|
|
|
|
Sampey (OP)
Legendary
Offline
Activity: 2632
Merit: 1040
|
|
July 19, 2018, 07:56:09 PM |
|
Hi Sampey, I have a question regarding the interface for C.A.T.
It seems to me that c.a.t. cannot be navigated using only the keyboard; am I right? I ask because I was thinking of automating some operations I do frequently on CAT via scripts, so I can do them easily without much input from my part. But it seems the mouse is needed.
not sure about that. probably java have a default GUI order and you can navigate tabs and buttons using some keyboard combinations.....but i'm not an expert about that
|
|
|
|
AmodeusLex
Member
Offline
Activity: 94
Merit: 10
|
|
July 26, 2018, 11:41:21 AM |
|
Is there a Russian FAQ? Or thread here?
|
|
|
|
sw629241
Newbie
Offline
Activity: 53
Merit: 0
|
|
July 29, 2018, 01:31:20 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 support@bitfinex.comwith [API Update September 2018] as the email subject. Does this mean that he is going to delete the API KEY? wtf... again
|
|
|
|
Sampey (OP)
Legendary
Offline
Activity: 2632
Merit: 1040
|
|
July 29, 2018, 05: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 support@bitfinex.comwith [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.
|
|
|
|
stfnnn
Member
Offline
Activity: 75
Merit: 10
|
|
July 31, 2018, 08:38:10 PM Last edit: July 31, 2018, 08:55:56 PM by stfnnn |
|
I don't understand this: 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 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?
|
BTC send to 1DZK7skHmfLYgu1ZvfiVTRTKGhwfkQn6xH are lost in /dev/null !!
|
|
|
Sampey (OP)
Legendary
Offline
Activity: 2632
Merit: 1040
|
|
July 31, 2018, 08: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.
|
|
|
|
stfnnn
Member
Offline
Activity: 75
Merit: 10
|
|
July 31, 2018, 08: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
|
BTC send to 1DZK7skHmfLYgu1ZvfiVTRTKGhwfkQn6xH are lost in /dev/null !!
|
|
|
Sampey (OP)
Legendary
Offline
Activity: 2632
Merit: 1040
|
|
July 31, 2018, 09: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/feesDecimal 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/OpenPositionsInput: 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 <position_txid> = 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
|
|
|
|
stfnnn
Member
Offline
Activity: 75
Merit: 10
|
|
July 31, 2018, 09: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?
|
BTC send to 1DZK7skHmfLYgu1ZvfiVTRTKGhwfkQn6xH are lost in /dev/null !!
|
|
|
Sampey (OP)
Legendary
Offline
Activity: 2632
Merit: 1040
|
|
July 31, 2018, 09: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.
|
|
|
|
cryptcollector
|
|
August 01, 2018, 07: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
|
|
|
|
Sampey (OP)
Legendary
Offline
Activity: 2632
Merit: 1040
|
|
August 01, 2018, 08: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 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.
|
|
|
|
cryptcollector
|
|
August 02, 2018, 07: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 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
|
|
|
|
prototype_nsx
Newbie
Offline
Activity: 32
Merit: 0
|
|
August 03, 2018, 07:42:08 AM |
|
Hi Sampey, sent you a pm for Auto Update Suspended on 20th July. Can you check?
|
|
|
|
|