Go Wallet update — Redundancy progress

Why is this all important?

Well there’s a BUNCH of different components to the way that DigiByte Go Wallet gets information to you, and they all need to talk to each other

How DigiByte Go works

What’s new?

First of all, the wallet codebase itself has had a significant overhaul with a number of back-end improvements, library updates, bug-fixes, code tidy-ups, and more.

Server Status Monitor

We’ve got a new intermediary which keeps an eye on a bunch of servers:

New DWS server

We’re replacing the previous DigiByte Wallet Service server with a new one. This is in all new hosted infrastructure, it runs independently from other servers, and is well equipped to handle things in to the future.

Insight back-end work

There’s been some MAJOR work underway regarding the DigiExplorer back-end, which I’ll go in to more in the future, but needless to say this is a HUGE positive for us, in making the Insight API’s and Explorer front-end more reliable than ever before.

DigiExplorer.info high availability

We’ve been doing work to get DigiExplorer in a higher availability setup so that it’ll load-balance between two servers. This is why you can’t get to DigiExplorer.info at present, as it’s finishing being re-done now.

How does the infrastructure look now?

Well, something more akin to this:

The new infrastructure setup



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Josiah Spackman

Josiah Spackman


I write interesting things about cryptocurrency, especially DigiByte