1 of 68

Wiki

Edge Community Wiki

Edge is pioneering the future of the Internet by introducing the world's first dedicated edge computing platform, breaking the grip of the mega corporations that have turned us all into digital serfs. By harnessing the untapped computing potential around us, Edge not only decentralises the cloud but also champions a more sustainable, faster, and democratic digital frontier.

Edge is the protocol of web3. Its versatile web services empower you to launch everything from dynamic websites to immersive games. Take part in the evolution and reclaim the web for everyone.

This is a living document that is regularly updated. Last update: 29th March 2025

The Edge Community Wiki is intended as the go to resource for all things Edge. Here you can learn about the technologies behind the platform; find out how to contribute to the network; how to participate in project governance; read answers to common support questions; and browse network FAQ.

If you'd like to contribute, please reach out to a community manager on the Edge Discord.

The source for the wiki can be found here: github.com/edge/wiki

Getting Started

Object Storage

Edge Object Storage provides highly redundant, fast, secure and affordable storage for all types of data.

Edge Storage is currently in development

Files in the Edge Network are encrypted and split into hundreds of pieces, and are then distributed across nodes in the network. This approach ensures the security of your data. Encryption keys are under your control, and no complete file is stored on a single device.

The availability of files and transfer performance in and out of the network is managed through replication and proximity to the point of use, making Edge the ideal solution for backup, file transfer and app level data storage.

Features

Secure

Files are encrypted and split into hundreds of pieces, which are then distributed across hundreds of nodes. This provides a level of security that is unmatched in market.

Highly Performant

Edge object storage supports multi-threaded and concurrent downloads. And its use of in memory caches ensure the fastest possible access to your files.

Reliable

Every fragment of every file is stored in multiple locations, building redundancy in to the heart of the solution. In addition, reed-Solomon erasure coding enables file rebuilding in the unlikely event of data loss.

Cost Efficient

Because it’s decentralized and built using the spare capacity all around us, Edge storage is significantly cheaper to use than traditional cloud solutions.

Integrated

Edge Object Storage is fulyl integrated within the Edge ecosystem, meaning that it can be used as the origin for Edge CDN, as a filestore for Edge Functions or as extended storage for implementations using the Edge Ledger.

Edge Tokenomics

$XE is the coin of the XE Blockchain, a layer 1 solution designed for fast transactions mapped to resource usage. It is bridged into the Ethereum network on a 1:1 basis with the $EDGE token.

Transactions within the Edge Network are free. Bridging $XE in/out of the network to $EDGE in other networks – such as Ethereum – carries a variable gas fee.

For transactions out of Edge Network, this fee is taken in $XE. Individuals can choose their target gas fees and the bridge will automatically transmit their transaction to meet the target set. This acts to help to keep transaction fees as low as possible.

For transactions into the Edge Network, the gas fee is taken in the native token of the other chain (for example, in $ETH).

As a network native coin, $XE does not count towards the circulating supply of $EDGE. Therefore service usage, staking, governance and fees all act to reduce the circulating supply of $EDGE by locking value in the network itself.

Changes relating to network tokenomics are run through project governance

$XE

$XE is the coin of the XE Blockchain, a layer 1 solution designed for fast transactions mapped to resource usage. It is bridged into the Ethereum network on a 1:1 basis with the $EDGE token, meaning that for every 1 $XE bridged out of the Edge Network, you will receive 1 $EDGE.

$XE is used for the purchasing of Edge services, for staking, network governance, and for node rewards.

Transactions

Transactions within the Edge Network are free.

There is an active governance proposal to introduce a small fee to help to maintain the security of the chain (mitigating against flood attacks). These fees would be burned. You can access and vote on the proposal here:

Service Purchase

Services can be purchased directly in $XE.

Node Staking

Edge is a Proof of Stake network. Contributing a node to the network requires a POS in $XE. Stakes are locked in the network for a minimum period of time and for the duration of the node being online.

Nodes that are found to be bad actors will have their stake penalised or removed. Stakes reclaimed by the network in this manner are burned (sent to a zero address in the XE chain).

Network Governance

Participation in network governance requires a stake locked in the network in $XE. This can be a stake used for the contribution of a node or an unassigned stake used purely for governance participation.

Fees tied to the raising of proposals in the governance mechanism are put into the growth fund.

Buy Back and Make

A buy back and make programme assigns network revenue recieved in fiat and other cryptocurrencies to the dev fund and to the growth fund.

Burn

75% of network revenues is burned. The coins are sent to the zero address of the network at the end of every month: xe_0000000000000000000000000000000000000000

$EDGE

$EDGE is a tradable utility token on the Ethereum network (ERC-20). It is the entry point to the Edge ecosystem and can be used for the purchasing of Edge services.

$EDGE tokens can be bridged into the Edge network and converted to $XE using the Edge Bridge. The relationship between $EDGE and $XE is 1:1, meaning that for every 1 $EDGE bridged into the network, you will receive 1 $XE.

When $EDGE is bridged into the network, it is locked in the token bridge hot wallet 0x956.., which is backfilled by the bridge cold wallet 0x8f18.. if necessary. Currently over 85% of all tokens are circulating as $XE, and thus locked in the $EDGE cold wallet (deployer contract).

When services are purchased in $EDGE, the $EDGE is automatically bridged into the network, reducing circulating supply.

Service Purchase

Services in the Edge Network can be purchased with $EDGE. They are also available for purchase within the Visa and MasterCard networks. Enterprises wishing to be invoiced directly can do so by reaching out on: sales@edge.network

Purchases made in $EDGE are automatically bridged in to Edge Network and swapped for $XE.

Purchases made in fiat (Visa/MasterCard) or in other cryptocurrencies are swapped for $EDGE before being bridged into Edge Network, converting them to $XE.

Liquidity Mining

An $EDGE liquidity pool is available on Uniswap. This is part funded by the network treasury, part by individual contributors.

Uniswap applies a small fee for every trade that takes place on their platform and automatically sends this to a liquidity reserve. Whenever a liquidity provider decides they want to exit the $EDGE pool, they will receive a portion of the total fees from the reserve relative to their staked amount in $EDGE the pool.

In addition to this, a 0.75% fee is applied to all $XE transactions moving through the network bridge. This amount is automatically deducted from the sent amount and is collected in an $XE vault wallet (xe_4845075Ad790DD979Ab3f7834Ff507244e7a5449).

Monitoring Project Tokenomics

The network explorer exposes all on-chain activity and can be used for the monitoring of network transactions.

In addition to this, the explorer exposes a series of endpoints covering key tokenomic figures such as circulating supply. These can been seen below:

Endpoint

URL

Maximum Supply

Total Supply

Circulating Supply

Staked Supply

Burned Supply

To see a raw numerical response for each endpoint, add ?raw=true to the end of the URLs above. For example: https://xe.network/api/supply/maximum?raw=true

Dev Fund

The Dev Fund holds $XE assigned to support the technological development of the Edge Network.

The use of these funds is under the control of the core team, with guidance regarding focus provided through project governance.

The dev fund is designed to be used for core development. This includes developer remuneration, hardware and software costs, securing IP rights and any other directly associated overheads.

The dev fund is funded by a buy back and make programme, with network revenues converted to $XE and transferred to the fund.

Growth Fund

The Growth Fund holds $XE assigned to support the marketing and growth in uptake of the Edge Network.

The use of these funds is under the control of project governance, meaning that community members can raise proposals for its use, and vote on proposals raised.

The growth fund is designed to be used for activities outside of core development. This includes exchange listings, marketing, third party integrations, partnerships and community engagement.

The growth fund is initially funded through a dilution applied to all current $EDGE holdings. A buy back and make programme assigns a percent of network revenues to the growth fund. In addition to this, a percent of the gas fees from the network bridge are put into the growth fund.

The Growth Fund is controlled through network governance

Project Roadmaps

The project roadmap for Edge provides a guide to the current and upcoming development focus for the platform. The roadmap is maintained at a high level and is deliberately low resolution. Individual work streams have their own development schedules and lists, which are maintained in Git.

The roadmap is updated regularly as priorities change and new requirements are confirmed

Technical Roadmap

Rolling Priorities

Alongside specific technical milestones there are high level project goals that the core team are working towards. These include moving the project to a full open source footing; moving to full decentralisation in all areas of the network stack; preferencing anonymity and privacy; and deeply embedding community governance throughout the project's organisational structures.

The nature of these tasks is such that it isn't possible to schedule them as finite deliveries. Rather they are understood by the entire team as objectives, and are consistently being worked towards.

Getting and Storing Tokens

Project Governance

Contributing to the Network

Supporting the Network

Support

$XE Distribution

$XE distribution closed at the end of September 2021

A total of 50 million $XE were minted and distributed at genesis. In addition to this, 10 million $XE were locked in the network to be mined and released as node rewards.

Distribution Break Out

The Dev Fund holds $XE assigned to support the day-to-day development of the network. The Growth Fund holds $XE assigned to support the marketing and growth in uptake of the Edge Network. The Staking Contract holds $XE locked in the network as governance and node stakes. The Community distribution are the $XE held by individual supporters and customers of the Edge Network.

