Exchange Deposits and Withdrawals Monitoring

[SwiftAdviser]

Summary

Develop a system to monitor deposits and withdrawals of TON on exchanges

Bounty Context

Currently, there is a lack of a system to monitor the deposits and withdrawals on different exchanges. While some exchanges offer their own APIs with this information, there are inconsistencies and variations in their data. This makes it difficult to holistically manage and analyze the data.

Potential Solution
Develop a solution that leverages the APIs offered by the exchanges, incorporating any disparate data sets into a user-friendly format. (like grafana or metabase)

The system should be designed to manage data from:

• OKX
• Bybit
• Mexc
• Kucoin
• Bitget
• Paribu
• Coinone
• Gate.io

Defenition of Done

• Query APIs from all mentioned exchanges for deposit/withdrawal data
• Consolidate disparate data sets into a coherent format
• Implement a user-friendly interface to interact with the data

REWARD

• SBT Bounty Reward
• TBD USD in TON

🪄 Created with the help of TON Bounties Creator Bot.

[seriybeliy11]

I really like this idea, I can see the real benefits of it.

Technology stack includes React.js and Redux for the frontend, Node.js (Express.js) and Python (Django or Flask) for the backend, and PostgreSQL with Redis for the database. Docker and Kubernetes are used for containerization and deployment.

In my opinion, the cost breakdown:

Frontend: $800
Backend: $1000
Database: $600
Integration with Grafana/Metabase: $400
Testing, Documentation, Logging, and Monitoring: $600
Deployment and Scaling: $400

Total cost: $3800. The amount of data will be large and varied, hence the price. Ready to release the solution in 3-4 weeks. We can start immediately after the assignee

@SwiftAdviser do you think we can join you? We already have a similar case in our portfolio, and it was successfully implemented: https://github.com/seriybeliy11/Grants-Bounty-Tracker

thanks!

[seriybeliy11]

@SwiftAdviser what do you think of our proposal?

[SwiftAdviser]

It's a duplicate of #416