Hi everyone 👋

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

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

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

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

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

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

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

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

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

For example: xe_08b8083fb37CcBed785b4278B85Cf74aa7719A1E4

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

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

You can see chain synchronisation working here:

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