# 🛠️ chainconsole.com - Polkadot JS Apps Fork with Bug Fixes and Improvements **URL:** \ **Category:** Ecosystem\ **Tags:** ux\ **Created:** [March 13, 2026, 1:34pm UTC](https://forum.polkadot.network/t/chainconsole-com-polkadot-js-apps-fork-with-bug-fixes-and-improvements/17313 "2026-03-13T13:34:05Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![kukabi](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/kukabi/32/181_2.png) [@kukabi](https://forum.polkadot.network/u/kukabi)\ **Post date:** [March 13, 2026, 1:34pm UTC](https://forum.polkadot.network/t/chainconsole-com-polkadot-js-apps-fork-with-bug-fixes-and-improvements/17313/1 "2026-03-13T13:34:05Z")
## Background Polkadot JS Apps has always been **one of the key tools** for me in the Polkadot ecosystem, alongside [Multix](https://multix.cloud) and the [Polkadot JS signer extension](https://chromewebstore.google.com/detail/polkadot%7Bjs%7D-extension/mopnmbcafieddcagagdcbnhejhlodfdd). The application has been **in maintenance mode or worse for quite a while now** , and I’ve also been noticing multiple complaints in the community regarding **bugs, non-functional endpoints, and unmerged pull requests.** Following my shared frustration with persistent issues, **I decided to fork it, fix it, and launch it at [chainconsole.com](https://chainconsole.com)** in an effort to scratch my own itch, just as I did with Multix ([post #1](https://x.com/kukabi_/status/2013581524981956874), [post #2](https://x.com/kukabi_/status/2014003096997749247)) in January. I’ll share a Multix product update post later on, also news regarding Submerge, and other new projects, but today I’ll share with you the [Chain Console](https://chainconsole.com) updates. ## Bug Fixes & Improvements ### RPC Endpoint Fixes and Improvements One of the pain points of the application has been **non-responsive RPC endpoints**. There is a [GitHub action](https://github.com/polkadot-js/apps/blob/6ee42f5a3c418370e83a3c34e841a98e57e47a20/.github/workflows/chain-endpoints.yml) that checks endpoint liveness on the original repository. It creates GitHub issues as a report of its findings, but as can be seen on the [open issues list](https://github.com/polkadot-js/apps/issues), the piling results haven’t been taken care of. To fix this, I changed the endpoint model to include an availability flag ([c3291cf](https://github.com/helikon-labs/chainconsole/commit/c3291cfb14891b9a534eb937cab87d05d816d978)), so that an endpoint can be marked unavailable without removing it or commenting it out, and developed **a new [script](https://github.com/helikon-labs/chainconsole/blob/fee5447d4b57864dd4f9d216e3397184b4fb5eca/packages/apps-config/src/ci/updateEndpointAvailability.ts) that checks the endpoints twice every day in an [action](https://github.com/helikon-labs/chainconsole/blob/fee5447d4b57864dd4f9d216e3397184b4fb5eca/.github/workflows/update-endpoint-availability.yml), updates endpoints in the source code, and submits a [pull request](https://github.com/helikon-labs/chainconsole/pull/17).** While the older [script](https://github.com/polkadot-js/apps/blob/6ee42f5a3c418370e83a3c34e841a98e57e47a20/packages/apps-config/src/ci/chainEndpoints.spec.ts) only checked the available endpoints, the improved script checks all endpoints and toggles their availability in the source code. This allows **previously unavailable endpoints to become available again** if they pass the liveness test. Another improvement is that the RPC endpoint dropdown now **displays unavailable endpoints as disabled** rather than removing them altogether. This way, both users and RPC providers can view the complete set of endpoints registered for a chain. ![enabled and disabled RPC endpoints](https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/1/1821131a5bbfe9ac63fe075434e288d8bfe80be6.png) Chains with no available endpoints are not displayed, a decision that will be revisited. The commits related to these changes are [c3291cf](https://github.com/helikon-labs/chainconsole/commit/c3291cfb14891b9a534eb937cab87d05d816d978), [a87f630](https://github.com/helikon-labs/chainconsole/commit/a87f6300592cd517ef222358d968f0bc4a2d9745), [a4b1a90](https://github.com/helikon-labs/chainconsole/commit/a4b1a90b5a83d3abb3f4ecbac2bbda192a2f49ea), [0fbecd5](https://github.com/helikon-labs/chainconsole/commit/0fbecd5cff473e728a2d40a35a725afdae640786), [a05e445](https://github.com/helikon-labs/chainconsole/commit/a05e445f908f88f804423e7ccc0d608e547d6eb3), [675e53d](https://github.com/helikon-labs/chainconsole/commit/675e53d5cd1e22e0599d0ce6d56464c64c0f295e), [34134aa](https://github.com/helikon-labs/chainconsole/commit/34134aa5d3576558479b011a602d8d73a90304b2), [da2fa8d](https://github.com/helikon-labs/chainconsole/commit/da2fa8d848347d787414fce240c199207eff41c2), [7bacaa6](https://github.com/helikon-labs/chainconsole/commit/7bacaa6f56a97c4fd52b13cd08524d9d89bcba8a), [7707705](https://github.com/helikon-labs/chainconsole/commit/7707705ecd063b7b6055c961ca84b939c5a4bbc0), and a couple more. ### Account Details Side Panel Fixes The account details side panel that opens up when an account is clicked had **a number of UI issues.** These were fixed ([a7124d9](https://github.com/helikon-labs/chainconsole/commit/a7124d955b2569ea6276e053b9f8ca931bdc7ae4), [0c2dab0](https://github.com/helikon-labs/chainconsole/commit/0c2dab039ebfb55256bfe867816c87a9af00168e), [6a725ba](https://github.com/helikon-labs/chainconsole/commit/6a725ba07a0208a14791d8df4653b247f51f2592)) as illustrated on the screenshots below. | ![account details side panel UI issues](https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/b/bef4372d02946132d1e52c95b6dff7f0311ce3ee.png) | ![account details side panel UI fixes](https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/2/2fe0d36e54df064c0c45e096b5e273d1e90f8415.png) | ### Unbonding Time Fix for Asset Hubs The pop-up box that shows time left in unbonding on both the main accounts and staking accounts pages **incorrectly displayed an era overdue warning, and also sometimes displayed the wrong time left in the unbonding period.** I found out that this is due to the `session.progress` derive of the Polkadot JS API not always working correctly on Asset Hubs. Also, a mechanism in the application that identifies the block time incorrectly utilizes a 12-second block time on Asset Hub, where it needs to apply the 6-second block time on the relay chain. This also caused the _ **Withdraw Unbonded** _ button to appear prematurely. These were fixed with [f0d03b1](https://github.com/helikon-labs/chainconsole/commit/f0d03b1cec75d017803e906d32cba531c3740dee) as illustrated in the screenshot below. I will be further working on this issue to refine the solution. | ![incorrect era overdue warning](https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/9/9168e50f17c47db580a6627ba8442e02fd5a75d0.png) | ![correct remaining unbonding time](https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/8/87f28c9083448bb972ff4f8b44149573bda9880c.png) | ### Era Remaining Time Fix for Asset Hubs Stemming from the same root cause as the previous issue, **the remaining time for the staking era displayed incorrectly** for Kusama and Polkadot Asset Hubs. This was fixed with [6ba0293](https://github.com/helikon-labs/chainconsole/commit/6ba029365b7e8a9ebb3056e9a9d8b791e6928eff), as illustrated below. | ![incorrect remaining era time](https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/a/abc684a5dd7cc33a9cb6cb8a25c50d78a32ca9a1.png) | ![correct remaining era time](https://europe1.discourse-cdn.com/flex005/uploads/polkadot2/original/2X/f/f22179434b735deafb6fa828857a3857d0808d6d.png) | ### Removal of Unused Chain Resources The build processes revealed several unused resources for removed chains. These were removed in commits such as [0b6c00a](https://github.com/helikon-labs/chainconsole/commit/0b6c00ae4b6cf45bfb460db20aeeba7bf72478a7) and [2b34f7a](https://github.com/helikon-labs/chainconsole/commit/2b34f7a576b22f6538113430676abcc0b6f10076) to **clean up the code base** and keep it up-to-date. ### Fix Failing Tests for `typesBundle` and `chainTypes` These tests were excluded from the [main test command](https://github.com/polkadot-js/apps/blob/6ee42f5a3c418370e83a3c34e841a98e57e47a20/package.json#L64). They got fixed with [f3c77db](https://github.com/helikon-labs/chainconsole/commit/f3c77db9cde648ad2170e7c63305ca20e1f40ad5) and [ef2c605](https://github.com/helikon-labs/chainconsole/commit/ef2c605c19fcfd479c0928cddfbc1c3bad8cb948), and are [now included](https://github.com/helikon-labs/chainconsole/blob/fee5447d4b57864dd4f9d216e3397184b4fb5eca/package.json#L49), expanding the coverage of the main test command. ### Add Missing Icons for Several Chains Polkadot Coretime, and Westend Collectives, Coretime, and Penpal chains were missing icons on the original deployment. These were **assigned icons** , and they now display correctly on [Chain Console](https://chainconsole.com). ## A Leaner Direction Maintainability of an application depends a lot on **careful scope limitation and preventing feature bloat.** I made the decision to remove a number of relatively minor or dormant features to simplify the application. Here is the list of the **features removed** so far: - **Event Calendar:** Displayed important network events. Yet on the original deployment it looks almost empty, and I would guess that this feature could better be implemented in a separate application. ([64d03a1](https://github.com/helikon-labs/chainconsole/commit/64d03a19ea3317cfe45435b22fa1fbf9116d7953)) - **Claims:** To claim tokens from the ICO. ([b9d7e64](https://github.com/helikon-labs/chainconsole/commit/b9d7e64341e9f3d2453d5ab5d8306ca0261cdda0)) - **Vanity Account Generator:** An account generation tool is probably better suited for a wallet application, not the browser. ([a3ba7fc](https://github.com/helikon-labs/chainconsole/commit/a3ba7fc03550a7034cfdf8049b5b8ae2a4062af1)) - **Electron build:** Desktop application builder. The security benefits of using a desktop deployment are an upside for the Electron build, however, **the focus for Chain Console will remain on the web.** ## Roadmap Some work items that I’m planning to tackle: - Keep merging the updates made to the original repository. - Identify and handpick a number of issues and PRs to be implemented from the main repository posted by the community. - Fix a number of other urgent issues that have been bugging me, such as the occasional **Invalid** error when I try to submit a transaction on Asset Hub. - Make the application more interesting and pleasing UI-wise. ## Conclusion If anyone is interested in further developing this application, I would be happy to work with **front-end designers and product-minded people.** Drop a line if you’re interested. This effort is **fully intuition-driven** , and I find this application interesting and open to considerable development and expansion. Also feel free to open an issue or make pull requests on the repository linked below. Thanks for your time and attention. I’ll post future updates under this thread. ## Links - [https://chainconsole.com](https://chainconsole.com) - [https://github.com/helikon-labs/chainconsole](https://github.com/helikon-labs/chainconsole) ---
**Author:** ![bill\_w3f](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/bill_w3f/32/910_2.png) [@bill\_w3f](https://forum.polkadot.network/u/bill_w3f)\ **Post date:** [March 13, 2026, 1:57pm UTC](https://forum.polkadot.network/t/chainconsole-com-polkadot-js-apps-fork-with-bug-fixes-and-improvements/17313/2 "2026-03-13T13:57:27Z")
This is amazing - thanks Kukabi! ---
**Author:** ![muddlebee](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/muddlebee/32/11373_2.png) [@muddlebee](https://forum.polkadot.network/u/muddlebee)\ **Post date:** [March 13, 2026, 2:02pm UTC](https://forum.polkadot.network/t/chainconsole-com-polkadot-js-apps-fork-with-bug-fixes-and-improvements/17313/3 "2026-03-13T14:02:25Z")
This is cool 🥳 But I see [polkadot-js api](https://github.com/polkadot-js/api) isn’t being maintained anymore last release in Dec 9,2025, won’t this cause an issue going forward as I see its used in the [fork](https://github.com/helikon-labs/chainconsole/blob/fee5447d4b57864dd4f9d216e3397184b4fb5eca/package.json#L76-L80C38) also. So papi going forward? it will be a big migration but with a nice skills.md or [agents.md](https://agents.md/) will be very quick with the SOTA models. ---
**Author:** ![kukabi](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/kukabi/32/181_2.png) [@kukabi](https://forum.polkadot.network/u/kukabi)\ **Post date:** [March 13, 2026, 2:47pm UTC](https://forum.polkadot.network/t/chainconsole-com-polkadot-js-apps-fork-with-bug-fixes-and-improvements/17313/4 "2026-03-13T14:47:05Z")
Thanks a lot @bill_w3f, @muddlebee. It’s been a pleasure. @muddlebee you’re right, it still depends on the Polkadot JS API. My priorities were the issues I listed above, and I’ve been able to fix them, so it works for me for the moment. But there are definitely a lot of other areas of improvement/development. I personally like this app a lot, and I haven’t seen anything as comprehensive, happy to be pointed to one if it exists. I’m confident that the app can become unrecognizably better with the right approach, and persistence. I’m open to all suggestions regarding features, dependencies, and development methods, agentic included, with careful attention to unwanted bloat. ---
**Author:** ![ThomasR](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/thomasr/32/1227_2.png) [@ThomasR](https://forum.polkadot.network/u/ThomasR)\ **Post date:** [March 13, 2026, 3:27pm UTC](https://forum.polkadot.network/t/chainconsole-com-polkadot-js-apps-fork-with-bug-fixes-and-improvements/17313/5 "2026-03-13T15:27:40Z")
Tkx Kukabi ! You rock due ! 🙏 ---
**Author:** ![shawntabrizi](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/shawntabrizi/32/14_2.png) [@shawntabrizi](https://forum.polkadot.network/u/shawntabrizi)\ **Post date:** [March 13, 2026, 10:26pm UTC](https://forum.polkadot.network/t/chainconsole-com-polkadot-js-apps-fork-with-bug-fixes-and-improvements/17313/6 "2026-03-13T22:26:05Z")
@kukabi I should have rights to merge in changes to the official Polkadot JS apps repository. If you are interested to bring in some non-controversial changes into the repo, I would be happy to look at them and merge it. Not taking away from your efforts to fork and improve things on your own, but I think we can also help people who are unaware of your fork too. You will need to fix the permission you have on your PRs to allow code owners to contribute to your PRs, for example this PR is stuck in CI pipeline, and I cannot fix it. It says I do not have permission to push to the head branch. > > > This PR removes Permanence DAO RPC endpoints from Polkadot JS apps. The nodes wi…ll be discontinued by January 19th 2026. ---
**Author:** ![kukabi](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/kukabi/32/181_2.png) [@kukabi](https://forum.polkadot.network/u/kukabi)\ **Post date:** [March 14, 2026, 6:52am UTC](https://forum.polkadot.network/t/chainconsole-com-polkadot-js-apps-fork-with-bug-fixes-and-improvements/17313/7 "2026-03-14T06:52:41Z")
@shawntabrizi there’s apparently a [GitHub issue](https://github.com/orgs/community/discussions/5634) that prevents “Allow edits by maintainers” in cross-organization PRs. I rebased the PR, and it just passed the checks. I hope that fixes it. Regarding upstream contributions, thanks for the suggestion. I’ll do my best to forward the minor improvements such as icon fixes and non-controversial UI improvements. I didn’t initialize the repository as a GitHub fork to avoid the constant “x commits ahead, y commits behind” display, which gets really confusing as the fork diverges, but the fork began at [a7124d9](https://github.com/helikon-labs/chainconsole/commit/a7124d955b2569ea6276e053b9f8ca931bdc7ae4) if the maintainers would be interested in cherry-picking. ---
**Author:** ![stakeworld](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/stakeworld/32/1544_2.png) [@stakeworld](https://forum.polkadot.network/u/stakeworld)\ **Post date:** [March 17, 2026, 6:58pm UTC](https://forum.polkadot.network/t/chainconsole-com-polkadot-js-apps-fork-with-bug-fixes-and-improvements/17313/8 "2026-03-17T18:58:18Z")
@kukabi I applaud you action, while it also deeply worries me that it is needed. I was one of the people who raised the issue on the forum and the reaction was that there was not a problem; polkadot.js was still being maintained and updates were being pushed. There however are still multiple open PR’s, some since januari. Some endpoints haven’t been functioning for months but are still not disabled, either by the system or by the corresponding PR. It worries me because it sends a bad message to “the world” if the main interface of the polkadot ecosystem is neglected. The changes you made are elegant and neccesary. I would hope they find their way to the main application. If I were parity I would hire you to help with reviving the development of polkadot.js. ---
**Author:** ![shannonwells](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/shannonwells/32/5435_2.png) [@shannonwells](https://forum.polkadot.network/u/shannonwells)\ **Post date:** [March 17, 2026, 10:31pm UTC](https://forum.polkadot.network/t/chainconsole-com-polkadot-js-apps-fork-with-bug-fixes-and-improvements/17313/9 "2026-03-17T22:31:25Z")
You’re doing The Lord’s work and I thank you. ---
**Author:** ![kukabi](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/kukabi/32/181_2.png) [@kukabi](https://forum.polkadot.network/u/kukabi)\ **Post date:** [March 18, 2026, 9:07am UTC](https://forum.polkadot.network/t/chainconsole-com-polkadot-js-apps-fork-with-bug-fixes-and-improvements/17313/10 "2026-03-18T09:07:34Z")
Thanks a lot @ThomasR, @stakeworld, @shannonwells. I’m only building on top of what has been built so far, happy to see your support. @stakeworld I saw your comments earlier, I think on Element, I agree it’s not a good look. I hope this effort contributes positively. I’ll keep improving it. ---
**Author:** ![Thebicsam](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/thebicsam/32/2999_2.png) [@Thebicsam](https://forum.polkadot.network/u/Thebicsam)\ **Post date:** [June 19, 2026, 1:26pm UTC](https://forum.polkadot.network/t/chainconsole-com-polkadot-js-apps-fork-with-bug-fixes-and-improvements/17313/11 "2026-06-19T13:26:46Z")
Is this stuff still alive? i Can’t access it today ---
**Author:** ![Gr33nHatt3R](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/gr33nhatt3r/32/11205_2.png) [@Gr33nHatt3R](https://forum.polkadot.network/u/Gr33nHatt3R)\ **Post date:** [June 19, 2026, 1:36pm UTC](https://forum.polkadot.network/t/chainconsole-com-polkadot-js-apps-fork-with-bug-fixes-and-improvements/17313/12 "2026-06-19T13:36:46Z")
It seems to be working fine for me. > **[Chain Console - Polkadot](https://polkadot.chainconsole.com/#/explorer)**