The figures below represent the initial distribution percentages for $XE

Distribution

Percentage Allocation

Dev Fund

Tokens used for the ongoing development of the project.

13.03%

Growth Fund

Tokens used for the ongoing promotion and growth of the Edge Network. Under community governance.

8.36%

Staking Contract

Tokens locked in the network as stakes against contributed devices.

26.28%

Community Circulating

Tokens held by members of the Edge community.

28.99%

Founding Team

Core team token allocation. 5 year linear vesting schedule starting December 2021.

6.67%

Staked Node Rewards

Tokens locked in the network for slow release as node rewards. Released at a rate of 10% of remaining rewards per year.

16.67%

The Growth Fund is controlled through project governance.

Node Rewards

$XE has a mineable supply of 10 million coins, with a steady emissions curve tied to block time. Mined coins provide the yield for the network and are released as node rewards.

The maximum yield in year one is 1 million $XE (10%). This will be reduced in year two, further in year three and so on.

The following table shows emitted $XE from genesis and for the next five years:

Year

Emitted $XE

Supply Increase

2021/22

1,000,000

2.00%

2022/23

900,000

1.76%

2023/24

810,000

1.56%

2024/25

729,000

1.38%

2025/26

656,100

1.23%

2026/27

590,490

1.09%

2027/28

531,441

0.97%

2028/29

478,296

0.87%

Node rewards are held in a network-controlled wallet:

$XE Wallet Address

Project Updates

As part of Edge's ongoing commitment to transparency and development in the open, the core team write weekly updates to the Edge community.

Updates are weekly on Telegram and Discord. This archive is out of date.

There have been 206 of these so far.

Latest Update

The 2023 roadmap prioritisation proposal closed last week with 37 votes cast and 97.3% in favour. Thanks to everyone who voted and took part in the discussions.

You can find it here:

Today the first community proposal, to implement an automatic lottery system for active Hosts, closed with 34 votes cast, all in favour. Thanks to everyone who took part and to Pod & Max for submitting it.

You can find it here:

The core team have also just published another proposal: Implement a small fee for transactions within the XE Blockchain.

You can find it here:

And discuss it here:

This week the team has continued work on multi-Stargate support. This will be broken down into two release stages: first there will be an update to the connection mechanism between Hosts, Gateways, and Stargates, and then following this, there will be a migration over to a new cluster of Stargates. We’ll keep you updated as we continue to press ahead towards this.

There have been a number of mainnet releases this week:

Explorer v1.23.3 was deployed to mainnet. This patched a minor UI bug with the XE Burned amounts on the Overview page when accessed from mobile devices.

Index v2.4.7 was deployed to mainnet. This patch fixed a minor issue with the display of revenue burn transactions. Revenue burns will now show up as “Revenue Burn” rather than “Misc” in the burns view.

Explorer v1.24.1 was deployed to mainnet. This added a simple proxy endpoint for the Index API. All requests going to https://xe.network/api will be proxied through to the index API. For example, https://xe.network/api/blocks will return the results from https://index.xe.network/blocks. This makes it easier to access blockchain data.

