* canvas: Move contracts config to own file

* Reduce usage of parameter_types where possible

* Fix try-runtime compilation

Before this fix the relay chain node name was always a random generated, because we did not had
implemented all the required methods of the `CliConfiguration` trait.

sync solution from #887

* Added kanvas runtime

* Fix up benchmarking

* Fixup markdown stucture

* replace :emoji_name: by utf8
* fix up header hierarchy

* Merge canvas README

* Only use "Canvas" as a name

* Remove reference to Rocanvas

* Update Cargo.toml

* add checks to ci

* Update rand to v0.8.5

* Enable std_rng feature on rand

* Enable std_rng only when std is enabled

* Revert "Enable std_rng only when std is enabled"

This reverts commit 8fb3b72dbd6dc18bc19868b999b5b07cea4b7392.

* Move XCM configurations out into its own module

* Revert removal of the AccountNonceApi

Co-authored-by: Ignacio Palacios <[email protected]>

Co-authored-by: Ignacio Palacios <[email protected]>

Co-authored-by: Wilfried Kopp <[email protected]>

* chore: fix typos for consensus

* chore: fix typos for RelayChainError

* Return compressed PoV from collation

This enables us to also print the size of the compressed PoV.

* FMT

* Update Polkadot & Substrate

* Fix compilation

* Fixes

* FMT

* Added check to ensure invulnerables have associated validator keys before they are set

* Added check to ensure invulnerables have associated validator keys before they are set

* Update pallets/collator-selection/src/lib.rs

Co-authored-by: Keith Yeung <[email protected]>

* Added test for associated validators when setting invulnerables

* FMT

Co-authored-by: Omadoye Abraham <[email protected]>
Co-authored-by: Ricardo Rius <[email protected]>
Co-authored-by: Keith Yeung <[email protected]>
Co-authored-by: Bastian Köcher <[email protected]>

* add QueueConfigData setter

* update weights

* syntax change

* add test case

* fix Result error

* cargo fmt

* Apply suggestions from code review

Co-authored-by: Alexander Popiak <[email protected]>

* update

* one call per set

* cargo fmt

* cargo fmt

* mutate method

* cargo fmt

Co-authored-by: Alexander Popiak <[email protected]>

ci: fix publish-runtimes for rococo-parachain (or any other -parachain) failing on incorrect wasm path (#957)

* Update command for running benchmarks

* add --locked

Co-authored-by: Chevdor <[email protected]>

Co-authored-by: Chevdor <[email protected]>

Bumps [node-fetch](https://github.com/node-fetch/node-fetch) from 2.6.5 to 2.6.7.
- [Release notes](https://github.com/node-fetch/node-fetch/releases)
- [Commits](https://github.com/node-fetch/node-fetch/compare/v2.6.5...v2.6.7

)

---
updated-dependencies:
- dependency-name: node-fetch
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [node-fetch](https://github.com/node-fetch/node-fetch) from 2.6.1 to 2.6.7.
- [Release notes](https://github.com/node-fetch/node-fetch/releases)
- [Commits](https://github.com/node-fetch/node-fetch/compare/v2.6.1...v2.6.7

)

---
updated-dependencies:
- dependency-name: node-fetch
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Add the ability to suspend or resume XCM execution on the XCMP queue

* Rename QueueActive to QueueSuspended

* Add the ability to suspend the DMP queue

* Rename XCMP to DMP in comments where appropriate

Co-authored-by: Alexander Popiak <[email protected]>

* Add a bypass for XCMP queue suspension

* Revert "Add the ability to suspend the DMP queue"

This reverts commit 363ca09b41e40fce3f2740e7ab78f5c54781ca5c.

* Change controller origin to either root or council-issued origin

* Rename to ControllerOriginConverter

Co-authored-by: Alexander Popiak <[email protected]>

* Add safe_xcm_version to Genesis Specs (#743)

* add safe_xcm_version to genesis specs

* cargo +nightly fmt

* Point to xcm latest version

Co-authored-by: Alexander Popiak <[email protected]>

* Add production profile

* Fix opt-level

* Update Cargo.toml

Co-authored-by: Bastian Köcher <[email protected]>

* Move opt-level to release

Co-authored-by: Bastian Köcher <[email protected]>

* fix: remove duplicate event of pallet_balances

https://github.com/paritytech/substrate/blob/master/frame/support/src/traits/tokens/currency.rs#L158
https://github.com/paritytech/substrate/blob/master/frame/balances/src/lib.rs#L1647

Since 0.9.12 of substrate, there is no need for a separate of balances event in runtime.

* Update impls.rs

* Companion for substrate#10632

Signed-off-by: koushiro <[email protected]>

* cargo update -p clap

Signed-off-by: koushiro <[email protected]>

* Update substrate

* update lockfile for {"polkadot"}

Co-authored-by: Keith Yeung <[email protected]>
Co-authored-by: parity-processbot <>

* Update Substrate & Polkadot

* Hmm

* Set workspace hint path

* Test

* Use absolute path

* Update again

* pov-recovery: Enable pov-recovery as well on full nodes

Pov recovery was before only enabled for collators. The reason behind this was prevention of spam of
the relay chain for block recovery. However, recent events has shown that this wasn't a good idea.
So, this pr enables pov-recover for normal full nodes as well, but with a much higher delay before
trying to recover a block. This means that full nodes will wait in minimum 2.5 minutes and in
maximum 5 minutes before recovering a block. This should give collators in "normal mode" enough time
to recover a block (they wait in maximum 6 seconds after they have seen a new candidate in the relay
chain) before recovering a block. So, we should hopefully not spam the relay chain.

* FMT

* Fixes

* Fix documentation