By default the Polkadot{.js} extension injects all addresses that have been imported into the browser wallet when a connection is requested by a website.

In comparison, the Metamask extension on Ethereum/Moonbeam/Astar allows you to choose which addresses you want to share with the application:

Metamask connect address

How would this be accomplished with the Polkadot{.js} extension?

2 Answers 2


The Polkadot{.js} extension doesn't offer site-specific account permissions the same way that Metamask does.

However, you can set the global visibility of each individual account which will prevent the account information from being injected into the website when a connection is made.

To hide an account click on the eye icon (it will become red and crossed out when the account is hidden):

Polkadot hide account

Note that you will have to toggle the visibility settings every time you want to change which accounts are visible to an application.

  • Shame that there is no way to make it site-specific. It would be nice if there were some 'visibility templates' that could be attached to specific dapps.
    – Rtsne42
    Commented Mar 17, 2022 at 23:41
  • 3
    You should open a feature request, sounds like something that is easily programmable.
    – Shawn Tabrizi
    Commented Mar 18, 2022 at 1:37
  • 1
    There is an open request for proposals on the W3F grants program repo that addresses this and other privacy related features of polkadot.js: github.com/w3f/Grants-Program/blob/master/rfps/…. If anyone is interested in implementing it, you can submit an application on that repository.
    – smm
    Commented Mar 18, 2022 at 14:30

I can't comment yet, so all I'm left with is to answer:

I implemented this feature a couple months ago https://github.com/polkadot-js/extension/pull/1068 I published an article about it too: https://blog.chainsafe.io/polkadot-js-extension-new-privacy-feature-3f80900589ec

It will be part of the next release in production hopefully in the coming weeks. Releases of the extension are taken very seriously because the time it takes between the submission and going live can be very long (like a week). If you push something that hasn't been sufficiently tested, leaving users without a fix for a week is disastrous.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.