Skip to content

Commit

Permalink
GITBOOK-173: No subject
Browse files Browse the repository at this point in the history
  • Loading branch information
@brunopgalvao @gitbook-bot
brunopgalvao authored and gitbook-bot committed Sep 24, 2024
1 parent 2296f4f commit 77c6a4b
Show file tree
Hide file tree
Showing 4 changed files with 24 additions and 24 deletions.
6 changes: 3 additions & 3 deletions pop-cli-for-appchains/SUMMARY.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -20,9 +20,9 @@
* [Spinning up Kusama](<guides/spinning-up-a-polkadot-network/spinning-up-the-polkadot-network-1 (1).md>)
* [Spinning up Polkadot](guides/spinning-up-a-polkadot-network/spinning-up-the-polkadot-network-1.md)
* [Running a post-startup command](guides/running-a-post-startup-command.md)
* [Launching your Parachain on Polkadot](guides/launching-your-parachain-on-polkadot/README.md)
* [Onboarding your parachain locally](guides/launching-your-parachain-on-polkadot/running-on-paseo-locally.md)
* [Onboarding your parachain on Paseo](guides/launching-your-parachain-on-polkadot/running-on-paseo.md)
* [Launching your Parachain on Polkadot](guides/deploying-your-parachain-to-polkadot/README.md)
* [Launching your parachain manually](guides/running-on-paseo-locally.md)
* [Onboarding your parachain on Paseo](guides/running-on-paseo-1.md)

## POP CLI

Expand Down
4 changes: 2 additions & 2 deletions ...hing-your-parachain-on-polkadot/README.md → ...ying-your-parachain-to-polkadot/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ A typical development workflow for launching your parachain on Polkadot:&#x20;
* [ ] Under the hood, Pop CLI launches your parachain to Paseo Local TestNet automatically for development purposes:
* [ ] [Run your parachain on Paseo](../running-your-parachain.md)
2. When ready to test your parachain in a live environment with other parachains:
* [ ] Use [this guide](running-on-paseo-locally.md) to mimic the onboarding process for Paseo TestNet locally.&#x20;
* [ ] When comfortable with onboarding locally, then use the [next guide](running-on-paseo.md) to onboard to Paseo Live TestNet.
* [ ] Use [this guide](../running-on-paseo-locally.md) to mimic the onboarding process for Paseo TestNet locally.&#x20;
* [ ] When comfortable with onboarding locally, then use the [next guide](../running-on-paseo-1.md) to onboard to Paseo Live TestNet.
3. Launch on Polkadot
* [ ] The process here is similar to launching on Paseo.
4 changes: 2 additions & 2 deletions ...parachain-on-polkadot/running-on-paseo.md → ...or-appchains/guides/running-on-paseo-1.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@ Now that we have a stash account, we need to fund this account with some tokens

