# The new Polkadot community testnet **URL:** \ **Category:** Ecosystem\ **Tags:** digest\ **Created:** [November 28, 2023, 8:50am UTC](https://forum.polkadot.network/t/the-new-polkadot-community-testnet/4956 "2023-11-28T08:50:03Z")\ **Posts on this page:** 13\ **Page:** 2
**Author:** ![Birdo](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/birdo/32/948_2.png) [@Birdo](https://forum.polkadot.network/u/Birdo)\ **Post date:** [January 26, 2024, 11:35am UTC](https://forum.polkadot.network/t/the-new-polkadot-community-testnet/4956/21 "2024-01-26T11:35:23Z")
I have just posted for discussion the treasury proposal re: the testnet. As always, any feedback is welcome 🙂 > **[Paseo - A new testnet for Polkadot](https://polkadot.polkassembly.io/post/2100)** > > Currently, there are two testnets in the Polkadot ecosystem, both being paid for, serviced, and run by Parity: Westend, and Rococo. As a result of the decentralization of Parity, Rococo will be decommissioned in 2024 leaving a gap in Polkadot testnet... ---
**Author:** ![burdges](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/burdges/32/172_2.png) [@burdges](https://forum.polkadot.network/u/burdges)\ **Post date:** [January 26, 2024, 2:24pm UTC](https://forum.polkadot.network/t/the-new-polkadot-community-testnet/4956/22 "2024-01-26T14:24:54Z")
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: ```auto 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. > > > \# Existing \`relayVrfModuloSamples\` don't make too much sense > > Current approval… related values on Polkadot: > \`\`\` > noShowSlots: 2 > nDelayTranches: 89 > zerothDelayTrancheWidth: 0 > neededApprovals: 30 > relayVrfModuloSamples: 40 > \`\`\` > > relayVrfModuloSamples should be way less. With 200 valdiators and 40 parachains it should be around 6. > > \# Existing parameters don't make too much sense > > What is a good number for \`relayVrfModuloSamples\` depends on the number of validators and parachains. This parameter would need to be adjusted on any change in those numbers. It would be better to make \`relayVrfModuloSamples\` a function of those parameters and a different paramer to fine tune this relationship. > > \# Further tuning > > For our threat model it should be sufficient to have around 30 approvals in expectation. Therefore it might be sensible to reduce the number of \`neededApprovals\` a bit to avoid higher tranches kicking in too often to cover for variation. This might be helping in reducing load on approval voting. Other strategies like increasing the tick value should be done first though. > > \# Tasks > > \- \[x\] Pass motion on Kusama and Polkadot to reduce \`relayVrfModuloSamples\` to something more sensible. > \- \[\] Make sure whenever we are increasing \`maxValidators\` or the number of cores we also adjust \`relayVrfModuloSamples\` accordingly. > \- \[\] Make the second task obsolete by replacing \`relayVrfModuloSamples\` config with a tuning knob and derive the actual value based on that and the number of validators and parachains/cores. > > @Sophia-Gold > @burdges - expected variance would be interesting. > @sandreim ---
**Author:** ![Birdo](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/birdo/32/948_2.png) [@Birdo](https://forum.polkadot.network/u/Birdo)\ **Post date:** [February 1, 2024, 9:43am UTC](https://forum.polkadot.network/t/the-new-polkadot-community-testnet/4956/23 "2024-02-01T09:43:39Z")
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! ---
**Author:** ![rphmeier](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/rphmeier/32/126_2.png) [@rphmeier](https://forum.polkadot.network/u/rphmeier)\ **Post date:** [February 2, 2024, 9:39pm UTC](https://forum.polkadot.network/t/the-new-polkadot-community-testnet/4956/24 "2024-02-02T21:39:41Z")
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. ---
**Author:** ![Karim](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/karim/32/11334_2.png) [@Karim](https://forum.polkadot.network/u/Karim)\ **Post date:** [February 9, 2024, 4:33pm UTC](https://forum.polkadot.network/t/the-new-polkadot-community-testnet/4956/25 "2024-02-09T16:33:51Z")
Small update on this thread since the network is live 🥳, we already started ingesting all the blocks for the Paseo as well as monitor availability of the network. ![paseo_ingest](https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/9/9e3b526b0c3fcd935f39e0f14ae580f2573a69aa.png) 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. ✌ * * * 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](https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/b/b116694c351827000bd34a0e9b81f9fcf982d4ed.png) ---
**Author:** ![ntn\_x2](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/ntn_x2/32/167_2.png) [@ntn\_x2](https://forum.polkadot.network/u/ntn_x2)\ **Post date:** [February 20, 2024, 11:20am UTC](https://forum.polkadot.network/t/the-new-polkadot-community-testnet/4956/26 "2024-02-20T11:20:20Z")
What’s the status of the Paseo relaychain? When can Polkadot parachains expect to have their testnets onboarded there? ---
**Author:** ![Birdo](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/birdo/32/948_2.png) [@Birdo](https://forum.polkadot.network/u/Birdo)\ **Post date:** [February 23, 2024, 10:48am UTC](https://forum.polkadot.network/t/the-new-polkadot-community-testnet/4956/27 "2024-02-23T10:48:09Z")
Hi @ntn_x2 and all 🙂 We have setup a twitter account to make it easier to share information - please give it a follow → [https://twitter.com/PaseoNetwork](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. > **[Paseo board • paseo-network](https://github.com/orgs/paseo-network/projects/1/views/1)** > > Paseo board ---
**Author:** ![Birdo](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/birdo/32/948_2.png) [@Birdo](https://forum.polkadot.network/u/Birdo)\ **Post date:** [March 6, 2024, 3:11pm UTC](https://forum.polkadot.network/t/the-new-polkadot-community-testnet/4956/28 "2024-03-06T15:11:24Z")
Hi all, A quick update here 🙂 The proposal passed successfully, thanks to all those that voted and especially to those that voted in favour 😉 We have raised a proposal to set the curators for the bounty - as defined in the original proposal. We welcome your votes → [proposal link](https://polkadot.polkassembly.io/referenda/553) Onto progress, we are getting closer to launched the assethub on Paseo, the tentative date is next week. ---
**Author:** ![WilliamFreude](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/williamfreude/32/168_2.png) [@WilliamFreude](https://forum.polkadot.network/u/WilliamFreude)\ **Post date:** [March 21, 2024, 4:47pm UTC](https://forum.polkadot.network/t/the-new-polkadot-community-testnet/4956/29 "2024-03-21T16:47:47Z")
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? ---
**Author:** ![Birdo](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/birdo/32/948_2.png) [@Birdo](https://forum.polkadot.network/u/Birdo)\ **Post date:** [March 22, 2024, 9:21am UTC](https://forum.polkadot.network/t/the-new-polkadot-community-testnet/4956/30 "2024-03-22T09:21:24Z")
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! 🎉 [https://x.com/PaseoNetwork/status/1770486799682478504?s=20](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 👁 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](https://github.com/paseo-network/support) for that, they can use the custom issue template in [Sign in to GitHub · GitHub](https://github.com/paseo-network/support/issues/new/choose). 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 🙂 Again, please follow the twitter account for more info 🧠 ---
**Author:** ![Birdo](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/birdo/32/948_2.png) [@Birdo](https://forum.polkadot.network/u/Birdo)\ **Post date:** [April 8, 2024, 2:07pm UTC](https://forum.polkadot.network/t/the-new-polkadot-community-testnet/4956/31 "2024-04-08T14:07:01Z")
![image](https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/2/27ff51a35e09795f232de37920071c161fc39a4a.jpeg) An update from the testnet side 🙂 - 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](https://github.com/paseo-network/payouts) for more details - We are working on shipping the Polkadot v1.2 runtime upgrade ---
**Author:** ![RustSyndicate](https://avatars.discourse-cdn.com/v4/letter/r/f19dbf/32.png) [@RustSyndicate](https://forum.polkadot.network/u/RustSyndicate)\ **Post date:** [April 27, 2024, 12:32pm UTC](https://forum.polkadot.network/t/the-new-polkadot-community-testnet/4956/32 "2024-04-27T12:32:51Z")
@Birdo Been sending some xcm messages with Paseo today, works good. is there any block explorers that currently supports Paseo? Is Subscan going to support Paseo in a soonish future? ---
**Author:** ![Birdo](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/birdo/32/948_2.png) [@Birdo](https://forum.polkadot.network/u/Birdo)\ **Post date:** [April 29, 2024, 9:53am UTC](https://forum.polkadot.network/t/the-new-polkadot-community-testnet/4956/33 "2024-04-29T09:53:38Z")
gm, the paseo relay chain is already supported in subscan → [https://paseo.subscan.io/](https://paseo.subscan.io/) [Previous page](https://forum.polkadot.network/t/the-new-polkadot-community-testnet/4956.md?page=1)