Edge Latest articles from the team en 2019 Edge Network Technologies Ltd. All rights reserved. Fri, 18 Oct 2019 13:37:36 +0000 2019-10-18T13:37:36+00:00 en 2019 Edge Network Technologies Ltd. All rights reserved. Edge https://edge.network/assets/img/dadi-logo-colour.png https://edge.network 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 sweat.

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
Weekly Update: W/C 23rd September, 2019 https://edge.network/updates/announcements/weekly-update-wc-23rd-september-2019 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.

Mon, 30 Sep 2019 13:30:00 +0000 5d92253976825e078df8a27d Joseph Denne 2019-09-30T13:30:00+00:00
Weekly Update: W/C 16th September, 2019 https://edge.network/updates/announcements/weekly-update-wc-16th-september-2019 Hi everyone! 👋

In case you missed it, The Edge network won the award for “Best Edge Computing Platform” in Juniper Research’s Technology & Innovation Awards 💥

Here’s the press release: https://www.juniperresearch.com/press/press-releases/future-digital-award-winners-announced-for-technol

We’ve had a whole bunch of Edge stickers made!


Those Founding Node owners who opted for a new SD will receiving some with new card shortly. Anyone else that would like to get their hands on some can do so by completing this form:


We expect to be opening up self-onboarding to multiple nodes per account in early October.

The start of October will also see the release of automated earnings updates, with daily amounts being added to the dashboard.

A small refresh of the dashboard will be pushed to live to accommodate this too.

We’ve made strong progress with the refresh of the editorial interfaces for the SaaS version of what were our web services that will be launching later this year. The date picker, number fields, reference selection view, document deletion confirmation prompt, profile page and welcome page were all completed, as were font updates and several mobile improvements.

OKEx, CoinMarketCap and CoinGecko all updated our branding to Edge. A few more exchanges and listing sites to go, but we’re nearly there.

The network team made a significant update to caching in the Content Distribution service, which was released to mainnet today.

Specifically the short term cache has been altered on Gateway to be configurable on a per-domain basis, meaning we can now configure different caches for different customers.

They also successfully tested an important component for Object Storage - the propagation of file content between connected Gateways.

And some vital fixes were made to Host, delaying request contribution until CDN has been fully configured on the device. This removes the potential for bad job processing at the point of device start up.

The team have also been working on the delivery of an encrypted network overlay to prevent the sniffing of traffic. There are a few outstanding issues to be worked through, which we expect to be closed out next week.

Inflight pooling for Content Distribution has been introduced in the Go build of the software. This significantly improves performance when asynchronous asset requests occur.

We completed the integration of a new CRM platform internally which has been put in place to support the sales process for network services. My co-founder Will is going to be looking after customer onboarding.

We had confirmation of the move of an existing customers infrastructure in to Content Distribution on the network. We expect this to take place in October.

And finally a reminder that our next AMA will take place on the first Friday in October, the 04th.

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

Mon, 23 Sep 2019 13:30:00 +0000 5d891215a0f77d0766ba2da7 Joseph Denne 2019-09-23T13:30:00+00:00
$EDGE Now Tradable on OKEx https://edge.network/updates/announcements/edge-now-tradable-on-okex The rebrand of DADI to Edge has now completed on OKEx. Deposit and withdrawal services for $EDGE are now available.


  1. The project symbol DADI has be renamed as EDGE
  2. The original corresponding trading pairs have been updated to EDGE/USDT, EDGE/BTC

If you have any questions about the update, please reach out to us directly on one of our support channels.

Trade now at: https://www.okex.com

Thu, 19 Sep 2019 03:30:00 +0000 5d83a61a652e7706f9642a8f Bolaji Oyewole 2019-09-19T03:30:00+00:00
Edge Recognised as “Best Edge Computing Platform” in Future Digital Awards https://edge.network/updates/network/future-digital-awards-best-edge-computing-platform Juniper judged award entrants on a number of elements, specifically: Product Features and User Benefits; Product Innovation; Commercial Partnerships; Commercial Launches; Compliance & Certification; and Future Business Prospects.

The key strengths and advantages of Edge noted by the judging panel were:

  • Overall effect of increasing speed and efficiency in a wide range of applications.
  • Use of blockchain in edge computing.
  • 7 established B2B partners.
  • Network coverage in 60+ countries.
  • The fact that anyone with a laptop, mobile or any connected device can earn $EDGE tokens by supplying spare computational and storage capacity to the network.
  • The panel believe this idea is unique and innovative.
  • This is a prime product, as Juniper Research expects 5G and edge to increase massively in the coming years especially within sectors such as smart manufacturing and smart cities.
  • The business model leverages existing connected devices to provide computational power that can be monetised was seen as a huge plus.
  • Despite a lack of standards, the key strength here is the solution uses most connectivity standards.
  • Edge is open to partnerships with anyone who has a device.