Go to the [Polkadot Faucet](https://faucet.polkadot.io/) and fund your account:

<figure><img src="../../.gitbook/assets/Screenshot 2024-09-06 at 4.04.37 PM.png" alt="" width="563"><figcaption><p>Polkadot / Paseo Faucet</p></figcaption></figure>
<figure><img src="../.gitbook/assets/Screenshot 2024-09-06 at 4.04.37 PM.png" alt="" width="563"><figcaption><p>Polkadot / Paseo Faucet</p></figcaption></figure>

Cool. Make sure to add your account to the [Polkadot Signer extension](https://polkadot.js.org/) so that you can see your account appear in the [PolkadotJs Apps](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpaseo-rpc.dwellir.com#/accounts) UI.

Expand Down Expand Up @@ -120,7 +120,7 @@ With the account and session keys created, we can now ready our parachain for on

To onboard our parachain we need to grab the next available parachain ID on Paseo. We can use [PolkaotJs Apps](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpaseo-rpc.dwellir.com#/chainstate) and check the chain state for the next available parachain ID:

<figure><img src="../../.gitbook/assets/Screenshot 2024-09-05 at 5.03.46 PM.png" alt=""><figcaption><p>ParaId</p></figcaption></figure>
<figure><img src="../.gitbook/assets/Screenshot 2024-09-05 at 5.03.46 PM.png" alt=""><figcaption><p>ParaId</p></figcaption></figure>

> Make sure to note down the `paraId`. We will be using this in our next step
Expand Down
34 changes: 17 additions & 17 deletions ...n-on-polkadot/running-on-paseo-locally.md → ...chains/guides/running-on-paseo-locally.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ description: >-
hidden: true
---

# Onboarding your parachain locally
# Launching your parachain manually

## Introduction

Expand All @@ -16,10 +16,10 @@ hidden: true
A good development workflow:&#x20;

1. Run your parachain **locally** using Pop CLI to onboard your parachain to Paseo TestNet automatically for development purposes:
* [ ] [Run your parachain on Paseo](../running-your-parachain.md)
* [ ] [Run your parachain on Paseo](running-your-parachain.md)
2. When ready to test your parachain in a live environment with other parachains:
* [ ] Use this guide to mimic the onboarding process for Paseo TestNet. When comfortable with this process locally, then use the next guide to onboard to Paseo Live TestNet.
* [ ] [Onboard your parachain to Paseo Live TestNet](running-on-paseo.md)
* [ ] [Onboard your parachain to Paseo Live TestNet](running-on-paseo-1.md)

Let's get started.

Expand Down Expand Up @@ -60,7 +60,7 @@ pop up parachain -f network.toml --verbose
Paseo should now be running on your machine and producing blocks. We can now move towards setting up our parachain.

<figure><img src="../../.gitbook/assets/Screenshot 2024-09-24 at 12.20.38 PM.png" alt=""><figcaption><p>pop up parachain -f network.toml --verbose</p></figcaption></figure>
<figure><img src="../.gitbook/assets/Screenshot 2024-09-24 at 12.20.38 PM.png" alt=""><figcaption><p>pop up parachain -f network.toml --verbose</p></figcaption></figure>

## Setting up our parachain

Expand Down Expand Up @@ -162,15 +162,15 @@ Now that we have a stash account, we need to fund this account with some tokens

Add the stash account to the [Polkadot Signer extension](https://polkadot.js.org/) so that you can see your account appear in the [PolkadotJs Apps](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpaseo-rpc.dwellir.com#/accounts) UI.

<figure><img src="../../.gitbook/assets/Screenshot 2024-09-24 at 11.14.37 AM.png" alt="" width="375"><figcaption><p>Polkadot Signer Extension</p></figcaption></figure>
<figure><img src="../.gitbook/assets/Screenshot 2024-09-24 at 11.14.37 AM.png" alt="" width="375"><figcaption><p>Polkadot Signer Extension</p></figcaption></figure>

Make sure it appears in the PolkadotJs Apps UI:

<figure><img src="../../.gitbook/assets/Screenshot 2024-09-24 at 11.17.59 AM.png" alt=""><figcaption><p>PolkadotJs Apps UI</p></figcaption></figure>
<figure><img src="../.gitbook/assets/Screenshot 2024-09-24 at 11.17.59 AM.png" alt=""><figcaption><p>PolkadotJs Apps UI</p></figcaption></figure>

Notice that the balance is zero. Let's transfer some tokens from Alice's account to the stash account so that the stash account has funds to do transactions:

<figure><img src="../../.gitbook/assets/Screenshot 2024-09-24 at 11.23.53 AM.png" alt=""><figcaption><p>Send Funds</p></figcaption></figure>
<figure><img src="../.gitbook/assets/Screenshot 2024-09-24 at 11.23.53 AM.png" alt=""><figcaption><p>Send Funds</p></figcaption></figure>

> Optionally, if you knew your account beforehand, you could have pre-funded it when you spun up the Paseo network. More info [here](https://substrate.stackexchange.com/a/11930/29).
Expand Down Expand Up @@ -341,7 +341,7 @@ In order to run your parachain's collator node you will need the raw chain spec

This can be found in the output of when you ran the `pop up parachain -f network --verbose` command.:

<figure><img src="../../.gitbook/assets/Screenshot 2024-09-24 at 12.20.38 PM (1).png" alt=""><figcaption></figcaption></figure>
<figure><img src="../.gitbook/assets/Screenshot 2024-09-24 at 12.20.38 PM (1).png" alt=""><figcaption></figcaption></figure>

Copy this chain spec into our `my-parachain` directory:

Expand Down Expand Up @@ -420,43 +420,43 @@ We now need to onboard the parachain to Paseo.

Go to the Parachains tab.

<figure><img src="../../.gitbook/assets/Screenshot 2024-09-24 at 11.37.32 AM.png" alt=""><figcaption><p>Parachains Tab</p></figcaption></figure>
<figure><img src="../.gitbook/assets/Screenshot 2024-09-24 at 11.37.32 AM.png" alt=""><figcaption><p>Parachains Tab</p></figcaption></figure>

Select "+ ParaId" and make sure to use the stash account:

<figure><img src="../../.gitbook/assets/Screenshot 2024-09-24 at 11.38.09 AM.png" alt=""><figcaption><p>Reserve ParaId</p></figcaption></figure>
<figure><img src="../.gitbook/assets/Screenshot 2024-09-24 at 11.38.09 AM.png" alt=""><figcaption><p>Reserve ParaId</p></figcaption></figure>

Next, select "+ ParaThread". Make sure to use the stash account, upload your wasm and genesis state:

<figure><img src="../../.gitbook/assets/Screenshot 2024-09-24 at 11.38.50 AM.png" alt=""><figcaption><p>Register ParaThread</p></figcaption></figure>
<figure><img src="../.gitbook/assets/Screenshot 2024-09-24 at 11.38.50 AM.png" alt=""><figcaption><p>Register ParaThread</p></figcaption></figure>

It will take a moment for the ParaThread to onboard:

<figure><img src="../../.gitbook/assets/Screenshot 2024-09-24 at 11.39.09 AM.png" alt=""><figcaption><p>ParaThread Onboarding</p></figcaption></figure>
<figure><img src="../.gitbook/assets/Screenshot 2024-09-24 at 11.39.09 AM.png" alt=""><figcaption><p>ParaThread Onboarding</p></figcaption></figure>

Once onboarded, we now need to use sudo privileges (Alice account) on the Paseo Relay chain to "force" a lease for our parachain so that it can begin to use produce blocks.

Go to the "sudo" tab:

<figure><img src="../../.gitbook/assets/Screenshot 2024-09-24 at 11.45.44 AM.png" alt=""><figcaption><p>Sudo tab</p></figcaption></figure>
<figure><img src="../.gitbook/assets/Screenshot 2024-09-24 at 11.45.44 AM.png" alt=""><figcaption><p>Sudo tab</p></figcaption></figure>

Use sudo privileges on the Relay chain to force a lease for our parachain:

<figure><img src="../../.gitbook/assets/Screenshot 2024-09-24 at 11.46.09 AM.png" alt=""><figcaption><p>Force a lease</p></figcaption></figure>
<figure><img src="../.gitbook/assets/Screenshot 2024-09-24 at 11.46.09 AM.png" alt=""><figcaption><p>Force a lease</p></figcaption></figure>

> In production, leases are assigned via the result of an on-chain auction.
Wait for the lease to take effect:

<figure><img src="../../.gitbook/assets/Screenshot 2024-09-24 at 11.46.30 AM.png" alt=""><figcaption><p>Upgrading Parathread</p></figcaption></figure>
<figure><img src="../.gitbook/assets/Screenshot 2024-09-24 at 11.46.30 AM.png" alt=""><figcaption><p>Upgrading Parathread</p></figcaption></figure>

You will then see the parathread upgraded to a parachain:

<figure><img src="../../.gitbook/assets/Screenshot 2024-09-24 at 11.50.18 AM.png" alt=""><figcaption><p>Parachain Tab</p></figcaption></figure>
<figure><img src="../.gitbook/assets/Screenshot 2024-09-24 at 11.50.18 AM.png" alt=""><figcaption><p>Parachain Tab</p></figcaption></figure>

After a few moments, you should see the parachain producing blocks. The included / backed will update with the Relay chain's block number in which your parachain's block was included and backed. You can also check your collator logs to confirm.

<figure><img src="../../.gitbook/assets/Screenshot 2024-09-24 at 2.21.37 PM.png" alt=""><figcaption><p>Notice the included / backed</p></figcaption></figure>
<figure><img src="../.gitbook/assets/Screenshot 2024-09-24 at 2.21.37 PM.png" alt=""><figcaption><p>Notice the included / backed</p></figcaption></figure>

Congrats! Your chain is now producing blocks!

Expand Down

0 comments on commit 77c6a4b

Please sign in to comment.