Edge Latest articles from the team en 2019 Edge Network Technologies Ltd. All rights reserved. Thu, 14 Nov 2019 16:37:55 +0000 2019-11-14T16:37:55+00:00 en 2019 Edge Network Technologies Ltd. All rights reserved. Edge https://edge.network/assets/img/dadi-logo-colour.png https://edge.network Weekly Update: W/C 04th November, 2019 https://edge.network/updates/announcements/weekly-update-wc-04th-november-2019 Hi everyone 👋

First up this week: we’ve released a Beta version of the self-serve interfaces for Content Distribution 💥

You can access this now under the interfaces on my.edge.network and take the technology for a spin.

This includes access to the full imaging pipeline in the platform. We’ll be adding documentation for this to the main site soon.

The Beta gives you access to spin up the service for a single domain, with an additional domain unlocked for every device that you’ve contributed to the network.

The team have also been working on connectivity tests within Edge Cli.

And they’ve put the finishing touches on to the new Go version of the Content Distribution app, which will be deployed to mainnet next week.

The required builds for this have been prepared. And the required methods in the package that we use for caching – big-cache – have been created. This makes it possible to introduce conditional cache pre-warming on Gateway based on the frequency that a cached resource is accessed.

Which is a fantastic bit of tech.

We’ve released a series of performance improvements for Gateway, which includes a bi-directional RPC stream. This means a reduction in required concurrent http/2 connections and a reduction in latency between Host and Gateway.

There’s an outreach article that covers this, for those who fancy reading the more technical details: https://edge.network/en/knowledge/network/gateway-bi-directional-streaming/

And that’s it for now!

Enjoy your weekends.

Mon, 11 Nov 2019 14:30:00 +0000 5dcadeb17dcfb81e19265992 Joseph Denne 2019-11-11T14:30:00+00:00
Content Distribution: self serve available now https://edge.network/updates/announcements/content-distribution-self-serve Registered users have been given access to the configuration page for Content Distribution, available in the menu on https://my.edge.network. The Beta Free tier starts with a single zone, plus one additional zone per contributed network node. You’ll get a healthy 2GB data transfer, along with 5m requests per month and it’s really easy to get started.


You’ll need to tell us the domain (and subdomain if applicable) you’d like to use, the source url for your images and optionally that of your assets. We’ve set out some TTL options, so you can choose whether you want a longer cache for quicker responses, or a shorter one for content that’s likely to change frequently.

The Free Tier is running the latest version of Content Distribution, replicated globally, and will not receive direct support. As previously mentioned, this is a Beta, so uptime and availability are by no means guaranteed, although we’ll do our very best to reach out ahead of each major deployment. For those of you wishing to discuss the Enterprise option, we’ve also included a contact link.


Fri, 08 Nov 2019 18:00:00 +0000 5dc5a25a36e2c61e60c3e75e Arthur Mingard 2019-11-08T18:00:00+00:00
Gateway Bi-Directional Streaming https://edge.network/knowledge/network/gateway-bi-directional-streaming This week marks the release of a significant refactor as part of a focussed round of efficiency improvements set out to target the low level communication interfaces used by Gateway and Host. This specific change comprises of a change to the RPC (Remote Procedure Call) protocol used to distribute requests and receive responses from Host. RPC uses the client-server model to define procedures which suspend the caller whilst executing on the receiver. It allows two machines to perform a single synchronous operation when connected over a network where latency is otherwise a crippling factor.

In the last round of improvements we significantly reduced the number of RPC connections between Gateway and Host by streaming requests to the Host rather than sending one-by-one. This reduced latency, but didn’t affect the way Host returned payload to Gateway, which still required a connection per response.

In this release we removed the response method and adjusted the protocol that streams requests to the Host to also accept a stream of responses back, reducing the entire process to a single stream. This is made possible through gRPCs support for bi-directional streaming which takes advantage of the multiplexing capabilities of the http/2 protocol whilst structuring payload with Protocol Buffers, a serialization method with its own markup interface definition language.

