Rococo V1  -  A Holiday Gift to the Polkadot Community

2020-12-22 in  Parachains, Rococo
Avatar by Polkadot
Image

By: Rob Habermeier, Polkadot founder

On behalf of the Polkadot team,

The Rococo V1 Parachains Testnet is up and running. Rococo is a public testnet, maintained by Parity Technologies along with the Polkadot developer community, aimed towards testing both the parachains consensus process itself as well as parachains built by the community and their interactions with each other. Earlier this year, we launched Rococo V0, which was based off of our prototype parachains code. Now, we’re introducing Rococo V1, based on the latest version of parachain consensus — the same code that will run on Polkadot and Kusama. The parachains V1 codebase is our production-ready code for parachains consensus, which differs from V0 in the mechanisms by which parachains are included as well as having a more robust and extensible software architecture.

Parachain slots will be made available as technology allows, and will be allocated on a first-come, first-serve basis. Like Rococo-V0, we will periodically restart Rococo V1 as backwards-incompatible changes emerge to enable us as a dev team to iterate faster over parachain-related APIs and take us to an earlier launch of the parachains functionality on the Polkadot and Kusama networks. Registering a parachain on Rococo will also involve a commitment to run at least one validator node of Rococo as well as at least one collator of the registered parachain. Validator nodes will be run out of the `master` branch of the Polkadot GitHub Repository. Reach out to us on the Element channel below for more information on running a validator node. Over time, we may require teams to maintain more validator nodes.

We won’t be opening up parachain registration by the community until early next year, Jan. 4 at the earliest, so teams can rest and charge up over the holiday season. We’ve got a big year ahead of us.

The Rococo UI — blocks are coming in, along with parachain block events.

Rococo itself comes with support for XCMP-lite, our channel-based cross-parachain messaging protocol, which uses the relay chain as a transport mechanism. This is still being integrated in Cumulus, so you can look out for releases soon which provide APIs for using XCMP. Over the near future, we’ll be rolling out further parachain consensus improvements and optimizations on Rococo as we finish developing the last remaining components of parachains. After that point, we can safely call Polkadot’s codebase feature-complete.

Parachain developers and users of the Rococo testnet can join us in the Rococo Element Room

You can access the Rococo UI at Rococo Polkadot-JS Apps.

And our documentation on Parachains V1 is hosted in the Implementer’s Guide

Happy Coding and Happy Holidays,
Rob

arrow_upward
Related articles
Polkadot
XCM Part II: Versioning and Compatibility

Polkadot founder Gavin Wood inspects one interesting aspect of XCM in-depth: how XCM can change over time without introducing breakage between the very networks it is meant to connect....

Polkadot
XCM: The Cross-Consensus Message Format

This primer on XCM, Polkadot's inter-chain messaging format is the first in a series of articles explaining what it does, how it works, how to use it, and what it could become....

Kusama
Kusama’s First Batch of Parachains: An Interview with the Teams

This blog contains information provided by the projects Karura, Moonriver, Shiden, Khala, and Bifrost, in order of when they won their parachain slot. Discover what network each does, their achievements so far, and the phases ahead on their respective roadmaps....

Subscribe to the newsletter to hear about updates and events.
mail_outline
* To see how we use your information, please see our privacy policy.