Community. StockSharp

CQG Continuum Connection Error

2019-02-02T23:43:42Z

S#.Data Error: System.InvalidOperationException: Trader is not enabled to use CQG Web API Test. Contact your FCM.

AMP Global Clearing isn't quite sure how to help with this S#.Data error I'm getting. Any help or suggestions of how to make the CQG to S#.Data connection? Using default connection address: wss://api.cqg.com:443

Thanks for any help!

Interactive Brokers Can't Trade?

2019-02-04T15:54:54Z

When I traded with Interactive Brokers using C # Terminal, the order could not be traded.

About the selection of broker confirmation button?

2019-01-17T17:41:05Z

Hello! When I use the education course to create my own trading interface and select the broker, the OK button and the Delete button will be displayed as System. win. How is it?

Exception coming while connecting to JSE

2019-01-29T21:22:11Z

I am getting below exception, if you can help

ItchTrader 2019-01-29 07:37:45 PM Error "System.InvalidOperationException: License N101430 does not support 'ITCH_LSE'. at StockSharp.ITCH.ItchMessageAdapter.OnSendInMessage(Message message) at StockSharp.Messages.MessageAdapter.SendInMessage(Message message) in C:\Users\Administrator\Downloads\StockSharp-4.4.15\StockSharp-4.4.15\Messages\MessageAdapter.cs:line 375"

The new cryptoconnectors of the third round!

2019-01-24T15:17:47Z

Hello everybody! Perhaps you have already forgotten, but we continue our final cryptocrowdfunding. So now we announce the delivery of the next connectors and starting development of the new ones. From this day becomes available the connectors to Digifinex and BitBank Everyone who has taken part in fund-raising on it can get them here.

Also, this day we starts the development of cryptoconnectors to TradeOgre and CoinCap. You can join to our campaign and get the new connectors

Here<<

The ready-to-use connectors you can buy on our special page Pricing

[SUPPORT] How can I link windows for one security?

2019-01-16T10:48:30Z

I am used to software where I enter in the menu bar a security and then all windows in a workspace show eg market depth, chart, orders etc for this security. How can i do this in terminal? Why do I need to enter for each window the security individually?

Terminal can not send logs

2019-01-16T10:49:41Z

S#.Terminal 1/13/2019 9:51:32 AM +00:00 Error Prepare logs file error: System.IO.FileNotFoundException: Could not load file or assembly 'System.IO.Compression, Version=4.1.1.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified. File name: 'System.IO.Compression, Version=4.1.1.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' ---> System.IO.FileNotFoundException: Could not load file or assembly 'System.IO.Compression, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified. File name: 'System.IO.Compression, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'

WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

