Edge Latest articles from the team en 2021 Edge Network Technologies Ltd. All rights reserved. Sat, 17 Apr 2021 20:06:40 +0000 2021-04-17T20:06:40+00:00 en 2021 Edge Network Technologies Ltd. All rights reserved. Edge https://edge.network/assets/img/dadi-logo-colour.png https://edge.network The Cloud Is Not Enough https://edge.network/knowledge/network/the-cloud-is-not-enough Remember the dial-up days? For those of you blessed only to have experienced ‘modern’ internet connectivity, these were the dark ages of a single machine for each lucky household that would whirr and whine its way onto the ‘information superhighway’ – with time for coffee between page loads.

Offices may have had a lonely, shared computer sat in the corner; its only friend a tired fax machine, spewing paper across the desk in a desperate attempt to stay relevant as the new digital age beckoned.

But faxes would soldier on at least until data wires were wide enough to feed every machine in the room. Then wifi untangled us from cables. The world wide web found its way to mobile phones. Homes, offices, streets and cars filled with connected devices each hungry for kilobytes to turn into pixels for human consumption.

And now? 5G is about to usher in another connectivity revolution. But even with this paradigm expansion, we’re barely even finishing the prologue – let alone the first chapter – of the story of the internet.

There are already more connected devices on the planet than people. By 2023, 70% of cars will likely be networked. Estimates suggest the ‘internet of things’ will push the world past 40 billion machines harvesting data from servers laced together to form the infrastructure we call ‘the cloud’.

Those server farms right now are like the lonely fax machines of old. There’s life in them yet, but the change they face is inevitable. The world needs a solution for its data storage that grows exponentially with the new devices flooding the network designed to support it – and that means Edge technology.

Edge Network harnesses spare capacity in phones, laptops, set top boxes – ultimately any connected device with storage to spare – rather than relying on factories filled with old boxes, sweating under the fans of air conditioning to keep them cool. It means the internet is all around us and that almost every one of the new devices that connects brings with it the opportunity to expand the capacity of the cloud.

Only by placing the future of our digital infrastructure in the hands of Edge technology do we secure its potential. By bringing your business to Edge, you’ll benefit from faster and more efficient, scalable technology – and by offering up your spare capacity you can turn existing hardware into revenue.

Join us and be part of the future of the cloud.

Thu, 15 Apr 2021 17:00:00 +0000 60786d592e0f0a0019de43b4 Arthur Mingard 2021-04-15T17:00:00+00:00
Weekly Update: W/C 05th April, 2021 https://edge.network/updates/announcements/weekly-update-wc-05th-april-2021 Hi everyone 👋

Another short week this week after bank holiday weekend, but it was still jammed packed with development.

$XE moved ahead significantly (detail below). We are broadly on track for the end of April. Security testing starts soon, the output of which may affect timing in that anything highlighted that needs to be developed further will add time. This could add a week or two to the schedule. We’ll obviously keep the community updated as we progress.

We expect to be discussing tokenomics next week. And the Community Wiki will follow shortly thereafter.

Before I get into the week’s updates, a reminder that you will need to go through the swap process in Edge Console in order to be able to claim $XE. The swap process closes towards the end of May.

On to the weeks updates:

The refactor of the upgrade process on Gateway and Host extended to Stargate, and after some issues with the way that Edge atomicstore handled callbacks, a new version of each of the core apps have been pushed to testnet.

These will be deployed to mainnet towards the middle of next week if testing is successful.

Essential maintenance has taken place on network registries, specifically looking at reducing footprint and removing the reliance on a single third party. This is critical path stuff, adding further security and redundancy to the core of the platform.

We now have a fully synchronised mempool – with persistent storage – for pending transactions in the network chain. This includes database cloning for redundancy.

Transactions and the ledger are now fully integrated into the mining process.

API endpoints for $XE covering transactions were also completed. These are being used in the explorer and will eventually be made public.

The $XE Mainnet now has multiple nodes live across Europe. The initial deployment of the nodes also took place, moving us towards mainnet security testing.

Network DNS integration was also completed this week, along with core service proxies, status services, Grafana & Prometheus integrations and CI/CD jobs for builds & deployments.

We kicked off the engagement with the broadband provider mentioned in a previous update. There’s a lot of work happening here through Edit, with the expectation that core components of what’s being delivered will be running in the network in due course. As ever, as soon as we can share details on this, we will.

We picked up the domain ed.ge, which we’re planning on using for URL shortening in the network.

Chris wrote another article, The Network Under Your Nose:


And we sent the first Edge Digest, a fortnightly wrap up of all things Edge, delivered straight to your inbox. You can see the issue here:


If you’re not signed up, what are you waiting for! Sign up now at: https://edge.press

