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.
The overwhelming majority of effort in the SaaS team was on the Interface reskin, where amongst several updates worth highlighting:
- New media library, includes toggles for grid and table views
- New filters, including reworked UX on mobile
- New toolbar for document edit views
- Standardisation of look and behaviour between table and grid views
30 new leads were followed up this week, and a handful were given demo access to the network.
Backbone rentals for Stargates will be going live from Monday (30th September), initially with those members of the community who have already expressed interest and confirmed that they can meet the staking requirements.
There is a very limited supply of masternodes in the network at the moment, and while we expect their numbers to grow significantly over time, their number will always be very low relative to Hosts.
The performance that we have been able to get from the network software at Stargate level on current generation hardware is exponentially higher than earlier releases indicated would be possible. This means that there is significantly more capacity in the network at masternode level than originally benchmarked, which in turn means that their earning potential is significantly higher than originally indicated.
A single Stargate can run 100 Gateways. And a single Gateway can run 250 Hosts. This gives us a network-wide capacity of 450,000 Hosts today.
We also know that we can grow this capacity through the introduction of additional Stargates highly significantly, with an expected Stargate ceiling of around 2,500 nodes on current generation hardware.
In short, there is a lot of capacity for growth in the network.
What does all of this mean for those wanting to participate in masternodes? Simply that there is a far higher potential ROI on your proof of stake than initially modelled.
But of course we are right at the beginning of our journey. Alongside the ongoing commitment to development, it is critical that we focus on sales and the development of the networks customer base. To this end we will be opening up a referral programme to everyone in the community, starting with those participating in Stargates.
We will be reaching out with details relating to staking, rental fees, current expected earnings and further information about ROI potential to phase 1 Stargate participants on Monday.
When we have completed phase I Stargate onboarding, we will move on to the onboarding of Gateways.
The ability to run multiple Hosts per account will be enabled mid October.
Finally a reminder that our next AMA will take place on Friday 04th of October. That’s a week today.
And that’s it for this week! Thank you for your ongoing support.