In slightly less technical terms, this allows Gateway to asynchronously send unfulfilled requests to each Host whilst simultaneously receiving responses, all over a single connection. This reduces the number of open connections to the Gateway, removes the latency caused by establishing a new http/2 connection and only requires headers to be sent once.

One obstacle when moving to a fully bi-directional stream was migrating the concurrent request limiter method from Host to Gateway. With a single stream it was possible for a Host to suspend the RPC method by limiting the number of asynchronous operations using Channel Buffering. When the stream is bi-directional, the logic which previously provided a strict coupling between the RPC method and Hosts local request buffer became too fragile, so it was moved to Gateway.

The new logic stores the number of requests that are reserved by the Host, placing a temporary pause on the RPC method until the Host has satisfied enough requests to fall below the threshold. As some of you may have noticed last week, there were some teething problems with the first release. Under certain conditions where latency from one Host causes the request to be reassigned to another, Gateway was not successfully deducting the count of requests from the first, eventually causing the RPC method to indefinitely lock. After a quick refactor I can now report that the process is working as expected and having a significant positive effect on latency and a reduction in Gateway CPU usage.

Fri, 08 Nov 2019 12:30:00 +0000 5dc55cf607b2421e1ea48798 Arthur Mingard 2019-11-08T12:30:00+00:00
Weekly Update: W/C 28th October, 2019 https://edge.network/updates/announcements/weekly-update-wc-28th-october-2019 Hi everyone! 👋

It’s been another jam packed week here 🏃‍♂️

Earnings for October were pushed to network dashboards, with Stargates returning an average annualized ROI of 18.48%, and Hosts returning an average annualized ROI of 33.83%.

Daily earnings have been enabled in the network, with earning data now pushed to network dashboards once every 24 hours.

You can read about this in more detail here: https://edge.network/en/updates/network/daily-earnings/

API version 6 was released: https://github.com/dadi/api/releases/tag/v6.0.0

There are a whole world of updates and enhancements in this release, and we’ll be writing about them next week.

Publish version 3 was released: https://github.com/dadi/publish/releases/tag/v3.0.0

Note that this release requires API version 6.

The web service team continued work on improvements to the rich editor in Edit. Among other updates they implemented nested lists, improved keyboard navigation and the behaviour of the link prompt.

They also spent time planning for the implementation of third party data sources within the dashboards of our editorial interfaces.

The team continued work on the Edge Console framework, including closing out account login, creating a datasource plugin similar to that used in Web, and kicking off work on the Edge Console API layer.

And they continued work on Edge CLI connectivity tests and the integration of benchmarking into Network CDN for Host.

The team also integrated Slack reporting into Earnings service for internal monitoring.

A series of earnings service improvements were made along with a few bug fixes.

We’ve seen good growth in Hosts since multi-device onboarding kicked off, with some new nodes in far-flung spaces!

We remain on track to have interfaces for content distribution in open Beta for the community around the second week of November (TBC). We’re currently integrating front end templates, which will be released under my.edge.network in the first instance.

Finally, I expect to be releasing an update to our roadmaps next week.

And that’s it!

Enjoy your weekends 😊

Mon, 04 Nov 2019 14:30:00 +0000 5dc51985d7531f1e14772493 Joseph Denne 2019-11-04T14:30:00+00:00
Daily Earnings https://edge.network/updates/network/daily-earnings This month we have been trialing daily earnings calculations. Every day, in the early hours of the morning, while we sleep soundly in our beds, our robotic underlings diligently calculate the earnings for the previous day for every staked Host, Gateway, and Stargate on the network. While trialing the daily earnings process, we have kept the data for October hidden from users, but it is now visible for all to see.


Daily earnings will be visible as they are calculated from this point on. The process kicks off around 02:00 UTC every day, and your earnings will be visible anytime thereafter. Payouts will remain monthly for now.

If you haven’t set your wallet address in your account be sure to do so right away, by going to my.edge.network/account/wallet in order to avoid missing the payout window for this month.


