It also moves some simple scripts directly into the .gitlab.yaml file.

if the PVF pre-checking is disabled the runtime dispatchable will reject
any attempts of submission. This is also concern the unsigned tx
validation.

Right now, the `include_pvf_check_statement` dispatchable is effectively
uncallable because of the weight set to the maximum value. If we were to
benchmark it, it would become includable in a block, but since there
will be no active votes, the dispatchable won't do anything.

However, it will execute some code, like signature validation and
querying some storage entries. To be completely safe, we can bail out
early if the `pvf_checking_enabled` config is disabled. That's what this
PR does.

* Change EraIndex import path: companion #10671

* update lockfile for {"substrate"}

Co-authored-by: parity-processbot <>

* add fast-runtime feature for reduced session times

* make democracy periods fast on fast-runtime

* propagate fast-runtime feature through cargo.toml files

* add fast motion and term durations to Kusama

* Update runtime/westend/Cargo.toml

Co-authored-by: Kian Paimani <[email protected]>

* set session time to 2 minutes to avoid block production issues

* formatting

* update Substrate

* set democracy fast periods back to 1min

* set launch period and enactment period to 1 block in fast-runtime

* remove unnecessary westend period configs

* add prod_or_test macro to allow specifying prod, test and env values for parameter types

* move prod_or_test macro into common module and use it consistently

* rename macro to prod_or_fast

* cargo +nightly fmt

* bump impl_versions

* newline

Co-authored-by: Kian Paimani <[email protected]>

* add note that env variable is evaluated at compile time

* newline

Co-authored-by: Kian Paimani <[email protected]>

* newline

Co-authored-by: Kian Paimani <[email protected]>

* cargo fmt

* impl_version: 0

* impl_version: 0

* use prod_or_fast macro for LeasePeriod and LeaseOffset

* use prod_or_fast macro in WND and ROC constants

Co-authored-by: Kian Paimani <[email protected]>
Co-authored-by: Giles Cope <[email protected]>

In this PR, paras module emit runtime events on certain PVF pre-checking
related conditions.

Specifically, there are 3 new events in the paras module:

1. PvfCheckStarted
2. PvfCheckAccepted
3. PvfCheckRejected

All of those have identifiers for the parachain that triggered the PVF
pre-checking and the validation code that goes through the pre-checking.

The mechanics of those are as follows. Each time a new PVF is added, be
it due to onboarding or upgrading, the `PvfCheckStarted` will be
triggered. If another parachain triggers a pre-checking process for the
validation code which is already being pre-checked, another
`PvfCheckStarted` event will be triggered with the corresponding para
id.

When the PVF pre-checking voting for a PVF was finished, several
`PvfCheckAccepted/Rejected` events will be triggered: one for each para id that
was subscribed to this check (i.e. was a "cause" for it).

If the PVF pre-checking is disabled, then one can still expect these
events to be fired. Since insta PVF approval is syncronous, the
`PvfCheckStarted` will be followed by the `PvfCheckAccepted` with the
same validation code and para id.

If somebody is interested in following validation code changes for a PVF
of a parachain, they would need to subscribe to those events. I did not
supply the topics for the events, since I am not sure if that's needed
or will be used, but they can be added later if needed.

* Check authority status on active leaves update

Signed-off-by: Andrei Sandu <[email protected]>

* cargo changes

Signed-off-by: Andrei Sandu <[email protected]>

* Fix tests

Signed-off-by: Andrei Sandu <[email protected]>

* Add metric for authority status

Signed-off-by: Andrei Sandu <[email protected]>

* Revert "Fix tests"

This reverts commit 5bd56bb367ec0b01ecca04498b3974ab67bf3189.

* Revert "cargo changes"

This reverts commit ffea18fe3ca12b27e6471ad9f44592799ec90956.

* Revert "Check authority status on active leaves update"

This reverts commit 55a30ac81bf32a72e0b79ca2e7bb612344a5c43d.

* Test fixups

Signed-off-by: Andrei Sandu <[email protected]>

* fix

Signed-off-by: Andrei Sandu <[email protected]>

* update

Signed-off-by: Andrei Sandu <[email protected]>

* undo damage

Signed-off-by: Andrei Sandu <[email protected]>

* dont update status on runtime errors

Signed-off-by: Andrei Sandu <[email protected]>

* Fix tests

Signed-off-by: Andrei Sandu <[email protected]>

* fix inconsistency

Signed-off-by: Andrei Sandu <[email protected]>

* Review feedback

Signed-off-by: Andrei Sandu <[email protected]>