As a reminder, we’re now posting these updates to Discord first. Discord offers a much more structured environment for supporting community growth, and things like governance will be linked directly into the platform. So if you’ve not joined the server yet, now is the time!


And that’s it for this week.

Enjoy your weekends.

Fri, 09 Apr 2021 17:30:00 +0000 6072e8b12e0f0a0019de43b3 Joseph Denne 2021-04-09T17:30:00+00:00
The Network Under Your Nose https://edge.network/knowledge/network/the-network-under-your-nose Think of an average American household. Now imagine the energy that family uses across any given year by turning on lights, cooking food and watching TV. Multiply that by 17 million and you get the equivalent annual energy usage of the cloud computing industry during 2018.

It’s growing too. The exponential rise in connected digital services is upon us, with 5G around the corner and the juggernaut arrival of the much-hyped ‘internet of things’. Yet cloud computing can respond only by building bigger and bigger server farms.

To be fair, these larger data centres were more efficient than smaller traditional computer centers in their day. But we now live in a more waste-conscious world – and a world where technology has moved on. Why should our digital services be hosted on energy-hungry, dedicated machines in stadium-sized factories?

Edge reuses the hardware all around us to build the future cloud. A set top TV box, for example, is plugged in 24/7 but only in use for a few hours each day. On its own, it doesn’t provide much power, but when you join together the millions of devices installed in homes all over the globe it becomes an incredibly powerful resource.

We canvassed 2,000 members of the Edge community and the average disk space usage across laptop, desktop and mobile devices was 52.56% – leaving a massive amount of storage going spare.

Or, indeed, wasted.

The biggest beneficiary of this optimisation in hardware use? The planet. Not only do the factories and server farms gradually fade away, but we also make use of devices already manufactured – saving energy by building one product instead of many. More than that, reusing those devices already in our homes, pockets and offices means the internet is stored much closer to where it is consumed – and less energy is used to send and retrieve the data we need for everything from online shopping to streaming movies.

If you’d like a positive story to tell about the digital carbon footprint of your business, get in touch with a member of the Edge team and ask about onboarding. You’ll be in very good company.

Thu, 08 Apr 2021 17:30:00 +0000 606f4e042e0f0a0019de4380 Chris Mair 2021-04-08T17:30:00+00:00
Weekly Update: W/C 29th March, 2021 https://edge.network/updates/announcements/weekly-update-wc-29th-march-2021 Hi everyone 👋

It’s been a short week here, with today and Monday off for Easter.

TNC unlocked, and despite some teething problems are now processing transactions quickly.

The application deployment and configuration management package used by Gateway and Host have received a much needed refactor to improve reliability and reduce the potential for misconfigured applications responding to requests that they are unable to successfully complete.

Further protection was added to Gateway to avoid caching failed responses, and to force bad actors out of the priority queue.

The final components of the refactor are due to be completed next week, with the expectation that they will be deployed to mainnet before the end of the week.

There has also been a lot of work on the peer-to-peer protocol within the network chain to strengthen it for transactions, including refinements to the synchronisation mechanism and enhancements to its general robustness.

We test the technology by running with a blocktime as low as 500 ms, and pushing hundreds of thousands of transactions through the system. When launched we expect a blocktime of around a minute.

Work on the design of the web wallet – which is otherwise functionally complete – progressed. As did work on the chain explorer.

There has been considerable progress in the way that transactions are handled in the network. At the heart of this the platform is a cryptographic ledger, a deterministic data store that tracks wallet balances, is constructed from the transactions in every block, and has the ledger proof stored in every block.

Guiding Principles for network governance have been defined, based on work produced by the UNDP (the UN’s development agency).

Governance in the Edge Network is designed to be:

  1. Participatory. Community participation is key to the success of the network. Governance must be informed and organised.
  2. Consensus Oriented. There will be multiple points of view for each aspect of the network. The governance mechanism is designed to facilitate healthy and open debate.
  3. Accountable. Proposals that are raised through the governance mechanism must be followed up on by the core team.
  4. Transparent. Information must be freely available and directly accessible to those who will be affected by the proposals raised through governance.
  5. Responsive. Proposals should be responded to within a reasonable timeframe.
  6. Effective and Efficient. The governance mechanism should produce results that balance the needs of stakeholders while making the best use of the resources at hand.
  7. Equitable and Inclusive. There should be no barriers to community involvement in governance.

In addition guidelines for the core team have been produced, which will be published closer to the point of project governance moving to live. This will happen after the initial distribution of $XE.

With regard to the distribution of $XE, it will be available to claim to everyone that has been through the swap process to TNC in Edge Console.

In other updates, the refresh of the Ecohustler site moved to live. You can see it here: https://ecohustler.com

An update with a full eCommerce shop is set to go live within the next two weeks.

