Spinning up Paseo
How to spin up the Paseo Relay chain locally
Lets create a configuration file to launch Paseo Local:
As you can see, the sudo account (admin of the chain) is overridden with Alice
account. This allows us to make changes to Paseo Local if needed.
Run the network:
The
--verbose
flag provides us with extra information such as the location of the Paseo Local chain spec file.
Paseo Local should now be running on your machine and producing blocks!
Network Endpoints
Based on the paseo-local.toml
file, the following validator nodes are spun up:
Alice: ws://localhost:57731
Bob: ws://localhost:57735.
Charlie: ws://localhost:57739.
The rpc_port
for Alice has been specified, the ports for Bob & Charlie are dynamically assigned.
These endpoints come in handy when you want to interact with the chain (e.g. pop call chain
).
Configure Paseo Local
As of now, Paseo Local doesn't provide cores to validate parachain blocks on demand. We will have to make 2 calls to Paseo Local using Alice
as admin account.
First, configure Paseo Local to set coretime cores to 1
:
Note: the specified rpc port
57731
is specified in the createdpaseo-local.toml
file and is to interact with the validatoralice
.
Second, assign the core to the on demand pool:
For more examples of network configurations:
For more advanced options, such as specifying the Relay chain version, run the following command:
Learning Resources
🧑🏫 To learn about Polkadot in general, Polkadot.network website is a good starting point.
⭕ Learn more about parachains here.
🧑🔧 For technical introduction, here are the Polkadot SDK documentation resources.
Technical Support
Create a question and tag it with "
pop
"Share the StackExchange question in our Pop Support Telegram channel
Last updated