Joseph Denne, CEO and Co-Founder of Edge Network said:

“It is a testament to the hard work of the team here at Edge that we have won ‘Best Edge Computing Platform’ in this year’s Future Digital Awards and we are delighted to have been recognised by this award win. With edge computing expected to be a significant emerging technology, we see ourselves as a first mover in the space. Over the next few years we envisage our network growing well beyond the current 271 nodes, with 45 going live in the first week that we started self-boarding in September 2019, leading to a truly global, scalable and secure edge computing network.”

Elson Sutanto, Principal Analyst at Juniper Research said:

“Edge was an outlier when it came to judging this category, mainly due to their network being live in production and already allowing people to monetise their spare computing capacity. Along with IoT, 5G and blockchain, we see edge computing as a key emerging technology of the future.”

Wed, 18 Sep 2019 11:30:00 +0000 5d821036c8ff8606d0580c8d Chris Mair 2019-09-18T11:30:00+00:00
Weekly Update: W/C 09th September, 2019 https://edge.network/updates/announcements/weekly-update-wc-09th-september-2019 Hi everyone! 👋

It’s been another packed week for Edge. I’ve said it before and I’ll say it again: I’m amazed by the volume and quality of the work that is being produced by the team.

The engineering team have been cracking on with work on the front end to our publishing tools, specifically working on mobile compatibility for collection and documents views.

They also released CDN v4.0.0 RC1, which is currently being tested under test.network on the network.

Alongside this, updates were made to the current release candidate of API (6.0.0 RC2), fixing some issues that arose from the ongoing testing and adding some requested features around media.

A strong start was made on documentation for the upcoming features for API in support of our SaaS proposition, particularly building OpenAPI specs for new endpoints. This work led to a review of the existing OpenAPI specs, as well as writing new ones for the parts of API that were not covered (e.g. the REST interface for managing documents).

This is an an important step to take as part of our vision for the revamped documentation, allowing us to convey information about the various endpoints in visualisations such as this one:


Work on the Go version of CDN moved forward strongly, with another modifier being introduced, this time for entropy.

The application has also been undergoing performance benchmarking, with a feedback loop leading to improved performance under heavy load.

The focus for this development stream is both performance and footprint for the application. The currently deployed build of CDN weighs in at ~568MB, which while workable in the current device set, presents serious issues for embedded devices. It also uses up a lot of disk space that could otherwise be being used for Object Storage.

The new version is currently sat at ~14MB – a huge improvement.

The team have also been working on further securing the network, introducing an encrypted network overlay to remove the ability to snoop on container-to-container traffic.

Work was finished on the consensus mechanism used by gateways as part of the distributed DAG (the database used for storing file shards and other data for Edge’s next milestone release).

Work was undertaken to improve the consul session capture routine, which is now much more performant as a result.

And we’re now down to the last few tickets relating to earning automation. We hope to be deploying this update soon, and moving to much more regular reporting of earnings, as well as upping the frequency for payouts.

Our legal advisors closed out work on a new reseller contract, which is being put in place with a series of new partners, starting in October.

Adam wrote about some updates to the network explorer, which you can read here: https://edge.network/en/updates/network/network-explorer-updates/

And we attended an event with the PPA, which was focused on strategic partnerships. The attendee list for our workshops with the PPA next month continues to grow.

We received a brief for an exciting new project with a well known brand, who are considering building on our platform.

There are now 60 registered devices through self-onboarding, of which 45 are staked and earning. That takes the total staked position in the mainnet to 1.15m $EDGE.

Finally our next AMA will take place on the first Friday in October, the 04th. It’s been a while since we held one (as a result of our laser like focus on getting self-onboarding done), so I’m sure they’ll be a lot to cover off. So get your questions in ahead of time!

And that’s it for this week.

Enjoy your weekends 😀

Mon, 16 Sep 2019 13:30:00 +0000 5d7f672e424e23076fb4f256 Joseph Denne 2019-09-16T13:30:00+00:00
Network Explorer Updates https://edge.network/updates/network/network-explorer-updates The first thing you’ll notice is that Hosts are now being mapped. We’ve restored the network device location functionality, which, when zoomed out, gives an accurate overview of the network within the last minute. With privacy in mind though, we fuzz the locations slightly. This means that when you zoom in, node positioning won’t be exact.


You can now also view more information about network devices, with Stargates exposing their name, location and architecture. (Note that Stargates are currently only running on amd64 chipsets.)


Gateways also have their location and architecture exposed. In addition the Stargate that the Gateway is currently connected to is listed. This shows the state of the network as of the last minute.


Hosts are exposing the Stargate that they’re connected to, along with their location where available, and their architecture. Now that both Founding Nodes and self-onboarded Nodes are live on the network, you will start to see a number of different architectures here.


