The new Polkadot community testnet

I have just posted for discussion the treasury proposal re: the testnet.
As always, any feedback is welcome :slight_smile:

3 Likes

If I understand, we’re test parachain logic and parachain interactions here, but not kusama or polakdot paramaters, yes?

If so, then we could retune the approval checker paramaters, and also make parachains shutdown sometimes. Although very insecure, one extremely light configuration looks like:

num_validators = num_para_validators = 5
backing_group_size = 1  // It's possible this messes up collators
needed_approvals = 1  // Very insecure
num_cores = 10
relayVrfModuloSamples = 2  // = needed_approvals * num_cores / num_validators

We need much heftier parameters if we’re testing polkadot itself of course, but roughly this works if we’re only testing parachain logic, and messaging between parachains. We’ll need much heavier parameters for some parachain to test how effectively they use elastic scaling probably.

You could increase the machine specs too, so then you could increase relayVrfModuloSamples and num_cores, and maybe needed_approvals, but without increasing num_validators too much.

6 Likes

thanks Jeff.
That’s right, the point of the testnet is for parachain logic and interactions.
Protocol testing will happen on Westend.

I’ve made sure the teams managing the runtime / network have seen your post, thanks for the info!

3 Likes

Yeah, that’s a good suggestion - the testnet isn’t going to be economically secure anyway, so we might as well change the parameters to optimize for the number of cores (and therefore simultaneous users) rather than the security of those cores.

3 Likes

Small update on this thread since the network is live :partying_face:, we already started ingesting all the blocks for the Paseo as well as monitor availability of the network.


We’re now working on setting up further monitoring to provide both insights and an overview of the activity on the Paseo testnet, which will certainly give unique early previews of developments and experiments.

We’ll report on these too. :v:


Once this works out we should start figuring out the modalities of the Rococo Testnet Sunset Party to bid Rococo good bye, as this will serve as a prime example of the community working together for the same goal: a reliable and robust community-run test net.

byebyerococo

7 Likes

What’s the status of the Paseo relaychain? When can Polkadot parachains expect to have their testnets onboarded there?

Hi @ntn_x2 and all :slight_smile:
We have setup a twitter account to make it easier to share information - please give it a follow → https://twitter.com/PaseoNetwork

We completed a large runtime upgrade to v1.1.2 just ahead of Polkadot.
The next step for Paseo is to build the runtime for the assethub and get it deployed in the next week.

It’s looking like we will be able to start onboarding parachains in the next 2-3 weeks from now.

We also have a public github board which we’re using if anyone is specifically interested in monitoring the individual details.

4 Likes

Hi all,
A quick update here :slight_smile:
The proposal passed successfully, thanks to all those that voted and especially to those that voted in favour :wink:

We have raised a proposal to set the curators for the bounty - as defined in the original proposal. We welcome your votes → proposal link

Onto progress, we are getting closer to launched the assethub on Paseo, the tentative date is next week.

4 Likes

Hi @Birdo et al.

IIUC, Paseo is accepting validators and parachains already. Would it be possible to compress the onboarding requirements and steps here quickly?

Hi all,
some super exciting news - we have finally launched the asset hub and we are now accepting registration from parachains to migrate from Rococo to Paseo! :tada:

https://x.com/PaseoNetwork/status/1770486799682478504?s=20
It would be great if you can follow our twitter(x) account and engage with this post to increase the visibility for others :eye:

If you’d like to migrate from Rococo Paseo, please see the detail here:
https://github.com/paseo-network/paseo-action-submission/blob/4e14e4cafc6eb97108e0d0b825b139f51e50d02b/pas/PAS-9-Onboard-paras-slots.md

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 Sign in to GitHub · GitHub.

If you are interested in becoming a validator on the network, please see the below steps
https://github.com/paseo-network/paseo-action-submission/blob/4e14e4cafc6eb97108e0d0b825b139f51e50d02b/pas/PAS-1-onboard_infrastructure_providers.md please be aware we are close to being over subscribed for validators, but please register your interest :slight_smile:

Again, please follow the twitter account for more info :brain:

5 Likes

image

An update from the testnet side :slight_smile:

  • We now have onboarded six external parachain teams
    Nodle, Laos Network, POP network, Frequency, Integritee, xcavate

  • The proposal to set the curators passed and we are now taking payout requests for Q1 and Q2. Payouts will start being approved from this week. Please see GitHub - paseo-network/payouts: For raising payout requests for Paseo for more details

  • We are working on shipping the Polkadot v1.2 runtime upgrade

2 Likes