-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Agile Coretime Usage Guides - UI guides - Parachain guides * Add RegionX UI snapshots * Add Lastic snapshots * Add on-demand parachain instructions * rename * adder collator instructions * collation on-demand * Bulk coretime * reorg content and add section titles * Add DOT and KSM deposit values * Update learn-guides-coretime-parachains.md * Add info note * minor fixes * minor fixes * Update docs/learn/learn-guides-coretime-marketplaces.md Co-authored-by: bader y <[email protected]> * Update docs/learn/learn-guides-coretime-marketplaces.md Co-authored-by: bader y <[email protected]> * Update docs/learn/learn-guides-coretime-marketplaces.md Co-authored-by: bader y <[email protected]> * Update docs/learn/learn-guides-coretime-marketplaces.md Co-authored-by: bader y <[email protected]> * Update docs/learn/learn-guides-coretime-parachains.md Co-authored-by: bader y <[email protected]> * Update docs/learn/learn-guides-coretime-parachains.md Co-authored-by: bader y <[email protected]> * Update docs/learn/learn-guides-coretime-marketplaces.md Co-authored-by: bader y <[email protected]> * Update docs/learn/learn-guides-coretime-parachains.md Co-authored-by: bader y <[email protected]> * Update docs/learn/learn-guides-coretime-parachains.md Co-authored-by: bader y <[email protected]> --------- Co-authored-by: bader y <[email protected]>
- Loading branch information
1 parent
8a09d11
commit 41c3d1e
Showing
17 changed files
with
196 additions
and
1 deletion.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,64 @@ | ||
--- | ||
id: learn-guides-coretime-marketplaces | ||
title: Coretime Marketplaces | ||
sidebar_label: Coretime Marketplaces | ||
description: Usage guides for coretime marketplaces | ||
keywords: [coretime, blockspace, parathread, parachain, cores] | ||
slug: ../learn-guides-coretime-marketplaces | ||
--- | ||
|
||
The tutorials in this document utilize: | ||
|
||
- [CoreHub on RegionX](https://app.regionx.tech/), a user interface | ||
for purchasing and managing Coretime regions. | ||
|
||
- [Lastic](https://test.lastic.xyz/start), a Coretime marketplace user interface. | ||
|
||
:::caution | ||
|
||
Both RegionX and Lastic are under active development and are released only for testing purposes. | ||
|
||
::: | ||
|
||
## RegionX | ||
|
||
The RegionX CoreHub offers options to purchase and manage cores. | ||
|
||
![RegionX-UI](../assets/coretime/RegionX-UI.png) | ||
|
||
### Purchasing Cores with RegionX | ||
|
||
RegionX allows for purchasing core with accounts hosted on wallets like Subwallet, Talisman, Nova | ||
Wallet and Polkadot-JS Extension. Select the account to be used for the coretime purchase (displayed | ||
on top right) and ensure that both the relay chain and coretime chain are connected (displayed on | ||
bottom left). Then, click on the purchase button to sign and broadcast the transaction. | ||
|
||
![RegionX-purchase-bulk-coretime](../assets/coretime/regionx-purchase-core.png) | ||
|
||
### Managing Cores with RegionX | ||
|
||
The Regions dashboard lists all the cores purchased through the connected wallet account along with | ||
the basic information of the respective core. It allows for partitioning, interlacing, transfers, and | ||
assigning tasks. | ||
|
||
![RegionX-regions-dashboard](../assets/coretime/regionx-manage-cores.png) | ||
|
||
## Lastic | ||
|
||
Lastic is a marketplace for buying and selling blockspace. For more information, check | ||
[Lastic's official documentation](https://docs.lastic.xyz/). | ||
|
||
### Purchasing Cores with Lastic | ||
|
||
Lastic allows for purchasing core with accounts hosted on wallets like Subwallet, Talisman, Nova | ||
Wallet and Polkadot-JS Extension. Select the account to be used for the coretime purchase and then, | ||
click on "buy core" button to sign and broadcast the transaction. | ||
|
||
![Lastic-purchase-bulk-coretime](../assets/coretime/Lastic-UI.png) | ||
|
||
### Managing Cores with Lastic | ||
|
||
Lastic enables you to transfer your core to another account, utilize it for a parachain, split it | ||
up, change block production frequency, or assign it to a task. | ||
|
||
![Lastic-manage-core](../assets/coretime/Lastic-manage-core.png) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,129 @@ | ||
--- | ||
id: learn-guides-coretime-parachains | ||
title: Agile Coretime for Parachains | ||
sidebar_label: Coretime for Parachains | ||
description: Agile Coretime from Parachains perspective | ||
keywords: [coretime, blockspace, parathread, parachain, cores] | ||
slug: ../learn-guides-coretime-parachains | ||
--- | ||
|
||
The landscape for parachains on {{ polkadot: Polkadot :polkadot }}{{ kusama: Kusama :kusama }} | ||
changes with the rollout of [Agile Coretime](./learn-agile-coretime.md). With | ||
[auctions](./learn-auction.md) being phased out in favor of direct coretime sales, the existing | ||
parachains on the relaychain and the prospective parachains are presented with the following | ||
scenarios: | ||
|
||
- Migrating from a legacy parachain lease into a bulk coretime model | ||
- Starting with bulk coretime model from scratch | ||
- Running a parachain with on-demand coretime purchases ("pay as you go") | ||
|
||
The parachain lease auctions will stop on-chain with the enactment of the | ||
[runtime upgrade 1.2.0](https://github.com/polkadot-fellows/runtimes/releases/tag/v1.2.0), and the | ||
existing leases will be migrated to bulk coretime automatically. Leases that are yet to be started | ||
will be canceled and the locked {{ polkadot: DOT :polkadot }}{{ kusama: KSM :kusama }} | ||
will be refunded. The existing parachains benefit from | ||
[coretime renewals](https://docs.lastic.xyz/coretime/renewals.html) which allows for the continued | ||
assignment of bulk coretime for a core without going through the regular purchasing process. | ||
|
||
:::info | ||
|
||
The tutorials below assume that you have already developed the parachain runtime and a fully configured | ||
parachain collator for the target relay chain using Polkadot-SDK. | ||
|
||
::: | ||
|
||
For the tutorials below, | ||
[the adder test parachain](https://github.com/paritytech/polkadot-sdk/tree/6f3d890ed35bfdee3e3f7d59018345635a62d1cd/polkadot/parachain/test-parachains/adder) | ||
on Polkadot-SDK has been used. To compile the `adder-collator`, run the command below in the | ||
Polkadot-SDK repository. | ||
|
||
``` | ||
cargo build -r -p test-parachain-adder-collator | ||
``` | ||
|
||
After the test parachain collator node is successfully compiled, export its genesis state and the | ||
code using the following commands. If the export succeeds, these two files should appear in | ||
the Polkadot-SDK repository. | ||
|
||
``` | ||
./target/release/adder-collator export-genesis-state genesis | ||
``` | ||
|
||
``` | ||
./target/release/adder-collator export-genesis-wasm genesis-wasm | ||
``` | ||
|
||
## Reserve ParaID | ||
|
||
The first step is to register a `ParaID` for the on-demand parachain. This can be done through | ||
Polkadot-JS UI by navigating to Network > Parachains > Parathreads and clicking on ParaID button. | ||
Ensure that you have sufficient tokens to reserve the displayed `ParaID` successfully. | ||
|
||
:::info | ||
|
||
Reserving a `ParaID` requires a deposit of 40 KSM on Kusama and 100 DOT on Polkadot. | ||
|
||
::: | ||
|
||
![coretime-reserve-paraID](../assets/coretime/coretime-reserve-paraID.png) | ||
|
||
## Register Parachain State and Code | ||
|
||
The next step is to register the parachain's genesis wasm and state, which you should have generated earlier. | ||
|
||
:::info | ||
|
||
Registering the state and wasm code of the parachain requires a deposit that is computed based on | ||
the size. For the `adder-collator` example here, it turns out to be around 46 KSM on Kusama and 116 | ||
DOT on Polkadot. As, the deposit used for registering `ParaID` is already counted in for this | ||
deposit, the total deposit requirement for registering `ParaID`, state and code for `adder-collator` | ||
is around 46 KSM on Kusama and 116 DOT on Polkadot. | ||
|
||
::: | ||
|
||
![coretime-register-parathread](../assets/coretime/coretime-register-parathread.png) | ||
|
||
After successful registration, the parachain starts onboarding as a parathread. | ||
|
||
![coretime-onboarding-parathread](../assets/coretime/coretime-parachain-onboarding.png) | ||
|
||
## Run Parachain Collator | ||
|
||
While the parachain is onboarding, start syncing the collator using the following command to rapidly | ||
sync with the specified relaychain. | ||
|
||
``` | ||
./target/release/adder-collator --parachain-id= $ParaID --chain=rococo --sync fast-unsafe | ||
``` | ||
|
||
## Run a Parachain with Bulk Coretime | ||
|
||
Now, you can purchase bulk coretime on [Coretime chain](./learn-guides-coretime-marketplaces.md) and | ||
assign the purchased core to the registered `ParaID`. The snapshot below is from | ||
[Lastic](https://test.lastic.xyz/) interface. | ||
|
||
![coretime-bulk-assign-lastic](../assets/coretime/lastic-assign-core.png) | ||
|
||
After successful assignment of the core, the `adder-collator` logs show new collations at regular | ||
intervals, gradually incrementing the state by `2`. | ||
|
||
![coretime-collation-bulk](../assets/coretime/coretime-collation-bulk.png) | ||
|
||
## Run a Parachain with On-demand Coretime | ||
|
||
After the collator node is fully synced with the relay chain, navigate to Developer > Extrinsics on | ||
the relay chain and issue `onDemandAssignmentProvider.placeOrderAllowDeath` extrinsic from the | ||
account that registered the `ParaID` by specifying sufficient `maxAmount`for the transaction to go | ||
through successfully. | ||
|
||
![coretime-ondemand-assignment](../assets/coretime/coretime-on-demand-assignment.png) | ||
|
||
With each successful on-demand extrinsic, the parachain head changes (you may have to zoom out on | ||
the browser for parachain head details to show up on Polkadot-JS UI). | ||
|
||
![coretime-ondemand-parahead](../assets/coretime/coretime-on-demand-parahead.png) | ||
|
||
The successful collation can also be verified in the parachain collator logs. It can be | ||
noticed that with each parachain block, the state of `adder-collator` is incremented by `2`. | ||
|
||
![coretime-new-collation](../assets/coretime/coretime-create-new-collation.png) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters