@@ -211,40 +211,26 @@ Refer to the [setup instructions](#manual-setup) to run a local network for deve
211
211
212
212
See [ the ` bridge-hubs ` readme] ( parachains/runtimes/bridge-hubs/README.md ) for details.
213
213
214
- ## Rococo 👑
215
- [ Rococo] ( https://polkadot.js.org/apps/?rpc=wss://rococo-rpc.polkadot.io ) is becoming a [ Community Parachain
216
- Testbed] ( https://polkadot.network/blog/rococo-revamp-becoming-a-community-parachain-testbed/ ) for parachain teams in the
217
- Polkadot ecosystem. It supports multiple parachains with the differentiation of long-term connections and recurring
218
- short-term connections, to see which parachains are currently connected and how long they will be connected for [ see
219
- here] ( https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frococo-rpc.polkadot.io#/parachains ) .
214
+ ## Testnets
220
215
221
- Rococo is an elaborate style of design and the name describes the painstaking effort that has gone into this project.
216
+ ### Paseo
222
217
223
- ### Build & Launch Rococo Collators
218
+ [ Paseo] ( https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpaseo.rpc.amforc.com#/explorer ) is the newest testnet for Polkadot,
219
+ replacing Rococo as a decentralised, community run, stable testnet for Parachain teams and dapp developers to build on.
220
+ For more information, check the [ Paseo repo] ( https://github.com/paseo-network ) .
224
221
225
- Collators are similar to validators in the relay chain. These nodes build the blocks that will eventually be included by
226
- the relay chain for a parachain.
222
+ ### Westend
227
223
228
- To run a Rococo collator you will need to compile the following binary:
224
+ [ Westend] ( https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fwestend-rpc.polkadot.io#/explorer )
225
+ is a long running testnet for Polkadot,
226
+ primarily intended to provide a testing environment for Parity to test the latest changes in the SDK.
229
227
228
+ ### Testnet Parachains
230
229
231
- ``` bash
232
- cargo build --release --locked --bin polkadot-parachain
233
- ```
234
-
235
- Once the executable is built, launch collators for each parachain (repeat once each for chain ` tick ` , ` trick ` , ` track ` ):
236
-
237
- ``` bash
238
- ./target/release/polkadot-parachain --chain $CHAIN --validator
239
- ```
240
-
241
- You can also build [ using a container] ( ./docs/contributor/container.md ) .
242
-
243
- ### Parachains
230
+ A few testnet parachain instances:
244
231
245
- - [ Asset Hub] ( https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frococo-statemint-rpc.polkadot.io#/explorer )
246
- - [ Contracts on Rococo] ( https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frococo-contracts-rpc.polkadot.io#/explorer )
247
- - [ RILT] ( https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frococo.kilt.io#/explorer )
232
+ - [ Asset Hub Westend] ( https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fwestend-asset-hub-rpc.polkadot.io#/explorer )
233
+ - [ Frequency Paseo] ( https://polkadot.js.org/apps/?rpc=wss%3A%2F%2F0.rpc.testnet.amplica.io#/explorer )
248
234
249
235
The network uses horizontal message passing (HRMP) to enable communication between parachains and the relay chain and,
250
236
in turn, between parachains. This means that every message is sent to the relay chain, and from the relay chain to its
0 commit comments