In addition we have added endpoints for token supply information, including circulating supply (https://xe.network/api/supply/circulating), maximum supply (https://xe.network/api/supply/maximum), total supply (https://xe.network/api/supply/total), burned supply (https://xe.network/api/supply/burned) and staked supply (https://xe.network/api/supply/staked).

These endpoints include monitored address references and a brief summary of the purpose of the figure.

Index v2.5.0, v2.5.1, and v2.5.2 were deployed to mainnet too. This series of updates introduced some new supply endpoints to the API. These endpoints allow you to see the total, max, circulating, burned, and staked supplies of XE. These will be used in upcoming changes to the explorer and will also be used by CoinMarketCap & CoinGecko as we work to improve our listings on those sites.

Account v1.14.7 was deployed to mainnet, fixing a minor UI bug in Firefox.

In other news, Chris held a marketing focused live chat on telegram. This will be repeated in the coming weeks, and will probably happen on Twitter Spaces to allow for the session to be recorded. Watch this space.

Some of you may have noticed transactions for Write For Edge. For those of you who missed it, we’ve launched a docs site for Edge Products.

This can be found at https://docs.edge.network/ (short link: ed.ge/docs).

We’ll be creating (with your help) a series of guides relating to the use of Edge products and services. From setting up linux boxes, to configuring CDN, to operating microservices on top of Edge servers using docker.

If you're a technical writer or have good knowledge about Linux systems and/or open-source software, you can get paid to write tutorials. You can find out more about the programme here:

We’ve already had a number of tutorials contributed, which you can find here: https://docs.edge.network/edge-servers/tutorials

This week saw the addition of two new tutorials for Edge Servers:

Posted by: Joseph Denne

Edge Products

There are three products live in the network mainnet today, Edge Servers, Edge DNS and Edge CDN. More products are in development, including Edge Storage, Edge Functions and Edge DB.

Together these products allow you to create and run fully decentralised applications and websites.

Edge Product Use Cases

Hosting

Static websites can be run through CDN

An example of a static site hosted via Edge Content Delivery can be seen here:

Dynamic sites can be delivered using Edge Servers, which as VPSs are capable of running practically any application.

Hosting on the Edge ensures a lightening fast experience for your end users, increasing conversion and retention.

Content Delivery

The performance of applications and websites can be improved through the use of CDN, which distributes images, media and assets as close to the end audience as possible.

Edge CDN includes a full media pipeline, enabling you to transform, optimise and intelligently cache your media library using simple and robust URL parameters.

Edge CDN can be used a drop in replacement for existing CDNs, and can be added to websites and apps without a CDN in place quickly and easily.

Domain Routing

DNS is a critical part of the Internet and for all online businesses. Edge enables the management of DNS routes, providing an authoritative DNS service that offers instant updates, hyper-local routing, high redundancy, and advanced security with built-in DDoS mitigation.

Highly performant DNS has a real-world impact on the performance of your entire product. Slow domain lookup times compound with each request that your website or app triggers for the ned user. Edge DNS has been shown to increase overall performance by 65%+.

Edge Object Storage enables fully decentralised, high performance and secure file storage, backup and file sharing for individuals and businesses. Files stored in the Edge Network can be encrypted with your own private keys, and are broken in to hundreds of pieces, providing an extremely secure data storage solution.

Application Acceleration

Caching API endpoints at the edge of the network accelerates your products responsiveness, improving user experience, helping to drive deeper engagement and higher conversion.

Customer Success

Edge technology is in production use today, powering some of the best digital experiences online.

Monocle

Monocle use Edge CDN for the management of images and audio across their estate, including on their website at monocle.com, in their mobile app M24 and, via a sync-up with InDesign, in the publication itself.

High resolution source images are scaled and intelligently cropped by Edge CDN, significantly reducing the weight of work for their editorial teams.

We’ve streamlined our production with Edge, saving time and ensuring an optimal experience for our end users. – Joe Gwynn, Head of Technology | Monocle

View property: monocle.com

Ecohustler

Ecohustler is an environmental news outlet, activism network and shop. Making use of the the cleanest available technology is central to their mission. Edge is unique in its use of the spare capacity in the devices all around us, meaning reduced emissions through lower power consumption.

Edge helps us reach our audience energy efficiently, using spare capacity in existing devices rather than building dedicated data centres. – Matt Mellen, Founder | Ecohustler

View property: ecohustler.com

PPA

The Professional Publishers Association represents publishers across the UK. They are partnered with Edge, recognising the workflow optimisation and cost savings that the technology brings to their sector.

Edge CDN optimises publisher workflow, making it easier and faster to deliver media to readers. – Owen Meredith, CEO | PPA

View property: ppa.co.uk

Empire

Bauer Media use Edge CDN to power their vast image library across hundreds of websites and mobile applications. It enables their product teams to rapidly deploy solutions that use code to edit imagery.

Edge helps us deliver experiences in days and weeks not weeks and months. – Matt Hobbs, CTO | Bauer Media

View property: empireonline.com

Foundland

Recognising that every second spent loading represents an incremental reduction in sales conversion for e-commerce, Foundland use Edge CDN to ensure high-performance delivery to their global audience.

Edge has given us the ability to provide a customer experience that is identical regardless of location. We can drive traffic across global marketing platforms without worrying about the high costs of regional infrastructure. – Sarah Khalaf, Founder | Foundland

View property: foundland.com

Podcast

"Conversations on the Edge" was a series of audio shorts discussing the Edge Network and how it is poised to change the Internet.

Episode 38, 11th February 2022

Introducing the Edge Network marketing consultation – we’re about to change gear when it comes to outreach and we want your input. Listen, then head to Discord to discuss.

Episode 37, 04th February 2022

Why we open source: this week we talk about the tech strategy and philosophy for Edge Network and how all roads lead to DAO.

Episode 36, 28th January 2022

Time to get involved: the shape of the Edge Network community and how you can have a say in the future of our project. It begins with active new roles in Discord – the start of our road to DAO. Listen to find out more.

Episode 35, 21st January 2022

The world according to Edge: what global reach means to us and why we’re able to offer market-leading cloud services wherever you live.

Episode 34, 13th January 2022

The last 12 months were big for crypto and HUGE for Edge. This week, we review the year that was 2021 and look forward to 2022.

Episode 33, 24th December 2021

Edge is the infrastructure of Web3 – but what is Web3 and why does it matter? And how does Edge Network fit into its decentralised future?

Episode 32, 17th December 2021

Using Dropbox or Google Drive to store and share files? Upgrade to a faster and greener Web3 alternative by – you guessed it – Edge Network. Here's te lowdown on why you need to join the waitlist.

Episode 31, 10th December 2021

Interest in Edge Network has never been higher, so this week’s Conversations on the Edge is one for the noobs – and a reminder for the rest of the community as to why we’re Faster, Greener and More Secure.

Episode 30, 03rd December 2021

More digital brands are choosing to host projects on Edge Network as each week passes. This week, we run through the headline network customers and talk about why they are pioneers.

Episode 29, 27th November 2021

We've been busy. Record $EDGE token transactions, exchange announcements and a new launch for Haven Protocol on Edge Network. Time to check in with founder Joseph Denne on all this, plus plans for 2022.

Episode 28, 19th November 2021

We announced a new exchange this week – what does that mean for $EDGE and what is our strategy for building the token community? Listen to find out.

Episode 27, 12th November 2021

Weighing up whether to buy $EDGE tokens? Thinking about earning revenue by contributing to Edge Network? Want to find out how the roots of our project go all the way back to 2013? Then you want Edge Wiki. Here's an intro to the home of all Edge knowledge.

Episode 26, 05th November 2021

Running a project on blockchain? Want the chance to host your website or digital product on Edge Network for free? Listen up – we're about to launch a campaign to support crypto business.

Episode 25, 29th October 2021

Are you proud of your cloud? Does anyone in your business even think about the impact of your digital services on the environment? Here's how Edge Network can make your digital products look good.

Episode 24, 22nd October 2021

What is CDN? A deeper dive into just one of the applications offered by Edge Network – now in active use with over 70 digital brands.

Episode 23, 15th October 2021

So you want to be a part of Edge Network. You want to to earn revenue for contributing spare capacity from your laptop or desktop machine as soon as possible. Here’s how to be ready…

Episode 22, 08th October 2021

‘Tech for good’ isn’t only about code, it’s a code of practice. And it starts by being open about our mission – in this week's episode we talk about transparency and fairness, from weekly updates to the power of the crowd.

Episode 21, 01st October 2021

The Edge of reality: blockchain needs real projects to provide value beyond its tokens – and Edge, with its live products and customers, is proof of this. Listen to find out why.

Episode 20, 24th September 2021

With $EDGE now released and value on the rise, it’s time to think about staking – and your chance to earn revenue for contributing to Edge Network. This week – on our 20th episode! – we tell you why.

Episode 19, 17th September 2021

This week's Conversations on the Edge invites you to plant trees – but because you want to, not because you feel like you have to.

Episode 18, 10th September 2021

Edge Network uses your private devices to store its data – and that’s what makes it more secure than the traditional cloud. This week's Conversations on the Edge tells you why.

Episode 17, 03rd August 2021

The world needs more and more Internet and the technology of Edge Network is the only digital infrastructure solution. On this week’s episode, we explain why.

Episode 16, 27th August 2021

This week, why switching digital services to Edge Network will make your business greener, faster and more cost-effective. It's a change you can make right now using CDN...

Episode 15, 20th August 2021

In a changing world we need a more sustainable internet – and that begins with cloud infrastructure. This week, we examine how Edge Network is part of a new generation of technology for cleaner cloud services.

Episode 14, 13th August 2021

Edge Network harnesses the power of people to change cloud services – and with it the world. We call it 'crowd infrastructure', and this episode of Conversations on the Edge explains how you can be a part of it.

Episode 13, 06th August 2021

Most of you probably know Edge Network is powered by blockchain technology, but did you know why? Or how? This explainer has all the answers – listen, and then wonder why you're not already a customer or contributor to the network.

Episode 12, 30th July 2021

The Edge Network team returns for another edition of Conversations on the Edge – this time about the exponential rise in demand for digital services. Can traditional cloud infrastructure cope? How does Edge Network promise to change things for the better?

Episode 11, 23rd July 2021

How does Edge Network keep safe the data entrusted to it by its clients? How does it compare to traditional cloud services? In this latest episode we talk to Edge founder Joseph Denne and the network’s Blockchain Lead, Adam K Dean about security.

Episode Ten, 16th July 2021

It's episode 10 of Conversations on the Edge and we focus on content delivery. Edge CDN is the real-world opportunity to move your digital business to the 'future cloud' for faster and greener apps and websites. It's not all about performance, either – Edge CDN is a feature-rich market leader in its own right.

Episode Nine, 09th July 2021

This week: Edge Network and security. Is your data any more secure in the traditional cloud because it is locked up miles away on massive servers in fortress factories? Spoiler alert: no. It just makes access to that data slower and more expensive.

Episode Eight, 02nd July 2021

Edge offers enhanced network performance for optimal user experience – an ideal application for media brands. This week's Conversations on the Edge looks at how Edge Network helps digital media services differentiate, from providing lightning-fast page load to carbon-efficient technology.

Episode Seven, 25th June 2021

Every time you so much as move on the Internet, someone profits from your action – and in almost half of all cases that will be Google, Amazon or Microsoft. This week's Conversations on the Edge looks at how Edge Network seeks to share revenue from digital services and why that will make the Internet a fairer place.

Episode Six, 19th June 2021

Is the cloud really just smog? This week in Conversations on the Edge, we examine digital infrastructure and carbon footprint – does the industry need to clean up its act? And does Edge Network offer the technology to do this? (Spoiler alert: yes.)

Episode Five, 11th June 2021

Half of the Internet is hosted by just three companies. Is that fair? This week in Conversations on the Edge, we look at the network that powers our new digital society – and how it should be in the hands of the many, not the few.

Episode Four, 04th June 2021

We’re on the cusp of unprecedented demand for data storage and traditional infrastructure just won’t cut it. In our fourth episode of Conversations on the Edge, we discuss the future of the Internet – and why we need a new cloud.

Episode Three, 28th May 2021

Episode three in our new series of audio shorts deals with localisation. Our team discusses Edge as the local-global network – how nodes located in home and offices everywhere reduces the distance between storage and consumption and builds a greener internet.

Episode Two, 21st May 2021

The second instalment in our new series of audio shorts discussing Edge Network and how it is poised to help change the Internet. This week, we examine how Edge reuses the hardware all around us to build the future cloud – a faster and greener digital infrastructure that scales with future demand.

Episode One, 14th May 2021

This week, our host talks to founders Joseph Denne and Chris Mair about fairness – whether the future of the web is in the hands of too few people and how Edge technology is designed to redress the balance.

Weekly Updates

As part of Edge's ongoing commitment to transparency and development in the open, the core team write weekly updates to the Edge community.

An Introduction to Staking

If you have spare computational power you can earn income by being an Edge Host.

Edge nodes earn $XE coins in return for this, and these can be used to purchase services from the network, or exchanged for $EDGE for trading in the wider crypto marketplace.

Stakes also form an important part of the tokenomics of the platform, locking value in the network and reducing overall circulating supply.

Staking software is available on desktop (Windows, Linux, MacOS): http://ed.ge/staking ****

To add a node to the network you have to provide a stake in $XE via your Edge Wallet or edge CLI.

Proof of Stake

Proof of Stake (POS) in the Edge network is designed to incentivise system stability and security while ensuring a high level of decentralisation.

Staking levels are set based on the capacity requirements in the network in any given period. As the Edge Network is a marketplace, it is important to ensure that node contributions match customer demand, and that these requirements remain balanced.

In the event that a Node does not meet minimum availability targets, penalties will be applied against their POS. You can think of this as an uptime guarantee. Uptime is more important for Stargates than for Gateways and for Gateways than for Hosts, and the availability requirements are set accordingly. Stargates must meet a 99.9999% availability, whereas for Hosts availability is set at 20%. Availability can be low for Hosts because of how the system is architected: it is designed to allow for a high level of disconnect and reconnect at this level.

As the requirements for Nodes grows, the proof of stake required at each level in the network will be reduced. This metric is a balance of supply, demand and network availability.

** Only Host onboarding is currently available to the community. More information about onboarding Gateway/Stargate nodes will be provided in future. **

Stake amounts

Node Type

$XE Stake Required

Expected Yield (Av.)

Stargate

250,000

20%

Gateway

25,000

15%

Host

100

10%

Stake amounts are subject to change

Edge CLI

This document is written for Edge CLI v1.5.3 and may not be up to date or necessarily complete. The output shown in examples may also change over time. The most accurate and up-to-date documentation is available as helptext within Edge CLI itself. Access helptext by adding --help to any command, for example edge --help or edge tx ls --help

All usage examples here refer to the edge binary for continuity, but some examples actually use testnet data. Do not take information displayed in examples from this page as authoritative - it is for illustrative purposes only.

Global options
Wallet
Transaction
Stake
Device
About Edge

Global options

Edge CLI includes some global options that affect all commands. These can be provided before or after the sub-command.

Wallet option

The -w, --wallet <file> option allows you to specify a different path to your wallet than the default. This may be useful if the default path is not usable or you want to use multiple wallets.

The wallet is stored in a single JSON file, so the <file> should not be a directory.

Verbose option

The -v, --verbose option toggles greater verbosity in output. For example, CLI by default truncates stake hashes for readability:

% edge stake ls | awk '/Hash/ {print $2}' | head -n 1
f151dfbb9bb9

With greater verbosity, the full hash is shown:

% edge stake ls -v | awk '/Hash/ {print $2}' | head -n 1
f151dfbb9bb924c13a55d11ebaef4a49c061e849300ce101c5c0850fe9516499

Debug option

The --debug option enables detailed output for complete visibility of CLI's behaviour. It also enables greater detail of any errors that may occur. This may be useful if you are having problems with CLI and you (or Edge support) need more information about what is happening.

The debug option effects _very_** noisy, sometimes abstruse output and its use is discouraged when not absolutely necessary.**

The debug option may be useful for understanding if you intend to contribute to the CLI codebase.

Other options

Other global options include disabling output colours with --no-color and specifying Docker connectivity (for device commands) with --docker-socket-path. You can see all available global options by running edge --help.

Global options are not displayed when viewing the helptext for specific commands, but are available to all commands nevertheless.

Wallet

Wallet commands enable you to manage the XE wallet used by CLI. You can use a single wallet across multiple devices, or different wallets, depending on your needs.

Create a Wallet

edge wallet create

This command creates a new XE wallet. This is an interactive command that asks you for a passphrase and private key export preference. Example:

% edge wallet create
A wallet already exists. Overwrite? [yn] y

To ensure your wallet is secure it will be encrypted locally using a passphrase.

Please enter a passphrase:
Please confirm passphrase:

Wallet xe_6B4C26b2BC0Fa4AA7B182266eEB5AdFba83AD998 created.

Would you like to (v)iew or (e)xport your private key? [ven] e
Enter filename to export private key to: my.key

Private key saved to my.key.

If you choose not to view or export your private key, you can still retrieve it later using the edge wallet info command. See 'Display Information' below.

You can use this command non-interactively by providing all the options upfront. Example:

% edge wallet create -f -p 'mypassphrase' -K my.key
Wallet xe_6926C5ED28aAF6Aa12D842029fF81b014F107450 created.

Private key saved to my.key.

Run edge wallet create --help for more information on options.

Restore a Wallet

edge wallet restore

This command restores an XE wallet. This is an interactive command that asks you for a private key and passphrase. Example:

% edge wallet restore
Please enter a private key:

To ensure your wallet is secure it will be encrypted locally using a passphrase.

Please enter a passphrase:
Please confirm passphrase:

Wallet xe_1c0561A342099962cD4a699f55DCfb9Fd6772bf2 restored.

Similarly to the create command, this command can be used non-interactively by providing all options upfront. Run edge wallet restore --help for more information on options.

Display Information

edge wallet info

This command displays XE wallet information. By default it will only display the wallet address:

% edge wallet info
Address: xe_E82c7c2320b5F38A00ee5275E228eE708f79e3f8

If the -p, --passphrase or -P, --passphrase-file option is specified, the private key is also shown:

% edge wallet info -P passphrase.txt
Address: xe_E82c7c2320b5F38A00ee5275E228eE708f79e3f8
Private key: [REDACTED FOR WIKI]

Display Balance

edge wallet balance

This command displays your current XE wallet balance.

% edge wallet balance
Address: xe_1c0561A342099962cD4a699f55DCfb9Fd6772bf2
Balance: 706,168.950000 XE

Forget Wallet

edge wallet forget

This command forgets (deletes) your XE wallet. If no wallet is found, it has no effect.

% edge wallet forget
Address: xe_A0505511d43D98BAf391f0801a9C589291F8D645

Are you sure you want to forget this wallet? [yn] y

Your wallet is forgotten.

Transaction

Transaction commands enable you to send XE to other wallets and display historic transactions to/from your wallet.

For ease of use, the command edge transaction ... can be abbreviated to edge tx ... as shown in usage examples.

Send a Transaction

edge tx send <amount> <wallet>

This command sends a specified XE <amount> to the given <wallet> address. The amount can be specified in XE or mXE (0.000001 XE) by providing the unit e.g. 100xe or 100mxe. If no unit is given, XE is assumed.

You must provide your passphrase to sign the transaction.

An example of sending 10 XE to the testnet supply wallet:

% edge tx send 10 xe_00009f6354aa0449eACA1Af54FCf7171cAc85cB7
You are sending 10.000000 XE to xe_00009f6354aa0449eACA1Af54FCf7171cAc85cB7.
10.000000 XE will be deducted from your wallet. You will have 705,533.950000 XE remaining.

Proceed with transaction? [yn] y

This transaction must be signed with your private key.
Please enter your passphrase to decrypt your private key, sign your transaction, and submit it to the blockchain.

Passphrase:

Your transaction has been submitted and will appear in the explorer shortly.

https://test.network/transaction/a3a2067139179c2ac390a23e3000b023f7b3ac2401aec2846c5d27513e809669

This command can be used non-interactively by providing all options upfront. Run edge tx send --help for more information on options.

List Transactions

edge tx list|ls

This command lists historic transactions to/from your XE wallet, from most recent to oldest. You can paginate transactions with the -l, --limit and -p, --page options. If these are not set, it will fetch your 10 most recent transactions.

An example fetching one (the most recent) transaction:

% edge tx ls -l 1
Page 1/98

Tx:        a3a2067139179c2ac390a23e3000b023f7b3ac2401aec2846c5d27513e809669
Nonce:     83
Block:     126409
At:        2022-00-02 13:30:41
To:        xe_00009f6354aa0449eACA1Af54FCf7171cAc85cB7
Amount:    10.000000 XE
Signature: ba3a8e549beb67c95da29e7ba4365a10cc2743e336fca68ed1edb094676041bb6478aa4d88c9eb820969428615172f08062c4a523cceef1ede98c2214a88561601

List Pending Transactions

edge tx list-pending|lsp

This command lists any pending transactions that have not yet been processed by the XE blockchain. There are no options for this command.

Stake

Stake commands enable you to manage your stakes on the XE blockchain. A stake is required for each device with which you intend to contribute computing power to the Edge network.

Display Staking Information

edge stake info

This is an informational command that displays current staking amounts, as configured on the XE blockchain.

% edge stake info
Current staking amounts:
  Stargate: 250,000.000000 XE
  Gateway:   25,000.000000 XE
  Host:         100.000000 XE

Create a Stake

edge stake create <type>

This command creates a stake which, once processed by the XE blockchain, allows you to run a device of the specified <type>.

**The types available are Host host, Gateway gateway, and Stargate stargate. At this time, only Host stakes are available to contributors. Access to create Gateway and Stargate stakes will be updated in future.

Your stake will be created via a blockchain transaction, signed using your private key. You will need to enter the passphrase for your XE wallet to decrypt your private key for this purpose.

An example of creating a Host:

% edge stake create host
You are staking 100.000000 XE to run a Host.
100.000000 XE will be deducted from your available balance. You will have 703,668.950000 XE remaining.

Proceed with staking? [yn] y

This transaction must be signed with your private key.
Please enter your passphrase to decrypt your private key, sign your transaction, and submit it to the blockchain.

Passphrase:

Your transaction has been submitted and will appear in the explorer shortly.

https://test.network/transaction/0b86daf2b729fb5d1fea8f8b41d8b2907358cb11dc052b3451c9fc0b0763bc0f

This command can be used non-interactively by providing all options upfront. Run edge stake create --help for more information on options.

List Stakes

edge stake list|ls

This command displays all stakes associated with your wallet. For example, the stake that was created above:

% edge stake list | head -n 7
ID:      1a6e6511e3f8
Hash:    1df3e124915c
Tx:      0b86daf2b729fb5d1fea8f8b41d8b2907358cb11dc052b3451c9fc0b0763bc0f
Created: 2022-01-26 11:14:18
Amount:  100.000000 XE
Type:    Host
Status:  Active

Unlock a Stake

edge stake unlock <id>

Unlocking a stake places the associated XE funds in a waiting period (currently 90 days) after which they can be released back to your XE wallet balance.

For ease of use, you can enter a truncated stake ID (minimum 3 characters).

For example, unlocking the stake created above:

% edge stake unlock 1a6e6511e3f8
You are requesting to unlock a Host stake.
After the unlock wait period of 90 days, you will be able to release the stake and return 100.000000 XE to your available balance.

Proceed with unlock? [yn] y

This transaction must be signed with your private key.
Please enter your passphrase to decrypt your private key, sign your transaction, and submit it to the blockchain.

Passphrase:

Your transaction has been submitted and will appear in the explorer shortly.

https://test.network/transaction/050b5ae60652e8578a6ab415c5352874dd60c4a2987c7ec90451ca3793aa7431

This command can be used non-interactively by providing all options upfront. Run edge stake unlock --help for more information on options.

Release a Stake

edge stake release <id>

This command releases an unlocked stake, returning its funds to your XE wallet balance.

For ease of use, you can enter a truncated stake ID (minimum 3 characters).

To reclaim the full amount, your stake must have exited the unlock wait period (currently 90 days). Alternatively, you may use the -e, --express option to immediately release the stake for a fee.

For example, express-releasing the stake created above:

% edge stake release 1a6e6511e3f8 -e
You are releasing a Host stake.
1,875.000000 XE will be returned to your available balance after paying a 25% express release fee (625.000000 XE).

Proceed with release? [yn] y

This transaction must be signed with your private key.
Please enter your passphrase to decrypt your private key, sign your transaction, and submit it to the blockchain.

Passphrase:

Your transaction has been submitted and will appear in the explorer shortly.

https://test.network/transaction/357e386771e2797dd4515ec2431f6d94d789360cea0db8fc5ae87ec5e00909ba

This command can be used non-interactively by providing all options upfront. Run edge stake release --help for more information on options.

Device

Device commands enable you to manage your device's participation in the Edge network.

Before using device commands, ensure the prerequisites are met:

Ensure your device meets the minimum specification (see Network Nodes)
Install Docker (v18.06+ required)

Device commands will not work if Docker is not running on your device.

If you are setting up a device for the first time, see Set up a Host for step-by-step guidance.

Add Device

edge device add

This command adds your device to the Edge network. This works by associating your device's ID with a stake. You must have created a stake already, and you will need to enter your passphrase to sign the assignment transaction.

An example of adding a new device to the network:

% edge device add
Initializing device...

Select a stake to assign this device to:

1. 2afb74887fb9 (Gateway)
2. 69213d41cb2b (Host) (assigned to xe_8f5e0d...)
3. eb4c6478073b (Host)
4. 93e3718dba1d (Host)
5. 25f47bf9b04a (Host)

Enter a number: (1-5) 3

You are adding this device to Edge Testnet.

This device will be assigned to stake eb4c6478073b, allowing this device to operate a Host node.

Add this device? [yn] y

This transaction must be signed with your private key.
Please enter your passphrase to decrypt your private key, sign your transaction, and submit it to the blockchain.

Passphrase:

Your transaction has been submitted and will appear in the explorer shortly.

https://test.network/transaction/99447fb4eb6734f6dbdab6d508e127f7d4b936702af911accb2e9dff3e06df2a

Your device assignment may take a minute or two to be processed by the XE blockchain. Afterwards, the other edge device commands will be usable.

This command can be used non-interactively by providing all options upfront. Run edge device add --help for more information on options.

Display Information

edge device info

This command displays information about your device and the stake to which it is associated. For example:

% edge device info
Network: Testnet
Device:  xe_3c627b72081a813B7864caB71f5DbA0D232E7053
Type:    Host
Stake:   eb4c6478073b

Start Device

edge device start

This command starts the network node on your device. This is determined by the type of stake to which the device is assigned.

% edge device start
Checking Host version...
Updating Host v2.1.0-40...
Host started

Display Device Status

edge device status

This command displays the current operational status of the node on your device: namely, whether it is running or stopped.

% edge device status
Host is running

Update Device

edge device update

This command checks for an update to the node, downloading the update automatically if necessary.

If the node is running, it will be stopped and restarted to update to the new version.

% edge device update
Checking Host version...
Updating Host v2.1.0-40...
Host is up to date

Nodes are normally self-updating, so you should not normally need to use this command. However, it may be usefupl if you are troubleshooting or developing the node application.

Restart Device

edge device restart

This command restarts the node without checking for an update. If the node is not already running, this has no effect.

% edge device restart
Host restarted

Stop Device

edge device stop

This command stops the node. If the node is not already running, this has no effect.

% edge device stop
Host stopped

Note that stopping a node does not remove the device from the network - it merely makes it inoperational until it is started again.

Remove Device

edge device remove

This command removes the device from the Edge network. This consists of unassigning the device from the stake, stopping the node, and destroying the device's identity. (A new identity will be created if the device is added back to the network.)

An example of removing a device from Testnet:

% edge device remove
You are removing this device from Edge Testnet.

This will remove this device's assignment to stake eb4c6478073b (Host).

Remove this device? [yn] y

This transaction must be signed with your private key.
Please enter your passphrase to decrypt your private key, sign your transaction, and submit it to the blockchain.

Passphrase:

Unassigning stake...

Your transaction has been submitted and will appear in the explorer shortly.

https://test.network/transaction/3926669c672b47a1a67f08f5baaee09a57222aa6ec17529228bba4c69b117dc8

This device has been removed from Edge Testnet.

This command can be used non-interactively by providing all options upfront. Run edge device remove --help for more information on options.

It is possible to improperly remove a device from the network: by destroying Docker data (containing the device's identity), or through hardware failure that renders the device unusable. This does not render the stake irrecoverable. You can assign the stake to another device by running edge device add there and selecting the same stake again, overwriting the device assignment.

About Edge

Some commands are purely informational and do not affect your device or wallet in any way.

Community Links

edge community

This command displays links to Edge communities and publications.

Proposal Guidelines

Governance proposals are actively encouraged and are open for anyone with a governance stake. There is a standard format for proposals that should be followed, which is described here.

Proposal Structure

The structure of a proposal is simple, and consists of Title and Proposal detail. These are separate input boxes on the Draft Proposal screen.

The Title maps to an H1 tag in HTML.

The Proposal detail is markdown formatted. Headings within this section should be H2, H3 etc. (i.e. not H1, as this is used for the title.) A markdown code reference can be seen below.

Proposals must be at least 500 characters (between 70 and 125 words with spaces included). This threshold is set to ensure that a minimum level of clarity is provided. This threshold is enforced, and you won't be able to advance to preview your proposal until the minimum requirement is met.

Note: proposals are submitted to the XE Blockchain and are permanent. Once submitted they cannot be changed

Proposal Detail

The structure of the proposal detail should match the following structure:

Summary
Proposal detail
Rationale

The Summary should provide a general introduction/overview to your proposal in a sentence or two (and no more than two paragraphs).

The Proposal detail should set out the detail of your proposal, and contain specific details about what the proposal would do and achieve if implemented. At the end of the proposal detail you should set out the key points as a summarised bullet list, as follows:

It is proposed that:

Item 1
Item 2
Item 3
...

The Rationale should lay out the reasons for, and benefits of, your proposal.

Real World Example

A good example of this structure can be found here:

Markdown Reference

The following reference covers the markdown styling that is supported in the governance system. This is a subset of the markdown reference. The system will remove items such as images and inline HTML to help to keep goverance clean and spam free.

Headers

## H2
### H3

H2

H3

Emphasis

Emphasis, aka italics, with *asterisks* or _underscores_.

Strong emphasis, aka bold, with **asterisks** or __underscores__.

Combined emphasis with **asterisks and _underscores_**.

Emphasis, aka italics, with asterisks or underscores.

Strong emphasis, aka bold, with asterisks or underscores.

Combined emphasis with asterisks and underscores.

Lists

1. First ordered list item
2. Another item
    1. Ordered sub-list
    2. Another item
3. Actual numbers don't matter, just that it's a number
4. Ordered sub-list
    - Unordered sub-list
    - Another item
5. And another item

First ordered list item
Another item
1. Ordered sub-list
2. Another item
Actual numbers don't matter, just that it's a number
Ordered sub-list
- Unordered sub-list
- Another item
And another item

Links

Note that links are automatically extracted into a references section at the end of the proposal.

[I'm an inline-style link](https://www.google.com)

[I'm a relative reference to a repository file](../blob/master/LICENSE)

I'm an inline-style link[1]

I'm a relative reference to a repository file[2]

References

https://www.google.com
../blob/master/LICENSE

Code and Syntax Highlighting

Inline `code` has `back-ticks around` it.

Inline code has back-ticks around it.

```
var s = "Here's an extended code block";
alert(s);
```

var s = "Here's an extended code block";
alert(s);

Blockquotes

> Blockquotes are very handy in email to emulate reply text.
> This line is part of the same quote.

Quote break.

> This is a very long line that will still be quoted properly when it wraps. Oh boy let's keep writing to make sure this is long enough to actually wrap for everyone. Oh, you can *put* **Markdown** into a blockquote.

This is a very long line that will still be quoted properly when it wraps. Oh boy let's keep writing to make sure this is long enough to actually wrap for everyone. Oh, you can put Markdown into a blockquote.

Quote break.

Blockquotes are very handy in email to emulate reply text. This line is part of the same quote.

Horizontal Rule

Three or more...

---

Hyphens

***

Asterisks

___

Underscores

Note: Gitbook doesnt support horizontal rules in macdown, so a preview isn't available

Line Breaks

Here's a line for us to start with.

This line is separated from the one above by two newlines, so it will be a *separate paragraph*.

This line is also a separate paragraph, but...
This line is only separated by a single newline, so it's a separate line in the *same paragraph*.

Here's a line for us to start with.

This line is separated from the one above by two newlines, so it will be a separate paragraph.

This line is also begins a separate paragraph, but... This line is only separated by a single newline, so it's a separate line in the same paragraph.

Network Nodes

An Edge node is a computing device that is connected to the Edge Network in order to contribute its spare capacity.

Node Types

There are three key node types in the network:

Host

Hosts provide the processing and storage capacity in the network. Designed for mixed device types with varying capability, Hosts can be run behind a home router without the need for router configuration.

Minimum specification

Standard bandwidth: 15 Mbit/s+
Low availability: 20%+
CPU: 1x quad-core 1.2 GHZ+
RAM: 1GB RAM+
Disk: 50GB HDD+

Minimum device specification requirements are subject to change

Gateway

Gateways are the entry point to the network, acting as an aggregate point for Host node capacity. They manage job queues and deliver job requests to Hosts on the basis of a rolling Host score, preferencing the Host nodes most likely to quickly perform a certain task at any given moment in time.

They are high-connectivity devices.

Minimum specification

Medium bandwidth: 250 Mbit/s+
High availability: 99%
CPU: 1x quad-core+ @ 2.5GHz+
RAM: 64GB RAM+
Disk: 1TB SSD+

Stargate

Stargates are the masternodes in the Edge Network. They run the $XE blockchain and provide the domain name system that makes Gateway/Host resources addressable. They are responsible for the secure running of the network. They monitor resources and control device yields.

Stargates are intended for high-connectivity environments: think data centers and high bandwidth office environments, and are designed to be single, powerful machines rather than a cluster of smaller, less powerful machines.

Minimum specification

High bandwidth: 1 Gbit/s+
High availability: 99.9999%
CPU: 2x quad-core+ @ 2.80GHz+
RAM: 128GB RAM+
Disk: 2TB SSD+

Network Backbone

The core team at Edge manage a series of nodes in order to ensure and front run capacity requirements in the network. The backbone is housed with data centre partners all over the world and includes Stargates, Gateways and Hosts.

Backbone Rentals

Nodes in the network backbone are made available for staking to members of the community. This gives access to nodes without the requirement for providing hardware and connectivity yourself.

Stake levels are the same as if you were running a node yourself, but the nodes yield is split between the staker and the dev fund, with 75% going to the stake provider and 25% going towards future network development.

Yield distribution figures are subject to change

A Brief History

Edge is the infrastructure of Web3. A peer-to-peer network and blockchain providing high performance decentralised web services, powered by the spare capacity all around us.

Edge was founded in 2013 as a decentralised alternative to the cloud. Originally called DADI, which stood for "Decentralised Architecture for a Democratic Internet", the company was renamed Edge in July 2019, taking the name of the network at the heart of the project to better reflect the evolution of the technology and its mission.

A crowdsale was held in 2018 to raise funds for the delivery of the core network. Set against a five year roadmap, the crowdsale distributed $EDGE tokens to supporters and future customers.

Edge's testnet - running on the domain test.network - was launched in January 2018. The first release of the mainnet was in May 2018. The first products built on top of the Edge Protocol are DNS, Content Delivery and Edge Servers, all of which are live and in production.

In 2019 Edge was recognised as the “Best Edge Computing Platform” in the Future Digital Awards.

In 2021 the blockchain in the network used for the tracking of network requests was extended to become a mechanism for value transfer. This introduced $XE, a coin used for value attribution within the network. the XE Blockchain is a layer 1 solution that bridges in to other networks. $XE is used for the payment of services; for network staking; for the distribution of node yields; and for community governance. It is currently bridged to the $EDGE ERC-20 token within the Etheruem network.

In 2022 the first fully anonymous computing platform was launched. Edge's account system using a private key for security, giving direct access to Edge Servers, Edge DNS and Edge CDN.

The project roadmaps for Edge capture the near to mid term development priorities, focused on the core network layer as well as individual services on top of the network (such as Object Storage, Edge Functions and Edge DB).

Edge Network Technologies Limited is a not-for-profit company limited by guarantee. Registered in the United Kingdom this company operates under instruction from the Edge DAO.

Mission & Vision

To Uphold the Founding Principles of the Web

The Internet was conceived as a global, democratic communication network - a mesh of computers where information and power were equally distributed. This principle is under attack from all sides. Companies like Google, Amazon and Microsoft are centralising control, while powerful lobbying groups are working to undermine net neutrality. We are facing a future where you are the customer – and the product – of a network controlled by only a handful of global corporations.

We want to reverse this relationship – to give the ownership of the network to everyone that is connected to it, and to make them the beneficiaries of the revenue that comes from its use.

The Edge Network as the Standard for the Decentralised Web

A network of millions of nodes, directly addressable and usable by anyone. A governance system free from individual or multinational control, organised by a Decentralised Autonomous Organisation.

Content Delivery

Edge Content Delivery is the world’s first CDN running exclusively on the edge. It's kinder to the environment and better for business.

Available now

Edge’s architecture creates a hyper-local peering system that routes traffic from nodes that are as close to the end consumer as possible – going as far as delivering within the local network loop.

This reduces the distance and volume of data being moved, which massively increases the performance of services.

Features

Hyper local

Edge CDN has hundreds of nodes in over 80 countries, getting your content closer to your audience than ever before.

Integrated Image Transformation

Edge Content Delivery includes a media pipeline that allows for just in time image manipulation: Blur, filter, flip, format, resize, rotate, saturate, sharpen and crop. This offsets the weight of media management to your delivery solution.

Real Time Optimisation

Real time compression and resizing of assets at the point of request saves an average of 60% in filesize, speeding up delivery, reducing your overall costs and increasing conversion.

End to End TLS

Take workload off your origin by serving SSL certificates directly at the edge, accelerating performance and increasing availability.

Cost Effective

Edge CDN saves 20%+ on average vs. traditional CDNs as a result of better media compression and the use of edge devices instead of centralised data centres.

Documentation

Documentation can be found here: edge.network/en/content-delivery/documentation

IRL

Edge content delivery can be seen running on Monocle.com, where it handles all media and asset delivery.

Checking the headers from an image call returns the cache state for the asset in the network, as well as the device IDs of the nodes involved in its delivery.

Live Example

Image

https://img.monocle.com/book-of-italy-chooser5-6058b1e-6059ca40f12b2.jpg?g=center&q=50&dpr=2

Headers Returned

HTTP/1.0 200 OK =>
Access-Control-Allow-Origin => *
Cache-Control => public, max-age=86400
Cdn-Version => 0.0.9
Content-Length => 180462
Content-Type => image/jpeg
Date => Tue, 23 Mar 2021 12:48:14 GMT
Edge-Device => deb70d83-ca59-4345-adbc-da1ae06e76ca
Edge-Gateway => fb7fe194-9b46-4bcc-b7ae-e813dbc4d278
Edge-Host => c41babfe-c9dd-43cb-aa1b-a5b31dc4d953
Etag => "180462-b12ba916f5f133e321ee67706cb8ba29f1014f4adf0b90a0a234d2cbe4b60022"
Strict-Transport-Security => max-age=10886400; includeSubDomains
Vary => Accept-Encoding
X-Cache => HIT
X-Cache-Origin => request
X-Cache-Type => mem

Launch Edge CDN Now

The Edge Network

The Edge Network is a computing platform that runs in the spare capacity found all around us. It's the cloud, decentralised.

What is Edge Networking?

Edge networking is a distributed computing paradigm which brings data storage and computation as close to the point of need as possible, pushing applications, data and computing power away from centralised data centres.

This reduces the volumes of data that must be moved, the consequent traffic, and the distance the data must travel, providing lower latency and reduced transmission costs.

The Edge Ledger

The Edge (XE) Blockchain is a original chain, designed and built entirely by the core team

The blockchain at the heart of the network records device usage and value attribution. It uses an internal coin called $XE, run on the XE Blockchain, which is a layer 1 solution that provides fast transfers within the network that are fee free for value attribution. $XE includes bridging functionality that allows the coin to be bridged in to other networks. In this way $XE can be converted to $EDGE on the Ethereum network.

The genesis transaction for the XE Blockchain is imprinted with the project's mission: The Internet Belongs to Everyone

Network Architecture

The network's novel architecture has multiple node types that enable the connectivity of devices in multifarious network settings.

The Local Global Network

Edge comprises hundreds of nodes contributed by individuals and businesses around the world. It is designed to provide hyper-local processing and storage capacity for networked applications, enabling digital services that are more performant than ever before.

Edge's technology harnesses the spare capacity that exists in the devices all around us. Take for example set top boxes, which are turned on 24/7, but only in use for an average of a few hours every day. In isolation a set top box doesn’t provide that much power, but when you knit the 35 million devices installed in homes in the UK it becomes an incredibly powerful resource.

BGP Routing

The Edge network utilizes BGP (Border Gateway Protocol) operating within network masternodes to inform top level routing decisions in the network. BGP is the protocol that makes the Internet work. It does this by enabling data routing on the Internet by looking at all of the available paths that data could take from point to point, and picking the best route.

Internal Network Routing

Edge is network aware, and capable of routing within local networks to minimise the hops involved in any given request.

If you are a network owner or have a significant hardware estate, you can offset the cost of network services by contributing to the network. In addition, by enabling delivery within your own network, you can reduce north-south transport, effectively converting it to east-west transport between devices and end users within your own estate.

Security

Denial of Service attacks continue to escalate in scope, becoming ever more distributed, with growing volumes of traffic. Attacks increase your cost and impact your revenues, customer experience and brand.

Edge’s layered approach to security effectively defends against DDoS attacks, preventing disruption to your core services, and keeping your apps online

Additional Reading

These links are designed to enable you to delve deeper in to the Edge network:

Network Coverage: edge.network/en/global-reach
Security: edge.network/en/security
Monitoring: edge.network/en/monitoring
DDoS Protection: edge.network/en/ddos-protection

Technology deep dives from the core team:

Finding a Stargate: ed.ge/knowledge/finding-a-stargate
edge-cli: Connectivity check: ed.ge/knowledge/edge-cli-connectivity-check
Gateway Bi-Directional Streaming: ed.ge/knowledge/gateway-bi-directional-streaming
Edge SSL: ed.ge/knowledge/edge-ssl
An Introduction to Telemetry: ed.ge/knowledge/an-introduction-to-telemetry
Finite State Machine: ed.ge/knowledge/finite-state-machine
Edge Storage Deep Dive: ed.ge/knowledge/edge-storage-deep-dive
Scaling the Edge: ed.ge/knowledge/scaling-the-edge
Managing Stakes with Edge CLI: ed.ge/knowledge/managing-stakes-with-edge-cli

Top level concepts and vision:

A Fairer Internet: ed.ge/knowledge/a-fairer-internet
The Local, Global Network: ed.ge/knowledge/the-local-global-network
The Network Under Your Nose: ed.ge/knowledge/the-network-under-your-nose
The Cloud Is Not Enough: ed.ge/knowledge/the-cloud-is-not-enough
Hidden in Plain Sight: ed.ge/knowledge/hidden-in-plain-sight
The Network That Works for You: ed.ge/knowledge/the-network-that-works-for-you
Cleaning Up the Cloud: ed.ge/knowledge/cleaning-up-the-cloud
The New Media Platform: ed.ge/knowledge/the-new-media-platform

Setting up a Host

Onboarding is now open for Host nodes on the Edge network, with support for:

Linux based x64/arm64 devices
MacOS x64/arm64 devices
Windows x64/arm64 devices

Minimum Specifications

To see the minimum required device specifications, please take a look at Network Nodes.

Devices with higher performance/capacity will return a higher yield

Installation Process

The process of onboarding a host has been designed to be as straightforward as possible.

The process is as follows:

Install Docker (vs. 18.06+)
Install Edge CLI (edge)
Create/restore a wallet
Create a stake
Assign the device
Start node

Prefer a visual guide? Check out the tutorial by community member Pod.

Install Edge CLI

Browse Edge Network Files to find the right build of CLI for your system, and download it to an executable path.

Note that there are separate builds for mainnet and testnet so make sure you download the right one for your purposes.

For example, to download the mainnet CLI on an Ubuntu x64 host:

curl -s https://files.edge.network/cli/mainnet/linux/x64/latest/edge -o /usr/local/bin/edge && chmod +x /usr/local/bin/edge

In the same path as the file you downloaded, you can find a checksum file which you can compare against to ensure your download was not corrupted. If you downloaded the latest Linux x64 build (as above), you would find its checksum here.

sha256 $(which edge)

You only need to manually download Edge CLI once. Afterwards, you can use edge update to automatically update the CLI, including checksum validation.

When you download an Edge CLI binary, it's recommended to keep the original filename i.e. edge for mainnet and edgetest for testnet to help distinguish them on your own system.

Create/Restore Wallet

Now you have Edge CLI installed, you need to set up an XE wallet for it to use. If you already have an existing wallet then you can restore that using your private key, alternatively, you can create a new wallet.

Create a wallet

If you do not already have an XE wallet, CLI can create one for you. Run this command for an interactive setup:

edge wallet create

You will be asked to set a passphrase. This will be used to encrypt your new wallet. The setup will also offer you a copy of your private key so you can back it up securely.

Restore a wallet

If you already have an XE wallet and have the private key in hand, run this command to restore it for CLI to use:

edge wallet restore

You will be asked to provide your private key and a passphrase. The private key will be used to restore your wallet, and the passphrase will encrypt it.

Create Stake

If you do not already have funds in your XE wallet, you will need to get acquire some before you can stake.

Funding your wallet

On the Testnet (XE) Explorer you can use the XE Automated Faucet to request funds.

On Mainnet, you will need to deposit EDGE to receive XE. This can be done via the Web Wallet.

Creating a stake

Now that you have funds, you can choose which type of stake to create. A stake allows network nodes to authenticate with the network, and can be one of the following three types:

Host (host)
Gateway (gateway)
Stargate (stargate)

Only Host onboarding is currently available to the community. More information about onboarding Gateway/Stargate nodes will be provided in future.

Run the following command to create a Host stake:

edge stake create host

This will advise of the stake amount required and your remaining available balance after creating the stake. You will need your passphrase in order to decrypt your wallet and sign the staking transaction.

Once the stake is created, you will need to wait a few moments until it is processed by the blockchain. To check the status of your pending transaction, you can run edge tx lsp. To check whether your new stake is available, you can run edge stake ls.

Prepare Device

Now that you have a stake, you can add your device to the network to run a node corresponding to the stake type. Run the following command to set up your device interactively:

edge device add

You will need your passphrase again for this transaction. Once it has been submitted to the blockchain, it'll take around 1-2 minutes before you're ready to start your node.

Run edge tx lsp and/or edge stake ls to check its status.

Start Node

Once the transaction has been confirmed, you're ready to start your node.

Run the following command:

edge device start

This will download and start the node software, which should then run in the background and self-update. Your device is successfully onboarded!

Further Usage

Edge CLI offers a variety of functions for managing your wallet, stakes, transactions, and the device itself. To display information about CLI commands and options, add -h or --help to any command, for example:

edge tx ls -h

Help

If you're struggling or encountering issues, then join our Discord server and let us know in the #onboarding channel and one of the team or a community member will be happy to help.

Apple Silicon M1 Chipsets

If you're using the new Apple Silicon M1 chipsets you may run into an issue running the CLI. These new chips have additional requirements and while we work to fix these issues, you may need to run the following command to unlock the edge binary:

xattr -cr /usr/local/bin/edge

Install Edge CLI

All releases of CLI for mainnet and testnet are available on Edge Network Files. You can browse it to find the suitable release for your system, or find the latest version in the table below:

Network

Arch

Binary

Checksum

Mainnet

Linux

x64

Mainnet

Linux

arm64

Mainnet

Mac OS

x64

Mainnet

Mac OS

arm64

Mainnet

Windows

x64

Mainnet

Windows

arm64

You can install Edge CLI manually by downloading the binary through the browser, or by using curl/wget. After downloading the CLI binary, move it to an executable and writable path and ensure the binary itself is also executable.

For example, to download the mainnet CLI on an Ubuntu x64 host:

curl \
  -s https://files.edge.network/cli/mainnet/linux/x64/latest/edge \
  -o /usr/local/bin/edge && \
chmod +x /usr/local/bin/edge

You can verify your download by comparing its checksum with the one in Edge Network Files:

On Linux, sha256 $(which edge)
On Mac OS, shasum -a 256 $(which edge)

Once Edge CLI is installed, run edge --version to check it is usable. If the Edge CLI version is displayed without error, it's ready to use:

% edge --version
Edge CLI v1.5.3 (Mainnet)

When you download an Edge CLI binary, it's recommended to keep the original filename i.e. edge for mainnet and edgetest for testnet. This naming helps to distinguish them on your device.

On Mac OS, downloading the Edge CLI through a browser may cause difficulty running it due to Mac OS' security model, resulting in the message, _"edge" is damaged and can't be opened. If you encounter this problem, delete the downloaded binary and use curl to redownload Edge CLI, and it should work then.

Updating Edge CLI

After Edge CLI is installed, you can run edge update (or edgetest update) to update it in-place when a new version becomes available. This method also validates the checksum automatically, ensuring the update is successful and secure.

In order to ensure stability on your device, Edge CLI does not self-update in the background. It's recommended to check for updates periodically to ensure your CLI is up to date. You can check for a new version without updating Edge CLI by running edge update check. Edge CLI will also automatically check for updates in normal use.

If for whatever reason you are unable to self-update Edge CLI, or you need to change to a specific version, you can download it again from Edge Network Files following the same steps you used for the original installation.

Next Steps

Now that Edge CLI is installed on your device, you can contribute to the network by setting up a Host. For more information about CLI usage, have a look at the Commands Overview.

Careers

To attract the best people we have to be flexible – and trust our people to work however suits them.We think it makes Edge a pretty special place to work.

Join the Core Team

Philosophy

"We don't do 'hack' or 'innovation' days because everyday, engineers get to personally innovate. We don't piggy-back off old technology or patch and hack our way to delivering something we aren't proud of. We research and experiment with bleeding edge technologies and collaborate to build out the perfect set of platform services. We peer review and share vital engineering knowledge, encouraging each other to step up and embrace the most challenging of technical tasks.
"All of those things are awesome." – Arthur Mingard, Edge Core Team

Principles

Parkinson's Law states that work expands to fill the time allotted for it. No matter the size of the task, it will often take precisely the amount of time you set aside to do it, because more time means more deliberation & procrastination.

We hold this to be true and actively work to counteract it. The core team at Edge is deliberately small and fast moving, allowing a high level of flexibility, ensuring that the project retains the ability to pivot as stakeholder requirements evolve.

Work Asynchronously

Individual team members more or less works at their own pace, with collaboration and agreement being handled by asynchronous mechanisms.

No 9 to 5

Get the job done on time (and don't upset the client) and you can work the hours you want.

Work at Your Own Pace

We handle things like collaboration and sign off through the best tools for the job, all in support of asynchronous working.

Minimal Meetings

Unless we really need to powwow in person, we keep in touch using cloud-based tools like Slack (much more efficient, believe us).

Work Where You Want

Yes, be diligent, stick to deadlines and do great work. But where and how you do it is up to you.

Perks

A job that works around your life (not the other way round)
Work with some of the most talented people in the world
No need to commute
No need to be tied to a desk
Plenty of excuses to meet up with the rest of the team
Work on things you'll love
Get paid for giving a shit

Tokens

What Is the Difference Between $XE and $EDGE?

$XE is the internal coin of the Edge Network. It is used for attribution of value to nodes, for staking and for network governance. It provides for fast, free transactions.

$EDGE is a utility token on the Ethereum network. It is available for trading and exchange.

You can convert $XE to $EDGE and vice versa using the Edge Network Bridge.

What Is the Relationship Between $XE and $EDGE?

$XE and $EDGE are of equal value. The 1:1 relationship is because the coin and the token perform different functions in the network, with $XE as a layer 2 solution designed to facilitate fast and free transactions within the network. $XE is bridged out to Ethereum, a process that converts the $XE to $EDGE.

Why Is the Network Coin Named XE?

The X is from the ISO standard for currencies that are not specific to a certain country. It has been used because Edge sees it's coin as the standard unit of account for edge computing. X-Edge, hence XE.

Where Can I Get Hold of the Network Token?

What Is the Contract Address for $EDGE?

0x4ec1b60b96193a64acae44778e51f7bff2007831

When Will the $XE<>$EDGE Bridge Open?

The XE Bridge is open! It opened on Thursday September 09th, 2021 at 5pm UTC. More information can be found in the weekly core team updates.

Why is my withdrawal taking so long?

If the transaction speed fee you provided is lower than current gas costs, the bridge will wait until gas fees are low enough to process the transaction within the threshold you set. In this circumstance the time depends on the costs in the Ethereum network.

How are Gas Fees Paid in the Network Bridge?

When you withdraw $XE through the Bridge, gas is paid in XE. When you deposit $EDGE to the Network, gas is paid in Eth via your Metamask wallet.

Why Is the Holder Number Shown in DEXTools Relatively Low?

$XE is a layer 2 blockchain that bridges between chains. This means that there are more holders of the coin $XE within the network that there are holders of the token $EDGE outside of the network. The ratio is currently around 5x the number shown in DEXTools and other Ethereum explorers.

Set up a Host

The process of onboarding a Host is designed to be as straightforward as possible.

Prerequisites

Ensure your device meets the minimum specification (see Network Nodes)
Install Edge CLI
Install Docker (v18.06+ required)

Devices with higher performance/capacity will return a higher yield.

Process

Once the prerequisites are satisfied, the process to set up a host is as follows:

Create/restore a wallet
Create a stake
Assign the device to the stake
Start the node

The instructions below refer to the edge mainnet CLI. If you are using the edgetest testnet CLI, simply substitute edgetest as appropriate.

Create/restore a Wallet

An XE wallet is required to participate in the network. This will hold your staked funds and earnings. An XE wallet consists of an XE address (which looks like xe_abcd...) and a private key.

Edge CLI allows you to use an existing wallet, or can create one for you if you need one.

Create a wallet

Run the following command for interactive setup:

edge wallet create

You will be asked to set a passphrase. This will be used to encrypt your new wallet. The setup will also offer you a copy of your private key so you can back it up securely.

Restore a wallet

If you have an XE wallet already, for instance from the web wallet, you can restore it with your private key using the following command:

edge wallet restore

You will be asked to provide your private key and a passphrase. The private key will be used to restore your wallet data, and the passphrase will encrypt it.

Create Stake

If you do not already have funds in your XE wallet, you will need to get acquire some before you can stake.

Funding your wallet

On the Testnet (XE) Explorer you can use the XE Automated Faucet to request funds.

On Mainnet, you will need to deposit EDGE to receive XE. This can be done via the Web Wallet.

Creating a stake

Now that you have funds, you can choose which type of stake to create. A stake allows network nodes to authenticate with the network, and can be one of the following three types:

Host (host)
Gateway (gateway)
Stargate (stargate)

Only Host onboarding is currently available to the community. More information about onboarding Gateway/Stargate nodes will be provided in future.

Run the following command to create a Host stake:

edge stake create host

Prepare Device

Now that you have a stake, you can add your device to the network to run a node corresponding to the stake type. Run the following command to set up your device interactively:

edge device add

You will need your passphrase again for this transaction. Once it has been submitted to the blockchain, it'll take around 1-2 minutes before you're ready to start your node.

Run edge tx lsp and/or edge stake ls to check its status.

Start Node

Once the transaction has been confirmed, you're ready to start your node.

Run the following command:

edge device start

This will download and start the node software, which should then run in the background and self-update. Your device is successfully onboarded!

Further Usage

Edge CLI offers a variety of functions for managing your wallet, stakes, transactions, and the device itself. Have a look at the Commands Overview for more information.

Help

If you're struggling or encountering issues, then join our Discord server and let us know in the #onboarding channel and one of the team or a community member will be happy to help.

Apple Silicon M1 Chipsets

xattr -cr /usr/local/bin/edge

Nodes

What Is an Edge Node?

An Edge node is a computing device that is connected to the Edge Network in order to contribute its spare capacity. Edge nodes earn $XE coins in return for this, and these can be used to purchase services from the network, or they can be swapped for $EDGE tokens, which can be traded.

Who Can Run an Edge Node?

At the moment the software for running an Edge node is only available for Linux. However versions are being made available for Windows, OSX and mobile devices.

What Is a Stargate?

Stargates are Edge masternodes. They are responsible for the routing and security in the network, for monitoring resources and for controlling the payout contract.

What Is a Gateway?

Gateways are Edge masternodes. They are responsible for connectivity in the network and act as the entry points for end user requests.

What Is a Host?

Hosts are Edge nodes responsible for the provision of computational power and storage within the network.

Is Edge Proof of Work or Proof of Stake?

Edge operates a hybrid model of proof of stake and proof of work. Proof of stake is used to help to secure the network, with a stake required to operate a node. Proof of work is used to distribute yield based on the jobs that nodes successfully complete in the network.

Do we need to manually update our Edge hosts or do they upgrade automatically?

When a new version goes out, all nodes receive a notification and automagically update, and if a node is offline, upon connecting to the network, it'll receive a message that it needs to update, which it will then do. Should something happen and your node not appear to be updating, it can be manually updated by running edge device update.

I have an old stake, how do I transfer it to my XE wallet?

If you have a legacy stake, you need to fill in the stake transfer request form, which you can find here: https://ed.ge/stake-migration-request. After that, you'll receive an email from the team confirming the request, or asking for more information, and once your request has been verified, you'll have a stake transferred to your XE wallet. Be sure to include as much information as you can.

Can I lose my stake if I make a mistake during device setup?

Simply put, no. You're not at risk of losing your stake while setting up a node. When you create a stake, you're locking a portion of XE but that stake, that portion of XE, remains in your wallet. When you assign a device to a stake, it is simply updating the stake with the assigned device ID. The only things that you can do to a stake are unlocking them and releasing them, and the XE within a stake will always be returned to the wallet in which they live.

Do I have to run my Host node 24/7?

Not at all. If you can contribute a device 24/7 then it'll be able to handle more jobs and therefore will earn more, but it isn't a requirement. If your machine with spare capacity is only available sometimes, for example during the day, that's fine too. There are no uptime requirements for Hosts and the network is designed to allow Hosts to join as they become available and leave as they become unavailable.

Once a stake has been migrated, how do I assign it to a Host?

Migrated stakes are actually no different from regular stakes, so once you have your stake, you can use it just like you would a regular stake you created with the CLI. To assign a host, it's simply a case of running edge device add and following the instructions.