* Dont derive primitive Default

Signed-off-by: Andrei Sandu <[email protected]>

* add dummy_session_info helper

Signed-off-by: Andrei Sandu <[email protected]>

* unset parachain validator status if no longer authority

Signed-off-by: Andrei Sandu <[email protected]>

* update

Signed-off-by: Andrei Sandu <[email protected]>

* damn

Signed-off-by: Andrei Sandu <[email protected]>

* 🤦



Signed-off-by: Andrei Sandu <[email protected]>

closes #4611

* cargo: sync workspace members with dependencies

* Remove bridges stuff

* Fix

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

* approval-voting: add more logs

* approval-voting: query finalized block on startup and increase look back

* runtime-api: do not cache None SessionInfo

* approval-voting: add more logs

* approval-voting: query finalized block on startup and increase look back

* Add some docs to prevent a time loop.

* Review remarks.

* fix tests

* update lockfile for substrate

Co-authored-by: parity-processbot <>

the feature was removed in https://github.com/paritytech/parity-processbot/pull/358

* Switch types to use `RuntimeDebug` instead of gated `Debug`

This is useful for when you want to debug in wasm and enable the
`force-debug` feature of `sp-debug-derive`.

* Fixes

* 🤦

* Move XCM runtime configurations into their own files

* Update copyright year

* Fix compilation errors

* Import XCM types in westend runtime unit tests

* CI: remove rococo from CI

* CI: typo

* CI: another typo

Co-authored-by: CI system <>

* Better docs on non initialized state.

* Document better what is happening.

* More precise errors.

* cargo fmt

* Remove sleep and use polkadot test service

Signed-off-by: Andrei Sandu <[email protected]>

* updates

Signed-off-by: Andrei Sandu <[email protected]>

* Fix other tests

Signed-off-by: Andrei Sandu <[email protected]>

* Run metrics tests separately

Signed-off-by: Andrei Sandu <[email protected]>

* copy some substrate utilities

Signed-off-by: Andrei Sandu <[email protected]>

* update runtime metric test

Signed-off-by: Andrei Sandu <[email protected]>

* Remove sleep from cli tests

Signed-off-by: Andrei Sandu <[email protected]>

* cargo

Signed-off-by: Andrei Sandu <[email protected]>

* Polkadot companion for Substrate#10463 (#4519)

* Grandpa and Beefy protocol names include chain id

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

* chain_spec: include fork id

* use simplified protocol name

* fix after merge

* avoid using hash default, even for protocol names

* update lockfile for substrate

Co-authored-by: parity-processbot <>

* configuration: Update upgrade validation delay doc (#4662)

* typo

Signed-off-by: Andrei Sandu <[email protected]>

* review feedback

Signed-off-by: Andrei Sandu <[email protected]>

* cargo lock

Signed-off-by: Andrei Sandu <[email protected]>

* use testnet profile

Signed-off-by: Andrei Sandu <[email protected]>

* Don't run with runtime-benchmark feature

Signed-off-by: Andrei Sandu <[email protected]>

* conditional compile up one level

Signed-off-by: Andrei Sandu <[email protected]>

Co-authored-by: Sergei Shulepov <[email protected]>

* Companion: code-substitute: Switch from `block_hash` to `block_number`

* Update Substrate

Looks like it is an artifact of prior code and now it is redundant.

This commit implements the last major piece of #3211: the subsystem that
tracks PVFs that require voting, issues pre-check requests to
candidate-validation and makes sure that the votes are submitted to the
chain.

* refund the lost deposit of historical nick module

* Fix doc

* add comments etc.

* guard it better

* more log

* fix build

* Fix locked deposit of council voters

* add account ids as comment

Happened on Kusama for some not yet known reason.

* support best Beefy RPC through arc<mutex>

* beefy RPC through lockless message passing - wip

Not working because channel can't be simply opened and receiver passed
to `rpc_extensions_builder` because `rpc_extensions_builder` has to be
`Fn` and not `FnOnce`... and and Receiver side of mpsc can't be cloned

yay!..

* beefy RPC through lockless message passing

* beefy: use specialized type definitions

* bubble up service errors from BEEFY RPC

* update lockfile for substrate

Co-authored-by: parity-processbot <>

* rename malus.Dockerfile

* ci chores

* fix pipeline

* Grandpa and Beefy protocol names include chain id

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

* chain_spec: include fork id

* use simplified protocol name

* fix after merge

* avoid using hash default, even for protocol names

* update lockfile for substrate

Co-authored-by: parity-processbot <>