Hello Jan,
We are trying to detail a bug within the CryptoClient solution:
For Kucoin marketplace, we found a sign inversion between the RestApi result and the Websocket result of SubscribeToBalanceUpdatesAsync (our use-case: quote position in perpetual futures).
In order to give you the proper input for the bug description, we are trying to trace the websocket data given by Kucoin.
Currently, we have done the following:
builder.Logging.SetMinimumLevel(Microsoft.Extensions.Logging.LogLevel.Debug);
...
.AddCryptoClients(globalOptions =>
{
globalOptions.RateLimiterEnabled = false;
globalOptions.OutputOriginalData = true;
globalOptions.CachingEnabled = true;
globalOptions.ApiCredentials = new CryptoClients.Net.Models.ExchangeCredentials();
}, kucoinOptions: (ku) =>
{
ku.Rest.OutputOriginalData = true;
ku.Socket.OutputOriginalData = true;
}, coinExOptions: (ce) =>
{
ce.Rest.OutputOriginalData = true;
ce.Socket.OutputOriginalData = true;
})
but are not successful at tracing Kucoin websowket data.
Again, thanks for your great work!!!
Very best regards,
Eric & Philippe
Hello Jan,
We are trying to detail a bug within the CryptoClient solution:
For Kucoin marketplace, we found a sign inversion between the RestApi result and the Websocket result of SubscribeToBalanceUpdatesAsync (our use-case: quote position in perpetual futures).
In order to give you the proper input for the bug description, we are trying to trace the websocket data given by Kucoin.
Currently, we have done the following:
but are not successful at tracing Kucoin websowket data.
Again, thanks for your great work!!!
Very best regards,
Eric & Philippe