@DaneshBansal I asked most of that in the tradingqna forum, consider reading through the entire thread.
https://tradingqna.com/t/a-comprehensive-overview-of-nse-s-new-retail-algo-trading-framework/181989/10
1) The circular says sharing the same sta…
Zerodha team seems to be happy just building stable production systems. But they shouldn't forget that client communication is an important part of running a broking business. It's not good that there has been no response on this thread after Feb 19…
Ok, you have a point.
I still think it's an edge case (especially the malicious scenario), but now I agree some minimal verification might need to be implemented. Perhaps Zerodha team can use their existing user/API telemetry data to estimate how …
@drjunemoone no offense intended. It's just that this is a paid API so generally only serious users will use it. And once you register an IP address, a malicious actor can't willy nilly change it just to spoof someone else's account. People can only…
@drjunemoone it sounds like you're an algo provider to be concerned about cloud providers repurposing static IPs across various users?
Handling inactive IPs is fine theoretically, but conversely it just adds overhead if I have to compulsorily shoot…
@Matti
Market orders won't be allowed for the commodity segment. The other segments will allow market orders with market protection.
There isn't any separate order type for market orders with market protection in the API docs.
https://kite.trade/do…
The SOP requires that all algo strategies be hosted on the broker's cloud.
can you please point out the specific page numbers/document which has this requirement? and do you mean ALL algo strategies or only those which exceed 10 OPS?
I think while we wait for the Kite team to work on this, you could do a one time manual download, and moving forward just store the order data locally as and when you place orders
Not a question, just a comment.
I was getting an error while importing kiteconnect module 'lib' has no attribute 'SSL_CTX_set_ecdh_auto'
this was resolved when I upgraded pyopenssl from v20 to v23 using:
pip install pyopenssl --upgrade
Thank you very much, @rakeshr. I am able to stream without any issue now after starting to use celery (~2000 instruments over one websocket )
This thread can be closed now.
Thanks @rakeshr ! I'll try out celery and other queue managers and respond here if they work out.
Just to confirm - Is this error happening because the threaded ticker is not finished with processing the previous tick when it's hit with a new tick …
