Practical overview
When it fits
Use it when a Polkadot or Substrate dapp needs access to extension-managed accounts and signing, while transaction construction and network submission remain in the surrounding application.
Who it is for
- Polkadot and Substrate users who need browser-managed accounts for dapps
- Dapp developers integrating account discovery and transaction-signing requests
- Extension developers building interfaces compatible with the project's injection model
Documented uses
- Create or import Polkadot and Substrate accounts in the extension
- Expose associated accounts to a compatible dapp
- Request signatures through the injected @polkadot/api Signer
- Build or integrate a compliant browser extension interface
Requirements & limits
The README documents Chrome Web Store and Firefox Add-ons installation paths. The repository is public and licensed under Apache-2.0.
- It supports account management and signing, but not wallet functions that construct and submit transactions to the network.
- Dapp integration can use @polkadot/extension-dapp rather than managing raw injected objects directly.
- The codebase is TypeScript and separates runtime, UI, dapp-wrapper and injection packages.
- The documented API exposes account addresses, optional names and optional genesis hashes.
- A development build requires browser extension loading and the repository's documented build workflow.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Build a development browser extension
Build the documented Chrome or Firefox development version and load it into a browser for development.
Before you start
- A browser with its extension development interface
- The repository source
- Corepack and Yarn, as referenced by the build instructions
Steps
Enable Corepack with the documented corepack command when required.
Install dependencies with yarn install.
Build the Chrome or Firefox package with yarn build:chrome or yarn build:ff.
Load packages/extension/build as an unpacked Chrome extension or load its manifest.json as a temporary Firefox add-on.
Refresh or reload the extension after making changes.
Expected outcome
A development build is loaded in the selected browser for viewing changes.
Guide limitations
- The instructions describe building and loading the extension, not successful transaction execution or network submission.
- The documented development flow uses browser-specific debugging interfaces.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 2 October 2026
- Original website title
- polkadot-js/extension · Official homepage title · retained in its source language

