PAS0044: Onboarding Parachains - Slots

paseo-network / paseo-action-submission

Paseo Tesnet - RFCs

4 stars 38 forks source link

PAS0044: Onboarding Parachains - Slots #44

Closed al3mart closed 7 months ago

al3mart commented 8 months ago

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

Closes #11

al3mart commented 8 months ago

Thanks for the review @ltfschoen!

hbulgarini commented 8 months ago

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 commented 8 months ago

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

al3mart commented 8 months ago

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.

itsbirdo commented 7 months ago

@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 commented 7 months ago

Could we get this approved in parallel ?

https://github.com/paseo-network/support/pull/23
https://github.com/paseo-network/support/pull/24 @itsbirdo @hbulgarini @carlosala

al3mart commented 7 months ago

@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.