Rococo
- repository: https://github.com/paritytech/polkadot-sdk
- chain specs: https://raw.githubusercontent.com/paritytech/polkadot-sdk/master/polkadot/node/service/chain-specs/rococo.json
Goals
- Community Parachain testnet environment
- XCM Playground for Parachains and Dapps on Parachains
Features
-
parachains: Parachains can register on Rococo
-
governance: Modules are available, however not used
-
auctions / crowdloans: Both modules available, however not used
-
XCM: XCM v2 available on Rococo
-
staking: Modules are available, however not used (POA System)
-
assigned_slots pallet: Parachains need to register using this pallet
Expectations
- parity: Run the nodes for the system; keep the system updated (runtime and nodes) in line with Kusama updates; manage parachain onboarding (see contacts)
- community: Keep parachain updated; onboard their builders into their rococo parachain for testing; make the most out of XCM
Chain information
Property | Value |
---|---|
network type | testnet |
chain type | relaychain |
sudo | true |
decimals | 12 |
block time | 6 seconds |
token | ROC |
ED | 33333333 units |
consensus | PoA |
Validators
- Parity Only
RPC Endpoints
- Parity:
wss://rococo-rpc.polkadot.io:443
API Endpoints
- subscan:
https://rococo.api.subscan.io
Bootnodes
No Bootnode found
Release Cycle
Following the Polkadot 3 weeks cycle
Contacts
- website:
https://github.com/paritytech/subport
Faucet
A faucet can be found at: #rococo-faucet:matrix.org
Documentation:
Notes
Rococo is a community relay chain, to allow everyone to test it is functionality. Different stages of parachains have different needs, and Rococo tries to accommodate to these as best as it can. Two type of parachain slots exist on Rococo: Long Lasting slots and Short term slots. As long as a project has a parachain on either Kusama or Polkadot, they are entitled to having a parachain on Rococo, running besides it. This allows for all production chains to have a testing bed, as well as to onboard the projects working on their chains. If a project does not have a production parachain, then they will be assigned a short lease slot, which allows them to test the parachain functionality and still give room for everyone to test out
Rococo does not replace local testing for projects. This is always encourage for fast iterations and comprehensive testing for teams. In Rococo teams should test more cross-chain functionality with other teams, and allow developers to test the infrastructure as well
Last updated: 2024-01-03 16:18 - commit 7af9b4c7…