The charitable event that Cookalong is holding for Muscular Dystrophy UK can be found here: https://mduk.cookalong.tv

Chris and I took part in a series of conversations destined for podcasts. More on that in the coming week or two.

Paul wrote about the importance of decentralisation, community and citizen ownership: https://edge.network/en/knowledge/network/a-fairer-internet

And Chris wrote about the high level concept of the Edge Network itself, which you can see here: https://edge.network/en/knowledge/network/the-local-global-network

Finally the finishing touches were put on the first of what will be fortnightly email updates. We expect to be sending this out soon.

If you’re not on the mailing list, sign up now: https://edge.network/en/#join

And that’s it for this week.

Enjoy the Easter weekend.

Fri, 02 Apr 2021 17:30:00 +0000 606c26932e0f0a0019de437d Joseph Denne 2021-04-02T17:30:00+00:00
The Local, Global Network https://edge.network/knowledge/network/the-local-global-network Think for a second about where these words come from. Stored in a file somewhere on a server and piped to your device as quickly and efficiently as possible.

In a traditional cloud environment, this will be the data centre closest to you (probably). And that will likely be a large farm of servers in a purpose-built warehouse as close as viably possible to population density.

But there aren’t thousands of these. For most hosting and infrastructure companies there aren’t even hundreds. Yet there are millions of people demanding their data – and that means billions of miles travelled to send information between servers and browsers on devices the world over.

What if we reduced these distances? What if we could have millions of smaller ‘data centres’ all around us rather than centralised large facilities? The answer would be a faster, cheaper and greener way to distribute and access digital services.

This is how Edge works. It doesn’t require farms of servers. It makes use of millions of devices already in our homes and offices to disseminate data storage among all of us – lacing together laptops, desktop PCs, games consoles or any device with spare capacity to make the global internet more local for all of us.

Web pages load faster. Files download more quickly. Videos are watched more seamlessly. Less energy is consumed in both storage and consumption of services too, meaning Edge makes your carbon footprint smaller.

It’s why we call Edge ‘future cloud’. Anyone can be part of this by contributing to the network – and if your business runs digital services, talk to us about how providing capacity to Edge Network can be offset against your infrastructure bills.

Thu, 01 Apr 2021 15:30:00 +0000 6065ed342e0f0a0019de4369 Chris Mair 2021-04-01T15:30:00+00:00
A Fairer Internet https://edge.network/knowledge/network/a-fairer-internet Imagine this pandemic but without the internet. With no web of connected devices feeding an infrastructure that brings us food and shopping; that links us to distant friends and family; that allows large swathes of society to work with limited interruption.

Feels vital, doesn’t it? A dependency brought into sharp focus not a moment too soon – advancing technology will soon plug millions more machines into the cloud, drawing and sending data for everything from automated, AI-driven domestic deliveries to consultations with your doctor.

Connectivity has crossed the threshold from luxury to necessity. It’s now analogous to water supply or power for heat and light, which makes it all the more troubling that the infrastructure on which this new matrix for society is built is owned by so few.

Amazon Web Services currently hosts more than 9 million websites. Estimates have its market share at over 30% for cloud services. Google Cloud is around 13%, Microsoft Azure 7%. Surveys suggest more than 60% of tech professionals are currently running a cloud app with AWS.

Edge believes there is a different way. Our network is a not for profit organisation. Instead of investing in factories filled with servers effectively hoarding services key to our new digital society, we provide a lightweight infrastructure that allows us all to build the cloud around us – we each own a stake in ‘our’ network and each earn revenue from it.

Anyone with a laptop, mobile phone, games console or desktop PC (for example) can offer spare capacity to Edge, providing secure and performant cloud services to all. Instead of lining pockets of the world’s richest individuals, Edge rewards everyone with revenue from the services we share.

Join us by registering today.

Thu, 25 Mar 2021 17:30:00 +0000 605cb5332e0f0a0019de4360 Paul Regan 2021-03-25T17:30:00+00:00
Weekly Update: W/C 22nd March, 2021 https://edge.network/updates/announcements/weekly-update-wc-22nd-march-2021 Hi everyone 👋

It’s been another jam packed week here, as we push towards the release of $XE.

$EDGE itself is ready (contracts + the bridge). Distribution will be in $XE, which will be available to claim and which can be bridged out to $EDGE at the end of April/early May (TBC depending on development pace on remaining items).

The network team changed the way Gateway handles device scoring to ignore responses that include error codes. Typically a response from CDN with an error return faster because there is no asset manipulation, therefore scoring based on a quick but failing response gives far too much priority to a device that has configuration issues.

The way applications are launched in the network is getting a large refactor, including the introduction of the Edge Finite State Machine package in order to avoid conflicting states and duplicate containers. This is expected to be delivered at the very start of April.

