Bitcoin Forum
February 22, 2019, 09:41:56 AM
 News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 Home Help Search Login Register More
 Pages: 1 ... 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 [198] 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 ... 261
 Author Topic: 【BOT】 🌟 C.A.T. Cryptocurrency Automatic Trader 5.2 🌟  (Read 502355 times)
Sampey
Legendary

Online

Activity: 2058
Merit: 1025

 August 24, 2017, 01:29:04 PM

and manage to buy 250 xrp then the price rises and you buy another 300 at 0.1224 it then rises again and you buy another 150 at 0.1229 and another 300 at 0.1231.

Now the weighted average is 0.122585 ((250×0.1220+300×0.1224+150×0.1229+300×0.1231) / (250+300+150+300) = 0.122585) of the buy orders. However I assume that CAT will sell once it sees that it bought something. Lets say the first 2 orders ( the 250 and 300) get sold at 0.1314 and the other 2 (150 and 300) get sold at 0.1311.

Can you tell me what CAT does to calculate these profits? I assume it will use the history api for this to check if it bought and sold?

when TradeHistory API is available, things are simple.
In that case you will have 3 trades

250 at 0.1220
300 at 0.1224
150 at 0.1229
300 at 0.1231

So from 1 PING you will have 4 PONG with 4 Different reference price.

Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1550828516
Hero Member

Offline

Posts: 1550828516

Ignore
 1550828516

1550828516
 Report to moderator
talkingdreams
Member

Offline

Activity: 89
Merit: 10

 August 24, 2017, 01:31:59 PM

and manage to buy 250 xrp then the price rises and you buy another 300 at 0.1224 it then rises again and you buy another 150 at 0.1229 and another 300 at 0.1231.

Now the weighted average is 0.122585 ((250×0.1220+300×0.1224+150×0.1229+300×0.1231) / (250+300+150+300) = 0.122585) of the buy orders. However I assume that CAT will sell once it sees that it bought something. Lets say the first 2 orders ( the 250 and 300) get sold at 0.1314 and the other 2 (150 and 300) get sold at 0.1311.

Can you tell me what CAT does to calculate these profits? I assume it will use the history api for this to check if it bought and sold?

when TradeHistory API is available, things are simple.
In that case you will have 3 trades

250 at 0.1220
300 at 0.1224
150 at 0.1229
300 at 0.1231

So from 1 PING you will have 4 PONG with 4 Different reference price.

But let's say all orders first fill (the 1000). And you manage to sell only 600. How do you know which is sold?
Sampey
Legendary

Online

Activity: 2058
Merit: 1025

 August 24, 2017, 01:42:03 PM

and manage to buy 250 xrp then the price rises and you buy another 300 at 0.1224 it then rises again and you buy another 150 at 0.1229 and another 300 at 0.1231.

Now the weighted average is 0.122585 ((250×0.1220+300×0.1224+150×0.1229+300×0.1231) / (250+300+150+300) = 0.122585) of the buy orders. However I assume that CAT will sell once it sees that it bought something. Lets say the first 2 orders ( the 250 and 300) get sold at 0.1314 and the other 2 (150 and 300) get sold at 0.1311.

Can you tell me what CAT does to calculate these profits? I assume it will use the history api for this to check if it bought and sold?

when TradeHistory API is available, things are simple.
In that case you will have 3 trades

250 at 0.1220
300 at 0.1224
150 at 0.1229
300 at 0.1231

So from 1 PING you will have 4 PONG with 4 Different reference price.

But let's say all orders first fill (the 1000). And you manage to sell only 600. How do you know which is sold?

Any Order have an OrderID

So i have the relationship between any order and his trades.

leetrung74
Newbie

Offline

Activity: 10
Merit: 0

 August 25, 2017, 01:59:14 AM

Email form Bitfinex:
Bitfinex is growing faster than ever, and we are pleased that our platform, trading engine, and APIs have remained reliable and performant during these exciting days.
However, in order to continue to be able to accommodate current demand and future scaling, the Bitfinex REST and WebSocket APIs will be upgraded on Thursday, August 31st.
You are receiving this email because it appears you might be a Bitfinex API user and we wish to alert our API users about these changes in particular, as the changes may affect automated trading applications using the APIs.

