* update substrate

* Hopefully fix compilation

* network: rename roles to role

* runtime: fix runtime-benchmarks compilation

Co-authored-by: Pierre Krieger <[email protected]>

* ci: kusama-nightly-staging: remove builds for the branches and trigger deployment directly

* ci: kusama-nightly-staging: remove ii and fix

* Companion PR to splitting Roles

* Fix network tests

* Fix service build

* Even more fixing

* Oops, quick fix

* use is_network_authority in grandpa service config

Co-authored-by: André Silva <[email protected]>

Before the validator only send the keys if it was updated and thus the
collators would "never" be informed about the key of the validator.

* Don't depend directly on libp2p

* Fix bad import

* add dummy parachains.toml

* flesh out parachains.toml

* finish phase-1 rendering

* render to svg instead

* put graphviz svg through sanitizer so github can render

* return to PNG

* Fixes for democracy using Scheduler

* Revert branch change

* Emojis

Up to now consensus instances used the main channel to communicate with
the background network worker. This lead to a race condition when
sending a local collation and dropping the router before driving the
send local collation future until it is finished. This pr changes the
communication between worker and the instances to use their own
channels. This has the advantage that we don't need an extra
`DropConsensusNetworking` message as the network is dropped
automatically when the last sender is dropped.

Updating the heads was accidentally removed in some other pr.

* Fixes for democracy using Scheduler

* Revert branch change

* Fix council collective genesisi values

* Update Cargo.lock

* Update Cargo.lock

Co-authored-by: Shawn Tabrizi <[email protected]>

* add pov-block gossip message to network

* tests for pov-block gossip

* integrate pov-block gossip into main protocol

* message validation fetches pov blocks

* remove stray dbg! invocation

* test that pov-block is fetched from relay-parent topic

* Use `add_benchmark` macro

* Return error if `batches` is empty

* Update Cargo.lock

* Companion for #5463 (#953)

* Fix test with genesis block 0

* Update Cargo.lock

* Companion pr for substrate#5448

* Update Substrate reference

* Adapt code to API changes

* Update sp-io

* fix for offchain phragmen

* Update unix time stuff

* upgrade substrate

* fix telemetry endpoint

* improve msg

* upsub

* Revert branch change

* Fix some

* Fix build

* Add transaction source.

* Bump substrate.

* Fix tests.

* Adds a SigningContext type

* Bump spec versions

* Fixes requested changes

* Bump ParachainHost api_version and guard signing_context call

* Improve error message

* If there is no signing_context api use default value

Co-authored-by: Robert Habermeier <[email protected]>

* update new on_initialize syntax

* update substrate

* update spec_version

* Parachains double vote handler initial implementation.

* Make tests test the actual slashing.

* Implement SignedExtension validation of double vote reports.

* Fixes build after merge

* Review fixes

* Adds historical session proofs

* Review fixes.

* Bump runtime spec_version

* Get the session number from the proof

* Check that proof matches session

* Change signature type on DoubleVoteReport

* Adds docs and removes blank lines

* Removes leftover code

* Fix build

* Fix build after a merge

* Apply suggestions from code review

Co-Authored-By: Robert Habermeier <[email protected]>

* Prune ParentToSessionIndex

* Remove a clone and a warning

Co-authored-by: Robert Habermeier <[email protected]>
Co-authored-by: Gavin Wood <[email protected]>

* Bump parity-util-mem

* Change util mem version to wildcard

* Updates for the new democracy

* Introduce progressive democracy

Also move to "master" branch of Substrate ready for continuous
sync with Substrate master.

* Add cli to wasm tests, update and bring closer to the substrate browser code

* Remove ws.js

* Update cli/src/browser.rs

Co-Authored-By: Pierre Krieger <[email protected]>

* Update browser.rs

Co-authored-by: Gavin Wood <[email protected]>
Co-authored-by: Pierre Krieger <[email protected]>

Co-authored-by: Gav Wood <[email protected]>

we were getting double-posts for newly-published releases - we don't need to post to the channel when releases are updated.

* Move publish_draft_release to test stage

Also remove the alert_pending_release job since it's no longer needed

* delete alert_pending_release.sh

* Add splitting substrate changes into subsections

* Remove migration code.

* Bump Substrate

* Bump runtime