The test.network build of the $XE chain has been updated with a series of P2P Synchronisation fixes & enhancements.

It’s also been under continuous load testing, and has shown itself to be stable. We’ve pushed it hard, with 5 second block times and heavy usage. Adam will share some more data on this front next week all being well.

A metrics dashboard for the chain has been deployed giving us a bunch of insight and trend data.

$XE wallet generation and restoration is now complete in the client-side JS wallet.

A wallet utilities module and support API have also been completed. This will be made publicly available, allowing third parties to interact with it directly.

This includes crypto functions such as wallet generation, public key to checksum address, checksum address verification, private key to private key phrase generator, private key phrase to private key recovery, private key to public key, private key to address and wordlist generation.

As we move towards the issuance of $XE we’ve taken the opportunity to make some small changes to the Edge logo.

This from Ravi –

“After living and working with the word mark and the ‘e’ icon over the past 18 months, we felt it wasn’t quite as well balanced as it should be and needed a little refinement.

“The original logo was intended to convey balance, uniformity and simplicity. The 4 circles being the starting point of the letter forms. There was a slight angle applied to the endings of the cross section on the ‘e’ and ’g’. This little detail has now been simplified and removed in favour of a straight edge.

“Although this is a small detail, the straight edge adheres to the ideas of simplicity and clarity and makes for a more balanced, less fussy shape.”

Here’s the update:


And here’s the icon:


The brand pages on the site will be updated next week.

We have also been putting together a community wiki for the project. This is near completion and does a great job communicating the scale of the project and how much has been achieved so far.


We’ll be making this public in mid April, along with a whole lot of additional information relating to $XE, $EDGE and the network bridge.

The definitions around project governance have been moved forward, with guiding principles defined along with guidelines for the use of governance for the core team.

This will be laid out in detail in the wiki.

Cookalong are hosting an evening with William Sitwell – a charity event in support of Muscular Dystrophy UK. I’ll share the link as soon as it’s available.

The updates to the Ecohustler site mentioned in earlier updates is set to go live on Monday, with eCom functionality following the week after.

And finally, we have had a couple of business meetings this week, including with a leading motorsport. Chris is leading on partnerships and special projects, and has been doing a great job getting the network and its tech in front of some really exciting organisations.

And that’s it for this week.

Enjoy your weekends.

Mon, 22 Mar 2021 18:30:00 +0000 606605c72e0f0a0019de436c Joseph Denne 2021-03-22T18:30:00+00:00
Weekly Update: W/C 15th March, 2021 https://edge.network/updates/announcements/weekly-update-wc-15th-march-2021 Hi everyone 👋

Happy Friday! I hope you’ve had a good week. There’s a lot happening here, so we’re a little later than usual this evening with this weeks update.

Evolving the blockchain within the Edge Network to work for transactions has involved a lot of updates, such as the addition of persistent storage for transaction entries; changes to the blocktime and synchronisation; and updates to the security model.

This is the blocktime over a 30 minute period:


We’re likely to settle on a time of around a minute, which provides a good balance between performance and data resolution.

To get into more detail I have Adam K Dean with me again this week. He’ll provide a deeper breakdown of the work being done on the layer 2 chain:

Adam K Dean:

Hi everyone!

This week the team introduced a whole raft of improvements to the XE peer-to-peer protocol, adding in fault tolerance for forks and simultaneously mined blocks, and improving the latency considerably, especially important for allowing fast chain synchronisation for new nodes (something that we think will be important in the near future).

The technical implementation of the $XE wallet is now complete. Wallets are generated using the Edge Wallet (which runs entirely in the browser). You generate a private key and there is a corresponding public key, from which your $XE wallet address is derived. When you send $XE from your wallet to another wallet, you sign the transaction with your private key. That signature can then be used with the transaction data to produce an $XE wallet address, which is then compared with the claimed sender to ensure that the transaction was really sent by you. This is now functionally complete.


We’ve made the decision to enforce checksums on XE addresses (based on EIP-55), reducing the chance of mistyping an address. The wallet interface will only allow you to send coins to a valid address, but also the blockchain itself will enforce this, as all transactions are verified before being processed.

When generating your wallet, in addition to receiving your private key, you’ll also receive a private key phrase. Private key phrases consist of 22 five-letter words, and are used to recover your private key. We use a custom word list consisting of 4,096 five letter English words. It is worth noting that private key phrases are not the same as BIP-39 mnemonics, and each private key phrase maps only to a single wallet address.

Here’s a full address example:

Private key:        e35c5b8f514bca3b30b4d90c8994f340394bb76e7ba6699b092d4db04742707a
Private key phrase: tones siker murva bused smaze reply rimes naive mirex gamey fawny
                    noisy rosed trope primy pashm bland stoup reads lamby knish piths
