lazear / gemini Goto Github PK

I can't believe I am the first to discover this problem. This would never surface if you start using this repository with a fresh Gemini Exchange generated API key. So, technically this is a user error. This is not the first repository for utilizing the Gemini API that I have used. The previous repository set a nonce equivalent to UtcNow.Ticks . When I switched to the Lazear repository, the nonce was out of sequence and low. This resulted in Bad Request 400 errors issued by the exchange. To make it a little worse the Lazear repository obscures the error by setting the order response status equal to null making it a little harder to figure out why private API methods were not working. I solved the problem by modifying the Wallet.Authenticate method to set the Nonce to UTCNow.Ticks. All methods operate perfectly now. Great work M. Lazear! Many thanks!

Message truncation and/or missing message segments occur in "large" messages. I have not found the precise definition of large. This is not a problem with Gemini library, It is occurring at the microsoft c# class level. I've worked around this by using the REST interface when WebSockets returns an invalid JSON string. This is not a preferred way to handle this. Simply changing the WebSocket buffer size does not resolve the problem. I suggest using a different WebSocket class library.