We are happy to announce that we now have 6 Stargates staked, and they have been active for the entire month of October. We’d like to thank our community for their ongoing support. We are now in the process of getting the Gateways ready for community staking, and will have more information on that for you soon.

We are happy to report that Stargates are currently running at an annualized ROI of 18.48%.


We now have an incredible 311 staked and operational Hosts in the network. Since we announced Multi-device Onboarding last week, our community been busy adding devices to the network from all around the globe. Just look at the increase in Hosts below:


Hosts are currently running at an annualized ROI of 33.83%, earning an average of 166 $EDGE each this month.

The amount Hosts earn per day depends on a number of factors, including the number and value of jobs completed, which in turn is driven by demand in the network. Because of this your earning will differ from the average, as well as between nodes (if you are running more than one). We are continuing to build out telemetry services, integrating more metrics and extracting more information from the network data available. We will be exposing more of this data as we go, and expect to be able to show a count of jobs completed over time in the near future.

What to expect in November

You can expect to see your earnings reported every day in November. And payouts for October will be completed next week. Remember, if you haven’t set your wallet address in your account be sure to do so right away, by going to my.edge.network/account/wallet. If you do miss this months payout window, not to worry, you’ll simply receive the earnings next month.

Fri, 01 Nov 2019 16:00:00 +0000 5dbc5320c8ada71e0f37ebfa Adam K Dean 2019-11-01T16:00:00+00:00
Weekly Update: W/C 21st October, 2019 https://edge.network/updates/announcements/weekly-update-wc-21st-october-2019 Hi everyone! 👋

I’m posting early today because I’m traveling this afternoon ✈️

Still, today’s update will be larger than the last couple of weeks. I can’t believe it’s already Friday. Time is flying right now!

Daily earnings will be running from Halloween 👻, meaning that you will see the updates in your dashboards from Friday 01st November.

Multiple Hosts per account are now enabled 💥

In support of this Edge CLI 1.4.1 has been released. Please update before installing additional nodes. You can do this by running:

apt install edge-cli

Stargates are now showing in the dashboards of those of you who have staked against our existing Stargate deployments. As more Stargates are added over time, more spaces will open up staking.

On Stargates, payouts are currently being evenly distributed. This is because the distribution of load in the network is very uneven at this level because of the relatively low capacity use of masternode. As this changes we will move to an actual-work basis. Timings on this are TBC, and are dependent on sales efforts.

The network team kicked off work re-platforming My Edge (Web) to Edge Console (which is being written in Nuxt). As part of this work they wrote a custom datasource plugin for Nuxt to simplify integration with API and added internationalisation (i18n) with multi-language support.

They also started work to migrate My Edge API to version 6, and fixed issue with Stargate device status in User Devices.

Work began on CLI connectivity check functionality, allowing users to check if devices are fit for the network.

And Consul Token Cleaner builds were setup.

Edge CDN has been in testing on test.network, with comparisons against DADI CDN run over the week. Work has also been done to ensure that all methods behave in the same way.

The team also implemented a number of fixes to network CDN, including resolving a timeout issue and resizing style issues.

And they have been preparing for October earnings, specifically looking at staked Stargate support.

The web services team have been working on additional updates to the rich editor in our interfaces set along with changes to the Markdown serialiser.

They are also pretty much done with the next release of API, which we expect to be released next week. Work has also started on a series of updates to the account functions in API.

We’ve had a number of customer meetings this week, including three new opportunities.

Finally, we expect to have interfaces for content distribution in open Beta for the community when Arthur’s back, so in the second week of November (TBC). The processes are all integrated and ready to go. We’re currently working on the front end designs, which will be released under my.edge.network in the first instance.

And that’s it!

Enjoy your weekends 🙂

Mon, 28 Oct 2019 14:30:00 +0000 5dc51877e5287b1e040ba691 Joseph Denne 2019-10-28T14:30:00+00:00
Multi-Device Onboarding https://edge.network/updates/network/multi-device-onboarding You can now add as many Hosts to the Edge Network as you’d like. You can read about how to set up node here:


In support of this Edge CLI 1.4.1 has been released. Please update before installing additional nodes. You can do this by running:

apt install edge-cli

We look forward to seeing your new devices online!

Fri, 25 Oct 2019 14:00:00 +0000 5db305c6eb5ba81e23ad6cce Adam K Dean 2019-10-25T14:00:00+00:00
Weekly Update: W/C 14th October, 2019 https://edge.network/updates/announcements/weekly-update-wc-14th-october-2019 Hi everyone 👋

This week has been pretty full on, so this will be another short update, as I’m still going!

We’ve had a whole series of customer and potential customer meetings this week, and have also been in pitch for an interesting new engagement. These have been pretty much back to back, hence not being active in channel as much as usual.

So you are aware, Arthur is away for the next couple of weeks, taking a much deserved holiday. Adam will be carry his duties during this period.

The team made good progress closing out the snagging list on the updates to our editorial interfaces. They also pushed through a series of updates to the content for the new site in support of what were our web services. I expect this be going live in November now. There’s still a bunch to do, but it’s coming along well.

We have an internal beta of the Content Distribution configuration interfaces within dashboard on my.edge.network up and in testing.

This is going to be released to the community to enable you all to use and feedback on the service sooner rather than later (November). It’s very much a beta, and we have a roadmap for its development, but it will be pretty neat to have the service usable directly from within account pages.

The team has also been hard at work migrating an existing customers property to our web services. This goes in to testing next week.

The updates to our roadmaps discussed last week progressed much further this week. The new roadmap is pretty detailed, and is packed with deliverables. I’m not sure when we’ll be releasing this yet, but you’ll be the first to know.

There have been a bunch of improvements to ACL cleanup for expired Vault tokens. These had been causing latency in remote DC distributions, so it’s great to see this improved.

And etag support has been added to the Go distribution of Content Distribution and pushed to test.network where is currently being put through its paces, alongside all of the other components in the updated app.

And that’s it for this week. Enjoy your weekends!

Mon, 21 Oct 2019 13:30:00 +0000 5dc51704192ddb1e283889ca Joseph Denne 2019-10-21T13:30:00+00:00
Weekly Update: W/C 07th October, 2019 https://edge.network/updates/announcements/weekly-update-wc-07th-october-2019 Hi everyone 👋

Another week gone – time is flying at the moment.

The web services team ran a full creative review and worked through amends to our editorial interfaces on the back of feedback from the session. The interfaces are looking really strong now, and I hope to be sharing them soon.

They worked on a series of general bug fixes and improvements, as well as progressing a restructure of our documentations.

The network team has been focused on fixing a bug with session storage which was occasionally failing to capture sessions when they were closed and opened within a small timeframe.

They have also been working to introduce a more accurate device status in explorer, which now shows when a device was last connected.

A new method for cleaning up old ACL sessions has been progressed, and the finishing touches have been made to the new Content Distribution app, which is live in test.network, and which will be put through its paces on Monday.

We’ve also been busy working on the roadmap for the next two quarters and in to next year, which we’ll be releasing soon.

And the method used for syncing requests with Hosts was optmised and refined.

We opened discussions with a number of potential new customers. As ever it’s early days, but the discussions have been positive.

And finally we released a significant update to the Edge Network Explorer, which brings a number of improvements, the more noticeable among them being an ability to see when a device was last seen on the network, as well as a much quicker update cycle (now measured in seconds!).

You can read about this more here: https://edge.network/en/updates/network/tracking-devices-on-the-network/

And that’s it!

Enjoy your weekends.

Mon, 14 Oct 2019 13:30:00 +0000 5dc515638429dd1e46854399 Joseph Denne 2019-10-14T13:30:00+00:00
Tracking devices on the network https://edge.network/updates/network/tracking-devices-on-the-network Image

While you see the changes to the explorer, a lot of what goes on actually happens beneath the surface. Yesterday, you may have noticed that all Hosts appeared offline in the explorer as well as in the dashboard, and remained that way for a few hours. This was actually part of a major update to our synchronization layer—you’ll learn about that more soon—which meant we had to put the explorer into a maintenance mode for a few hours while we upgraded the sync services that manage the aggregation of data from the network which powers, among other things, the explorer.