XE address:         xe\\\\\\\\\\\\\\\_48aaDa674Abc7C34f9c979720575E5CBd1A98FCf

Design for the wallet itself moved forward and we’ll start implementing the frontend next week.

We’ll be sharing some screens soon.

In addition to the above, we’ve also rolled out a new monitoring layer among the various infrastructure parts, improving our server monitoring capabilities. But in addition to this, it also hooks into the blockchain nodes, allowing us to record key metrics over time and ensure that the $XE blockchain network continues to run smoothly without having to delve into the logs (which are obviously huge).

To aid stability we’ve put a deployment process in place which enables rolling deployments, meaning that we have a seamless update process that doesn’t risk downtime.

And finally we’ve been pushing the $XE blockchain network significantly in testing (on test.network), which includes measures such as reducing the blocktime to ~5 seconds (as you saw above), simulating network failures, and spinning up numerous new nodes resulting in heavy P2P protocol traffic, and have seen synchronisation of these new nodes working extremely effectively with no degradation of the blockchain network performance.

Joseph Denne:

Thank you Adam!

In other news, like with Host nodes, Stargates and Gateways will be opened up for staking with the launch of the new token. We expect there to be a limited set of additional Stargates added to the network this year, which will be allocated on a first come first serve basis. And Gateways in the network will be made available for staking for the first time, also on a first come first serve basis.

Those of you currently staking will have your stakes ported over to the new setup. There should be nothing for you to do to ensure that your devices are running and generating yield.

The $EDGE<>$XE bridge now monitors gas costs and allows individuals to choose how much they want to pay. This works to the advantage of holders and is designed to keep costs to a minimum.

It updates rates every minute:


Chris and I expect to be sharing the finer points of the tokenonmics of the reissue with you all over the next fortnight.

We’ve also changed the way CDN reports an error in configurations which will improve the way Gateway cache’s results. Strict config errors will no longer be cached for 60 seconds.

The new version of our logging package now no longer triggers an application failure when a Fatal message is reported. Whilst this was designed as an improvement, it had a short term effect of not restarting Stargate when a connection to Consul was severed. We have now patched and deployed a fix for this.

Gateway queue has been working reliably on Mainnet for 14 days now. Some scheduled minor bug fixes will be deployed next week, along with a few upgrades that should improve performance even further.

The Edit team pitched to a major infrastructure provider here in the UK. This one has amazing alignment with the network in terms of service use and network scaling.

A major update to the Ecohustler site - ecohustler.com - moved into final testing. This will enable eCommerce and carbon-offset services via their site. We’ve been given the go ahead to include a “Hosted on the Edge” banner on the site, which will be a good showcase for the network.

And finally, our social activation campaign has kicked off. You will start to see the output from this next week. This includes a reactivation of our newsletter, which will be sent once a fortnight. If you’re not signed up, sign up now: https://edge.network

And that’s it for this week.

Enjoy your weekends.

Fri, 19 Mar 2021 18:30:00 +0000 6059f7022e0f0a0019de435d Joseph Denne 2021-03-19T18:30:00+00:00
Weekly Update: W/C 08th March, 2021 https://edge.network/updates/announcements/weekly-update-wc-08th-march-2021 Hi everyone 👋

We’ve been hard at work integrating the method of value exchange into the internal chain in the network. This is going very well. Nodes are up and running with the P2P protocol and we’re currently working on optimisations for the synchronisation protocol.

The internal network token is called $XE. Network transactions are fee free and instant.

We expect to be distributing $XE at the end of April this year, which is a little later than originally planned, factoring the changes to enable the use of the internal ledger as a layer 2 solution.

We’ll be sharing the tokenonmics and the approach for the reissue ahead of time.

The Eth contract for $EDGE is ready. As is the staking contract and process. Work on the bridge between $XE and $EDGE is ongoing. This diagram illustrates how the bridge and the chain within the network works:


The diagram also shows how the chain interacts with various other parts of the Edge ecosystem.

The Bridge process handles the conversion of $EDGE to $XE and vice versa. The web wallet allows the creation & management of wallets and associated funds, including allowing internal transactions among $XE wallets, and helping facilitate the depositing of $XE via the Ethereum bridge contract, as well as withdrawing $XE via the Bridge service.

Wallets are client-side. You will generate, own and be responsible for your own private keys.

The format for $XE addresses is as follows: xe_[HASH]

For example: xe_08b8083fb37CcBed785b4278B85Cf74aa7719A1E4

Other areas covered in the diagram include the interaction of Staking & Governance functions with the Staking & Governance services, and the interaction of Stargates with the Earnings services which in turn generates payout transactions direct to your associated $XE wallets automatically.

Of course there is also the $XE explorer, providing full transparency of all transactions and Host contribution data.

