Cecile Tonglet
8a445a4250
* Initial commit Forked at:9e28ea67b6Parent branch: origin/master * WIP Forked at:9e28ea67b6Parent branch: origin/master * WIP Forked at:9e28ea67b6Parent branch: origin/master * WIP Forked at:9e28ea67b6Parent branch: origin/master * CLEANUP Forked at:9e28ea67b6Parent branch: origin/master * CLEANUP Forked at:9e28ea67b6Parent branch: origin/master * WIP Forked at:9e28ea67b6Parent branch: origin/master * Pushed branch for polkadot & substrate * WIP Forked at:9e28ea67b6Parent branch: origin/master * using rococo and tick * Revert "using rococo and tick" This reverts commit d81db9246ff7061478649ffea3e49e417fcb6959. * debug * WIP Forked at:9e28ea67b6Parent branch: origin/master * Revert "Revert "using rococo and tick"" This reverts commit 45ec2be89f2b8af82da8dcb9d19d900571598766. * WIP Forked at:9e28ea67b6Parent branch: origin/master * Update rococo-parachains/src/service.rs * WIP Forked at:9e28ea67b6Parent branch: origin/master * WIP Forked at:9e28ea67b6Parent branch: origin/master * WIP Forked at:9e28ea67b6Parent branch: origin/master * Revert "WIP" This reverts commit d3f63ed0a314ffe12c0066124076736017981b80. * WIP Forked at:9e28ea67b6Parent branch: origin/master * CLEANUP Forked at:9e28ea67b6Parent branch: origin/master * CLEANUP Forked at:9e28ea67b6Parent branch: origin/master * CLEANUP Forked at:9e28ea67b6Parent branch: origin/master * Use inprocess validation * CLEANUP Forked at:9e28ea67b6Parent branch: origin/master * CLEANUP Forked at:9e28ea67b6Parent branch: origin/master * Fix failing test * CLEANUP Forked at:9e28ea67b6Parent branch: origin/master * CLEANUP Forked at:9e28ea67b6Parent branch: origin/master * increase logs * Removed a bit of logs * Revert branch change * CLEANUP Forked at:9e28ea67b6Parent branch: origin/master * Test without STDIN close detection * Bypass validation pool * Switch to rococo-branch * Move start_test_collator to rococo-collator * CLEANUP Forked at:9e28ea67b6Parent branch: origin/master * CLEANUP Forked at:9e28ea67b6Parent branch: origin/master
Cumulus ☁️
A set of tools for writing Substrate-based Polkadot parachains. Refer to the included overview for architectural details, and the Cumulus workshop for a hand-holding walkthrough of using these tools.
It's easy to write blockchains using Substrate, and the overhead of writing parachains' distribution, p2p, database, and synchronization layers should be just as low. This project aims to make it easy to write parachains for Polkadot by leveraging the power of Substrate.
Cumulus clouds are shaped sort of like dots; together they form a system that is intricate, beautiful and functional.
Consensus
cumulus-consensus is a
consensus engine for Substrate
that follows a Polkadot
relay chain. This will run a
Polkadot node internally, and dictate to the client and synchronization algorithms which chain to
follow,
finalize,
and treat as best.
Runtime
The cumulus-runtime is wrapper around Substrate runtimes that provides parachain
validation capabilities and proof-generation routines.
Collator
A Polkadot collator for the parachain is
implemented by cumulus-collator.
Rococo 👑
Rococo is the testnet for parachains. It currently runs the parachains Tick, Trick and Track.
Rococo is an elaborate style of design and the name describes the painstaking effort that has gone into this project. Tick, Trick and Track are the German names for the cartoon ducks known to English speakers as Huey, Dewey and Louie.
Build & Launch Rococo Collators
Collators are similar to validators in the relay chain. These nodes build the blocks that will eventually be included by the relay chain for a parachain.
To run a Rococo collator you will need to compile the following binary:
cargo build --release -p rococo-collator
Once the executable is built, launch collators for each parachain (repeat once each for chain
tick, trick, track):
./target/release/rococo-collator --chain $CHAIN --validator
Parachains
The parachains of Rococo all use the same runtime code. The only difference between them is the parachain ID used for registration with the relay chain:
- Tick: 100
- Trick: 110
- Track: 120
The network uses horizontal message passing (HRMP) to enable communication between parachains and the relay chain and, in turn, between parachains. This means that every message is sent to the relay chain, and from the relay chain to its destination parachain.