ccxt-dev/ccxt

CCXT – A JavaScript / Python / PHP cryptocurrency trading API with support for more than 120 bitcoin/altcoin exchanges

athenawisdoms

@athenawisdoms

@kroitor Thats very good! Has any pricing information been released yet? I am still a student, hoping for an affordable price

Igor Kroitor

@kroitor

Has any pricing information been released yet?

The pricing is very close to this: https://github.com/ccxt/ccxt/issues/56#issuecomment-527194069

I am still a student, hoping for an affordable price

If you take part in developing and supporting it after the release – you can get a free CCXT bRO license.

hivemall

@hivemall

hey @kroitor what is recmd install for python after reviewing the repo. i checkout the last tag and now?

pip install . from root dir or from root/python dir ? both have setup.cfg file

hivemall

@hivemall

i did from the latter, was fine so far

athenawisdoms

@athenawisdoms

@kroitor What is your recommendation for writing an app that can handle the high concurrency workloads associated with subscribing to many WS servers in CCXT Pro? Will you choose Python or Node for this role?

Igor Kroitor

@kroitor

@hivemall it is usually pip -e path/to/ccxt/repo/python (ending with the python folder, if you want to install from git, otherwise just run pip install ccxt)

@athenawisdoms technically, the performance is pretty much the same between WS+py vs WS+js – both use the same underlying bsd socket mechanisms (built into the OS)

Igor Kroitor

@kroitor

@Mr-Robot88 hey ) I finally got an answer from ByteTrade on market orders – indeed, it has to submit a zero price for market orders, so I've uploaded a fix to CCXT and it should work normally as of CCXT 1.22.46. Let me know if you still have issues after updating to the most recent version. Thx again!

F. Eugene Aumson

@feuGeneA

Coinbase Pro sent out an email saying all clients need to be using Server Name Indication, in their TLS negotiation, or else they'll be denied access. how can i confirm that ccxt supports SNI?

i did find ccxt/ccxt#2193 , which implies that it should "just work", but i'd like a more explicit confirmation

Igor Kroitor

@kroitor

@feuGeneA technically, the SNI is handled by the SSL/TLS negotiation, which is a functionality that is introduced with 3rd-party libraries, like openssl and built-in lower-level protocols. CCXT operates on a higher level, so it does not differentiate between these transports. Thus, if SNI works on your system/environment in general – it will work with CCXT as well.

F. Eugene Aumson

@feuGeneA

@kroitor i see thank you for your reply

Igor Kroitor

@kroitor

you're welcome)

Igor Kroitor

@kroitor

@hollylisa_gitlab i didn't have the time to debug it yet, but will do my best to get to it asap

holly

@hollylisa_gitlab

Awesome, thank you

@kroitor

athenawisdoms

@athenawisdoms

@kroitor Why was an infinite loop used to get new orderbook updates instead of Nodejs event emitters/listeners?

const ccxtpro = require ('ccxt.pro');
(async () => {
    const exchange = new ccxtpro.binance ({ enableRateLimit: true })
    while (true) {
        const orderbook = await exchange.watchOrderBook ('ETH/BTC')
    }
}) ()

Igor Kroitor

@kroitor

@athenawisdoms in short, it's because using direct control allows better codestyle, more readable and architecturally superior code compared to using EventEmitter and callbacks. The latter is considered an outdated approach nowadays, because it requires inversion of control (people's brains usually don't think in inverted mode). In ES6+ it is recommended to design with async generators instead. CCXT Pro tends to go with the modern approach, and it is designed for the async syntax. Under the hood, we still have to use inverted control flow sometimes, because of the dependencies and ws libs that can't do otherwise. So it kinda supports both ways. But recommends and encourages direct control flow.

Igor Kroitor

@kroitor

The same is true not only for JS/ES6, but for Python 3 async code as well

@athenawisdoms with async style you don't have to use infinite loops at all, it was just shown as a very basic usage example

Modern ES6+ syntax allows you to combine and split the execution into parallel execution pathways with direct flow, and then merge them back when you want. You can group them, prioritize them, and what not.

So, there's really no hard requirements on loops or whatever is driving your logic.

Igor Kroitor

@kroitor

So, if you want, say, 3 parallel execution pathways each running 7-11 steps sequentially, and another one running 3 steps periodically – there's no problem to write it out with direct async syntax. You would go crazy trying to manage that with events, event emitters and callbacks.

Hope that answers your question )

Igor Kroitor

@kroitor

One more thing to add: with promises you can easily convert from direct async style to inverted event style, back and forth

athenawisdoms

@athenawisdoms

@kroitor Thank you for your explanation :)

TradePlan

@TradeplanIO_twitter

hi @kroitor any update on how to sign up for CCXT pro ? the last thing i cant find is https://github.com/ccxt/ccxt/issues/56#issuecomment-527194069 which says its close but thats it.

Igor Kroitor

@kroitor

@TradeplanIO_twitter hey) check this out: https://github.com/ccxt/ccxt/issues/6332#issuecomment-586626802

chiqianguai

@chiqianguai

so many ppl here, surprise

I have a question about binance future trades, how to create order ? I tried binance.create_order(), but something is wrong. I also tried binance.fapiPrivatePostOrder(), also failed.

chiqianguai

@chiqianguai

solved, I use fapiPrivatePostOrder

Igor Kroitor

@kroitor

@chiqianguai see here:

Just add the defaultType to options in constructor params )

ccxt/ccxt#6488

https://github.com/ccxt/ccxt/issues/6458#issuecomment-583534034

ccxt/ccxt#6428

https://github.com/ccxt/ccxt/search?q=defaultType+future&type=Issues )