Skip to content

Latest commit

 

History

History
47 lines (36 loc) · 2.76 KB

PAS-9-Onboard-paras-slots.md

File metadata and controls

47 lines (36 loc) · 2.76 KB
PAS title status author created
9
Onboarding Parachains - Slots
Proposed
Alejandro (@al3mart)
27-02-2024

Changelog

Version Description Author Date
1.0 Initial version @al3mart 12-03-2024

Summary

Means to onboard a parachain to Paseo via leases and slot assignment. This PAS is to be deprecated once parachain scheduling via coretime is deployed in Paseo.

Abstract

In this document users can find the steps to follow to register their parachain in Paseo.

  • Maintainers of a live parachain in Polkadot or Kusama will be granted a slot in Paseo for 1 year long.
  • Maintainers of parachains in development, or those that have not yet secured a slot in Kusama or Polkadot, will be assigned a lease for a shorter period of time: 2 weeks long.

Motivation

At the moment of writing there is no way a user without access to root origin can get their parachain's block finalised by Paseo.

Specification

Overview

Users can do a regular registration via dispatching the extrinsics registrar.reserve to reserve a ParaId and registrar.register to submit their code and state. To obtain a slot for your parachain, aka upgrading your parathread to a parachain, users can log an issue in Paseo's support repository for that, they can use the custom issue template in https://github.com/paseo-network/support/issues/new/choose. This might be handy in case the root action is needed in the relay chain, for instance. Users can always open an issue in case their desired ParaId is < 4000. Resources will be assigned as long as the network is not at capacity. This depends on the number of validators supporting the network. For this test environment we work with the assumption that there should always be at least 2 validators per parachain running in the network.

_If you are willing to support the network, please see PAS#1.

Rationale

The onboarding process is bounded by the resources available in the network. Meaning that we will prioritize parachains that are already live and need a testbed for their users, while trying to maintain a healthy ratio of teams that just need sporadic resources from Paseo. Teams having secured a slot in either Kusama or Polkadot will receive leases for the duration of 1 year. Teams that have not yet secured a slot in the above mentioned relay chains, will receive leases for at most two continued weeks at a time.

Copyright

Copyright and related rights waived via CC0.