Skip to content

Commit 1d981fe

Browse files
nhussein110xLucca
andauthored
Update tutorials/polkadot-sdk/parachains/zero-to-hero/deploy-to-testnet.md
Co-authored-by: 0xLucca <[email protected]>
1 parent 5855ee8 commit 1d981fe

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

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

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -97,9 +97,7 @@ Polkadot SDK-based blockchains are defined by a file called the [chain specifica
9797
- **Plain chain spec** - a human-readable JSON file that can be modified to suit your parachain's requirements. It serves as a template for initial configuration and includes human-readable keys and structures
9898
- **Raw chain spec** - a binary-encoded file used to start your parachain node. This file is generated from the plain chain spec and contains the encoded information necessary for the parachain node to synchronize with the blockchain network. It ensures compatibility across different runtime versions by providing data in a format directly interpretable by the node's runtime, regardless of upgrades since the chain's genesis
9999

100-
!!!tip
101-
The chain spec is only used for genesis, when you start the chain for the first time. If you are doing runtime upgrades in the future, you do not need to generate a new chain spec.
102-
100+
The chain spec file is only required during the initial blockchain creation (genesis). You do not need to generate a new chain spec when performing runtime upgrades after your chain is already running.
103101
The files required to register a parachain must specify the correct relay chain to connect to and the parachain identifier you have been assigned. To make these changes, you must build and modify the chain specification file for your parachain. In this tutorial, the relay chain is `paseo`, and the parachain identifier is `4508`.
104102

105103
To define your chain specification:

0 commit comments

Comments
 (0)