In order to continue to be able to handle spikes in platform load, we need to make adjustments to how we return historical snapshot messages when authenticating to the WebSocket APIs. Currently, the snapshots hos, hts, hfts, hfos, hfls, and hfcs are returned in the WebSocket feed after authenticating. As of August 31st, these snapshots will no longer be returned via the WebSocket feed (both V1 and V2) after August 31 and equivalent REST endpoints are available as replacements. All update messages will remain unchanged.

If your API application relies on these historical snapshots, these changes may affect your application. Please take the time to review the following and make sure to properly update your code if needed.

CHANGES EFFECTIVE IMMEDIATELY

These changes are preparations for the changes that will be made on August 31.

New restV1: /v1/orders/hist (limited to last 3 days and last 1000 results)
restV1 Authenticated historical orders query (can be called only once per minute)
https://docs.bitfinex.com/v1/reference#rest-auth-orders-history
New restV1: /v1/offers/hist  (limited to last 3 days and last 1000 results)
restV1 Authenticated historical margin funding offers  (can be called only once per minute)
https://docs.bitfinex.com/v1/reference#rest-auth-offers-hist
restV1 Authenticated historical margin funding trades
New restV2: /v2/platform/status
Status of the platform
• Maintenance mode: trading engine pause / resync (after event 20060 is triggered)
• [1] Active: normal operations (after event 20061 is triggered)
https://docs.bitfinex.com/v2/reference#rest-public-platform-status
RestV2 ERR_MAINT will be returned by all API endpoints during the maintenance period.
https://docs.bitfinex.com/v2/docs/rest-general#section-maintenance
New restV2: /v2/auth/r/funding/credits
Active funding credits (funds used in positions)
https://docs.bitfinex.com/v2/reference#rest-auth-funding-credits
new restV2: /v2/auth/r/funding/credits/hist
Inactive funding credits (funds used in positions)
https://docs.bitfinex.com/v2/reference#rest-auth-funding-credits-hist
New restV2: /v2/auth/r/funding/loans
Active funding loans
https://docs.bitfinex.com/v2/reference#rest-auth-funding-loans
new restV2: /v2/auth/r/funding/loans/hist
Inactive funding loans
https://docs.bitfinex.com/v2/reference#rest-auth-funding-loans-hist
New restV2: /v2/auth/r/funding/offers
Active funding offers
https://docs.bitfinex.com/v2/reference#rest-auth-funding-offers
new restV2: /v2/auth/r/funding/offers/hist (limited to 3 days)
Historical funding offers
https://docs.bitfinex.com/v2/reference#rest-auth-funding-offers-hist
new restV2: /v2/auth/r/funding/offers/SYMBOL/hist (limited to last 3 days)
Historical funding offers by symbol
https://docs.bitfinex.com/v2/reference#rest-auth-funding-offers-hist
New restV2: /v2/auth/r/funding/trades/hist (limited to last 15 days)
New restV2: /v2/auth/r/funding/trades/SYMBOL/hist (limited to last 15 days)
New restV2: /v2/auth/r/orders
Active orders
https://docs.bitfinex.com/v2/reference#rest-auth-orders
New restV2: /v2/auth/r/orders/hist (limited to 3 days)
Historical orders
https://docs.bitfinex.com/v2/reference#rest-auth-orders-hist
New restV2: /v2/auth/r/orders/SYMBOL/hist (limited to last 3 days)
Historical orders by symbol
https://docs.bitfinex.com/v2/reference#rest-auth-orders-hist
New restV2: /v2/auth/r/trades/hist (limited to 7 days)
New restV2: /v2/auth/r/trades/SYMBOL/hist (limited to last 7 days)
New restV2: /v2/auth/r/movements/hist (limited to last 90 days)
Historical movements (deposits/withdrawals) history
https://docs.bitfinex.com/v2/reference#rest-auth-info-funding
New restV2: /v2/auth/r/movements/CURRENCY/hist (limited to  90 days)
Historical movements (deposits/withdrawals) history by currency
https://docs.bitfinex.com/v2/reference#rest-auth-info-funding
WebSocket event code 20060 now means: Maintenance start
Pause trading is suggested until receiving 20061
Note that there is no change in the behaviour, this is just a more meaningful description
WebSocket event code 20061 now means: Maintenance end

CHANGES DEPLOYED on 2017-08-31

Some of these change can result in backward compatibility issues. Please make sure you will adjust your code to prevent unexpected behavior of your application.

