Polkadot-JS: Moving Forward Table of Contents Summary Intro About Myself Goals & Overview Priorities Releases & Documentation Issues & Bugs Features & PR’s Delegation & Organization Conclusion Special Thanks Summary Over the past few years, the Polkadot ecosystem has thrived with critical suppo…

Hey @kianenigma , as for making interaction with XCM easier, consider to check out our XCM tool set. There are tools such as XCM SDK, XCM API and even XCM Router. We have playground for the tools deployed live so each tool can be tested easily. Feel free to explore more here: [image] GitHub …

Great to hear @Tarik , all the best with it! Further to Kian’s comment, I’ve just made an issue to get the ball rolling on the discussion about adding coretime views here

[image] kianenigma: Provide one new package that is meant to make the process of building multichain scenarios easier, such as @polkadot/multichain or similar. The current mode should be mainly on maintenance and easy fixes. Something like this should not be done anymore on polkadot-js. Shiny…

[image] bkchr: I also think that there should be some new developer console that directly builds on top of polkadot-api as well. Branded as developer console from the beginning. This is a key requirement, without a complex app like a developer console using the API is very difficult to adapt …

Thanks for taking the lead and great post @Tarik , I’m glad you’ll still welcome external contributors. I’m familiar with these codebases and I have availability these days to contribute to their open-source maintenance. I agree that it’s very important for the issues to be well defined to help inb…

Thank you all for the support! It means a lot. I am sure we will need all the help we can get as the wheels start turning. I had a few necessary days off to recalibrate, and reset in the mountains and now I am ready to get the engine fully running for this endeavor. Things I have on the immediate l…

[image] bkchr: The current mode should be mainly on maintenance and easy fixes. Something like this should not be done anymore on polkadot-js. Shiny new stuff should be build on top of polkadot-api from @josep and co. I generally agree, but correcting things that are obviously a mistake (eg. …

Good to hear @Tarik . I would love to contribute to the tooling side :smiley: also if you could add good first issue label to the repos mentioned above, that will be great :rocket:

[image] tbaut: but you can count on me to help on the extension front It would be amazing if you could please look into this :pray: I could provide a lot more context than what’s in the issue :slightly_smiling_face:

Polkadot-JS: Moving Forward

Tech Talk

josep February 26, 2024, 1:27pm 18

Likewise

Topic		Replies	Views
Polkadot JS Progress Update & Moving Forward - BlockDeep Tech Talk	2	579	November 28, 2025
Polkadot JS Roadmap Update - BlockDeep Ecosystem	6	573	July 24, 2025
Decentralized Futures: Ecosystem DevRel Team for Polkadot by PaperMoon Ecosystem decentralized-future	12	1645	March 8, 2024
Polkadot JS Apps messaging & rebranding thoughts Ecosystem	28	1553	April 15, 2023
Decentralized Futures Proposal: Polkadot Cloud - dApp UI Library and Platform Ecosystem ux , decentralized-future	11	1520	March 10, 2024

Polkadot-JS: Moving Forward

Related topics