Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix the cryptotracker plugin #1134

Merged
merged 1 commit into from
Oct 12, 2023
Merged

Fix the cryptotracker plugin #1134

merged 1 commit into from
Oct 12, 2023

Conversation

niljub
Copy link
Contributor

@niljub niljub commented Sep 13, 2023

Hello Jarvis Team,

I saw the cryptotracker stopped working, so I switched the defunct API and built a solution using Binance's API. This pull request aims to address the issue by implementing the following changes:

  1. API Replacement: I've replaced the outdated API with Binance's API.

  2. Code Refactoring: I have refactored the code to ensure it seamlessly integrates with Binance's API endpoints. This includes modifying the request and calling the data to match the new API structure.

  3. Switch to USDT: To address limitations I've made USDT (Tether) the default USD pairing for the cryptotracker. This change was necessary due to Binance not having any USD pairs.

Switch to Binance API: To enhance the reliability and accuracy of cryptocurrency tracking, I have migrated the plugin to use the Binance API.

Use of USDT: With the transition to the Binance API, we are kind of forced to use USDT (Tether) as the base trading pair for tracking cryptocurrencies.

JSON Structure Update: As a result of switching to the Binance API, the JSON data structure received from the API has undergone some modifications. These changes have been incorporated into the code.
@pnhofmann pnhofmann merged commit 2997bd6 into sukeesh:master Oct 12, 2023
@pnhofmann
Copy link
Collaborator

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants