noah222

Connecting constantly is the only sure solution. And then it is simply necessary to build a technical solution that does not fail on an occasional missed message. Lets say you...

Also, there is no reason to use the cbpro websocket client. To me it seems clunky. Make your own connections using websocket for better control of the process. Its only...

I would use the level 2 channel through direct interaction with the API since it is quite a bit more stable and easy to manage: https://docs.pro.coinbase.com/#the-ticker-channel The code for orderbook...

This looks pretty nice. I'll have to try it. Thanks!

what feed are you using? I've been using the 'matches' feed and have had no lapse in data. Be aware that there was recently an issue with bitcoin and the...

I use my own script for managing a connection to the feed data, and the subscription message is: message = { "type": "subscribe", "channels": [{"name": "matches", "product_ids": ["ETH-USD"]}] } I...

I've been running my own web-socket routine in a separate thread. I re-subscribe every minute and have a 10 second timeout on the receive command. This has worked very reliably...

I don't think the code here is being maintained anymore, but it is very fast already. The best way to handle errors is with a try, except block surrounding each...