Tokyo Pre-Release

Tokyo release

• Chainbridge module addition
• Assets pallet updates
• Frontier EVM integration
• Faster governance times (1 week round-trip: 2 day launch period, 4 day voting, 1 day enactment)
• New testers for upgrades + frontier
• New CI with caching
• Removed Signaling and Voting modules
• Prometheus + Grafana dashboard script for anyone to use.

New York

New York v3.1.0 Edgeware Release

This release culminates a node and runtime update to Substrate 2.0! This release is not necessary to run the runtime upgrade that will follow as we have reached some stability regarding runtime upgrades. It is always recommended to node operators that they run the latest release software.

Runtime Upgrade

This runtime update includes amongst other things:

• The assets pallet
• Ink! 3.0 compatible contracting system
• Identity migration to recover all lost identities from 1st upgrade
• Bounty system for the Treasury

Summary:
  Generator  : srtool v0.9.5
  GIT commit : 7512597db423d93ac17a4499e82d2a14ecd5ab76
  GIT tag    : v3.1.0
  GIT branch : master
  Time       : 2020-10-07T19:29:35Z
  Rustc      : rustc 1.47.0-nightly (d7f945163 2020-07-19)
  Size       : 2273 KB (2328302 bytes)
  Content    : 0x0061736d0100000001d4033d60037f7f...3531363320323032302d30372d313929
  Package    : edgeware-runtime
  Proposal   : 0x249623e9ec28e752a0ce6355f7d5527956799a50e28228958497f3a9bcc0bd1f
  SHA256     : 7aa3dcf12618310075070c0983dd67c565f69f6488e803cfea712f80cb4a062c
  Wasm       : ./target/srtool/release/wbuild/edgeware-runtime/edgeware_runtime.compact.wasm

Naples

Naples v3.0.8 Edgeware Release

The Naples release targets the 1st mainnet upgrade both in terms of runtime and client functionality. It is expected that all node operators upgrade to this version on the mainnet, prior to the upgrade, in order to not be slashed.

Node configuration

A common note that has been mentioned in community channels is with regards to syncing and producing blocks on mainnet with these nodes. Currently, all validators running these nodes are working very well, much better than earlier versions. We still recommend the --wasm-execution Compiled setting below in addition to other settings you may have your nodes on.

edgeware --chain=edgeware --wasm-execution Compiled

If peer discovery seems to be lagging, consider running with the following configuration

edgeware --chain=edgeware --legacy-network-protocol

Once the network is fully up-to-date on these nodes, you should remove the legacy protocol flag.

Parameter updates

Below are notable values of the runtime that have changed.

• 1 hour sessions
• 6 hour eras
• 2 week bonding duration
• 1 week slash deferral
• 128 max nominators rewarded
• 3/4 of council to cancel slashes
• ExternalMajorityOrigin 60%
• FastTrackOrigin 75%
• CancellationOrigin 66%
• 2 week council motion duration
• Treasury ApproveOrigin 60%
• Treasury RejectOrigin 50%

Beresheet (testnet release)

This release is for the new Beresheet testnet that replaces the Berlin testnet! It features roughly the same exactly runtime the the future Edgeware mainnet will follow. We started this network with the same runtime as the current mainnet and recently upgraded it with a similar runtime upgrade that is planned for the mainnet launch! The only difference is that the session length on this network is very fast 1 minute long!

Bergmannkiez (v3.0.5-testnet)

This is a node release for the Berlin Testnet that pegs to the first runtime upgrade. The runtime upgrade was pushed a couple weeks ago and has been running smoothly. There are some logging issues with this node though they don't seem to manifest in any mission-critical bugs. Currently, these nodes are running smoothly on Berlin.

A summary of things fixed and added:

1. Timestamp arithmetic issues are gone.
2. Memory leak issues facing v3.0.1 nodes are gone.
3. Chainspecs are directly accessible in the binary now as proposed from: #156
4. GRANDPA service worker prevents forced authority set changes as well as in runtime.

I recommend running this version on Berlin, not the mainnet yet unless you accept the risk. There is still more testing and probably at least another node update required to make things nicer on mainnet. It is likely this node will run smoothly once the upgrade is pushed to the mainnet as well.

If you're interested in helping out with core dev/devops on Edgeware and interested to join my working group. Please feel free to reach out on https://commonwealth.im/edgeware or reach me at email [email protected].

Edgeware Mainnet

This is to fix a mixup that happened on the previous renaming of the original v1.0.1 node.

Ok, the fixes have been fixed. Please clear your state if you had run a previous version of the mainnet so that you won't have any trouble once the chain starts. There is a new genesis spec so all things considered this is a clean start.

As always, if not building from source, you'll need absolute paths to the chainspecs

./edgeware --chain /path/to/some.chainspec.json --name <NAME>

Edgeware Berlin Testnet

Updated bootnodes for mainnet launch as well as config files for Berlin testnet.

To run from binary you must provide the absolute paths to the binary and chainspecs as follows:

/path/to/edgeware --chain /path/to/chainspec.json

סוף testnet v099

v0.9.9

Connect to newest testnet README update

v0.9 Erdős

Overview

Corrected balances issue, CPU stall issue, and slashing issue.

Successful in-flight runtime upgrade from 0.9.0 to 0.9.1 and 0.9.2. Also passed other tests.

• v0.9.0: Balance transfers off, slashing off.
• v0.9.1: Balance transfers on, slashing off.
• v0.9.2: Balance transfers on, slashing on.

Usage

Run ./setup.sh
Run ./target/release/edgeware --chain=chains/edgeware-0.9.0.json --name {INSERT_NAME}

v0.5.0 Prayin

Run ./setup.sh
Run ./target/release/edgeware --chain=edgeware --name {INSERT_NAME}