There are many additional features in the pipeline, including distinguishing Founding Nodes, showing the connections between Stargates, Gateways, and Hosts, and introducing usage statistics directly from the network’s telemetry service.

You can access the explorer here: https://explorer.edge.network

Thu, 12 Sep 2019 01:30:00 +0000 5d7a248455201707116183a3 Adam K Dean 2019-09-12T01:30:00+00:00
$EDGE Now Tradable on Bitfinex https://edge.network/updates/announcements/edge-now-tradable-on-bitfinex The rebrand of DADI to Edge has now completed on Bitfinex. Deposit and withdrawal services for $EDGE are now available.


  1. The project symbol DADI has be renamed as EDGE
  2. The original corresponding trading pairs has been updated to EDGE/USD, EDGE/BTC, EDGE/ETH

If you have any questions about the update, please reach out to us directly on one of our support channels.

Trade now at: https://www.bitfinex.com

Tue, 10 Sep 2019 14:30:00 +0000 5d77b7a0652e7706f9642a84 Bolaji Oyewole 2019-09-10T14:30:00+00:00
Weekly Update: W/C 02nd September, 2019 https://edge.network/updates/announcements/weekly-update-wc-02nd-september-2019 Hello everyone 👋

What a busy week.

The first full week of self onboarding for the network has run pretty smoothly. We now have 262 nodes in the network overall, 22 of them self on-boarded, with an additional 23 in the process of being setup.

45 new nodes in 6 days!

In the coming few weeks we will be moving from a manual activation switch in the network (which we’re using for testing and feedback at the moment), to a fully automated process.

We’ll also be lifting the restrictions around the number of nodes that a single individual can run.

Within Edge Host the dApps themselves - Agent, Host and CDN - are all automatically updated. Edge CLI ( edge-cli ) however needs to be updated manually by those running a self on-boarded node.

We’re improving it all the time, with daily builds being pushed to the APT repository at archive.edge.network. Version 1.2 was released yesterday containing minor fixes and introducing the stop command.

We also removed the risk of starting Agent more than once, and have improved the flexibility in the auth component, adding the ability to use env variables.

We are working towards opening up the Github repository for edge-cli to allow access to release notes and the like, and are looking at methods for letting users know that there’s an update.

In the meantime, here’s how you update it:


$ sudo apt update


$ sudo apt install edge-cli


As expected, the new nodes coming in to the network unearthed a few items that needed attention, and this has been our primary focus this week. For example, we found a case whereby Host was failing to properly resolve DNS for origin domains for the Content Distribution service in certain cases, which was as a result of issues with local resolvers. The fix for this was to build in a call to an internal resolver in the network.

To assist with this sort of thing in future the team added nslookup to the remote commands available to Agent, which makes DNS debugging much easier for us in light of some failing lookups we were seeing earlier in the week.

Outside of testing on the back of self onboarding moving to live the team have also been progressing the updated interfaces for the next milestone release of Publish. It has a new name as well.

The interfaces for Edge DNS have also progressed significantly, and we expect them to be moving in to integration with mainnet next week. This will be our first fully public service – a major milestone for the network.

There are a few updates for my.edge.network, specifically tidying up the node interface now that multiple nodes can be added to a single account. This will be a point release, as the service will ultimately be merged with the interfaces being developed for service use.

We also extended my.edge.network account update hooks to handle password changes to create new ACL tokens.

The anonymous account functionality mentioned last week has progressed significantly. We have progressed the build to enable enhanced account functionality, including 2fa, and has also been further the security approach through the use of per field authentication for account records.

Collision testing for the hashing mechanism behind the anonymous account system is underway. We’re running hundreds of millions of account creation events this weekend to understand the collision rate for the chosen mechanism.

We’re working a method that makes the crypto key as user friendly as possible. So while it would easy to just use an extremely long code, we think it’s overkill in this sort of setup.

Work to update the network explorer continued, specifically plugging it in to the Host telemetry layer, which involves reading individual node session data, enabling the correct rendering of Host status.

On which, the team improved the detail of network session storage by adding Datacenter, which significantly improves our ability to track devices through the network explorer.

This work goes in to code review on Monday, and we expect to have the node status back to providing real time telemetry very soon.

We progressed discussions to migrate one of our largest customers to the latest releases of our web services. We also discussed the process of moving them on to our DNS service, and migrating form a VPC of CDN to the mainnet. Watch this space.

We began work on API integration for another mobile application for an existing customer.

We moved forward with work on the Golang build of the Content Distribution layer for the network. This is a stripped down and lightweight evolution of the existing NodeJS web service, but specifically tailored to the network where a smaller app footprint has a significant performance benefit.

And we completed initial Gateway DAG consensus tests in the testnet (test.network). The DAG is used to distribute shared and hashed storage data across the network, a key component ahead of the beta release of storage on testnet at the end of the month.

Finally, we added new Gateway to mainnet (non-earning), right here in London.

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

Mon, 09 Sep 2019 01:30:00 +0000 5d76375c91a3920743144690 Joseph Denne 2019-09-09T01:30:00+00:00
Weekly Update: W/C 26th August, 2019 https://edge.network/updates/announcements/weekly-update-wc-26th-august-2019 Hello everyone 👋

First up, self on boarding is now ready in the Edge network 💥

Expect an article on this on site soon, inclusive of FAQ. But in the meantime:

Onboarding is open for Linux based AMD64/ARM devices via our Apt repository at https://archive.edge.network

The process is super straight forward.

As previously discussed, because this is the first time that we have had a varied set of devices on the network, their enabling for production traffic will be on a gated first come first serve basis until we have completed testing in the mainnet.

The process is as follows:

  1. Install Docker (vs. 18.06+)
  2. Install Edge Cli (edge-cli)
  3. Connect your device to your my.edge.network account
  4. Provide your refundable proof of stake (the wallet address will be provided by a member of the team)
  5. Await enabling for production traffic in the network

Here’s the process for installing Cli:

  1. Add the Edge repository to your sources
$ echo "deb https://archive.edge.network/ /" > /etc/apt/sources.list.d/edge.list
  1. Import the public key for the repository
$ wget -q -O - https://archive.edge.network/KEY.gpg | apt-key add -
  1. Update Apt
$ sudo apt update
  1. Install Edge Cli
$ sudo apt install edge-cli

Once done you will need to add you device your account at my.edge.network, which is done at the command line through Cli as follows:

  1. Attach your device to your account
$ edge-cli login -u "email@address.com"
  1. Register your device
$ edge-cli register
  1. Start the node
$ edge-cli start

And that’s it.

Note: devices will not be visible on your dashboard until they have been enabled for production on the network.

Once done a member of the team will be in touch for the funding of your device’s PoS and the enabling of the device on the network.

Note that we’ll be about tomorrow to assist with the process. We expect to be onboarding a few devices this weekend, and will ramp up onboarding next week from Monday.

Once we have full confidence in the process we will move to automate the enabling of devices in the network in full.

Exciting times!

Next up, as you will have seen, $EDGE is now tradable on KuCoin and IDEX. I appreciate that it’s taken a while for the updates to filter through the exchanges, so thank you for sticking with us!

CoinMarketCap will be updating the ticker once the majority of exchanges have updated, which we expect to be very soon.

The Tiipr app has been approved by Apple, and is now live and in production testing.

We met with the PPA again this week, with agreements finalized for our upcoming workflow workshops and breakfast sessions. We’ve agreed a content outreach partnership, which I’ll share more on in a couple of weeks.

The SaaS team for web services team have been working on the finalisation of API access keys, ready for the release of API 6.

API 6 comes with a bunch of new updates, including but not limited to:

The team have been also been head down and focused on reskinning Publish, as we move it forward to bring it inline with the new branding for our web services stack. We’re very excited to be able to share this with you. Watch this space!

A note on network stats:

We’ve moved a bunch of additional production traffic to the network over the past few weeks, and have been compiling performance data on the products using the network vs. their performance before they were using the network.

This will be being presented as a series of success stories for the edge.network site in due course, but I wanted to share a few key metrics with you for one of the products currently in production vs. it’s performance prior to moving to the network.

  1. Avg. Domain Lookup Time (sec) 0.05 (Edge) vs 0.06 (legacy stack), an improvement of 20.19%
  2. Avg. Server Connection Time (sec) 0.25 (Edge) vs 0.33 (legacy stack), an improvement of 25.10%
  3. Avg. Server Response Time (sec) 0.51 (Edge) vs 0.6 (legacy stack), an improvement of 18.69%
  4. Avg. Page Download Time (sec) 0.0246 (Edge) vs 0.03 (legacy stack), an improvement of 18.84%

Note that while we’re not really comparing like for like (as the Edge network is a pretty unique platform that is highly localising content worldwide as opposed to delivering out of a single central source), the metrics clearly demonstrate the benefits of the technology, even before factoring in cost savings.

We have an exciting new approach to user account management in the network which is currently in testing. This focuses on anonymity and the protection of your data, and makes use of a lot of the functionality coming in API 6. We’ll share more on this soon.

We’re basically looking at methods of enabling the anonymous use of the network.

And finally a new member of the networking team joined the fold.

We’ll introduce him at our next AMA. He’s working on core network technologies and the next version of Content Distribution.

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

Mon, 02 Sep 2019 13:30:00 +0000 5d6cdc96b30a5f07fde365cc Joseph Denne 2019-09-02T13:30:00+00:00