The Edge Community team compile frequency asked questions and answers. These are published and updated here.
The name Edge refers to the edge of the network. The Internet is made up of millions of discreet networks that are connected together. Devices within these network that are close to the end users of network services are described as being "at the edge".
The Edge Network was first released in 2018, but the technology has been in actvie R&D since 2013.
The Edge Network was originally concieved by Joseph Denne, Will Lebens and Chris Mair. Joseph and Will continue to serve as guarantors for the not for profit and look after day to day operations.
The core team is currently comprised of 12 people. Edge is an all-remote company, and has been since inception. You can read about how we work here:
Yes. You can access it here:
Edge has its own blockchain, developed end-to-end by the core team. The chain is called the XE Blockchain, and the Edge Ledger runs on top of that technology.
Layer 2 is a collective term for solutions designed to help scale your application by handling transactions off of the main Ethereum chain (layer 1). Transaction speed suffers when the network is busy, which slows down processing and also increases the cost of transactions.
$XE currently runs as a layer 2 solution, which enables fast and free transactions within the Edge Network, which are essential to the running of the technology.
The Edge Network is a completely unique technology stack, originated by the core team and developed over many years. It is predominantly written in TypeScript.
Edge's source code is currently partially open source, with plans for going fully open source in motion. You can access projects code repository on GitHub at: github.com/edge
Private keys are needed to sign transactions in the XE Blockchain, so no matter what type of wallet application you are using, the private key has to be available in order to create those cryptographic signatures. The XE Web Wallet stores the private key locally, encrypted using your chosen passphrase. The Web Wallet is a client-side application only (not server-side).
Your private keys never leave your device, and they are only decrypted when a transaction needs to be signed. This is the reason that the wallet asks you for your passphrase every time you send a transaction.
$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.
$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.
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.
0x4ec1b60b96193a64acae44778e51f7bff2007831
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.
Weekly UpdatesIf 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.
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.
$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.
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.
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.
Stargates are Edge masternodes. They are responsible for the routing and security in the network, for monitoring resources and for controlling the payout contract.
Gateways are Edge masternodes. They are responsible for connectivity in the network and act as the entry points for end user requests.
Hosts are Edge nodes responsible for the provision of computational power and storage within the network.
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.
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
.
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.
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.
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.
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.
Edge CDN is available now and can be accessed via the account system.
Edge Object Storage is currently in active R&D. A proof of concept exists and is currently being tested and evolved. A beta release is expected to be reelased for community testing at some point later this year.
Edge Servers are available now and can be accessed via the account system.
Edge DNS is available now and can be accessed via the account system.
Edge's vision and roadmaps are extensive, while resource and time is limited. This means that the core team have to prioritise features and focus. These decisions can be influenced by the community through network governance.
Project GovernanceYes. Edge's primary community is Discord. You can join the Edge server here: ed.ge/discord
Weekly. The latest udpate is always available in the Community Wiki.
📰Project UpdatesAn archive of previous weeks is also available.
Weekly UpdatesYes, from time to time, although these have been less regular since the move to Discord, as the team are active and available to answer questions as they arise.
There is an archive of previous AMAs available in the Edge Community Wiki.
AMA ArchiveOn the Edge Website: edge.network