PAS0044: Onboarding Parachains - Slots

[al3mart]

PAS Proposal pointing the details of onboarding a parachain to Paseo.

Closes #11

[al3mart]

Thanks for the review @ltfschoen!

[wilwade]

Two notes around length of slots, but otherwise appears straightforward and easy to follow.

[hbulgarini]

As per internal discussion in the Paseo core team we are determining that parachains on Paseo that are testing the protocol will have the lease for 2 weeks. Then parachains already active on Polkadot/Kusama will have a longer period of 1 year.

Of course all this will be revisited soon with coretime.

[hbulgarini]

@al3mart please proceed with the changes requested so we can merge this one.

[al3mart]

Feedback has been addressed.

As per the conversations we had and until on-demand scheduling arrives to Paseo; 1 year worth of LPs will be assigned to teams who have a live network running in either Kusama or Polkadot, and at most two weeks worth of LPs to teams who don't have their parachains running live yet.

[wilwade]

Looks good to me. One optional text cleanup.

[itsbirdo]

@hbulgarini I still believe we should offer 30d not 14d for new slots. Less overhead for the teams and 14d extra doesn't hurt us really imo

[al3mart]

Could we get this approved in parallel ?

• feat(para-onboard): para onboarding template support#23
• fix(onboard-paras): name should be a string support#24
  @itsbirdo @hbulgarini @carlosala

[al3mart]

@hbulgarini I still believe we should offer 30d not 14d for new slots. Less overhead for the teams and 14d extra doesn't hurt us really imo

I don't see why we shouldn't allow for longer runs while the network has capacity for it.