Claire's Monster

@rapcmia ok, only the websocket changes (the `5m` interval). The REST requests go through for the non-WS, but they do not update on the status page. It must be a...

@rapcmia Silly mistake, I tried to re-use the historical fill method, but it is shielded by the self.ready() and thus never get the latest candles. I separated the REST call...

I think so, @rapcmia ?

@yancong001 I am working on a conda `v4-proto`/`v4-client` recipe, it would be great if you can integrte it to the environment.yml (instead of pypi) when it is published on conda-forge

The `injective` SDK is also on conda-forge, that could possibly highlight conflicts at the environment installation instead (there he goes again with his conda rant)

Sure, I will. Are you actually using it (I have not looked at your PR)? Currently, I have the `node-service-base-dev` and the `v4-proto` (Python/JS) in staged-recipe: https://github.com/conda-forge/staged-recipes/pull/27037 https://github.com/conda-forge/staged-recipes/pull/27076 So, it...

`Streamlit` has been refactored, the updated way to access `cli` is: `from streamlit.web import cli` Should I add this update to the PR?

The issue seems to be with `default` vs `conda-forge`, same version though: 

@darosior @jemshit Please revisit the assertions made above. `coincurve` (master, yet to be pushed to pypi) is actively maintained and tracking fairly decently the updates made by the bitcoin-core maintainers...

@darosior I have also prepared a conda-recipe for `python-bip32`. It is pending review of the `coincurve` recipe. Are you interested in being a maintainer for that recipe?