Hello, dear HASHLYNK community, and welcome to the first edition of the HashLink updates! From now on, every release will be preceded by a post of its own on our blog. In it, you’ll find out what’s new, what’s changing and what we’re currently working on.

Let’s get started with version 1.1 and our new auto-update feature.

The key points at a glance

  • From 16 October 2026, version 1.1 will be rolled out gradually and automatically to all HashLink systems.
  • You don’t need to do anything. The update installs itself, and your settings are kept.
  • The miners pause briefly during the update. After that, everything carries on as usual.
  • The main new features are easier operation and corrected displays.
  • From now on, all updates arrive automatically, without any manual remote maintenance.

What’s new in version 1.1?

With version 1.1, we mainly fine-tuned the operation. The interface now shows more clearly what your system is doing, important functions are quicker to reach and some displays have been corrected.

  • Miner slots are now shown explicitly in the user interface. This no longer gives the impression that any number of miners can be added.
  • The power button at the bottom left now deactivates the active schedule instead of activating a separate standby mode. If no schedule is active, it opens the schedule view.
  • When you tap a miner on the home screen, its miner editor opens directly.
  • Unused miner slots are no longer shown in the statistics view.
  • The home screen no longer stays empty when no miners have been added yet.
  • After an error threshold has been exceeded, the power button no longer wrongly indicates that mining has been paused.

Until now, we installed updates manually via a remote maintenance interface. For the early phase, that was a good compromise, because it let us test new features quickly at our pilot sites. With the growing number of customers, however, it was no longer practical. We needed an automatic update system.

We faced four challenges:

  • HashLink runs for long periods without human intervention. Updates therefore have to install themselves, too.
  • Mining should not be interrupted at all if possible, or only briefly.
  • HashLink works with very different mining setups, energy management systems and electrical installations. Not every combination can be reproduced in our internal tests.
  • For our team of two developers, the maintenance effort has to stay manageable.

After a few experiments, we chose Velopack. Velopack is a freely available, field-proven software library that takes care of the update process and can be integrated with little effort.

This is how it works:

  1. We publish a finished update on our server.
  2. Once a day, HashLink checks whether a new update has been released.
  3. If an update is available, HashLink shuts down all connected miners and itself in a controlled way.
  4. The update is downloaded and installed.
  5. The new version starts, takes over your settings and resumes operation.

To keep things running as smoothly as possible, we roll out updates gradually in groups known as tranches. Only when one group is running stably does the next one follow. This gives us the certainty of confirming every new version in real operation before it reaches the entire fleet.

Outlook

Alongside internal improvements, we are currently working on two larger topics:

  • Antminer integration: The standard interface (stock API) of Antminer devices is to be integrated directly into HashLink.
  • Electricity price algorithm: By the end of the year, an algorithm is to follow that continuously compares mining revenues with electricity market prices. For customers with a variable feed-in tariff, this should further improve the overall yield.

Questions, feedback or wishes for upcoming versions? Feel free to get in touch, we look forward to hearing from you.

Moritz Schalk, BSc
Software Engineer

Moritz Schalk specialises in control software and secure network architectures. He develops the HashLink user interface and is responsible for HASHLYNK’s network infrastructure.