But how do we gather this data, where does it come from, and how does it work?

Follow me as we venture on a curiosity voyage into the depths of the network.

Devices & The Network

Our first stop on this curiosity voyage is the network itself. This is where the data begins to form. When a device connects to the network, a session is created within the Stargate it connects to, and this remains active until the device goes offline.

This session contains information such as which device it belongs to, which service it pertains to (all services, the Agent service as well as the Host service, have their own sessions) as well as some other useful metadata too.


Synchronization layer

Our next stop on the curiosity voyage is the synchronization layer. In this shadowy place, thousands of little robots work tirelessly to… okay, they’re just software programs. But these synchronization services run day and night, watching each and every Stargate for the smallest change to their sessions.

When a change is detected, these synchronization services—or sync—work out what has happened. Has a device come online? Has a device gone offline? Has it done both?

Once the sync service has determined both what has happened, and which device it has happened to, it records this data in the contributor database. When a device comes online, a new session is created with information such as location, time, the Stargate the device has connected to, and some device specific information such as the CPU architecture. When a device goes offline, the sync service closes this session, recording the exact date and time that the device left the network. And when it comes back online again, the whole cycle begins again.


Turning data into information

The last stop on our curiosity voyage may be familiar to you, it’s where we turn the data into information, linking up data about devices with data about their activity, to bring you the Edge Network Explorer.

Previously, the explorer would be querying the network directly, running through Stargates to get an idea of where devices were, what they were up to, and when they were last seen. This wasn’t very efficient so we could only update the data roughly every ~2.5 minutes.

Now that the data is managed by the sync service layer, the explorer is now able to query the data more often, meaning we can drastically increase the refresh rate. We’ll be trialing some different numbers in the coming weeks but we’re starting with a 60 second refresh rate. That’s 250% quicker than before, meaning the data you see in the explorer is closer to the heartbeat of the network than ever before. Kapow!

In addition to this, the data we’re seeing is more reliable and up to date than ever before, with over 130 online devices being seen yesterday, their every activity viewable in real time.


More where that came from

If you think that’s great, you’re right. But there’s more where that came from. Earlier this month we made some major improvements to our earnings and payout layer, and coming soon you’ll start to see your earnings appear day by day, so stay tuned, as we’ll be writing more about that.

Fri, 11 Oct 2019 17:30:00 +0000 5da0bcddf0b4f81e47c9e90a Adam K Dean 2019-10-11T17:30:00+00:00
Weekly Update: W/C 30th September, 2019 https://edge.network/updates/announcements/weekly-update-wc-30th-september-2019 Hi everyone 👋

We had an AMA today, so today’s update will be short and sweet.

First up, here’s the transcript of the AMA: https://edge.network/en/knowledge/network/ama-recap-october-04th-2019/

And here’s the update for the week:

The network team fixed a bug with auto certificate generation for Content Distribution which was causing the unnecessary recreation of certificates when Gateway rebooted. In certain circumstances this could have caused a cascade effect, knocking Gateways offline, so it was good catch.

They also deployed an improved request locking method that allows more hosts to attempt a request that is taking a long time to resolve.

The migration of CDN to Go moved along well, with improvements in performance and caching, along with other general refactors.

An issue with earnings calculation was fixed ahead of the payout process, which we expect to run early next week. The team also diagnosed an issue with session storage which will be deployed next week.

Further changes to the dashboard were made along with the introduction of a FAQ section to the site in support of self onboarding, which will be live soon.

The BD team delivered a workflow workshop with a global publisher yesterday, which went really well.

The web services team have been focused on getting the reskin work for Publish complete, and have been working on general bug fixes alongside this effort.

And there’s been good progress made on the support site for the revisioned services set. Still no live date, but we’re getting closer.

And that’s it for this week! Thank you for your ongoing support.

