Xojo Development – Centralized Crypto Monitoring

This entry is part 3 of 4 in the series Xojo Development

Ah the joys of mining for your favorite cryptocurrencies, paying top dollar for over-priced GPUs, try for months to develop some crypto monitoring solution, and then come to find that the difficulties have risen absurdly to squash all hopes of profits, while also finding your GPUs lowering back down to MSRP levels. Joy…..this is joy.

Centralized Crypto Monitoring – Proof of Concept

So this post isn’t about any of that at all, instead it’s a more hopeful development that came out of 15minutes of coding this morning. Having spent some time dabbling in XMR-Stak’s miner earlier this year, I had produced one of the first proof-of-concepts for json outputs for it before they finally went their own way and created their own. Back then, my goal was the actual goal of today’s code session, I wanted to create modified miners that produced JSON results so that I could build apps that could track. The idea was simple, the vast number of your mining machines are producing JSON results of their statuses, and your aggregate those results using a centralized application that could communicate to them. While your miners should be locked away pretty secure, it’s far too simple to just open a simple firewall rule for this web-interface and grab the results, while keeping those systems secure. I don’t want the miners to communicate outward to some other service, and I didn’t want to open-up public firewall ports and forwards for each miner, nor did I want to assign different ports to each miner. While this idea is far from being the first, as my friend advised me (here’s a shoutout to @Melt and his PiMP/Miner.farm service. DISCLAIMER: I’ve never used their service, but he’s done great work in other projects I’ve seen), I think it’s unique to find something that’s multi-platformed, self-hosted, and can even be made into an iOS app with much of the same codebase thanks to Xojo.

The following is just proof-of-concept screenshots, using EWBF’s Cuda miner as the base, later in this article i’ll detail some of the future additions I’d like to release:


The design so far is pretty simple: Input the miner’s IP information, and then based off of the Miner type, it makes the JSON calls. For instance with EWBF in the above examples: will result to which is it’s JSON function. From there we get the Miner’s IP, can view its status, number of GPUs, the speeds, etc. The miners in that example are not hard-coded, but live from my test bench for the screenshots.

Future plans include the following:

  • Support for more Miners (xmr-stak stands out as one)
  • Support for plugin/profile creations to add unsupported miners in the future
  • Turn the CCM app into a server that includes a web interface
    • If it’s a server, then we can build addon apps and never expose those miners. One such add-on app could be iOS for instance!
  • Build the iOS proof-of-concept

Hit me up in the comments if you want to see anything else come from this!

For those wondering, no this is not quite open-source’d yet, but I also have no qualms with releasing it soon either. Just want to get a full version pushed that can hold its own first. I’ll be happy to share the code to anyone that asks to test it though in the meantime on a closed license

Would you like to help fund this project to turn into something bigger?

Xojo Projects

Select Payment Method
Personal Info

Donation Total: $5

Series Navigation<< Xojo Development – Plesk – update 6/25Xojo Development – Crypto Currency Monitor – Update 8/10/2018 >>

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.