You can see chain synchronisation working here:


The chain runs in Stargates and each Stargate has an API for interacting with the chain. The spec for the API will be published as part of a second phase, and third parties will be able to provide integrations in time.

A member of the community raised the question of the potential for bridging to other chains. This is possible, and a definite area of interest for future research and discussion.

With regard to staking, we are moving to a yield basis for rewards, with yield calculated based on performance – jobs completed – within a block window in competition with an individual node’s direct peers (Gateways>Hosts).

We are expecting a yield average of 10% for Hosts, 15% for Gateways and 20% for Stargates. The distribution model builds on the internal network market concept, rewarding where there is capacity requirement. The approach means that yield will be much higher in some cases and much lower in others.

In other news, we are moving the centre of gravity for our communications away from Telegram towards Discord. Why? Because it allows us to provide a more focused community experience, which we see as essential with the advent of project governance.

The good news you’re already reading this on Discord! Congratulations on being cool.

Jim has been back working with us again over the past year, and will continue to do so, advising on the evolution of the network chain and providing support for smart contract development.

A new white paper will be published soon. This provides details of the platform as it exists today, and is designed in support of community growth.

The engagement campaign I mentioned in an earlier update is ready and will be launching this month, ahead of the release of $EDGE. You can expect to see regular articles, social promotions, newsletters and more as we ramp up the activity. We’ll be pushing hard for community and network growth. Anything that you can do in support of these efforts would be greatly appreciated, including putting forward ideas through the governance function once it is up and running.

On network updates, there have been several major changes pushed to mainnet this week. Arthur is with me to run you through the latest.


This week we deployed the new device impact score and priority queue into production which had an immediate significant impact on response times.

This is a big subject, so I’ve written up as a separate article, which you can see here: https://edge.medium.com/priority-queue-aeb6c7abea0d

We fixed an issue that occasionally caused devices to miss-report the status of CDN’s state and subsequently receive jobs they were unable to fulfil. A patch fixed an issue that caused Gateway cache to flush after a fresh deployment. We also patched a minor bug with the impact score heap that caused memory issues when a device removal was attempted twice in quick succession.

Gateway now outputs the domain for cache size reporting, allowing us to easily understand the impact of each domain without the need to perform a lookup on the ID.

We migrated from using docker images per architecture (edge/host-amd64, edge/host-arm64) to a single unified image manifest edge/host.

And work continued on the API dedicated to capturing real time usage data from the network.


Thank you Arthur!

These changes to Gateway have made the network radically faster. It was already fast, but performance is now something else.

You can see a fully decentralised site here: https://thedecentralizedweb.com

(Check the site’s headers and you will the devices that participated in delivering it to you.)

Also this week, Edit held a few new businesses meetings, with some interesting opportunities for technology implementation being explored. Everything Edit does ladders back to the network.

Finally, something cool:

Type cdn.new in your browser and hit return.

And that’s all for this week.

Enjoy your weekends.

Fri, 12 Mar 2021 00:00:00 +0000 604f8c8a2e0f0a0019de435a Joseph Denne 2021-03-12T00:00:00+00:00
Weekly Update: W/C 01st March, 2021 https://edge.network/updates/announcements/weekly-update-wc-01st-march-2021 Hi everyone 👋

This is the one hundredth of these weekly updates. Quite the history! It’s been a good discipline to have, and I’ve really enjoyed doing them, so thank you to whoever it was in the community that first suggested them. And here’s to the next 100 🍻

It’s been an exciting week here, with big strides made in development as we move towards the reissue of Edge. The team has the best momentum it’s had in some time – you can feel the energy and the focus.

I have Adam with me this evening, who’s going to give you further insight into the approach for the implementation of $EDGE.


Evening all!

A number of you have spoken about the issue of gas fees in the Ethereum network and we’ve seen mention of potentially using ZK-Rollups and the like for staking and network transactions.

We’ve made use of an internal blockchain for tracking jobs for a while now, and it’s worked really well, but given our vision for the future and the prohibitive cost of using the Ethereum network for staking and governance, we’re evolving our native chain and are introducing wallet functionality, as well as providing a bridge between the Edge Chain and the Ethereum network (where $EDGE will be a tradable ERC-20 token).

This approach abstracts away the contract costs that come with running on the Ethereum network, and gives us the opportunity to introduce certain features to the Edge blockchain that will provide an additional level of traceability and transparency in the network.

Those of you who have been with us for a while will know that we’ve spoken about the use of the internal chain and our vision for it for quite a while, and this marks the next step in realising that vision, as we push forward to further decentralise more of the network.

We’ll be speaking more about this in the coming weeks, but the blockchain runs in the Stargate layer of the network, has a single distributed ledger made up of blocks that hold not only wallet to wallet transactions, but also network contribution and value attribution in the case of staked devices that are contributing to the operation of the network.

