Login Page - Create Account

DTC Protocol Discussion Forum


Date/Time: Fri, 29 Nov 2024 17:39:13 +0000



[ALPHA] BitMEX data available (Testnet)

View Count: 6297

[2015-09-04 13:33:20]
vbmithr - Posts: 204
Hi,

I started running a DTC server providing BitMEX Testnet[1] data.
It is a project in alpha state, lots of bad things can happen, etc. etc.

The server is available at host bitsouk.com port 5567.

Please report any bugs or issue encountered in this thread.

The goal of this project is to provide full DTC access to BitMEX (other exchanges will follow).

Thanks.

[1] testnet.bitmex.com
Date Time Of Last Edit: 2015-09-04 14:29:50
[2015-09-05 07:36:46]
DTC Engineering - Posts: 320
The other specification we need to be aware of is what is the default DTC encoding?

And did you implement support for the Encoding Request message? You do not need to as long as the Client is aware of the default encoding.

And we will program the default encoding into Sierra Chart for this particular service.
[2015-09-05 07:43:37]
vbmithr - Posts: 204
I'm using the fixed string binary encoding, and will not switch to anything else in the foreseable future.

I'm gonna implement encoding request/response just in case.
[2015-09-05 07:45:16]
DTC Engineering - Posts: 320
OK, we already knew this. This is just for the purpose of the public discussion to make this clear to others.

We do think the binary encoding is the best.
[2015-09-10 05:07:21]
DTC Engineering - Posts: 320
We are implementing this BitMEX DTC service in Sierra Chart.

Does it provide historical data support?

We can also maintain historical data for it using the Sierra Chart historical data servers and serve that back to Sierra Chart users.
[2015-09-10 07:54:12]
vbmithr - Posts: 204
Yes it provides historical data.

If you can/want maintain historical data for BitMEX for SC users, then I have no problem using this for historical data (simpler for me).
By the way, does this means the separate historical data address for DTC is now implememented in SC ?
[2015-09-10 09:28:54]
DTC Engineering - Posts: 320
We can use a separate historical data address. That can be implemented at this time. Just give us the address for the historical data for this service.
[2015-09-10 09:37:31]
vbmithr - Posts: 204
historical.bitsouk.com port 5568
[2015-09-10 10:14:49]
DTC Engineering - Posts: 320
OK we will set this up.

Does this address and port use TLS?
[2015-09-10 11:21:34]
vbmithr - Posts: 204
No, the historical data server does not use TLS.
[2015-09-10 13:15:51]
vbmithr - Posts: 204
We can also maintain historical data for it using the Sierra Chart historical data servers and serve that back to Sierra Chart users.

It would be absolutely awesome if you could provide historical data for the bitcoin exchanges you already support to my service so that I can focus on the trading features only! Is something like this possible ?
[2015-09-11 05:48:53]
DTC Engineering - Posts: 320
We have released 1295 of Sierra Chart.

Could you please test the new Bitmex service which is now listed. We have not yet done any testing.

It also supports downloading historical data from the address and port that you gave. This is done on a separate thread.

Encryption is done using TLS 1.2.

The connection to your service can be used in Sierra Chart Free Mode.

One note about free mode, is you cannot leave Sierra Chart running for more than 7 days without restarting it.
Date Time Of Last Edit: 2015-09-11 05:50:46
[2015-09-11 06:42:50]
vbmithr - Posts: 204
Amazing, thanks! Of course I will continue working on this.
[2015-09-11 09:32:35]
DTC Engineering - Posts: 320
In the next release you will see a new service listed for "Bitsouk".
[2015-09-11 09:39:48]
vbmithr - Posts: 204
I need to think exactly what service I'm going to provide.

I'm not sure what is best, one service = one exchange or one service implementing several exchanges.

I have to decide what is best from a software dev point of view, and also from a user experience point of view.

What would you do ?

For BitMEX, I will make both testnet and mainnet available with the DTC TradeMode enum:

Demo will be for BitMEX testnet, Live will be for BitMEX mainnet.
[2015-09-11 09:40:11]
DTC Engineering - Posts: 320
It would be absolutely awesome if you could provide historical data for the bitcoin exchanges you already support to my service so that I can focus on the trading features only! Is something like this possible ?

We can do this. We just want to wait a couple weeks until we see everything working properly. But you will need to provide us a Username and Password for access to the data.

And once you begin to get everything working well, please let others know about this. They can use this as a discussion forum for support.
[2015-09-11 09:41:50]
DTC Engineering - Posts: 320

I'm not sure what is best, one service = one exchange or one service implementing several exchanges.

It really would be best have one service implementing several exchanges.
[2015-09-11 09:49:31]
vbmithr - Posts: 204
Ok, great, thanks for the info!

So, my roadmap is to achieve complete and perfect support for BitMEX, both testnet and mainnet.

When I will support both, I will ask you to rename BitMEX (Testnet) into say "BitMEX" and add a TradeMode field (Testnet / Mainnet) corresponding to DTC TradeMode enum Demo / Live.

And only when this is done, I will move on to support several other exchanges within one service.
Date Time Of Last Edit: 2015-09-11 09:49:42
[2015-09-11 09:52:28]
DTC Engineering - Posts: 320
OK this will be fine.
[2015-09-12 10:55:02]
vbmithr - Posts: 204
So, in order to use the bridge:

- Install Sierra Chart 1295 or higher.
- Register to bitsouk.com, wait for an invite.
- Obtain an API key from the BitMEX testnet (testnet.bitmex.com). Instructions here: https://testnet.bitmex.com/app/apiKeys
- Add your API key in Bitsouk.
- With latest SC, Use BitMEX (Testnet) trading service. Use your Bitsouk credentials.

The service needs a valid BitMEX Testnet API key in order to function. If not provided, the connection will fail.

Data should be pretty much reliable, trading implementation has just started.
The service is in alpha state. But since it is using the BitMEX testnet, there is no risks whatsoever with it anyway.

We are aware that the testing process is not very straightforward. If not technically inclined, wait a bit till we smoothen things a bit :)
Date Time Of Last Edit: 2015-09-12 11:04:43
[2015-09-12 18:07:37]
DTC Engineering - Posts: 320
We connected to BitMex using "test" for the username and password and the server closed the connection and did not send the logon response message indicating an error logging on and then after closing the connection:

BitMEX (Testnet) | Connecting to the server 37.187.116.20. Port 5567 | 2015-09-12 14:04:21
Socket (19) | Connected. | 2015-09-12 14:04:21
Socket (19) | Starting TLS 1.2 connection. | 2015-09-12 14:04:21
Socket (19) | SSL connection established. | 2015-09-12 14:04:22
BitMEX (Testnet) | Connected to server. | 2015-09-12 14:04:22
BitMEX (Testnet) | Sending logon request message. | 2015-09-12 14:04:22
Socket (19) | Closed. No error. | 2015-09-12 14:04:23

It should send a proper Logon response and then close the connection.
Date Time Of Last Edit: 2015-09-12 18:08:09
[2015-09-13 10:37:25]
vbmithr - Posts: 204
Fixed in current release!
Date Time Of Last Edit: 2015-09-13 14:11:43
[2015-09-16 08:36:27]
vbmithr - Posts: 204
Support for BitMEX is now complete. Please test and report bug!

To post a message in this thread, you need to log in with your Sierra Chart account:

Login

Login Page - Create Account