Rhythm BlockBeats news, Polkadot testnet Rococo v1 releases parachain registration guidelines. When the network seems to be able to expand smoothly, Rococo will register parachains on a first-come, first-served basis. After the initial test of Rococo is successful, in the long run, Rococo will be integrated into the Westend test network.
p>
In order to improve the Los Rococo network quickly, the network will be updated and restarted regularly. This usually involves updates to the client and runtime code and resets of the chain state. Initial parachains go live every few days, and new parachains are only added when the network is running stably. During times of instability, Rococo may unregister parachains to reduce the load on the network, with the intention of re-registering these parachains after stability improves. When the network seems to be able to scale smoothly, parachains will be registered on a first-come, first-served basis.
Any parachain candidate participates in parachain registration The minimum requirements for the process are as follows:
1. Maintain at least one Rococo V1 validator
2. Maintain at least one parachain proofreader
3. Register through the Rococo V1 parachain registry ( https://forms.gle/Eacp7RaRm3VNion16 )
1. Maintain at least one validator (full block authority node) for the central Rococo relay chain https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frococo- rpc.polkadot.io#/explorer
a. Think of it as a Polkadot production node - see Running a Validator ( Polkadot)
b. Node Settings - Use one of the following options
i. Build from source:
1. git clone https://github.com/paritytech/polkadot
2. cd polkadot
;git checkout master
4. cargo build --release --features=real-overseer
5. ./target/release/polkadot --validator --chain rococo --name <your_rococo_validator_name>
ii. Using Docker:
1.  ;docker run -d parity/rococo:<tag_following_polkadot> --validator --chain rococo --name <your_rococo_validator_name>
c. generate your key
i. PolkadotJS-Apps connected to your validator node
ii. connected to your CLI of validator node
d. submit setKeys transaction
i. this ROC tokens will be required, you should have received ROC tokens sent to the Rococo address you registered on the github Rococo V1 parachain ( https://forms.gle/Eacp7RaRm3VNion16 )
e.   ;Check your node on Rococo Telemetry (https://telemetry.polkadot.io/)
f. Focus on the Rococo validator lobby Regarding the announcement of the Rococo V1 validator update, it may require one of the following scenarios
i. Update the client
ii. Update client and clear chain
2. Maintain at least one collator (full block authorization node) for the team's parachain
a.cd <root_cumulus_based_parachain_code>
b.cargo build --release
c. ./target/release/<parachain_collator_name> --version
d../target/release /<parachain_collator_name> export-genesis-state --parachain-id <your_registered_parachain_id> > genesis-state
e../target/release/< ;parachain_collator_name> export-genesis-wasm > genesis-wasm
f../target/release/<parachain_collator_name> --collator --parachain-id <your_registered_parachain_id> --execution wasm --chain rococo
3. Register through the Rococo V1 parachain registry ( https://forms .gle/Eacp7RaRm3VNion16 )
4. After receiving the ROC to the ValidatorId address, start submitting setKeys outside Rococo Transaction
5. Actively track the registration process: https://github.com/substrate-developer-hub/cumulus-workshop/blob /master/6-register/1-register.md#request-parachain-registration
< a href="https://mp.weixin.qq.com/s/RhxMFZtd7O_BcAm0iZbSHQ" target="_blank">Original link
Welcome to join the official BlockBeats community:
Telegram Subscription Group: https://t.me/theblockbeats
Telegram Discussion Group: https://t.me/BlockBeats_App
Official Twitter Account: https://twitter.com/BlockBeatsAsia