Mon, 07 Oct 2019 13:30:00 +0000 5d9c4021e6aa820793f8152a Joseph Denne 2019-10-07T13:30:00+00:00
AMA Recap: October 04th, 2019 https://edge.network/knowledge/network/ama-recap-october-04th-2019 Question 1

Will the dependencies that we use to install our nodes be replaced by decentralized solutions? I’ve read that Docker, for example, is backed by an In-Q-Tel venture which is publicly known to be a capital firm of the American CIA.?

Arthur Mingard: I can’t really comment on rumours around Docker and any CIA involvement, but we do have a general position on third-party dependencies - the fewer the better. We’ve already finished working on supporting Balena which we will introduce in the next quarter, and are also working on a binary solution that has no dependencies whatsoever!

Question 2

Why not give zip files to extract instead of new SD cards or port forwarding?

Arthur Mingard: Each device must be setup with a UUID so we can’t create a generic zip. The good news is we won’t have to update SDs again as they are now self-updating, just like self-onboarded devices.

Question 3

I’ve heard about voting rights. What are the specific things this will apply to and do you have an idea when and why the first voting will occur?

Joseph Denne: We’re going to be building a voting mechanism in to the heart of the network, which will give voting rights to all Stargates, and to the top performing Gateways and Hosts. (One vote one node.)
Voting rights will cover everything that has a material impact on the network, from key junctures in development to revenue distribution.

At the moment these sorts of decisions are taken by the team at Edge Network Technologies Ltd., the not for profit entity charged with the ongoing delivery the network. In time they will be broken out and voted on by participants in the network. This may also include customers. We like the idea of a customer board/panel being able to be part of this. There’s no timeframe in place yet. As soon as there, we’ll let you know.

Question 4

Will we be able to receive some kind of notification if a node, founding or self-onboarded, stops working?

Arthur Mingard: We are working on a solution to provide a number of notification channels, including email alerts, API subscriptions, Slack notifications and web hooks. We’ll be announcing plans around this shortly.

Question 5

Can we add a staked indicator to the explorer, for example 3.5% staked at the moment?

Joseph Denne: I love this. Yes. We’ll add it to the backlog.

Question 6

Who wrote the copy of the website?

Arthur Mingard: It’s entirely generated with AI

Question 7

Have you hired or considered hiring data scientist to learn from the data captured in telemetry services, QA etc.?

Joseph Denne: We previously had a data scientist who was an actual astrophysicist on the team (they specialised in brown dwarfs if you can believe it). They leant us a lot of insight, and it will probably be useful to get more insight like this in future. But for now, we’re focused on core services and performance.

Question 8

Does the DNS service allow for cnames or aliases at the apex in a similar way to the alias in AWS and if so, does it allow off network?

Arthur Mingard: Yes, this is now supported, both on and off the network. This feature was deployed early last month and has proven to be very useful.

Question 9

How can Edge improve the performance for users connecting using public DNS settings such as

Arthur Mingard: We’re working on a process that removes the reliance on BGP network routing, favoring a more accurate process of locating the closest device. This is likely to be delivered in Q1 2020.

Joseph Denne: BGP requires the maintenance and continual monitoring of routing peers to work efficiently in a network like Edge, and given that the network has a clear and up to date understanding of its own shape, it makes sense for us to look to how we can improve traffic distribution at this level.

Question 10

The list of hosts is showing which Stargate they are connected to. Shouldn’t there be a reference to a Gateway instead? I thought the communication was like this: Stargate < > Gateway < > Host. Do Hosts skip going through a Gateway if a Stargate is closer?

Arthur Mingard: Stargates and Gateways serve two very different purposes. Stargates handle DNS, network coordination and service distribution, and Gateways handle http requests, queueing and app distribution. We are looking at ways to make Gateway act as a mirror for the Stargate coordination data so there’s every chance this process will eventually add some performance increase. It’s worth noting that once DNS has resolved to a Gateway, the requests and responses are handled by Gateway and Host only, and have no dependency on Stargate other than low loading operations like coordination.

Question 11

When will we be able to downscale the hosts? I would love to have a node on a server that doesn’t meet the requirements of a raspberry but very close.

