Polkadot JS Roadmap Update - BlockDeep

Ecosystem
1

Polkadot JS Roadmap Update - BlockDeep

Hello again from the BlockDeep team!

This is Part 2 of our Polkadot JS Updates. In our previous update we delved into what we have been working on so far on PJS, and some of the new features we have implemented.

In this update, we’d like to share a few feature ideas, and an initial roadmap we’re exploring. Our goal is to gather feedback from the community to help us guide the direction of PJS development:

The Road Ahead

Maintenance and Support

We will continue to provide regular maintenance and support to the entire Polkadot JS suite of tools and libraries, and this includes:

  • Updates to API and Developer Interface based on Polkadot SDK releases
  • Bug fixes and stabilization
  • Regular audits and addressing any reported security issues
  • Continuous releases and documentation

Enhancements

In addition to regular support and maintenance of Polkadot JS codebase, we will continue to improve it with new features and enhancements. To begin with, we are proposing the following new features for the Developer Interface and API:

Proposed Features

  1. :magnifying_glass_tilted_left: Event Filtering by Account (Developer Interface)
    Right now, the explorer shows all events, making it hard to find those tied to your own accounts. We’re proposing an optional toggle to filter events to only those involving user accounts registered on its PolkadotJS instance. This would improve readability and reduce noise, specially for devs that are testing on active chains where finding a specific event can become a hassle.

  2. :star: Favorite chains (Developer Interface)
    Navigating to a specific parachain currently requires diving through its relay chain and scrolling through the list of parachains which can be tedious for users who regularly switch between chains. We’d like to introduce a way to mark favorite chains for quick and easy access.

  3. :globe_with_meridians: Simplified Chain Endpoint Selection (Developer Interface)
    Selecting an RPC endpoint can be confusing for new users, who may not understand what it is or which one to use. To improve usability, we’re proposing automatic selection of a rotating default endpoint from a pool of reliable public nodes. This avoids overloading a single provider and helps prevent centralization. Advanced users will still be able to manually choose their preferred endpoint via a dropdown.

  4. :counterclockwise_arrows_button: Teleport Feature Enhancement (Developer Interface)
    While Asset Hub (AH) is expected to play a central role in most activities post–AH migration, teleporting of assets from AH still only supports the Relay Chain as a destination. This feature aims to expand support to additional system parachains, such as People, BridgeHub, and others, enabling smoother teleport UX across these chains.

  5. :bellhop_bell: Notification Panel (Developer Interface)
    We’re proposing a new notification panel in the navigation bar to improve visibility into recent transactions. It would display basic details like transaction type, status, and a clickable block number or hash. Toast notifications would also include links to the relevant block, making it easier for users to track their activity (especially on chains without Subscan support).

  6. :fountain_pen: Multisig Tab (Developer Interface)
    Multisig approval requests are currently shown via a small pink icon, which can be easy to miss. We’re proposing a dedicated Multisig tab under the Accounts page, serving as a centralized area to review and act on pending multisig transactions more clearly.

  7. :blue_book: Interactive Developer Docs for Custom Chains (API)
    We’re building a tool that lets you generate interactive documentation for your chain to make it easier for developers to understand how to use the chain specific types. It’s often unclear what values need to be passed into extrinsics, RPC calls, or runtime APIs, especially when dealing with custom types. While importing the api-augment package and setting up ESLint helps with type hints, it still doesn’t show how a parameter should be structured. This new functionality will spin up an interface (via CLI) for any given chain, displaying all extrinsics, runtime APIs, events, etc. and their parameters, along with mock data for each call.

Cleanup and Deprecation

An important part of the maintenance process is cleanup, refactoring, and deprecation of features that are not being used as intended, or not needed anymore. In light of this, we have identified the following areas of codebase that could be deprecated:

:atom_symbol: Electron App Deprecation: :red_exclamation_mark:Community Feedback Wanted

The Electron version of the Polkadot JS UI hasn’t seen much usage, and maintaining it can require ongoing effort (especially around security) that could instead be spent on developing or improving features like the ones proposed above. We’re considering phasing out active support for Electron, but we want to hear from the community first: Is it still useful to you? Your feedback will help us decide whether it’s worth continuing to maintain.

Call for Feedback

We’re excited to help improve Polkadot JS, but we want to build it with the community. Let us know which of these features resonate with you, or if there’s anything else you’d want to see added. Your input is essential in helping us make Polkadot JS better for everyone.

If you would like to share specific feedback, please feel free to post it on Twitter/X and tag us @0xBlockDeep, OR you can send it to info@blockdeep.io with subject line “Polkadot JS Feedback”.

-BlockDeep Team

5 Likes