<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Edge - Medium]]></title>
        <description><![CDATA[Upholding the founding principles of the Web through the democratisation of computational power. - Medium]]></description>
        <link>https://medium.com/dadi?source=rss----a5531445a1f---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Edge - Medium</title>
            <link>https://medium.com/dadi?source=rss----a5531445a1f---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:57:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/dadi" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[2020 Network Computing Awards Finalist]]></title>
            <link>https://medium.com/dadi/2020-network-computing-awards-finalist-f953f5f9d86?source=rss----a5531445a1f---4</link>
            <guid isPermaLink="false">https://medium.com/p/f953f5f9d86</guid>
            <category><![CDATA[edge]]></category>
            <category><![CDATA[edge-networking]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[edge-computing]]></category>
            <dc:creator><![CDATA[EDGE Network]]></dc:creator>
            <pubDate>Sat, 22 Feb 2020 10:50:36 GMT</pubDate>
            <atom:updated>2020-02-22T10:50:36.205Z</atom:updated>
            <content:encoded><![CDATA[<h4>Edge is a finalist in the 2020 Network Computing Awards in the “Network on the Edge” category!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1fIkvBkt5WCXDequnUk7ng.jpeg" /></figure><p>Edge has been nominated alongside Clearblade, Cloudera, Dell EMC, EdjX, Hitachi Vantana, IBM and Silver Peak.</p><p>Support us by casting your vote now: <a href="http://www.networkcomputing.co.uk/ncawards/?page=nca2020vote">http://www.networkcomputing.co.uk/ncawards/?page=nca2020vote</a></p><p><em>Written by Chris Mair. Chris is the Founder &amp; Marketing Director of Edge Network Technologies.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f953f5f9d86" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dadi/2020-network-computing-awards-finalist-f953f5f9d86">2020 Network Computing Awards Finalist</a> was originally published in <a href="https://medium.com/dadi">Edge</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Edge Console]]></title>
            <link>https://medium.com/dadi/introducing-edge-console-980ef39b809f?source=rss----a5531445a1f---4</link>
            <guid isPermaLink="false">https://medium.com/p/980ef39b809f</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[network-edge]]></category>
            <category><![CDATA[edge]]></category>
            <category><![CDATA[edge-computing]]></category>
            <dc:creator><![CDATA[EDGE Network]]></dc:creator>
            <pubDate>Mon, 10 Feb 2020 14:29:40 GMT</pubDate>
            <atom:updated>2020-02-10T14:29:40.416Z</atom:updated>
            <content:encoded><![CDATA[<h4>We are excited to announce the initial release of Edge Console, the successor to My Edge and the first stage in a comprehensive upgrade of our web apps.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PvrU49d1N_bTMu4pmqJ0Ng.jpeg" /></figure><p>You may have already discovered it, having been redirected from My Edge, but if not, you can access it by heading here: <a href="https://console.edge.network/">https://console.edge.network</a></p><p>You can sign in as usual, using your existing email and password (and 2FA if enabled).</p><p>This release marks an exciting new chapter in the development of our web apps, and sets us up to be able to deliver updates faster and more efficiently than ever before. Edge Console represents the tip of a spear that includes a whole host of infrastructure improvements behind the scenes. This includes improvements to the process by which we build, deliver and manage essential network support services; and the migration of the network database and accompanying Network API to this new platform. All of this work has been done without interruption to mainnet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8w1om6oxQTCwb0Jb.jpg" /></figure><p>The intrepid code explorers among you may have noticed that we’re using Nuxt.js — a Vue.js framework. We’ve built a Nuxt.js based framework from the ground up which will power this and future web apps, such as the Edge Explorer. While the first version of Edge Console has been a like for like redevelopment of My Edge, by using Nuxt.js and building for the future, we’re going to be able to bring you more updates, more often. Over the coming weeks you will notice changes here and there, as we continue to respond to feedback and improve the user experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6FbkCeiR_QOw-lSY.jpg" /></figure><p>In addition to this, we’re working on the next milestone — Content Distribution paid tiers, all managed through Edge Console. There are still lots of other things in the works as well, like automated onboarding for contributors, stake management for those who wish to migrate devices, and further down the line, a spangly new Edge Explorer built using the same framework as Edge Console.</p><p>Now, I think among you there are a few data nerds like me. And data nerds like me like numbers. So let’s take a look at some numbers. At the time of release, Edge Console is comprised of 504 commits, including 94 supporting commits in the new Network API. There have been 199 builds of Edge Console, and 171 deployments to development. Plus it is estimated over 482 cups of tea were consumed during the development of Edge Console. I expect many more will be consumed in the coming months.</p><p>Thanks for reading, and we hope you enjoy Edge Console.</p><p><em>Written by Adam K Dean. Adam is the Principal Network Engineer at Edge Network Technologies.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=980ef39b809f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dadi/introducing-edge-console-980ef39b809f">Introducing Edge Console</a> was originally published in <a href="https://medium.com/dadi">Edge</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weekly Update: W/C 27th January, 2020]]></title>
            <link>https://medium.com/dadi/weekly-update-w-c-27th-january-2020-8c511b2d351?source=rss----a5531445a1f---4</link>
            <guid isPermaLink="false">https://medium.com/p/8c511b2d351</guid>
            <category><![CDATA[cdn]]></category>
            <category><![CDATA[edge-computing]]></category>
            <category><![CDATA[content-distribution]]></category>
            <category><![CDATA[edge]]></category>
            <category><![CDATA[network-edge]]></category>
            <dc:creator><![CDATA[EDGE Network]]></dc:creator>
            <pubDate>Sun, 02 Feb 2020 09:57:01 GMT</pubDate>
            <atom:updated>2020-02-02T09:57:01.198Z</atom:updated>
            <content:encoded><![CDATA[<p><em>As part of our ongoing commitment to transparency and development in the open, our founder writes weekly updates to the Edge community. This is the 43rd of these updates, originally posted to Telegram.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zrcbpsPF3QJmRMLvVqM-zg.jpeg" /></figure><p>A few of us have been sick this week, myself included… my brain has been functioning at around 10%, at best 🤧</p><p>The network team have been working on FIDO key support and auth on the new Console, which is currently in final testing.</p><p>Based on free and open standards from the FIDO Alliance, FIDO Authentication enables password-only logins to be replaced with secure and fast login experiences. This means that Console will support keys such as the YubiKey and the Feitian ePass.</p><p>They have also migrated API in the network to version 6 and have added endpoints for CLI in order to support device names.</p><p>Device names are used on your dashboard and on the explorer making it easier to identify devices. Previously only the UUID was shown, which isn’t shown on your dashboard.</p><p>A new version of Edge CLI has been released. It now shows device name under the ‘info’ command:</p><p>$ edge-cli info</p><p>GRPC support has been added to Stargates ahead of the release of GRPC connectivity between Gateways and Stargates.</p><p>An issue with diskcache was resolved. In short, cache watchers were recreated multiple times, which meant that it was technically possible for the Gateways to become overloaded with Go routines and eventually could cause a crash.</p><p>We added PNG background colour support to CDN.</p><p>For example:</p><ul><li>Original: <a href="https://cdn.edge.network/edge.png">https://cdn.edge.network/edge.png</a></li><li>Green background: <a href="https://cdn.edge.network/edge.png?bg=1dd36c">https://cdn.edge.network/edge.png?bg=1dd36c</a></li><li>Blue background: <a href="https://cdn.edge.network/edge.png?bg=1d48d3">https://cdn.edge.network/edge.png?bg=1d48d3</a></li><li>Red background: <a href="https://cdn.edge.network/edge.png?bg=d31d35">https://cdn.edge.network/edge.png?bg=d31d35</a></li><li>Hot pink background: <a href="https://cdn.edge.network/edge.png?bg=ff33cc">https://cdn.edge.network/edge.png?bg=ff33cc</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*0hWNwidekK_rJQWN.png" /></figure><p>…Try your own 🙂</p><p>Pretty cool!</p><p>In addition, you can now independently scale the background from the image itself.</p><p>For example:</p><p><a href="https://cdn.edge.network/edge.png?bg=1dd36c&amp;bgw=500&amp;bgh=250&amp;w=200&amp;h=200">https://cdn.edge.network/edge.png?bg=1dd36c&amp;bgw=500&amp;bgh=250&amp;w=200&amp;h=200</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*Vdp7wJYJ2VwSRepv.png" /></figure><p>Also on CDN, we discussed and planned changing the routing mechanisms in the service, specifically moving from a defined origin per content type (images/assets) to a process of mime type extraction and delivery. This has the benefit of enabling CDN to properly handle files without file extensions.</p><p>It also streamlines deployment by removing any assumptions about end user use from the platform.</p><p>And finally, design for the update of the DADI Foundation to the Edge Initiative was completed. The new site should be going live in the coming month or so, along with a wealth of research and supporting materials that have been generated by the Foundation.</p><p>We’ll be sharing the logo and the look &amp; feel ahead of launch.</p><p>And that’s it for this week!</p><p>Enjoy your weekends. I’ll be in bed nursing this chest infection 🤧</p><p><em>Written by </em><a href="https://josephdenne.com/"><em>Joseph Denne</em></a><em>. Joseph is the Founder &amp; CEO of Edge Network Technologies.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c511b2d351" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dadi/weekly-update-w-c-27th-january-2020-8c511b2d351">Weekly Update: W/C 27th January, 2020</a> was originally published in <a href="https://medium.com/dadi">Edge</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weekly Update: W/C 20th January, 2020]]></title>
            <link>https://medium.com/dadi/weekly-update-w-c-20th-january-2020-8a45ad0b2fa6?source=rss----a5531445a1f---4</link>
            <guid isPermaLink="false">https://medium.com/p/8a45ad0b2fa6</guid>
            <category><![CDATA[edge-computing]]></category>
            <category><![CDATA[edge]]></category>
            <category><![CDATA[network-edge]]></category>
            <dc:creator><![CDATA[EDGE Network]]></dc:creator>
            <pubDate>Sun, 02 Feb 2020 09:55:31 GMT</pubDate>
            <atom:updated>2020-02-02T09:55:31.335Z</atom:updated>
            <content:encoded><![CDATA[<p><em>As part of our ongoing commitment to transparency and development in the open, our founder writes weekly updates to the Edge community. This is the 42nd of these updates, originally posted to Telegram.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OVhQPy9mkpMWIQOnLd6gLw.jpeg" /></figure><p>Hi all 👋 We’ve been flat out all week. In a good way 🙂</p><p>The network team released the latest build of Gateway which comes with cache recovery, a feature that persists the cache to disk and re indexes on reload. This removes cold starts for CDN on Gateway restart, which massively improves performance in this scenario as well as our overall capacity overhead.</p><p>They also put the finishing touches to the new Console, including a few bug fixes and some minor changes to UX. There’s just one more round of UX revisions remaining before launch!</p><p>The Gateway update also added some extra stats to telemetry, making it easier for us to monitor the number of Hosts connected to each server.</p><p>Two more entries for CDN have been added to the roadmap: the first is to support PNG background colour setting and the second is an image data parameter which will list the most prominent colours.</p><p>A deployment of API version 6 is almost complete, with the initial migration taking place early next week, expected to be complete at the start of February.</p><p>CLI is due to be updated soon, with a number of extra features added to the ‘info’ command.</p><p>A bug fix for the diskcache resolves an issue where an update to the TTL value in a live deployment of CDN would cause Gateway to throw errors.</p><p>The team also started work on the GRPC connection between Stargate and Gateway which will provide a much faster route to delivering configuration data between the two services, eventually replacing the existing reliance on Consul Key/Value store, which remains stable but will eventually exhibit issues with the current rate of onboarding.</p><p>We are now at 572 nodes.</p><p>Here’s a graph showing network growth over the past year:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gCUhNG821ks0S8bD.jpeg" /></figure><p>Pretty strong growth overall. We know we can scale <em>way</em> above this, and are very excited for the coming year.</p><p>And that’s it for this week! Thank you for being a part of our community.</p><p><em>Written by </em><a href="https://josephdenne.com/"><em>Joseph Denne</em></a><em>. Joseph is the Founder &amp; CEO of Edge Network Technologies.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a45ad0b2fa6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dadi/weekly-update-w-c-20th-january-2020-8a45ad0b2fa6">Weekly Update: W/C 20th January, 2020</a> was originally published in <a href="https://medium.com/dadi">Edge</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weekly Update: W/C 13th January, 2020]]></title>
            <link>https://medium.com/dadi/weekly-update-w-c-13th-january-2020-c73b0ad4f0b8?source=rss----a5531445a1f---4</link>
            <guid isPermaLink="false">https://medium.com/p/c73b0ad4f0b8</guid>
            <category><![CDATA[edge-computing]]></category>
            <category><![CDATA[network-edge]]></category>
            <category><![CDATA[edge]]></category>
            <dc:creator><![CDATA[EDGE Network]]></dc:creator>
            <pubDate>Sun, 02 Feb 2020 09:54:18 GMT</pubDate>
            <atom:updated>2020-02-02T09:54:18.188Z</atom:updated>
            <content:encoded><![CDATA[<h4>As part of our ongoing commitment to transparency and development in the open, our founder writes weekly updates to the Edge community. This is the 41st of these updates, originally posted to Telegram.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4O4dORXrZmxbXmFAZES0AA.jpeg" /></figure><p>Hi everyone 👋 It’s been a busy week 🙂</p><p>Our new project director has hit the ground running, defining a new process framework to help us better manage engagements and deliveries.</p><p>We assisted with the implementation of CDN on a series of sites new to the platform that we hope to see live in the near future.</p><p>The network team deployed the new diskcache feature to Gateway, reducing the amount of memory used and increasing the number of concurrent deployments of CDN.</p><p>They also delivered some of the vital infrastructure changes ahead of the release of Console, including upgrading API to version 6.</p><p>Work on the new Console progressed well ahead of testing and production release towards the end of the month.</p><p>We also deployed the latest GIF support features for CDN to Mainnet, which now includes the ability resize this image format.</p><p>And finally we migrated our roadmaps for this year to Git, a move that we hope will bring increased transparency through the tracking of changes over time. We’ll be making it public early next week (just as soon as Arthur in back in the country).</p><p>And that’s it for this week. Thank you for being part of our journey.</p><p><em>Written by </em><a href="https://josephdenne.com/"><em>Joseph Denne</em></a><em>. Joseph is the Founder &amp; CEO of Edge Network Technologies.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c73b0ad4f0b8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dadi/weekly-update-w-c-13th-january-2020-c73b0ad4f0b8">Weekly Update: W/C 13th January, 2020</a> was originally published in <a href="https://medium.com/dadi">Edge</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weekly Update: W/C 06th January, 2020]]></title>
            <link>https://medium.com/dadi/weekly-update-w-c-06th-january-2020-5e060efff99f?source=rss----a5531445a1f---4</link>
            <guid isPermaLink="false">https://medium.com/p/5e060efff99f</guid>
            <category><![CDATA[network-edge]]></category>
            <category><![CDATA[edge-computing]]></category>
            <category><![CDATA[edge]]></category>
            <dc:creator><![CDATA[EDGE Network]]></dc:creator>
            <pubDate>Sun, 02 Feb 2020 09:51:28 GMT</pubDate>
            <atom:updated>2020-02-02T09:51:28.729Z</atom:updated>
            <content:encoded><![CDATA[<p><em>As part of our ongoing commitment to transparency and development in the open, our founder writes weekly updates to the Edge community. This is the 40th of these updates, originally posted to Telegram.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*83zJ__0Q73CNoE8kCYQkEg.jpeg" /></figure><p>Happy Friday and Happy New Year!</p><p>You can read our 2019 TL;DR here: <a href="https://edge.network/en/updates/network/2019-tldr/">https://edge.network/en/updates/network/2019-tldr/</a></p><p>This week the network team worked on deploying API 6.x and running the data layer in a container, as well as working on backup solutions.</p><p>They also successfully deployed the Prometheus and Grafana services to Mainnet, and added some nice graphs to boot 🙂</p><p>Edge Console moved in to design review, which remains on track for the end of January.</p><p>The finishing touches are being put together ahead of the release of disk cache for Gateway.</p><p>Telemetry has been introduced into Gateway and the process around it have been refactored.</p><p>And telemetry was introduced to Stargate to log DNS requests.</p><p>Finally Arthur posted an article on replacing devices in the network. You can read it here: <a href="https://edge.network/en/updates/network/replacing-devices/">https://edge.network/en/updates/network/replacing-devices/</a></p><p>And that’s it! Short and sweet. See you next week.</p><p><em>Written by </em><a href="https://josephdenne.com/"><em>Joseph Denne</em></a><em>. Joseph is the Founder &amp; CEO of Edge Network Technologies.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e060efff99f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dadi/weekly-update-w-c-06th-january-2020-5e060efff99f">Weekly Update: W/C 06th January, 2020</a> was originally published in <a href="https://medium.com/dadi">Edge</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Replacing devices]]></title>
            <link>https://medium.com/dadi/replacing-devices-569f78076628?source=rss----a5531445a1f---4</link>
            <guid isPermaLink="false">https://medium.com/p/569f78076628</guid>
            <category><![CDATA[edge-computing]]></category>
            <category><![CDATA[network-edge]]></category>
            <category><![CDATA[edge]]></category>
            <dc:creator><![CDATA[EDGE Network]]></dc:creator>
            <pubDate>Sun, 02 Feb 2020 09:50:33 GMT</pubDate>
            <atom:updated>2020-02-02T09:50:33.205Z</atom:updated>
            <content:encoded><![CDATA[<h4>The rate of device onboarding has been increasing at a healthy rate since we launched self onboarding in the summer of 2019. Whilst some of our contributors have used their own hardware, we’ve also seen an unexpected number of cloud hosted instances the network.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wtvfZgB1MPwsN2Y1lkYsDA.jpeg" /></figure><p>The rate of device onboarding has been increasing at a healthy rate since we launched self onboarding in the summer of 2019. Whilst some of our contributors have used their own hardware, we’ve also seen an unexpected number of cloud hosted instances the network.</p><p>Whilst cloud hosted machines are a great choice for those who aren’t necessarily able to offer dedicated home hardware, they have posed a number of reliability issues that aren’t typically seen with owned hardware. We’ve heard stories of faulty instances, unexpected bandwidth caps and hidden costs that have forced many of the community to have to create new instances and go through the entire onboarding process again.</p><h3>Automated Staking</h3><p>Manual stake verification provided a necessary bottleneck as we optimized Edge CLI, as well as insuring the network was capable of handling the increase in capacity. We found and resolved load issues with the ACL service, the Host update process and the Key/Value storage mechanism which will ultimately shape the next roadmap, to be released this quarter.</p><p>The next stage is to introduce automated stake verification and completely remove ourselves from the picture. This will be accomplished in a series of changes across each part of the process.</p><h3>Stake verification key</h3><p>The first change will be with Edge CLI, the tool you’ve been using to launch and configure a device. The current iteration takes you as far as registration on the network, but then directs the user to contact a community admin to receive an address in order to complete the staking process. The next release will display the address, the amount of $EDGE required, and a unique key to be used in the transaction, as well as instructions on how to apply the key.</p><h3>Watching Service</h3><p>We’ll be dropping the manual process of checking the wallet address for your stake, replacing it with a watching service which will periodically look for your stake by matching the unique key you were provided against incoming transfers. When it sees your stake, it automatically applies the <em>transfer hash</em> to our record which is linked directly to your registered device.</p><h3>Stake Storage</h3><p>The new process will create stake entries in the Edge database and link them to your device during onboarding. It’ll also allow you to create unassigned stakes which you’ll be able to apply instantly during the registration process.</p><h3>Stake transfer</h3><p>Transferring stake has become widely recognised as a process in heavy need of automation, and by separating stakes into entities in the Edge database we’ll be introducing the kind of flexibility contributors have asked for. When migrating to a new device you’ll be able to instantly transfer a stake away from your legacy hardware using Edge CLI.</p><h3>Listing Stakes and Devices</h3><p>Edge CLI will ship with a new <em>list</em> feature which will allow you view a complete list of stakes and devices, as well as seeing which stakes are attributed to which devices, making it easier to identify the right stake to transfer.</p><h3>A note on migration and UUIDs</h3><p>A lot of people have wondered whether it is possible to replicate an existing device in order to migrate it to another piece of hardware. This is a perfectly reasonable question which hopefully stake transfer will resolve.</p><p>UUIDs are supposed to be unique to the device. When a device is faulty or for any other reason is required to be terminated, the UUID and the device name should not be transferred. The device should instead be marked as terminated, a new device with a new UUID created and the stake transferred. This process ensures that an accurate history of contributing devices exists, including historic hardware specifications which would otherwise be overwritten.</p><h3>Release</h3><p>There’s a lot of work ahead of us to get automated stakes in place, but we’re confident that it can be delivered in Q1 2020. I’ll be updating you on the progress as it happens, and appreciate all of the wonderful feedback so far.</p><p><em>Written by Arthur Mingard. Arthur is the CTO at Edge Network Technologies.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=569f78076628" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dadi/replacing-devices-569f78076628">Replacing devices</a> was originally published in <a href="https://medium.com/dadi">Edge</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2019 TL;DR]]></title>
            <link>https://medium.com/dadi/2019-tl-dr-55a384bb8e0b?source=rss----a5531445a1f---4</link>
            <guid isPermaLink="false">https://medium.com/p/55a384bb8e0b</guid>
            <category><![CDATA[content-distribution]]></category>
            <category><![CDATA[cdn]]></category>
            <category><![CDATA[edge]]></category>
            <category><![CDATA[network-edge]]></category>
            <category><![CDATA[edge-computing]]></category>
            <dc:creator><![CDATA[EDGE Network]]></dc:creator>
            <pubDate>Sun, 02 Feb 2020 09:49:06 GMT</pubDate>
            <atom:updated>2020-02-02T09:49:06.633Z</atom:updated>
            <content:encoded><![CDATA[<h4>2019 was a significant year for $EDGE. From the launch of the Mainnet in January, to the high pace of development (8,198 commits 💪) and growth in network reach (527 nodes and counting!), we’ve been flat out #BUIDLing.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U6XskAE3JEYf5v7pRHYWSg.jpeg" /></figure><p>The Edge Network was launched and has grown to over 500 nodes; we’ve served over 10 billion requests in the mainnet; hosted 8 AMAs; written 40 weekly updates; delivered 5 releases of API; 7 releases of Edit; 11 releases of CDN; and 8 releases of DNS.</p><h3>Project updates</h3><p>There were hundreds of updates in 2019 — far too many to list in full, but you can <a href="https://edge.network/en/updates/">see them all here</a>. Here’s a rundown of some of our favorites:</p><h4>Launching the World’s First Edge Network</h4><p>‘Constellation’ hit on the 02nd of January — the move of the Edge mainnet to live.</p><p><a href="https://edge.network/en/updates/network/dadi-launches-the-world&#39;s-first-edge-network/">https://edge.network/en/updates/network/dadi-launches-the-world’s-first-edge-network/</a></p><h4>Announcing Our Rebrand</h4><p>We announced the rebrand to Edge in June, and released the branding in July. The rebrand represented the culmination of months of work, synthesising everything that we know about edge computing, together with the core principles of our network, in to a coherent and powerful brand.</p><p><a href="https://edge.network/en/updates/announcements/introducing-edge/">https://edge.network/en/updates/announcements/introducing-edge/</a></p><h4>Delivering the HURIDOCS Grant</h4><p>Our charitable foundation — The Edge Initiative — made its first grant, supporting groundbreaking new tech for human rights defenders.</p><p><a href="https://edge.network/en/updates/announcements/huridocs-grant-announcement/">https://edge.network/en/updates/announcements/huridocs-grant-announcement/</a></p><h4>Launching the Network Explorer</h4><p>The first public release of our network explorer went live, giving an overview of the nodes active in the network.</p><p><a href="https://edge.network/en/updates/network/explore-the-edge/">https://edge.network/en/updates/network/explore-the-edge/</a></p><h4>Making Earning Data Available</h4><p>Founding Nodes were bought online with live network traffic and started earning in April. Earning date became available on the dashboards of node owners.</p><p><a href="https://edge.network/en/updates/announcements/earning-data-now-available/">https://edge.network/en/updates/announcements/earning-data-now-available/</a></p><h4>Enabling Self-Onboarding for Network Contributors</h4><p>Onboarding for self-hosted nodes on the Edge network opened in August, with support for Linux based AMD64/ARM devices.</p><p><a href="https://edge.network/en/updates/network/edge-network-now-onboarding/">https://edge.network/en/updates/network/edge-network-now-onboarding/</a></p><h4>Winning Best Edge Computing Platform at the Future Digital Awards</h4><p>Edge won “Best Edge Computing Platform” in the IoT Innovation category at the Future Digital Awards 2019. The award was given following a thorough judging process undertaken by the analyst team at digital research consultancy Juniper Research.</p><p><a href="https://edge.network/en/updates/network/future-digital-awards-best-edge-computing-platform/">https://edge.network/en/updates/network/future-digital-awards-best-edge-computing-platform/</a></p><h4>Enabling Self-Serve for Content Distribution</h4><p>Self serve for Content Distribution in the network was opened up to our community in November, enabling the use of the first network service without the need to interface with the Edge team.</p><p><a href="https://edge.network/en/updates/announcements/content-distribution-self-serve/">https://edge.network/en/updates/announcements/content-distribution-self-serve/</a></p><h3>Knowledge</h3><p>There were a whole bunch of technology updates in 2019, many of which were written about by the team. Here’s our pick of the best:</p><h4>Edge Storage Deep Dive</h4><p>The decentralised web puts computational power and storage right at the edge, enabling hyper-localised caching and fault-tolerant object storage. The primary focus of the network’s latest development round was Edge Storage. As Edge storage moves on to Mainnet for live testing, Arthur Mingard takes a look at what’s happening under the hood.</p><p><a href="https://edge.network/en/knowledge/network/edge-storage-deep-dive/">https://edge.network/en/knowledge/network/edge-storage-deep-dive/</a></p><h4>Finite State Machine</h4><p>The performance of network applications can be measured not only by the speed at which they resolve requests, but also by their ability to recover from faults. We have engineered performance in relation to faults on the basis of a fail fast philosophy. In this article Arthur Mingard digs in to the detail of how this works in practice.</p><p><a href="https://edge.network/en/knowledge/network/finite-state-machine/">https://edge.network/en/knowledge/network/finite-state-machine/</a></p><h4>An Introduction to Telemetry</h4><p>Telemetry is a means by which data is collected from remote or inaccessible devices, or to be more accurate, a means by which it is transmitted by those devices to receivers. We have a lot of devices in the Edge network which operate in a similar fashion; which sit in all manner of inaccessible locations and operate on an egress-only basis. This article will introduce you to how we collect measurements from these devices.</p><p><a href="https://edge.network/en/knowledge/network/an-introduction-to-telemetry/">https://edge.network/en/knowledge/network/an-introduction-to-telemetry/</a></p><h4>Scaling the Edge</h4><p>Arthur Mingard discusses the migration from a single global VPC approach to network architecture to one of interconnecting VPCs.</p><p><a href="https://edge.network/en/knowledge/network/scaling-the-edge/">https://edge.network/en/knowledge/network/scaling-the-edge/</a></p><h4>Go Content Distribution</h4><p>Content Distribution service has been rebuilt in Go from the ground up as a network specific application, increasing performance and massively reducing its footprint.</p><p><a href="https://edge.network/en/updates/network/go-content-distribution/">https://edge.network/en/updates/network/go-content-distribution/</a></p><h4>Tracking devices on the network</h4><p>Adam K Dean breaks down the approach to device tracking in the Edge Network.</p><p><a href="https://edge.network/en/updates/network/tracking-devices-on-the-network/">https://edge.network/en/updates/network/tracking-devices-on-the-network/</a></p><h3>What’s in store for 2020</h3><ul><li>The launch of the Edge Console</li><li>The enabling of payments for services in the network</li><li>The launch of Edge Storage</li><li>New partnership announcements</li><li>+lots, lots more</li></ul><p>(Look out for a full roadmap update early in the New Year!)</p><h3>Finally, a thank you</h3><p>Edge is the world’s first edge network, and is at the forefront of a step change in our industry. 2019 was a highly significant year, from the launch of the mainnet to self onboarding and network growth. And there’ll be no let up in our pace in 2020.</p><p>The ongoing support of the community means a huge amount to the entire team. Thank you for being part of our journey.</p><p>Happy New Year.</p><p><em>Written by </em><a href="https://josephdenne.com/"><em>Joseph Denne</em></a><em>. Joseph is the Founder &amp; CEO of Edge Network Technologies.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55a384bb8e0b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dadi/2019-tl-dr-55a384bb8e0b">2019 TL;DR</a> was originally published in <a href="https://medium.com/dadi">Edge</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[KuCoin Upgrade Notice]]></title>
            <link>https://medium.com/dadi/kucoin-upgrade-notice-62d7c13a075c?source=rss----a5531445a1f---4</link>
            <guid isPermaLink="false">https://medium.com/p/62d7c13a075c</guid>
            <category><![CDATA[edge]]></category>
            <category><![CDATA[edge-computing]]></category>
            <category><![CDATA[network-edge]]></category>
            <dc:creator><![CDATA[EDGE Network]]></dc:creator>
            <pubDate>Sun, 02 Feb 2020 09:46:35 GMT</pubDate>
            <atom:updated>2020-02-02T09:46:35.486Z</atom:updated>
            <content:encoded><![CDATA[<h4>In order to update the symbol parameter value to EDGE in their APIs, KuCoin will suspend the trading services of $EDGE for a few hours starting at 15:00 on December 30, 2019 (UTC+8).</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fjj9N_za6kg7pvhlhxYbyQ.jpeg" /></figure><p>The upgrade process is expected to last approximately two hours. EDGE assets will be temporarily invisible during this period. Rest assured that your assets will be absolutely secure.</p><p>We will carry out the upgrade process in the following steps:</p><ul><li>The deposit and withdrawal services of $EDGE have been suspended</li><li>Trading will be halted in all $EDGE trading pairs at 15:00 on December 30, 2019 (UTC+8). For better management of your funds, we recommend that you cancel your pending orders of $EDGE.</li></ul><p>A further announcement relating to the opening of trading, deposit and withdrawal services will be made when the upgrade process completes. At that time, the symbol parameter value in the Open API will be updated to EDGE.</p><p>Thanks for your understanding and support!</p><p><em>Written by Chris Mair. Chris is aFounder Partner at Edge Network Technologies.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=62d7c13a075c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dadi/kucoin-upgrade-notice-62d7c13a075c">KuCoin Upgrade Notice</a> was originally published in <a href="https://medium.com/dadi">Edge</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weekly Update: W/C 16th December, 2019]]></title>
            <link>https://medium.com/dadi/weekly-update-w-c-16th-december-2019-1e8b8eba69cd?source=rss----a5531445a1f---4</link>
            <guid isPermaLink="false">https://medium.com/p/1e8b8eba69cd</guid>
            <category><![CDATA[edge]]></category>
            <category><![CDATA[edge-computing]]></category>
            <category><![CDATA[network-edge]]></category>
            <dc:creator><![CDATA[EDGE Network]]></dc:creator>
            <pubDate>Sun, 02 Feb 2020 09:45:20 GMT</pubDate>
            <atom:updated>2020-02-02T09:45:20.427Z</atom:updated>
            <content:encoded><![CDATA[<p><em>As part of our ongoing commitment to transparency and development in the open, our founder writes weekly updates to the Edge community. This is the 39th of these updates, originally posted to Telegram.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nhqTxklLPEN718fb1l9BuA.jpeg" /></figure><p>Hi Everyone 👋 🎅 🌲</p><p>We’ll be closed for Christmas from 1pm on December 24th, and then open again the 02nd of January. Monitoring and uptime support for the network will be operational throughout.</p><p>We set up some new sites with Content Distribution this week.</p><p>And we pitched edit to a few potential customers, who we’ll be meeting again in the New Year.</p><p>We have a new member of the team with us. Tim Ludlow joins us as a Project Director. He was previously Production Director @ Google Labs.</p><p>We picked up our award from Juniper for “Best Edge Computing Platform, 2019”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/622/0*jOqsf5_b0rxBJ__i.jpeg" /></figure><p>The network team started integrating the new diskcache package into Gateway.</p><p>Work on a refactor of the http(s) handlers also began, separating them into more manageable middleware.</p><p>The team have also been writing tests for Gateway, with a hope to achieve 75% coverage in time for Christmas.</p><p>Work kicked off on the next release of edge-cli which will use tokens rather than ACL credentials.</p><p>The team have also been working on a new deployment processes for some of the network management systems including the registry, build services and other key supporting services.</p><p>And work has continued on the new Console ahead of its release in the New Year.</p><p>And that’s it!</p><p><em>Written by </em><a href="https://josephdenne.com/"><em>Joseph Denne</em></a><em>. Joseph is the Founder &amp; CEO of Edge Network Technologies.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e8b8eba69cd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dadi/weekly-update-w-c-16th-december-2019-1e8b8eba69cd">Weekly Update: W/C 16th December, 2019</a> was originally published in <a href="https://medium.com/dadi">Edge</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>