We’re also going to be releasing a blockchain explorer, allowing anyone to see how much work the network has performed on a block-by-block basis, and follow the distribution of earnings to the contributing network nodes.

This is super exciting, and I can’t wait to share more about this over the coming weeks.


Thank you Adam!

In other news, the team continued work on staking & integration, completing a whole raft of functionality including stake, unstake, cancelunstake, withdraw, burn, and update events, linking that up successfully with network API.

As well as the huge effort focused on $EDGE, the team also rolled through updates to core certificates in the network, covering Stargate functionality, Vault, Jenkins, Registries and Auth.

The team also prepared updates for Monday morning’s mainnet update, which will include releases for agent & cli, completing the transition to the new naming convention discussed in last week’s update.

And they started work on a deep store for long tail device activity (deeper metrics that live off chain).

We attended a handful of new business meetings virtually. And Edit kicked off a new engagement, implementing tools in the platform in support of a blockchain related start up. Work continued on the three subscription-based platforms currently being supported by the Edit team.

And finally: we’re in the early stages of developing a research programme with a leading university relating to the environmental impact of cloud computing and the benefits that Edge brings to the table. This is a major area of focus for us, as the emission savings vs. the traditional cloud are considerable.

Being able to fully quantify this in an accredited way will enable the unlocking of the value of the carbon saving. This is significant when looked at through the lens of both businesses benefit from network use and future revenue potential through the sale of released offset.

And that’s it for this week.

Enjoy your weekends.

Fri, 05 Mar 2021 00:00:00 +0000 604f85e22e0f0a0019de4350 Joseph Denne 2021-03-05T00:00:00+00:00
Weekly Update: W/C 22nd February, 2021 https://edge.network/updates/announcements/weekly-update-wc-22nd-february-2021 Hi everyone 👋

TNC have shared the following letter with us, which they are happy for us to share with you as well:


We’ve had confirmation that 3% will be the baseline. Good performance in the market will result in this being raised further. We’ve also had confirmation that all 13 exchanges will be available day #1.

We know you’ll be frustrated by the further delay, but hang tight, there’s light at the end of the tunnel.

Please note that the swap process will be coming to a close soon. The original date was the 26th of March 2021. We’re adding a two month grace period to this, meaning that the swap window will close three months today on Thursday, 27 May 2021.

Thank you for being on this journey with us. We’ve made amazing progress with the platform and are excited for what 2021+ holds.

Chris Mair:

As we’ve been discussing over the past few weeks, the rollout of the $EDGE token is pushing ahead apace.

Over the next few weeks we’ll be providing a lot of additional information about the plans for the token, including detail on how staking will work and what governance looks like. We’ll also be talking about coming changes to help strengthen and grow the Edge community.

In the meantime we wanted to take a moment to provide the broad timelines for $EDGE getting back into the market.

The timeline for the rollout of $EDGE is as follows.

$EDGE contract launch and token minting:

  • Ready to go
  • In plan for the end of the second week of March

Staking contract launch:

  • In security testing
  • In plan for the second week of March

Stake migration:

  • Process starts early April

Token distribution:

  • In testing
  • In plan for the end of March

Governance contract launch:

  • Being integrated
  • In plan for April

Referral programme launch:

  • In plan for April

Please note that these timings are subject to change. (Things come up when you’re building!)

And to reiterate, we’ll be providing a lot of detail on the individual items above over the coming weeks. As we’ve mentioned previously, the relaunch of $EDGE will be happening regardless of how the TNC unlock plays out. We remain confident that the things will progress as planned, in which case we’ll reissue $EDGE with the support of TNC.

And if unlock doesn’t go as planned we’ll be reissuing $EDGE just with recut tokenomics, but without the involvement of TNC.

Either way we remain super confident of what lies ahead. Exciting times indeed.

Joseph Denne:

In other news… we kicked off our social engagement campaign, the outputs of which you will start to see over the coming days and weeks.

The Edit team moved forward the implementation of two new subscription builds.

The network team finalised the staking contract and are in testing. There’s a direct network integration which synchronises stakes from the chain to the network, which allows the enabling and disabling of contributed devices on the network as the stakes change.

Integration with the contract is being added to Console.

We’ve addressed an issue with the existing pinger package which is used to identify the nearest devices and will be deploying a fix for this to test.network next week.

As part of an enhancement to the Gateway queue we’ve been working on a new Worker Pool package which is designed to act as an internal pub/sub interface to the atomicstore - a public package we released earlier this year. The Edge Worker package is in its final testing and documentation stage.

Stargate has been updated to use the Worker package which has already significantly reduced memory usage and CPU load.

