h4110w33n / coinmetrics

An unofficial Python module for interacting with the Coin Metrics (coinmetrics.io) API.

Coin Metrics API for Python

An unofficial Python module for interacting with the Coin Metrics (coinmetrics.io) API. Currently, this library only impliments the Community API. The Pro APIs will be available in a later release.

Getting Started

This project's official documentation is hosted on Read the Docs. Below are some direct links to get you started.

• Install
• API Reference
• Usage

Donations

Like this project? Help fund others like it.

• BTC: bc1qf523ue5xdzxqpgt4nnmpj78d2snzqf3n7s0rmd
• USD: PayPal Donation

coinmetrics's Issues

Bring back Windows testing

As of the build provided below, we started seeing major issues with the TravisCI VM used for the test process. Specifically in the process to install pip.

https://travis-ci.org/h4110w33n/coinmetrics/jobs/618968643

This is being omitted as of the test patching 1 merge request, and long term intentions are to bring it back once the feature is more mature.

#13

Conda setup?

Determine if this package is suitable for Anaconda. More or less is an alternative to PyPi for how it matters to this project.

• Anaconda Cloud: https://anaconda.org/
• Conda Force: https://conda-forge.org/

Update to use the v2 API by default

The v1 Community API is going to be deprecated on July 15, 2019 per the Coin Metrics Twitter: https://twitter.com/coinmetrics/status/1141100420380680194

The v2 API needs to be implemented, while the v1 Pro API compatibility will be renamed or removed depending on what the fate of the v1 Pro API is.

• v2 API Documentation: https://docs.coinmetrics.io/api/v2/

The v2-stable-release branch has been stubbed out to start the work.

Pro APIs need a serious buildout

The ProAPIs require an API key to access. As of right, I don't have one. I'll be reaching back out to the Coinmetrics to see if I can get a key so this can be developed out.

Until then, this issue will remain open.

Major fixes for the CommunityLegacyAPI

The legacy API was neglected after the v2 release but is still functional. This issue is to track the bug-fixes required to get it back up and running.

Better Testing

Both the v2.2 and v2.3 updates are due to test issues that were triggered by minor changes in the API. Although the changes technically do not affect the usage of the library, they do cause build/test issues in Travis.

Revamping the test.py with less specific tests as was originally done in the v1/Legacy API would be the logical option. One APIs result was essentially fed into another. This more closely represented the general use case, as well as exercised more of the code/higher coverage.