* Initial commit Forked at:56753b7717Parent branch: origin/master * Copy runtime module from rococo Forked at:56753b7717Parent branch: origin/master * Also copy dependencies pallets and primitives Forked at:56753b7717Parent branch: origin/master * WIP Forked at:56753b7717Parent branch: origin/master * WIP Forked at:56753b7717Parent branch: origin/master * test-service * Move integration test * CLEANUP Forked at:56753b7717Parent branch: origin/master * Not sure what went wrong... * WIP Forked at:56753b7717Parent branch: origin/master * WIP Forked at:56753b7717Parent branch: origin/master * CLEANUP Forked at:56753b7717Parent branch: origin/master * fmt * CLEANUP Forked at:56753b7717Parent branch: origin/master * CLEANUP Forked at:56753b7717Parent branch: origin/master * Remove pallet contracts (not used) * Remove pallet parachain-info and token-dealer (not used) * Sort dependencies alphabetically * CLEANUP Forked at:56753b7717Parent branch: origin/master * CumulusTestNode for testing * Speed up block generation * Fix improper shutdown * rustfmt * runtime: replace const by storage * Fix for previous commit * Remove some generics * Move generate_genesis_state to cumulus-primitives * fmt * Remove message_example * fixup! Remove message_example * WIP Forked at:56753b7717Parent branch: origin/master * Half the solution to previous commit :( * Revert "Fix for previous commit" This reverts commit 60010bab6797487093ac8c790b3a536f7ca0895b. * Revert "runtime: replace const by storage" This reverts commit c64b3a46f0325a98922015e0cbf3570e2e431774. Not working for some reason... * Use helper Forked at:56753b7717Parent branch: origin/master * WIP Forked at:56753b7717Parent branch: origin/master * Remove test-primitives * Revert "Half the solution to previous commit :(" This reverts commit 9a8f89f9f06252198e6405057043c6b313f1aea4. * Revert "Revert "Half the solution to previous commit :("" This reverts commit 6a93f0f09d74ccdc3738dd78a777c483427c03ce. * Test with some extra extrinsics * WIP Forked at:56753b7717Parent branch: origin/master * CLEANUP Forked at:56753b7717Parent branch: origin/master * WIP Forked at:56753b7717Parent branch: origin/master * WIP Forked at:56753b7717Parent branch: origin/master * WIP Forked at:56753b7717Parent branch: origin/master * WIP Forked at:56753b7717Parent branch: origin/master * WIP Forked at:56753b7717Parent branch: origin/master * WIP Forked at:56753b7717Parent branch: origin/master * WIP Forked at:56753b7717Parent branch: origin/master * CLEANUP Forked at:56753b7717Parent branch: origin/master * Remove message broker
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.