at System.IO.Compression.ZipFile.DoCreateFromDirectory(String sourceDirectoryName, String destinationArchiveFileName, Nullable1 compressionLevel, Boolean includeBaseDirectory, Encoding entryNameEncoding) at StockSharp.Studio.Controls.Extensions.SendLogs[TConfig](BaseUserConfig1 config, Window owner, Products product, NotificationClient notificationClient, Nullable`1 duration, String caption, String text)

In Terminal with binance conector I don't see market depth or charts - why?

2019-01-15T20:26:51Z

In Terminal with binance conector I don't see market depth or charts - why?

TD Ameritrade Connector?

2019-01-11T18:22:57Z

Hello, do you have a connector for TDA?

https://developer.tdameritrade.com/apis

Are the connector libraries open source? Or for sale?

2019-01-07T21:00:18Z

I went to GitHub to try and find the connector libraries, specifically StockSharp.ETrade.* and I noticed only the raw DLLs are there.

Is the source code available? Can these be purchased separately?

Installing Stocksharp on Arch Linux, how?

2018-12-28T23:04:12Z

I would like to install Stocksharp on Arch linux but do not know how. Advice? Thanks.

Happy New Year!!!

2018-12-30T16:05:12Z

Hello dear friends! Well, that’s the end of 2018, we would like to thank you for being with us. We hope that this year has been successful for you, and perhaps a modicum of this success, including our merit. Today, let's remember what we managed to do in 2018, thanks to your support and interest in the platform. In the past year, we completed many landmark projects:

Cryptoconnectors crowdfunding (the frist and the second rounds). Now our platform supports 50+ different connections.
In the second round, we released several ready-to-use trading algorithms for cryptocurrency:synthetic arbitrage, pump dtector and carrier.
Next was the third crowdfunding, in which we moved away from the crypto and created connectors for MetaTrader 4 и MetaTrader 5. Now you can trade forex through your favorite broker.
We can not forget S#.Shell upgrade and release of absolutely new training course. By the way Christmas offer is still going!!!
And at the end of the year, we launched the final crypto crowdfunding round to create connectors for any crypto exchanges you want. And already made first delivery! Of course, this is not the whole list of what we managed to do; there were both individual solutions and regular updates of our Terminal, Designer products. All this work was carried out in the interests of the users, that is mean, yours. We hope that you are satisfied with the results and continue to use our solutions in the future in 2019! We wish you a Happy New 2019 Year

New crypto algorithms

2018-03-12T14:07:14Z

Hello, dear friend!

As you already know, we launched the second stage of crowdfunding for the crypto connectors on March 1st. This time, we did everything in a new way, including with regard to algorithms.

We will now provide algorithms without black boxes. All participants will be given strategies with source codes. To be the best in the market, unique settings are required for algorithms. Sometimes this is not possible without changing the code. We will be fully open to the supplied automation.

In this article, we describe the algorithms set up especially for you. This is our technical assignment. We specifically provide complete information BEFORE you choose to participate.

## Synthetic arbitrage

This idea is similar to our main crypto robot, Edward. Synthetic arbitrage is built on a long combination of BTC/ETH/LTC//ETH/BTC. Connectors to exchanges, where there are similar coins, are set for the strategy, and then it independently chooses the convergence-divergence on the found pairs to track the arbitrage situation.

Edward-Crypto News For those who use Edward-Crypto (напиши нам по указанным ниже контактам, если хочешь получить и эту стратегию). За счет значительно продвинутой модели торговли у существующего Эдварда, для него синтетический арбитраж будет возможен с опцией автопоиска нужных пар. Н(write to us at the contacts specified below if you want to get this strategy). Due to the significantly advanced trade model of the existing Edward, synthetic arbitrage will be possible for it with the option of auto-searching for the necessary pairs. For example, BTC//LTC//LTC/ETH/BTС. The program will automatically select an effective coin as pairs to search for arbitrage divergence. This option will be available only to users of Edward-Crypto!

Pump detector

This is a special automation, tracking the growth of cheap coins with cosmic returns in a few hours. The robot can either monitor and generate a signal or actively enter the position and exit it after a certain movement to take profit. The robot will track all coins on all available connections. Of course, we are talking about very cheap alts, where you can increase your deposits 10 times a day. The main advantage of the algorithm is to get out in time, but the robot, of course, will be faster than our hands.

Carrier

It's very simple - the transfer of money from one exchange to another by the robot. Auto selection of the cheapest coin for transferring, for example, BTC positions through intermediate conversion to cheaper cryptocurrency, i.e. Vertcoin, Ripple, etc.

Modularity The key point behind all of the strategies being developed is modularity! All of our strategies are run in unlimited quantities within the same program. Edward-Crypto will also act with new strategies, all in one bundle. The Converter will work, for example, in a pair with arbitrage strategies, watching for an increase in positions on certain exchanges.

We hope that this ambitious change in the second round will be even more interesting for you!

Have any questions? E-mail us at info@stocksharp.com and we will be happy to answer any of your questions. Do not put off the decision, just now one algorithm can be obtained for only 1000$, then the minimum investment will be doubled!!!

Are you ready?

Cyber Christmas!!!

2018-12-25T15:58:34Z

Hello dear friends! In addition to previously announced discounts on our absolutely new training course we decide to extend it on our other products! Let's start Cyber Christmas!!!

If during the year you did not have time to take part in our crowdfunding programs, or simply also want to get HFT connectors, cryptocurrency or MetaTrader ones, then this news is for you !!! Starting today, until the end of 2018, you have a chance to get it all with a discount of 20%!!!. And when you buy several products, the discount will be even greater!!!

You can take advantage of discounts right now on the pages:

Connectors<<

The Training course<<

We present the absolutely new StockSharp training course! And making gifts!

2018-12-21T12:33:36Z

Hello, dear friends! Today we have great news! We completely updated our training course The video that we posted here is a full first lesson. And we invite you to watch it. As you can see, we completely re-recorded the video lectures for the platform of 2018, made them simpler and more accessible to a wide range of algorithmic traders. We hope that our video confirms this.

Updating the course, we could not leave aside the materials for the lessons. We also tried to improve them, each code contains the necessary number of comments, which allows us to understand the essence of the program even without a video! Further, more, with the updated course, we give a new S#.Shell, which allow you to create your own robots faster and simpler.

Well, the main thing

until the new year, we offer our newest course with a 20% discount!
for those who previously acquired our previous course, we give a discount of 30%! Pls, send an e-mail on lesson@stocksharp.com to get it.

You can take advantage of discounts **:::center

Just now<<

The 3rd round! First delivery!

2018-12-18T19:03:51Z

Hello dear friends

As we announced at the last week, we provide the first crypto connectors from the 3rd round.

Our users have selected Quoinex and Zaif as first ones. Starting from this moment these connectors are available for all our products and the participants can get them here!

Also, if you want to get them as well, then we freeze the price for 2 days special for you. So the fee will be the 300$ only

At the same time, today we start developing the next three connectors: Digifinex, Idax, BitBank. The delivery will be 1 week later.

To know more about our campaign and join it you can **:::center

Here!<<

The first exchanges from the third round!

2018-12-11T17:19:17Z

Hello dear friends, on Thursday last week we have started our 3rd, unlimited crowdfunding round! And currently, there are 2 exchanges under development: Quoinex and Zaif. During the next week, we will deliver ready-to-use connectors to our customers. If you want to get these too, then take part in our campaign now, after delivery it will cost 400$ per connector. Just now you can get it for only 300$ per connector.

Except you can get any connector to any exchange you want. We will create and provide it to you for 300$ too! To know more about our campaign and participate in it you can **:::center

Here!<<

S#.UI - StockSharp Graphic Framework

2018-11-15T16:25:45Z

In this paper, I will show how to use graphic components included in S#.API, in order to create a fully-featured application of the S#.Shell:

You will learn how to make a professional-level program with connection settings, output of securities, prices, and charts (and all this is saved and loaded upon restart). And the complexity of creating such an application is not a few months, but just a few hours (it is no joke! read to the end). This is the main advantage of the graphic framework, which I called by analogy S#.UI (this name is unofficial, I think it up myself). I will not use complex constructs and design patterns that are understandable only to professional programmers. On the contrary, the paper's purpose is to show that the learning curve on creating your trading applications using S#.API is very short. You will also be interested if you work in a company and make your own unique software (for example, you work in proprietary trading or a brokerage company). In this paper, you will be able to learn the practice of creating such systems (especially if you have just taken up your duties).

What You Need

Visual Studio 2017 (Community, free version), in which we will program.
Free connection to test exchange trading, I will use QUIK.

Creating Project

We create a new WPF application in Visual Studio. After that we need to add the S#.API libraries, and how to do this is described here. I prefer installing with Nuget. Since all S#.API graphic elements are based on DevExpress, and DevExpress libraries are included in S#.API, it would be foolish not to use them. All information about DevExpress graphic elements can be found in Google. Let's go to the MainWindow.xaml window editor. We replace Window with DXWindow, we will need it to use different color schemes. Visual Studio will prompt us to add the necessary libraries. We split the window into three parts, there will be a bar with buttons of connection setting and connection at the top. The window with logs will be below. All other panels are in the middle. The easiest way is to split the window in this way using LayoutControl from DevExpress. We will add the elements we need to the resulting three parts.

Configuring Connection to Connector

We add two buttons, one button to configure connection and the second button to connect. To do this, we use the SimpleButton button from DevExpress. The buttons will be located at the top of application. We will place pictures familiar with Terminal and Designer on each button. We will see such an image in the upper right corner of the screen form. We double-click each button to create button click event handlers. In MainWindow code it is necessary to declare the connector, as well as the file location and name where the connector settings will be stored. We will open the connector configuration window in the connector settings button click event handler and save it to a file. We will check in the constructor whether there is a directory and a file with the connector settings and, if there is one, we will load it into the connector. Most S#.API objects have Save and Load methods, with which it is possible to save and load this object from an XML file. We connect the connector in the connection button click event handler method. Now we can run the program and test it.

Setting Dark Theme

I prefer a dark theme. Therefore, we make the program theme dark at once. To do this in the App.xaml file We replace Application with charting:ExtendedBaseApplication. Visual Studio will prompt us to add the necessary libraries. And in the file App.xaml.cs delete ": Application". The code will be the following. We write ApplicationThemeHelper.ApplicationThemeName = Theme.VS2017DarkName in the MainWindow constructor; Full code at the moment: Run to check the dark theme.

Creating Security Panel

We add the XAML folder where we will store all the created controls. We add our first UserControll to the folder, let's call it SecurityGridControl. We add one SecurityPicker element to it. In which the available securities will be displayed. Similar to the main window, we will use LayoutControl from DevExpress. We go to the main window constructor and change the central part to the tab view. We place created control with SecurityPicker in one of the tabs. Now we have the security panel, we need to set it a data source, in our case it is a connector. It was possible to write SecurityPanel.SecPicker.SecurityProvider = Connector in MainWindow constructor. But we will not place code in the MainWindow that is not related to it. Therefore, I will create the Instance static variable, and assign it the MainWindow value in the MainWindow constructor. Now we can call the MainWindow properties anywhere in our program using MainWindow.Instance.XXX code. In the SecurityGridControl constructor, we specify Connector as a data source. We run the program to check.

Adding Logging

The operation of the program, connector or robot must be monitored. For this purpose, S#.API has a special LogManager class. This class receives messages from sources and sends them to listeners. In our case, the sources will be Connector, strategies, etc., and listeners will be a file and log panel. In the MainWindow code, we declare the LogManager object and the location where it will be stored. In the MainWindow constructor, we create LogManager, set in it Connector as the source, and a file as the listener. Similar to the security panel, we create a log panel, add another UserControl to the XAML folder. We call it MonitorControl. We add the Monitor element to it. In the MonitorControl constructor, we set Monitor as a listener in LogManager. We add the created MonitorControl to the bottom of MainWindow. We run the program to check.

Creating Portfolio Panel

Similar to the security panel, we create a log panel, add another UserControl to the XAML folder. We call it PortfolioGridControl. We add the PortfolioGrid element to it. In PortfolioGridControl constructor, we need to subscribe to new portfolio appearance events and event of new position appearance at Connector. Thus, when a new portfolio appears, it will be displayed in the portfolio panel, and when a new position appears in the portfolio panel, the portfolio will update the position. We add the created PortfolioGridControl panel to the central part of MainWindow. We run the program to check. We have a tab with portfolios.

Creating Order Panel

The order panel in S#.API has the ability to register orders, cancel orders and reregister them. Similar to the security panel, we create an order panel, add another UserControl to the XAML folder. We call it OrderGridControl. We add the OrderGrid element to it. OrderGrid has the OrderRegistering event, the OrderReRegistering event, and the OrderCanceling event. Let's create their handlers. In the order registration event handler, we create an OrderWindow window where we need to specify data sources for securities, portfolios, and market data. For all cases, this will be the Connector. After that, we call OrderWindow using ShowModal method, if the OK button was clicked in this window, we register the order via the connector using the RegisterOrder method. We do the same in the order reregistration event handler. Only in this case the event receives the Order object - this is the order that needs to be reregistered. Therefore, in OrderWindow, we specify Order = order.ReRegisterClone(newVolume: order.Balance) to fill in the fields of the OrderWindow window. After that, we call OrderWindow using ShowModal method, if the OK button was clicked in this window, we will reregister the order via connector using the ReRegisterClone method. We pass to it old order, which should be cancelled, and the new one, which should be registered. In the order canceling event handler, it is enough to call the CancelOrder method and pass to it the order that need to be canceled. In order for Orders to be displayed in the OrderGrid, it is necessary in the OrderGridControl constructor to subscribe to new order appearance events and to a registration error event and pass these events to the OrderGrid. We add the created OrderGridControl panel to the central part of MainWindow. We run the program to check.

Creating Panel of Own Trades

Similar to the security panel, we create a panel of own trades, add another UserControl to the XAML folder. We call it MyTradeGridControl. We add the MyTradeGrid element to it. In the MyTradeGridControl constructor, we need to subscribe to the new own trade appearance events and pass it to MyTradeGrid. We add the created OrderGridControl panel to the central part of MainWindow. We run the program to check.

Creating Order Book Panel

Similar to the previous panels, we create an order book panel, add another UserControl to the XAML folder. We call it MarketDepthControl. In MainWindow we have already used LayoutControl, in this control we will also use LayoutControl. We split the panel into two parts horizontally. We add SecurityPicker to the left side, we use it when we created the security panel. Let's split the right part into vertical parts. There will be an order book on the top right. In MarketDepthControl, we need to set some MaxHeight value, otherwise the application will not start. Below the order book we will place the elements of specifying a portfolio, price, and order volume. Here it is worth noting the Label property of LayoutItem, it allows to set the text over the element. And also the SpinEdit element from DevExpress, in which it is convenient to set numerical values. These elements look like this. Even below, we will place the buttons to buy, sell. Full code. In the MarketDepthControl constructor, we set the security source for SecurityPicker and the portfolio source for PortfolioComboBox, in our case it will be Connector. We create a security selection event handler in SecurityPicker. We check in it whether the selected security is not equal to zero. If it is not equal to zero, we save the received security to a local variable, we will need it when updating the order book. After that, we clear and register the received security in Connector to receive an order book using the RegisterMarketDepth method. Using the GetMarketDepth method, we get the current order book on security to update the MarketDepthControl. To keep the order book updated in the MarketDepthControl constructor, we will subscribe to the MarketDepthChanged order book change event at the connector. In the handler of this event, we will check which security the received order book belongs to, and if it belongs to the security selected in SecurityPicker, we update MarketDepthControl with it. We add the created MarketDepthControl panel to the central part of MainWindow. At this stage, we can run the program and check the order book update operation. We create a buy and sell buttons click event handler. In each handler we create an Order, in which we specify the security selected in SecurityPicker, the portfolio selected in PortfolioComboBox, the volume and price from the corresponding SpinEdit. We register the order in Connector using the RegisterOrder method. Both handlers differ only by the order direction. Let's make that the SpinEditPrice value is changed to the selected quote price when selecting a quote in the order book. To do this, we will create a handler for the SelectionChanged event at MarketDepthControl. In which we will update SpinEditPrice value by the price of the selected quote if the selected quote is not equal to zero We run the program to check.

Saving Market Data

To save portfolios, securities, platforms, we need the CsvEntityRegistry class. We need to pass the entities storage location to it and call the Init method to load them. To save candles, trades, etc., we will need StorageRegistry. We will also need the SnapshotRegistry snapshot storages registry. All this we pass to Connector when it is created. Here I also specified that Connector will reconnect when the connection is broken, and also specified how many history days should be downloaded. The Connector.LookupAll(); string queries the available data. After starting the application, we will see that new folders have appeared in the Date folder. And when reconnecting the security and portfolio panels will already be filled.

Creating Strategy Panel

I will create the strategy panel just like all previous panels. We add another UserControl to the XAML folder. We call it StrategyControl. We split the screen form into two parts using the LayoutControl. There will be a tab with a candle chart on the left side. As well as a tab with strategy statistics, Here I use StatisticParameterGrid to display strategy statistics and EquityCurveChart to display profit and loss chart. In StatisticParameterGrid, we need to set some MaxHeight value, otherwise the application will not start. The strategy properties in PropertyGridEx will be configured on the right side. As well as strategy start and stop buttons. Full code. In the StrategyControl constructor, we set Connector as a data source for PropertyGridEx, we carried out similar actions in almost every control. We need to somehow pass the strategy to our control. To do this, in StrategyControl I will create a BindStraregy method that will receive a strategy, save a link to it in the local variable, and also set a strategy in PropertyGridEx and StatisticParameterGrid. Using the SetChart method, we pass the Chart candle chart to the strategy, after that, the Chart can be obtained in the strategy using the GetChart method. We also set the Connector for the strategy. When working with the profit and loss chart, it is necessary to take into account that the strategy may start and stop several times, so every time the strategy starts, the chart should be cleared. To do this, let's create the ResetEquityCurveChart method, in which we will first clear EquityCurveChart. After that we need to create graphic elements for EquityCurveChart, for them we can set a name, color and line type. Then, we subscribe to the PnL change event of the strategy and in this event handler we draw a new value on the EquityCurveChart profit loss chart. Full method code. We will call this method in the Start button click event handler. And also we will reset the strategy state and run it. We will stop the strategy in the Stop button click event handler. We add the created StrategyControl panel to the central part of MainWindow.

Creating Strategy

For example, let's consider creating a simple strategy with candles. Which will buy if the candle is growing (green), and sell if the candle is falling (red). Let's create another folder in the project and store all our strategies in it. We create a new class in this folder and call it SimpleStrategy. All S# strategies must be inherited from the base class Strategy. Since our strategy uses candles, we will create a public property CandleSeries, and set its default value in our strategy constructor. Here I specified that candles in CandleSeries will be TimeFrameCandle with time span of 15 seconds (TimeSpan.FromSeconds(15)). We can specify the candle creating mode for CandleSeries - BuildCandlesMode. I specified that candles will be built (MarketDataBuildModes.Build), by default they will be built from ticks, but we can specify other data types as well. Since we made the CandleSeries a public property, the CandleSeries can be additionally configured from the PropertyGridEx described in the previous paragraph. All strategies have methods that can be overridden, we will need to override the OnStarted method. Which is called before the launch of the strategy and allows to preset its starting state. Here we set the security for CandleSeries, which is specified in the PropertyGridEx. After that, we create a rule for processing the completed candle. See the documentation for details on working with rules. In the rule we specify the method that will process each completed candle, in our case it is the ProcessCandle method, it will be described later. After everything is set, we subscribe to the appearance of candles on the CandleSeries in connector using the SubscribeCandles method. In our case, the ProcessCandle method contains the main strategy logic. First of all, we need to determine whether the candle is real-time or historical, if the candle is historical, we ignore it. Not all strategies require this, for example, for strategies based on order books, this is not required, since order books are always real-time. There is no general way to determine whether a candle is real-time or historical, and in each strategy this problem will have to be solved independently depending on the strategy requirements. In this case, I will simply compare the candle closing time with the connector time, and if it does not exceed a certain lag, then I consider the candle real-time. Next, we consider what candle it is and what the strategy current position. If the candle is growing, then at a position equal to 0, we will open a position with a market order for the volume set by us in PropertyGridEx. If the candle is growing and the position is less than 0, we reverse the position. We do opposite actions for a falling candle. At the moment, our strategy is ready to work. It should be passed to SimpleStrategyControl, which we created in the previous paragraph using the BindStraregy method. We do this in the MainWindow constructor immediately after the MainWindow components are initialized. We run the program to check. The strategy works, trades are made, but there are no candles and trades on the chart yet.

Adding Candles and Trades to Chart from Strategy

In the paragraph about the strategy panel, we passed the Chart candle chart to the strategy using the SetChart method. In the OnStarted strategy method, we check whether the strategy has a chart set, and if it is set, then we initialize the chart, as well as subscribe to the events of new own trade appearance and candle change. InitChart chart initialization method. Here we save the link to Chart in a local variable. We clear the chart. We also create chart elements for candles and trades and pass them to the chart. The chart.GuiSync(()=>); construct is necessary in order to initialize the chart in the main thread. CandleSeriesProcessing is a method for drawing candles on a chart. Here we get a candle from the CandleSeriesProcessing event of the connector, create ChartDrawData to display it on the chart. We specify the time data.Group(candle.OpenTime), specify that the candle should be added to the candle element of the chart .Add(_chartCandleElement, candle);. And we specify that the chart should draw new data. We perform similar actions for trades. We run the program to check.

Short conclusion

It is not necessary to spend a lot of time to create a complex and professional-looking application. In a few hours we created the fully-featured application with the ability to configure, display and trade directly. Do not be afraid to try and create your own programs. I hope this paper will help you get used to this business.

Issue with Bitfinex connector

2018-11-20T14:55:15Z

Hi, I'm currently receiving the following error when trying to connect using the Bitfinex connector:

Method not found: 'Void Ecng.Net.WebSocketClient.Send(System.Object, Boolean)'.

This exception is thrown both by the sample application: Samples\SampleBitfinex and also by my own program which creates an instance of StockSharp.Bitfinex.BitfinexTrader and executes the Connect() method.

MetaTrader 5 connector is available now!

2018-11-09T15:51:51Z

Hello dear friends! Today, we are completing the delivery of products within 3rd crowdfunding round and present connector to MT5. Now the StockSharp platform allows trading by robots both through the most popular forex terminal MetaTrader 4 and through the 5th version of this product.

Participation in the project is still possible by the same prices until November 12!

We invite everyone who has not participated in the project to get the lifetime license for only 500$. Since November 12 1000$! Project participants, we invite you to get the connector here!