A number of fixes relating to the docker package have been deployed on test.network, including an issue where a poor connection to a Gateway could cause Hosts to temporarily spin up multiple CDN containers. This issue had no effect on performance, but slowed down the boot process by a number of seconds.

Gateway is now passing minute-by-minute stats updates to Stargate for Host work, which in turn is stored in the network API.

The Gateway load balanced queue has been successfully tested and will be released into production on the 08th March, along with a new version of edge-cli.

The edge-cli release will use a new naming convention, finally moving away from arch based images names (e.g. agent-amd64, agent-arm) to a unified docker manifest, where all releases of agent will exist under one path. The edge-cli release now only accepts the new format.

And finally, we completed a research project relating to the energy efficiency of the Edge Network and the potential that it has for a positive impact on climate change. The work looked at individual services, drawing comparisons with traditional cloud-based alternatives. The outputs are very compelling. We’ll be sharing them soon.

And that’s it for this week.

Enjoy your weekends.

Fri, 26 Feb 2021 18:30:00 +0000 603d368c2e0f0a0019de434d Joseph Denne 2021-02-26T18:30:00+00:00
Weekly Update: W/C 15th February, 2021 https://edge.network/updates/announcements/weekly-update-wc-15th-february-2021 Hi everyone 👋

It’s Friday again and we’re racing towards the end of the month 🏃‍♂️

TNC remain on track for unlock next week.

“Next week is the d-day for everyone” – Jason

For those concerned about this slipping again, as we’ve previously discussed, there is a rollout plan for $EDGE in place and the Edge token will be released regardless of what happens with the TNC unlock.

As my co-founder Chris said, “we are relaunching $EDGE soon with or without TNC. Our hope is that the merger will play out, that our current supporters are rewarded for their initial involvement in our project, and that we can give the tokenonmics of the platform the support it needs with TNC’s help. In that case we would reissue Edge in partnership with TNC. Supply will be controlled and distributed with the primary goal of building the network. This will include the involvement of existing holders.”

“But it’s not the end of the world if that doesn’t happen. If it doesn’t, we’ll reissue $EDGE with recut tokenomics, again with the main objective being to expand the network and its use. Might take us longer that way, but we’re still committed to doing that.”

The underlying utility of the token is to facilitate the creation of a secure edge network through the staking and rewarding of devices. This hasn’t changed, but the function of the token is also being expanded to include network governance.

Participation in governance will be available to all staked nodes, and it will also be possible to stake specifically to participate in governance (i.e. without running a node). Stakers will be able to create and vote upon proposals, with proposals requiring certain majorities in order to be passed. Stargates will be given a collective right to veto or to propose amendments to proposals.

A governance framework will be published, outlining all aspects of the development and running of the network that should be run through the governance function.

We are also creating a growth fund, an allocation of tokens whose us will be directed through the governance function. This is designed to be used for and by initiatives that help to drive the network forward, such as marketing ideas, the development of products that run on network services, exchange listings or rewards.

The plan is for the release of the new token to happen in the near future: in March or April. Most of the work involved, such as contract authoring, Console updates etc., has already been completed, and full details will be released soon.

Plans for the evolution of Edit.com moved ahead significantly, with interface changes developed that will provide a site builder to enable the grid based design of mobile-first websites based on a wide series of templates. This will dovetail with the editorial interfaces that are already in place, enabling the on-demand creation of sites of any shape and size.

The roadmap for Edit includes the use of semi-dynamic frontend apps, something that we’ve been doing as standard for the last year in preparation for these developments.

This will enable Edit to publish sites directly into the Edge network, meaning that we will have an on demand platform for the creation of fully decentralised sites, hosted entirely in the Edge network.

“Edit on the Edge” anyone?

It’s a pretty exciting set of developments that should bring a lot of use to network services.

Work continues on the implementation of the governance model and on-chain staking. Integration of the staking contract & the network is progressing well.

We have an update to edge-cli ready to go live next week which contains the hooks in support of the updates.

This update also moves edge-cli away from arch specific images - e.g. agent-amd64, agent-arm - to a docker manifest which automatically pulls the correct version based on the system arch. This has prompted a few changes to CLI to handle some issues relating to the way CLI chooses the correct image on a cold start.

Scheduled maintenance was performed on the network image registry which continues to maintain a 100% uptime. The first version of the load balanced queue was deployed onto test.network this week. This is a large overhaul of the queueing system that analyses devices based on their current and past performance and assigns requests based on this impact score.

A few small fixes are required on the back of this week’s testing after we expect to ship it for production. All being well it will move on to mainnet at the end of next week.

And that’s it for this week.

Enjoy your weekends.

Fri, 19 Feb 2021 18:30:00 +0000 603d32f52e0f0a0019de434a Joseph Denne 2021-02-19T18:30:00+00:00