Skip to content

Commit 0ea64f7

Browse files
authored
docs: update deploy-to-testnet.md to note deprecation of para_id in chain specs (#775)
1 parent 81ab749 commit 0ea64f7

File tree

2 files changed

+18
-0
lines changed

2 files changed

+18
-0
lines changed

llms.txt

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32621,6 +32621,15 @@ To define your chain specification:
3262132621

3262232622
You should now see your chain specification containing SCALE-encoded hex values versus plain text.
3262332623

32624+
32625+
!!!note "Deprecation of `para_id` in Chain Specs"
32626+
32627+
The `para_id` field in JSON chain specifications, added through the [`chain-spec-builder`](https://paritytech.github.io/polkadot-sdk/master/staging_chain_spec_builder/index.html){target=\_blank} command, is currently used by nodes for configuration purposes. However, beginning with Polkadot SDK release `stable2509`, the `para_id` field will no longer be required in chain specifications. Instead, runtimes need to be updated to implement the [`cumulus_primitives_core::GetParachainInfo`](https://paritytech.github.io/polkadot-sdk/master/cumulus_primitives_core/trait.GetParachainInfo.html){target=\_blank} trait to successfully operate with nodes using chain specs that omit the `para_id` field.
32628+
32629+
With the upcoming `stable2512` release, the `para_id` field will be completely removed from chain specifications in favor of the new runtime API. New nodes will be unable to start with chain specs containing the `para_id` field unless the runtime implements the `GetParachainInfo` trait. Ensure your runtime is updated to maintain compatibility with future node versions.
32630+
32631+
For guidance on performing runtime upgrades to implement this new trait, refer to the [runtime upgrade tutorial](/tutorials/polkadot-sdk/parachains/zero-to-hero/runtime-upgrade/){target=\_blank}.
32632+
3262432633
## Export Required Files
3262532634

3262632635
To prepare the parachain collator to be registered on Paseo, follow these steps:

tutorials/polkadot-sdk/parachains/zero-to-hero/deploy-to-testnet.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -148,6 +148,15 @@ To define your chain specification:
148148

149149
You should now see your chain specification containing SCALE-encoded hex values versus plain text.
150150

151+
152+
!!!note "Deprecation of `para_id` in Chain Specs"
153+
154+
The `para_id` field in JSON chain specifications, added through the [`chain-spec-builder`](https://paritytech.github.io/polkadot-sdk/master/staging_chain_spec_builder/index.html){target=\_blank} command, is currently used by nodes for configuration purposes. However, beginning with Polkadot SDK release `stable2509`, the `para_id` field will no longer be required in chain specifications. Instead, runtimes need to be updated to implement the [`cumulus_primitives_core::GetParachainInfo`](https://paritytech.github.io/polkadot-sdk/master/cumulus_primitives_core/trait.GetParachainInfo.html){target=\_blank} trait to successfully operate with nodes using chain specs that omit the `para_id` field.
155+
156+
With the upcoming `stable2512` release, the `para_id` field will be completely removed from chain specifications in favor of the new runtime API. New nodes will be unable to start with chain specs containing the `para_id` field unless the runtime implements the `GetParachainInfo` trait. Ensure your runtime is updated to maintain compatibility with future node versions.
157+
158+
For guidance on performing runtime upgrades to implement this new trait, refer to the [runtime upgrade tutorial](/tutorials/polkadot-sdk/parachains/zero-to-hero/runtime-upgrade/){target=\_blank}.
159+
151160
## Export Required Files
152161

153162
To prepare the parachain collator to be registered on Paseo, follow these steps:

0 commit comments

Comments
 (0)