Websocket books (v1 and v2): drop support for F2, F3 frequencies
Endpoint restV2: /v2/auth/r/offers renamed to: /v2/auth/r/funding/offers
Endpoint restV2: /v2/auth/r/funding renamed to: /v2/auth/r/info/funding
Endpoint restV1 /v1/book “timestamp” field will now contain the timestamp at the moment of calculation of the book
The “timestamp” field is deprecated and will be removed in a future update
Endpoint restV1 /v1/lendbook “timestamp” field will now contain the timestamp at the moment of calculation of the book
The “timestamp” field is deprecated and will be removed in a future update
WebSocket v1 and v2 authenticated: historical snapshots  hos, hts removed:
https://docs.bitfinex.com/v2/reference#ws-auth-historical-orders
Only snapshot hos will be removed, while updates on, ou, oc  will flow as usual. Historic Order Snapshot can be retrieved via REST calls:
WS V1 users: use  /v1/orders/hist
WS V2 users: use  /v2/auth/r/orders/hist
or /v2/auth/r/orders/SYMBOL/hist (to filter on specific pair)
Only snapshot  hts will be removed, while updates  te, tu will flow as usual. Historic Trades Snapshot can be retrieved via REST calls:
WS V1 users: use restV1  /v1/mytrades
WS V2 users: use restV2  /v2/auth/r/trades//hist
or /v2/auth/r/trades/SYMBOL/hist (to filter on specific pair)
WebSocket v2 authenticated: historical snapshots  hfts, hfos, hfls, hfcs removed:
https://docs.bitfinex.com/v2/reference#ws-auth-historical-offers
Only snapshot  htos will be removed, while updates fon, fou, foc will flow as usual. Historic Funding Offers Snapshot can be retrieved via REST calls:
RestV2: /v2/auth/r/funding/offers/SYMBOL/hist
or /v2/auth/r/funding/offers/SYMBOL/hist (to filter on specific currency)
https://docs.bitfinex.com/v2/reference#ws-auth-historical-credits
Only snapshot hfcs will be removed, while updates fcn, fcu, fcc will flow as usual. Historic Credits Snapshot can be retrieved via REST calls:
RestV2: /v2/auth/r/funding/credits/hist
or /v2/auth/r/funding/credits/SYMBOL/hist  (to filter on specific currency)
https://docs.bitfinex.com/v2/reference#ws-auth-historical-loans
Only snapshot hfls will be removed, while updates fln, flu, flc will flow as usual. Historic Loans Snapshot can be retrieved via REST calls:
RestV2: /v2/auth/r/funding/hist
or /v2/auth/r/funding/loans/SYMBOL/hist  (to filter on specific currency)
Only snapshot  hfts will be removed, while updates  fte, ftu will flow as usual. Historic Trades Snapshot can be retrieved via REST calls:
or /v2/auth/r/funding/trades/SYMBOL/hist  (to filter on specific currency)
These changes will work to ensure optimal API performance, with minimal latency, to the benefit of our users.

With Kind Regards,
bitfinex.com
support@bitfinex.com
Sampey
Legendary

Online

Activity: 2058
Merit: 1025

 August 25, 2017, 09:55:22 AM

@leetrung74 thank you so much.
i've checked what you post and i think that CAT won't be affected......
but for sure, the day they will switch something i'll be available to perform instant fix over the bitfinex api

btsnacker
Newbie

Offline

Activity: 10
Merit: 0

 August 25, 2017, 05:40:54 PMLast edit: August 25, 2017, 06:11:21 PM by btsnacker

Hi guys

CAT sold my ETH @ 279 EUR this morning, so I missed the top (285 EUR).
Tried to hop an the train @ 281 EUR again but this went nowhere so far.

How do you handle such situations using CAT (if at all)?

Thanks.
Sampey
Legendary

Online

Activity: 2058
Merit: 1025

 August 28, 2017, 10:28:26 AM

Hi C.A.T. users (and potential new users).
I'll be away from 29/08 to 01/08  so if you need to buy something (a core license or an api) pls pm me today.

50% Discount is still available

NobleGhost
Newbie

Offline

Activity: 25
Merit: 0

 August 29, 2017, 04:43:22 AM

Hi C.A.T. users (and potential new users).
I'll be away from 29/08 to 01/08  so if you need to buy something (a core license or an api) pls pm me today.

50% Discount is still available

Is trial version available?
Sampey
Legendary

Online

Activity: 2058
Merit: 1025

 August 29, 2017, 08:49:26 AM

Hi, probably i won't be able to reply to pm/msg until Friday 1 September.
So don't worry if you don't receive any response from me

