Polkadot Deployment Portal: May Update
Summary
We’re back! The latest edition of the PDP monthly updates is finally here and we’re pleased to bring you all the latest updates, developments and alpha from the PDP team. If you’ve not read the previous editions, check them out here and here.
The PDP is a new 1 Click Deployment solution for Polkadot that will revolutionize how you deploy a rollup on Polkadot.
Recap
In the previous edition of the PDP monthly update, the team took huge strides in development. We announced the PDP x POP CLI Integration, where the PDP can now utilise Pop CLI’s local rollup-building capabilities. Read more about the full integration here.
Not only this, but the PDP deployed the ‘pararegistration’ proxy, a completely new type of proxy built specifically by the PDP team. Approved and merged by the fellowship, this new type of proxy allows for seamless rollup deployment to all networks.
From UX improvements, talks and even beta testing, quite a bit was covered in the previous month’s edition of the PDP update. This month, once again, the team made huge improvements, from solving critical coretime issues to receiving the first of many feedback suggestions from our first cohort beta testers.
Beta Testing
Beta Testing is taking off, with now a full cohort of testers deploying their own rollups on Paseo and Westend. Our first beta testers had this to say,
“So far it’s amazing and a huge, huge step forward from anything we currently have”
“From what I’ve tested this is definitely better…Im generally a fan of SaaS and believe that this will make it much easier to deploy”
At first glance, the PDP has had quite the impression, as the testers are realising how easy it has become to launch a rollup on Polkadot. The team is building a product that abstracts the complexity of signing multiple transactions, simplifying rollup deployment to what it should be, 1 simple click.
The magic in action
Once you’ve hit sign & deploy, the following onboarding screen will be showcased, showing all the stages, step by step, from start to finish.
The PDP takes care of everything, including the acquisition and assigning of coretime.
Once ready, your rollup will appear in the rollup screen, where you can manage and view all your deployments, on all networks.
We’re always looking for contributors and testers to help provide valuable feedback and data for the PDP. Whether it be from the process itself, to UX or DevX related testing, we want to hear from you. If you’re interested in becoming a beta tester, sign up here.
Coretime Auto-Renewals
The engineers on the PDP team have been working on solving current issues that are facing the ecosystem. With the PDP, teams will not only be able to just launch and rollup, acquire coretime and deploy to Polkadot, they’ll also be able to keep their rollup live and producing blocks with PDPs Auto Renewal UI and Checklist.
This interactive guide, which is currently undergoing internal development and testing, assists parachain developers in setting up coretime auto-renewal once they’ve upgraded to a full core.
Omni-Node Support
The PDP now fully supports the omni-node! If you’re unsure of what the omni-node is, then check out the official Polkadot Documentation which explains it here. With this addition, the PDP will abstract away the runtime development from the node development, opening the gates for a multitude of more integrations in the future with runtime developers.
Monorepo Migration
The PDP has now migrated to a monorepo format, a huge piece of effort and milestone completed by the hardworking devs in the PDP team. The migration, whilst a heavy backend change, has allowed the team to be more efficient and thorough with their E2E Testing, alongside many other benefits.
E2E Testing
The E2E Testing, with many thanks to the monorepo, has been running smoothly and phase 1 is now finally completed. The PDP can now test run the first critical steps into deploying a rollup, from user interaction with the front end to deployment, overall dramatically improving the robustness of the entire system. Phase 2 of the E2E testing is currently being designed and testing should begin shortly.
AHM on Westend
Polkadot achieved a huge milestone last week, with the completion of the AssetHub Migration on the Westend network, one of Polkadot’s testnets. With the migration, key user functionalities such as Staking, Governance (Including Treasury) and Balances are being migrated onto Polkadot’s AssetHub, minimising the workload on the relay chain. For more information about the upcoming migrations and timeline, check out this forum post here.
The PDP team successfully built a solution compatible with this new account paradigm, ensuring that beta testing will face little to no issues.
OnDemand Coretime Buyer
The PDP team, in conjunction with the W3F have worked on developing an OnDemand coretime buyer where teams can continue to advance their chain even if they cannot yet purchase coretime in bulk.
The initial iteration is based on size of the transaction pool and how much time the rollup has gone without producing blocks. If you’d like to give it a test and provide feedback, then please get in touch and check out the repository here.
We’d also like to give @bader from the W3F a huge shoutout for this, without him this would not have been possible.
Conclusion
May was a big month for the team, with multiple areas developing in parallel. The beta testing is going smoothly, the ideas are incoming and the development of the tool is progressing nicely. We’re doing what we can to accelerate development to bring the PDP to teams sooner rather than later and break down that barrier teams would usually face.
That’s it for this month’s update, if you have any questions or want to learn more about the product, feel free to comment or get in touch with the team.
PDP Telegram
Want to chat 1-1?
Email: Remy@Parity.io
TG: @Remy_LeBerre
Check out the PDP X account too! 
https://x.com/PolkadotDeploy
A thank you to the team
This post was a collaborative effort from the Parity PDP, Product Strategy and Data teams, huge kudos to all who contributed their time between development to help write this article, provide updates and add content to this May monthly update.