Weekly Update: W/C 14th December, 2020

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 91st of these updates, originally posted to Telegram.

Lead article image

It’s Friday and it’s nearly Christmas. 2020 has been a bit of time vortex, huh?

Our roadmaps have been updated for 2021, providing a good view of our areas of development focus for the year.

You can see them here: https://github.com/edge/roadmap

The earnings issue reported by some of the community has been resolved. You should now see them accruing in your Console account.

A memory leak issue in Gateway was identified and fixed, awaiting deployment early next week. We’ve also started work on Certman, the certificate management service which will ease the pain we’ve recently been experiencing with certificate challenges, the process used to verify authorisation to produce a certificate.

A fix for a bug with earning calculations related to an overstating of jobs satisfied was released to both Testnet and Mainnet.

Check out Minima. It’s a mobile first blockchain that runs entirely in cache with instant transactions and support for smart contracts. It’s been in development for several years by a team that we know well here in London. Their mainnet is slated for July next year.


Their new site is running on Edit, API and CDN. You can see it here: https://minima.global

You can see the Edge Network working by checking the headers of an image on site. For example:



TNC’s testnet is now up and running with support for DApps and token issuance. We’ve tested it end to end and can confirm that’s working well. It has a web interface and a full-featured API.

There’s a bunch to do on scaling their network, but things are moving forward pretty quickly now.

Documentation for Edge CDN is now live on site. You can see it here:


This includes a good breakdown of the caching types that exist in the network, something that I don’t think we’ve spoken about before.

The network cache consists of two types of caching: Lightening Cache, which holds assets in-memory for 60 seconds; and a disk cache which persists assets in line with the configured cache TTL.

Lightening Cache is designed to respond as fast as possible for frequently requested assets, whilst disk cache makes it possible to persist files for far longer without degrading performance or consuming memory on the device.

You can determine the cache response by looking at the X-Cache-Type HTTP header on image requests from CDN, which will be set to mem if the asset is cached in-memory, and disk otherwise.

Upon expiration cached files are removed from the network cache and are re-cached the next time they are accessed, unless they are pre-warmed.

Cache pre-warming applies to assets that are accessed above a customer-specified threshold. It automatically re-caches them to the network in order to maintain a quick response when the asset expires. In addition to pre-warming the asset, the cache can be configured to persist an expired asset during the process of pre-warming, ensuring a reliable response for assets with a longer load time.

You can determine whether the cache response is pre-warmed by looking at the X-cache-origin HTTP header, which will be set to pre-warm if pre-warmed, and request if not pre-warmed.

The latest subscriptions deployment of Edit I mentioned in earlier update was deployed for BOL Foods.


It’s running on Edit, API, DNS and CDN. You can see it here:


This is the 89th of my weekly updates and the last one for 2020. I enjoy writing the updates: aside from being a good way to chat to you all, it acts as a kind of diary for me. It amazing how much you do and forget. I’ll be continuing them through 2021.

2020 has been a challenging year for most of us. We took a big hit on the back of covid-19, but have rolled with the punches and continued to push forward.

The crypto space is looking bright going in to 2021, and Edge remains one of the few token based utility projects with a direct and demonstrable real world application.

The delays on the back of TNC have been frustrating, but this will be moved to resolution sooner rather than later. And the Edge token will be being relaunched to re-enable staking and growth in the network.

We’ll provide details for this in the New year.

Until then, enjoy the Christmas holiday 🌲🎅🎁

Related articles

More updates articles
Mail icon

Like what you are reading? Want to earn tokens by becoming an Edge Node? Save money on your hosting services? Build amazing digital products on top of Edge services? Join our mailing list.

To hear about our news, events, products and services, subscribe now. You can also indicate which services you are interested in, which we use for research and to inform the content that we send.

* You can unsubscribe at any time by emailing us at data@edge.network or by clicking on the unsubscribe link which can be found in our emails to you. Read our Privacy Policy.
Winner Best Edge Computing Platform Technology & Innovation Awards
Presented by Juniper Research