Skip to content
Snippets Groups Projects
user avatar
gupnik authored
Step in https://github.com/paritytech/polkadot-sdk/issues/3268

This PR adds the ability for these pallets to specify their source of
the block number. This is useful when these pallets are migrated from
the relay chain to a parachain and vice versa.

This change is backwards compatible:
1. If the `BlockNumberProvider` continues to use the system pallet's
block number
2. When a pallet deployed on the relay chain is moved to a parachain,
but still uses the relay chain's block number

However, we would need migrations if the deployed pallets are upgraded
on an existing parachain, and the `BlockNumberProvider` uses the relay
chain block number.

---------

Co-authored-by: default avatarKian Paimani <5588131+kianenigma@users.noreply.github.com>
7c5224cb

Parachains

This directory is the home of Parity-developed parachain runtimes. This directory is runtime focused, and does not include builds of parachain nodes.

The general internal structure is:

  • chain-specs: Chain specs for the runtimes contained in its sibling dir runtimes.
  • common: Common configurations, impls, etc. used by several parachain runtimes.
  • integration-tests: Integration tests to test parachain interactions via XCM.
  • pallets: FRAME pallets that are specific to parachains.
  • runtimes: The entry point for parachain runtimes.

System Parachains

The runtimes directory includes many, but is not limited to, system parachains. Likewise, not all system parachains are in this repo.

Releases

The project maintainers generally try to release a set of parachain runtimes for each Polkadot Relay Chain runtime release.