CCXT – A JavaScript / Python / PHP cryptocurrency trading API with support for more than 120 bitcoin/altcoin exchanges
Thanks. A little expensive for my particular situation. Trying to build an online trading platform which would require unlimited exchanges. The idea is that it would be subscription based however $1k a month for just starting up would be too expensive for getting the ball rolling. Is there another way to work out a reasonable plan, based on amount of trades or something?
@bugs181 ccxt pro does not track the usage, see the explanations on the licensing here:
- https://github.com/ccxt/ccxt/issues/6543#issuecomment-593093958
- https://github.com/ccxt/ccxt/issues/6543#issuecomment-593094835
- https://github.com/ccxt/ccxt/issues/6543#issuecomment-593113742
- https://github.com/ccxt/ccxt/issues/6543#issuecomment-593115046
- https://github.com/ccxt/ccxt/issues/6543#issuecomment-593167561
- https://github.com/ccxt/ccxt/issues/6543#issuecomment-593724215
- https://github.com/ccxt/ccxt/issues/6543#issuecomment-593728452
(basically, all comments in this issue)
@bugs181 but we will consider adding a plan for your situation
you might want to read those comments on the licensing to understand it better
Awesome ) In general we wouldn't want to have any tracking or intercepting mechanism that would affect your direct communication with the exchanges. Because direct communication is one of the key points of CCXT/CCXT Pro. You would not want to use this lib, if all traffic went through our "standalone server" of some sort.
Indeed. That was a privacy and connectivity concern of our team as well. Our objective is to be fair to the open source world (CCXT pro, more specifically), however startups usually have an initial negative cash flow problem and we didn’t want to also run into that issue. We also need to be careful legally speaking because of government regulations. If/when the project takes off, we will most definitely be contributing financially and most likely PRs.
Starting off, we plan to pay toward whichever license plan is 20% of our profits. Just so we can hit that break even point with all additional costs.
Not sure how to find this out in the documentation. Is everything that the Bitmex websocket provides supported?
@jzay not yet, but we are going to unify margin/positional/leveraged trading in Q2, this is one of our topmost priorities for the coming future:
@jzay at this time it supports the public feed and the balance
@jzay you can see which methods are supported here:
ATTENTION! ALARM! ALARM! )
We are migrating from this chatroom to our new discoord server here:
Everyone is welcome to join! We will be happy to see you all there!
This chatroom will be archived after a while.
which one is used to cancel
@hivemall in fetch_my_trades, the
you can cancel the order by order id, but you cannot cancel a trade by a trade id.
the difference is explained in the Manual here: https://github.com/ccxt/ccxt/wiki/Manual#how-orders-are-related-to-trades
Please join discord here: https://discord.gg/dhzSKYU
This room will not be supported further.
id is the trade id, and the order is the order id.you can cancel the order by order id, but you cannot cancel a trade by a trade id.
the difference is explained in the Manual here: https://github.com/ccxt/ccxt/wiki/Manual#how-orders-are-related-to-trades
Please join discord here: https://discord.gg/dhzSKYU
This room will not be supported further.
I searched ccxt github issues but found no solutions.
@mortezae hi!
This chat has moved here: https://discord.gg/dhzSKYU
The .agent and .proxies should not be a part of exchange-specific .options.
So, instead of setting exchange.options.agent or exchange.options.proxies...
... you want to set exchange.agent (which must be a instance of the node's Agent class), or you want to set exchange.proxies.
I suggest to move this discussion to discord
You can also find the examples on using the Agent and proxies here:
New discord chat: https://discord.gg/dhzSKYU
Hey gentlemen...
It could be a long shot, but nevertheless....
Let's say I want to buy 1 BTC. As fast as possible and as close to the current (momentum) price as possible.
Can someone point me the way to a good strategy/algorithm, which could help me to accomplish it with minimum losses?
Again, I don't want to place an order for a limit price and sit there for hours, hoping it'd fill up. And I don't want to buy such a high volume (1BTC) for the market price, as my average price would drop down significantly.
It could be a long shot, but nevertheless....
Let's say I want to buy 1 BTC. As fast as possible and as close to the current (momentum) price as possible.
Can someone point me the way to a good strategy/algorithm, which could help me to accomplish it with minimum losses?
Again, I don't want to place an order for a limit price and sit there for hours, hoping it'd fill up. And I don't want to buy such a high volume (1BTC) for the market price, as my average price would drop down significantly.
What I'm looking for is some sort of a proven algorithm:
- Set limit order for 0.1% less of the price
- If it filled up only 10% of the order over 1-3-5m, cancel order and create a new one with a limit price 'current price less 0.2%'
- Repeat 1-2 until fully executed.
....something like that.
I'd appreciate if someone could share their knowledge here. And/or show me where I could find more info.