roger74
Newbie

Offline

Activity: 18
Merit: 0

 August 29, 2017, 04:34:21 PM

Bot warns the start of dumps? (in bitrex)

Possible dumps...

TillKoeln
Legendary

Offline

Activity: 1428
Merit: 1000

 August 30, 2017, 01:02:56 AM

thank you Sampey :-)

https://pastebin.com/raw/VAMkWSiS

boulard83
Full Member

Offline

Activity: 202
Merit: 100

 August 30, 2017, 01:18:27 AMLast edit: August 30, 2017, 01:31:30 AM by boulard83

very interesting, ill give i'd a try !

50% mean 0.1 BTC right ? It's still a good amount for a small trader.

PC Hardware junky | Gaming • 5930K • 32gb • GTX1070 • BenQ XR3501 144hz | Server • Dual E5-2670 16c/32t • 32gb ECC • GTX1050ti • 3 SSD + Multiple HDDs
TillKoeln
Legendary

Offline

Activity: 1428
Merit: 1000

 August 30, 2017, 02:35:40 PM

Hello Sampey :-)

there are a lot of "retrys" on the api calls for yobit.
even if yobit itself say 200ms per api call. seems the .net address too busy. to handle this timings.

overall process c.a.t. the most calls with the 200ms setting
but i have tried a bit and have to say that with 1 call per second are np retry`s
and they steady increase with reduced time between the calls.
it is far away from 5 Calls per second.

maybe it is too "simple "  but...   yobit has aditional the .io ending as backup. and so far as i can see
these server isnt affected by the heavy user load.    whenever i use the yobit.io address in the past
while yobit was lagging / slow.   it works for me fine.

could you try on your side if there is any better performance when you use yobit.io instead of yobit.net ? :-)

deepham
Newbie

Offline

Activity: 1
Merit: 0

 September 01, 2017, 06:33:16 AM

Hello,

my email: deephampt@gmail.com
octomob
Member

Offline

Activity: 140
Merit: 10

 September 01, 2017, 09:13:06 PM

Hello. I would like to buy CAT - reserve 1 copy for me please.
PM me please with details, i would like to also buy source code if possible

★ ★ ★ ★ ★   DeepOnion  ✔  Anonymous and Untraceable Cryptocurrency  ✔  TOR INTEGRATED & SECURED   ★ ★ ★ ★ ★
› › › › ›  JOIN THE NEW AIRDROP ✈️    ★    ✔ VERIFIED WITH DEEPVAULT  ‹ ‹ ‹ ‹ ‹
Sampey
Legendary

Online

Activity: 2058
Merit: 1025

 September 01, 2017, 09:17:08 PM

Bitzure
Newbie

Offline

Activity: 28
Merit: 0

 September 02, 2017, 01:30:55 AM

Hi Sampey,

Any chance at looking at adding Bitzure to C.A.T.?

Full API documentation available here: https://bitzure.com/documents/api_v2

Let me know if you need to know more or have any issues, or feel free to flick me a PM
Mortimer452
Hero Member

Offline

Activity: 532
Merit: 500

 September 02, 2017, 05:28:44 AM

I can't seem to get CATv5 to work with Bittrex

Created API keys on my Bittrex account, 2FA is enabled, key is allowed for read/trade limit/trade market, put the key and secret into the public/private key boxes in CAT, but it says "User XXXXXXX not found for Bittrex" when I click Login
Sampey
Legendary

Online

Activity: 2058
Merit: 1025

 September 02, 2017, 12:53:49 PM

I can't seem to get CATv5 to work with Bittrex

Created API keys on my Bittrex account, 2FA is enabled, key is allowed for read/trade limit/trade market, put the key and secret into the public/private key boxes in CAT, but it says "User XXXXXXX not found for Bittrex" when I click Login

because you need to buy/activate the bittrex api

Mortimer452
Hero Member

Offline

Activity: 532
Merit: 500

 September 02, 2017, 03:51:17 PM

I can't seem to get CATv5 to work with Bittrex

Created API keys on my Bittrex account, 2FA is enabled, key is allowed for read/trade limit/trade market, put the key and secret into the public/private key boxes in CAT, but it says "User XXXXXXX not found for Bittrex" when I click Login

because you need to buy/activate the bittrex api

I did purchase the Bittrex API, I will PM you

 Pages: 1 ... 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 [198] 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 ... 261