Arthur Mingard: The Raspberry Pi is a very low powered device so it’s unlikely we’ll be deploying CDN to something with less resources, so your device might not be able to contribute just yet. Storage will work on lower powered devices when we introduce it to the network. We will always aim to make the best use of resources and there is every possibility future service will have even lower requirements.

Question 12

What is the current process for someone to remove their stake and shut off their node? Will there be an easier way in the near future?

Joseph Denne: To shut it off you can just pull the power. To return the stake, right now you need to reach out to an admin, who will then disconnect your machine and give you instructions to prove wallet ownership. Your stake will then be returned. (Note that there is a 30-day cooling off period for Hosts.) And yes, we’re working on automating this whole process.

Question 13

Can marketing materials be made available to the community to assist with referrals to the network? Items such as downloadable brochures, flyers, post cards, etc. Also, who do you envision as the target market in these early stages?

Arthur Mingard: Throwaway culture is something we should all be keen to avoid. A business card or leaflet might seem insignificant, but with such a high percentage of them being discarded within hours of being received its more important than ever to think carefully before contributing in this way. Digital resources are the way forward, and that’s something we are keen to improve on!

Our target market - anything from a personal site to an enterprise platform. The concept of lowering cost and simultaneously increasing availability at the edge is applicable across the entire spectrum of digital propositions.

Question 14

Will Edge be listing on node monitoring sites such as Masternodes Online? If so, which ones and when?

Joseph Denne: Good shout. Yes. We’ve spoken to a few of these sites in the past and will pick up the conversations again now self-onboarding is live.

Question 15

The number of Stargates has gone down to 7, is it downsized?

Arthur Mingard: To improve network performance and reduce the number of hops we have removed Stargates that were not receiving traffic. These idle Stargates were serving no traffic, bouncing DNS requests on to other Stargates which was having an adverse effect on the speed of DNS resolution. We anticipate introducing more Stargates soon, in areas where there is higher demand.

Question 16

When will there be GPU-enabled nodes?

Joseph Denne: We’re working on giving the CDN application access to the GPU units in devices, which will be the first practical application of GPU resources within the network. Specifically, it will be used to increase the performance of image manipulation functions as part of the media pipeline in the Content Delivery service.

Question 17

When will Edge have onboarding from the site? It’s a bit weird to have to contact admins on Telegram for it.

Arthur Mingard: The initial phase of self-onboarding was designed to give us the flexibility needed to plan UX of the next iteration without introducing any technical debt. We are now moving onto the second phase, where an automated version will replace the current manual validation.

Question 18

I’m curious about the host SD card capacity cost/benefit as well. I planned on using a 128gb card on my Pi 4 but it was actually corrupt on delivery so I used an available 64gb. I figure that there would be, presently, no benefit but perhaps some future proofing for eventual features is worth planning for?

Arthur Mingard: Firstly, sorry to hear about your SD card. That’s very frustrating! Absolutely a good idea to offer up more space on the device - it will in time be used and compensated for.

Question 19

Why doesn’t my FN have the same behavior as my self-onboarded host? Because my FN works perfectly fine. They are connected to the same router & power outlet. They should have the same session lengths. Do they use different software or calculations on your back-end?

Joseph Denne: Each node on the network will perform different jobs depending on demand (jobs in the Gateway’s queue), latency, existing work done, and a few other variables. No two nodes are the same, no two nodes perform the same work, therefore no two nodes will earn the same amount.

Question 20

How about putting a QR code on the Edge dashboard for the staking address?

Arthur Mingard: This could be useful for improving mobile usability. We’ll put this in the backlog.

Question 21

My self-onboarded node has been online for all days except for a week early on in Sept. However, the traffic seems very unstable. How can it be that some days there is zero revenue, not 0.1 or 0.5 or something like that but 0? What kind of sites are currently running Edge services in the network? To me it feels like the algorithm for calculating earnings must be broken as I can’t see how the earnings pattern can reflect traffic on normal sites.

