diff --git a/components/Metadata.jsx b/components/Metadata.jsx index b757c20935ba..e0ab69a51aed 100644 --- a/components/Metadata.jsx +++ b/components/Metadata.jsx @@ -19,7 +19,6 @@ const Networks = [ { name: "Kusama Bridge Hub", rpc: "wss://kusama-bridge-hub-rpc.polkadot.io"}, { name: "Kusama Coretime", rpc: "wss://kusama-coretime-rpc.polkadot.io"}, { name: "Westend", rpc: "wss://westend-rpc.polkadot.io" }, - { name: "Rococo", rpc: "wss://rococo-rpc.polkadot.io" }, ]; // Common pallets specific to Polkadot/Kusama. diff --git a/docs/assets/paseo-chains.png b/docs/assets/paseo-chains.png new file mode 100644 index 000000000000..b5680eedba62 Binary files /dev/null and b/docs/assets/paseo-chains.png differ diff --git a/docs/assets/polkadotjs_network_parachains.png b/docs/assets/polkadotjs_network_parachains.png deleted file mode 100644 index b66d08fb76e6..000000000000 Binary files a/docs/assets/polkadotjs_network_parachains.png and /dev/null differ diff --git a/docs/build/build-hrmp-channels.md b/docs/build/build-hrmp-channels.md index accc1f64b06d..6d2a2e8cd5c2 100644 --- a/docs/build/build-hrmp-channels.md +++ b/docs/build/build-hrmp-channels.md @@ -70,8 +70,8 @@ between a parachain and the Asset Hub with `ParaID` 1000 is `0x3c0ae8030000` ![asset-hub-hrmp-channel](../assets/asset-hub/establish-channel-asset-hub.png) -Here is an example call with an XCM program sent from the parachain to Rococo relay chain to -establish channel a bi-directional channel with Rococo Asset Hub - +Here is an example call with an XCM program sent from the parachain to Paseo relay chain to +establish channel a bi-directional channel with Paseo Asset Hub - `0x0f001f000301000314000400000000070010a5d4e81300000000070010a5d4e80006000300c16678419c183c0ae8030000140d01000001003145` ![asset-hub-hrmp-channel-xcm](../assets/asset-hub/asset-hub-establish-channel-xcm.png) diff --git a/docs/build/build-light-clients.md b/docs/build/build-light-clients.md index 9b0525eaaa9f..ad9523661e95 100644 --- a/docs/build/build-light-clients.md +++ b/docs/build/build-light-clients.md @@ -69,8 +69,8 @@ blockchain network without relying on specific third parties. Application developers can now run a Substrate light client in any NodeJS environment ([@substrate/connect](https://www.npmjs.com/package/@substrate/connect)). Currently, Substrate -connect supports Polkadot, Kusama, Westend, and Rococo; because light clients are part of the -overall Substrate framework, they are available for Substrate-based blockchains. +connect supports Polkadot, Kusama, and Westend; because light clients are part of the overall +Substrate framework, they are available for Substrate-based blockchains. ### As a browser extension diff --git a/docs/build/build-network-overview.md b/docs/build/build-network-overview.md index c12355854eb0..ecfc3f0593e5 100644 --- a/docs/build/build-network-overview.md +++ b/docs/build/build-network-overview.md @@ -28,10 +28,6 @@ development or application-driven contexts. (is not reset back to genesis block). - **Paseo** - A community-run testnet which mirrors the Polkadot runtime. It is maintained by the community. - - **Rococo** - Parachains and XCM testnet. Occasionally reset (started over again with a new - genesis block). - - **Contracts** - Wasm-based Smart Contract enabled parachain testnet on Rococo, primarily for - [`ink!`](https://use.ink/) development. Polkadot mainnet has been running since May 2020 and has [implementations in various programming languages](../learn/learn-implementations.md) ranging from diff --git a/docs/build/build-parachains.md b/docs/build/build-parachains.md index e8d2fe0d1ae8..4e1fa9b7d3e4 100644 --- a/docs/build/build-parachains.md +++ b/docs/build/build-parachains.md @@ -298,30 +298,21 @@ available for this type of work. ## Testing a Parachain -### Rococo Testnet +### Paseo Testnet -[Rococo](https://github.com/paritytech/polkadot-sdk/tree/master/cumulus#rococo-) is a testnet built -for testing parachains. Rococo utilizes Cumulus and -[HRMP](../learn/learn-xcm-transport.md#hrmp-xcmp-lite) (Horizontal Relay-routed Message Passing) in -order to send transfers and messages between parachains. +[Paseo](https://github.com/paseo-network) is a testnet built for testing parachains. Paseo utilizes +Cumulus and [HRMP](../learn/learn-xcm-transport.md#hrmp-xcmp-lite) (Horizontal Relay-routed Message +Passing) in order to send transfers and messages between parachains. -Rococo runs a few test system parachains, like -[Asset Hub](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frococo-asset-hub-rpc.polkadot.io#/explorer), -[Contracts](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frococo-contracts-rpc.polkadot.io#/explorer), -[Coretime](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frococo-coretime-rpc.polkadot.io#/explorer), -[Encointer Lietaer](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frococo.api.encointer.org#/explorer), -and -[Bridge Hub](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frococo-bridge-hub-rpc.polkadot.io#/explorer). -It also runs several externally developed parachains. +Paseo runs a few test [system parachains](../learn/learn-system-chains.md) and externally developed +parachains. -### What Parachains are on Rococo Now? +### What Parachains are on Paseo Now? You can see the list of included parachains -[here](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frococo-rpc.polkadot.io#/parachains). A list of -proposed parachains is available -[here](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frococo-rpc.polkadot.io#/parachains/proposals). +[here](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpaseo-rpc.dwellir.com#/parachains). -### Obtaining ROC +### Obtaining PAS Follow the instructions [here](../learn/learn-DOT.md#getting-tokens-on-the-rococo-testnet) to get ROCs tokens. @@ -332,9 +323,9 @@ If you would like to connect to a parachain via [Polkadot-JS Apps](https://polka you may do so by clicking on the network selection at the top left-hand corner of the navigation and selecting any parachain of choice. -![rococo parachains](../assets/polkadotjs_network_parachains.png) +![rococo parachains](../assets/paseo-chains.png) -For the purpose of these following examples, we will be using the Rococo testnet "Custom Node" +For the purpose of these following examples, we will be using the Paseo testnet "Custom Node" underneath "Development", following the [parachain tutorials](https://docs.substrate.io/reference/how-to-guides/parachains/connect-to-a-relay-chain/). diff --git a/docs/general/glossary.md b/docs/general/glossary.md index 168f352f8ac5..7c40ddea5ed8 100644 --- a/docs/general/glossary.md +++ b/docs/general/glossary.md @@ -572,7 +572,8 @@ the information is not stored in the chain's trie, but along blocks. ## Rococo -The [testnet](#testnet) set aside for testing parachains, cumulus, and related technology. +Rococo was a [testnet](#testnet) set aside for testing parachains, cumulus, and related technology. +Please refer to Paseo test network. ## Root Origin diff --git a/docs/learn/archive/learn-crowdloans.md b/docs/learn/archive/learn-crowdloans.md index 021039646024..0892f19c1ca8 100644 --- a/docs/learn/archive/learn-crowdloans.md +++ b/docs/learn/archive/learn-crowdloans.md @@ -32,14 +32,6 @@ If you are here for guidance on how to contribute to a crowdloan, watch the vide -:::note Testing on Rococo - -For information on how to participate in the crowdloan and parachain auction testing on Rococo, -please see the -[Rococo content](../../build/build-parachains.md##testing-a-parachains:-rococo-testnet) - -::: - ## Crowdloan Campaigns vs Parachain Auctions It is important to recognize that starting a crowdloan campaign is **optional** for participating in diff --git a/docs/learn/learn-agile-coretime.md b/docs/learn/learn-agile-coretime.md index 2ace11103867..e5b802cc56b0 100644 --- a/docs/learn/learn-agile-coretime.md +++ b/docs/learn/learn-agile-coretime.md @@ -215,7 +215,7 @@ better use of the existing cores). #### Is there a UI for the Coretime Chain? Teams in the ecosystem are working on a UI. RegionX has released an app for testing on -Rococo: https://app.regionx.tech/. Without the UI, this would be automated from the parachains’ +Paseo: https://app.regionx.tech/. Without the UI, this would be automated from the parachains’ runtimes or manually with Coretime Chain extrinsics via polkadot.js. ### Coretime Pricing and Purchasing diff --git a/docs/learn/learn-collator.md b/docs/learn/learn-collator.md index 89146582bd5d..0f170e849689 100644 --- a/docs/learn/learn-collator.md +++ b/docs/learn/learn-collator.md @@ -83,16 +83,15 @@ A block is produced every 6 seconds. Blockchains that are built using Substrate are unable to hook onto the relay chain on their own. The Parity team built the [Cumulus library](https://github.com/paritytech/polkadot-sdk/tree/master/cumulus/) to address this. -Collators are being used on the -[Rococo](../build/build-parachains.md##testing-a-parachains:-rococo-testnet) testnet, and you can -learn more about how they are used with Cumulus via the -[Cumulus](https://github.com/paritytech/polkadot-sdk/tree/master/cumulus/) repository. More +Collators are being used on the [Paseo](../build/build-parachains.md#testing-a-parachain) testnet, +and you can learn more about how they are used with Cumulus via the +[Cumulus](hhttps://paritytech.github.io/polkadot-sdk/master/polkadot_sdk_docs/polkadot_sdk/cumulus/index.html) Rust documentation. More information can be found under the [Cumulus section](../build/build-parachains.md###cumulus) on the build parachain page. ## Guides and Tools - [Tutorial covering Cumulus and Collators](https://docs.substrate.io/reference/how-to-guides/parachains/connect-to-a-relay-chain/) -- [Rococo testnet guide](../build/build-parachains.md##testing-a-parachains:-rococo-testnet) +- [Paseo testnet guide](../build/build-parachains.md#testing-a-parachain) - [polkadot-launch](https://github.com/shawntabrizi/polkadot-launch) - a tool to quickly spin up a local Polkadot testnet based on some parameters like number of parachains, collator setup, etc. diff --git a/docs/learn/learn-guides-asset-conversion.md b/docs/learn/learn-guides-asset-conversion.md index 2c875e67ee6a..3e9c67c9a82d 100644 --- a/docs/learn/learn-guides-asset-conversion.md +++ b/docs/learn/learn-guides-asset-conversion.md @@ -18,11 +18,11 @@ see the [wallets](./wallets-index), [apps](./apps-index) and [dashboard](./dashb The [DOT ACP UI](https://github.com/MVPWorkshop/dot-acp-ui) project is part of Polkadot initiative for building front-end and UI for Asset Conversion Pallet on Polkadot's Asset Hub. Currently, the -app is deployed on Westend, Rococo and Kusama [here](https://app.dotacp.mvpworkshop.co/swap). +app is deployed on Westend and Kusama [here](https://app.dotacp.mvpworkshop.co/swap). ::: -The tutorial below demonstrates the complete journey from creating a liquidity pool on Rococo test +The tutorial below demonstrates the complete journey from creating a liquidity pool on Paseo test net and exploring all of the key functionalities of Asset Conversion pallet. ## Create a Liquidity Pool @@ -35,8 +35,8 @@ The `create_pool` function is used to create an empty liquidity pool along with asset. This asset's ID is announced in the `Event::PoolCreated` event. After creating a pool, liquidity can be added to it via the `Pallet::add_liquidity` function. -For example, the snapshot below shows how to create liquidity pool with `ROC` tokens and `EDU` -tokens with the asset ID `149` on Rococo Asset Hub. Creating this extrinsic requires knowledge of +For example, the snapshot below shows how to create liquidity pool with `PAS` tokens and `EDU` +tokens with the asset ID `149` on Paseo Asset Hub. Creating this extrinsic requires knowledge of [XCM Multilocations](xcm/fundamentals/multilocation/summary.md). From the perspective of AssetHub, an Asset Hub, the asset with an `AssetId` of `149` has a MultiLocation of @@ -66,9 +66,9 @@ calculates an optimal contribution of assets, which may differ from the desired be less than the specified minimums. Liquidity providers receive liquidity tokens representing their share of the pool. -For example, the snapshot below shows how to provide liquidity to the pool with `ROC` tokens and -`EDU` tokens with the asset ID `149` on Rococo Asset Hub. The intention is to provide liquidity of 1 -`ROC` token (`u128` value of `1000000000000` as it has 12 decimals) and 100 `EDU` tokens (`u128` +For example, the snapshot below shows how to provide liquidity to the pool with `PAS` tokens and +`EDU` tokens with the asset ID `149` on Paseo Asset Hub. The intention is to provide liquidity of 1 +`PAS` token (`u128` value of `1000000000000` as it has 12 decimals) and 100 `EDU` tokens (`u128` value of `1000000000000` as it has 10 decimals). ![Provide Liquidity](../assets/asset-hub/Asset-Conversion-Add-Liquidity.png) @@ -89,8 +89,8 @@ amount of the second asset in return. This function aims to provide predictabili outcomes, allowing users to manage their asset exchanges with confidence regarding the minimum return. -For example, the snapshot below shows how to swap `ROC` tokens to `EDU` tokens with the asset ID -`149` on Rococo Asset Hub. The intention is to swap 0.1 `ROC` tokens (`u128` value of `100000000000` +For example, the snapshot below shows how to swap `PAS` tokens to `EDU` tokens with the asset ID +`149` on Paseo Asset Hub. The intention is to swap 0.1 `PAS` tokens (`u128` value of `100000000000` as it has 12 decimals) to at least 9 `EDU` tokens (`u128` value of `90000000000` as it has 10 decimals). @@ -111,8 +111,8 @@ do not spend more than a predetermined maximum amount of the initial asset to ac target amount of the second asset, providing a way to control the cost of the transaction while achieving the desired outcome. -For example, the snapshot below shows how to swap `EDU` tokens with the asset ID `149` on Rococo -Asset Hub to `ROC` Tokens. The intention is to swap for obtaining 0.1 `ROC` tokens (`u128` value of +For example, the snapshot below shows how to swap `EDU` tokens with the asset ID `149` on Paseo +Asset Hub to `PAS` Tokens. The intention is to swap for obtaining 0.1 `PAS` tokens (`u128` value of `100000000000` as it has 12 decimals) for a maximum of 10 `EDU` tokens (`u128` value of `100000000000` as it has 10 decimals). diff --git a/docs/learn/learn-parachains.md b/docs/learn/learn-parachains.md index 03c2ffc83d2a..0fa13602f6ee 100644 --- a/docs/learn/learn-parachains.md +++ b/docs/learn/learn-parachains.md @@ -11,11 +11,11 @@ import MessageBox from "../../components/MessageBox"; import "../../components/M -:::info Testing on Rococo +:::info Testing on Paseo -For information on how to test coretime functionalities on Rococo, please see the -[Rococo Content](../build/build-parachains.md##testing-a-parachains:-rococo-testnet) on the -parachain development guide. +For information on how to test coretime functionalities on Paseo, please see the +[Paseo Content](../build/build-parachains.md#testing-a-parachain) on the parachain development +guide. ::: diff --git a/docs/maintain/maintain-endpoints.md b/docs/maintain/maintain-endpoints.md index 1735b29b8b8a..9313bc1e908e 100644 --- a/docs/maintain/maintain-endpoints.md +++ b/docs/maintain/maintain-endpoints.md @@ -24,8 +24,8 @@ Endpoints for all production and test networks are listed on the [Polkadot-JS UI](https://polkadot.js.org/apps/#/accounts) which are accessed from [here](https://github.com/polkadot-js/apps/tree/master/packages/apps-config/src/endpoints). Endpoints for Polkadot relay chain and Kusama relay chain, parachains, and Paseo test network are -maintained by the community. System Chains as well as Westend and Rococo test network endpoints -maintained by Parity Technologies are listed below: +maintained by the community. System Chains as well as Westend test network endpoints maintained by +Parity Technologies are listed below: