Docs
Submit an issue
Appchains on Polkadot
Appchains on Polkadot
  • WELCOME
    • Polkadot Appchains
    • Installing Pop CLI
    • How to contribute
  • GUIDES
    • Set up your development environment
    • Create a new parachain
      • Create an Assets parachain
      • Create a Contracts parachain
      • Create an EVM parachain
    • Benchmarking
    • Build your parachain
      • Build your runtime deterministically
    • Call a chain
    • Launch a Chain
      • Launch a Chain in Development
      • Launch a Chain to Paseo
        • Launch Paseo
        • Set up keys
        • Acquire Coretime
      • Deploy a chain with Polkadot Deployment Portal
      • Running a post-startup command
    • Securely Sign Transactions from CLI
    • Test runtime upgrades
  • POP CLI
    • welcome
    • install
    • new
    • bench
    • build
    • build spec
    • call
    • up
    • clean
    • test
Powered by GitBook
On this page
  • Network Endpoints
  • Configure Paseo Local
  • Learning Resources

Was this helpful?

Edit on GitHub
  1. GUIDES
  2. Launch a Chain
  3. Launch a Chain to Paseo

Launch Paseo

How to spin up the Paseo Relay chain locally

Lets create a configuration file to launch Paseo Local:

touch paseo-local.toml
[relaychain]
chain = "paseo-local"

[relaychain.genesis_overrides.sudo]
key = "5GrwvaEF5zXb26Fz9rcQpDWS57CtERHpNehXCPcNoHGKutQY" # Alice

[[relaychain.nodes]]
name = "alice"
rpc_port = 57731
validator = true

[[relaychain.nodes]]
name = "bob"
validator = true

[[relaychain.nodes]]
name = "charlie"
validator = true

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:

pop up network -f paseo-local.toml --verbose

For Pop CLI versions <0.7.0 the pop up network command is pop up parachain

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:

pop call chain --pallet Configuration --function set_coretime_cores --args "1" --url ws://localhost:57731/ --suri //Alice --sudo --skip-confirm

Note: the specified rpc port 57731 is specified in the created paseo-local.toml file and is to interact with the validator alice.

Second, assign the core to the on demand pool:

pop call chain --url ws://localhost:57731 --call 0xff004a0400000a000000040100e100 --suri //Alice --skip-confirm

For more examples of network configurations:

For more advanced options, such as specifying the Relay chain version, run the following command:

pop up network --help

Learning Resources

Technical Support

PreviousLaunch a Chain to PaseoNextSet up keys

Last updated 1 month ago

Was this helpful?

🧑‍🏫 To learn about Polkadot in general, website is a good starting point.

⭕ Learn more about parachains .

🧑‍🔧 For technical introduction, are the Polkadot SDK documentation resources.

Create a question and tag it with ""

Share the StackExchange question in our

https://github.com/r0gue-io/pop-cli/tree/main/tests/networks
Polkadot.network
here
here
Polkadot Stack Exchange
pop
Pop Support Telegram channel
pop up network -f paseo-local.toml --verbose