Arthur Mingard: Some sites on the network have a long cache, often between 1 day and 1 month. This level of caching means that there can be days where the number of requests are lower. If there are a number of Hosts connected to the same Gateway as your Host and perhaps they have a better connection, they will resolve more requests than yours. If there are very few requests then it is possible that your Host might not be used heavily. You are still payed a base value for the Host.

Question 22

Can we get clarification on what Hosts are currently doing in the network? Are they sending images/streaming video directly to the end user browsing a webpage that’s hosted on the network or do they have to route their traffic through a Stargate before getting to the end user?

Joseph Denne: In short, Hosts route traffic through Gateways: there’s no one to one relationship between an end user and a host, and their existing is completely hidden to the end user. Hosts are currently processing media (resizing, scaling, cropping etc.) ahead of delivery to the end user as part of the Content Delivery service. They also cache locally. Soon they will be used for storage, and in time for processing end customer apps as well.

Question 23

How will a trusted execution environment work with online software that’s based on JavaScript?

Arthur Mingard: The network isn’t written in JS - it’s in Go. And it provides an architecture that abstracts storage and processing from the online environment.

Question 24:

Why are a number of Hosts showing offline but docker ps shows containers running?

Arthur Mingard: We are addressing an issue with cached sessions now showing. No need to restart your device, but if you do see that docker has been running for more than 30 minutes and your device doesn’t show as online do get in contact and we’ll address it.

Question 25

Edge wants to be a central player in the edge computing market, but seems somewhat isolated in the industry right now. Are there plans on joining industry consortiums like LFEdge (Linux Foundation) or Edge Computing (Industrial Internet Consortium)? Is Edge striving for collabs with larger players in the cloud/edge market?

Joseph Denne: This is something that we have an eye on, but we have to pick what we focus on as there’s a lot to do, and limited resources. And while this sort of thing can be useful for pushing the industry forward and exposure, they can also use up a lot of time to little material effect. So in short, we have an eye on the various consortiums that are out there, and we’ll approach them when the time is right.

Question 26

What’s the current relationship between EDGE and INDX capital? Is Edge keeping an eye on company practices for those listed as ‘partners’? Was there a determined timeline in the partnership agreement for them to onboard their nodes in the network? How are they fulfilling their end of the deal?

Joseph Denne: We know the guys - they are here in London - and have leant them support. They tested with our containerized service and as far as we’re aware, the intention is for it to be used in time. We keep up to date on an ad-hoc basis, but haven’t spoken to INDX for around 3-4 months as far I’m aware.

Question 27

Can you elaborate on the current way of locking stakes in the originating contact and how this will be done in the future? When can we expect trustless (smart-contract-based) locking of stakes on self-onboarding?

Joseph Denne: It’s currently managed by the team as an interim measure, with funds going to a dedicated staking wallet, and from there to the originating contract. This is for ease of audit. In time we’ll be moving to a contract-based, fully automated process.

Question 28

Is hosting large scale ML or astronomy datasets a viable use case for the upcoming file-storage?

Arthur Mingard: Object Storage is meant for static files rather than evolving data, but there’s no reason that it couldn’t be used for this sort of data. We’re moving to Beta in the coming months for ephemeral data and to persistent data thereafter. The beta period will give us a lot of data/feedback which will in turn impact the use cases for the tech.

Question 29

Could peer2peer syncing protocols (e.g. bittorrent) be used to downloads large amounts of data directly from the hosts?

Arthur Mingard: There’s no plan for this at the moment, but the idea is sound. We’ll give this some thought.

Question 30

Have you considered deploying an easy to understand privacy policy framework for Edge hosts (and network as a whole)? Mainly to gather feedback and provide education on that front too from early on.

Joseph Denne: There’s a bunch of legal work to get through, and this is part of that. The setup of the network is within the legal of the UK, and the security approach is designed with the protection of individual hosts in mind. Anyway, yes!

Sat, 05 Oct 2019 13:30:00 +0000 5d9c41645a5d9c072ee9d446 Bolaji Oyewole 2019-10-05T13:30:00+00:00