Hi everyone! 👋

It's been another super busy week!

We released an update to the devices manager under my.edge.network, a point release that enables a more structured earnings view, as well as the ability to break out earnings by device.

The update also introduces support for multiple additional currency denominations for earnings, reflective of the currencies that you will be able to purchase Edge services in. This view will become configurable, enabling the selection of the currencies that are of most use to you.

There are further updates to these interfaces coming down the track, and they will ultimately be merged in to a single console for the management of contributed devices and the use of Edge services.

Earning automation goes live next week with the release of earning data for September.

This means that the node dashboards will be updated daily to reflect network activity and device earnings for the period.

Payouts will remain monthly and automated for now, but this will become a user-triggered event in time.

Edge sticker packs and replacement SD cards have all been sent out!

The network team have been hard at work adding CSS and JS compression to the Go build of the Content Distribution app, as well as adding a cache - one of the final pieces before we can begin testing in earnest on the network.

They have also been working on earning calculations, specifically building towards earning automation, which goes live next week.

Several improvements to the performance of the file sharder package used by Object Storage have been made, and DAG nodes have been added in to Host. In this context the DAG is being used to store an index of file shards.

The team have also been focused on improvement to the performance of the request queue, which will be released next week. This consists of a less rigid method of dequeueing requests to the Host app, where the longer a request remains unfulfilled, the more Hosts are allowed to concurrently attempt it.

And they have fixed a bug that has been known but unsolved on the network for over a year, whereby a 'ghost' service remained on Consul after the device left the network.

Support was added for email addresses to API client records, which will allow users of our SaaS proposition to sign in with their email rather than username. this will also allow us to introduce a password reset mechanism in to the core the future.