Installation

Two paths. Most people should take the first.

Chrome Web Store

1. Open the listing: Thru Wallet on the Chrome Web Store.
2. Confirm the extension id ocahgpmgfeapjnceaknkikanjikhjgok, the developer website thruwallet.vercel.app, and version 1.4.1.
3. Add it to Chrome. Pin it. The first run offers to create or import a wallet.
4. Read the privacy policy. The developer discloses that the item does not collect or use your data.

The listing is community software. It is not an Unto Labs product and it has not been audited.

The packaged 1.4.1 build targets betanet, which replaced the reset alphanet on 2026-09-26. It is the same code as release v1.4.1, merged as cee006e. Build from source if you want to audit it or patch it; otherwise the store package is the same thing.

Load unpacked

For a checkout you can read:

git clone https://github.com/buildbyravi/thru-wallet-ext.git
cd thru-wallet-ext
npm install
npm test
npm run build

Then:

1. Open chrome://extensions.
2. Enable Developer mode.
3. Choose Load unpacked.
4. Select the dist/ folder, not the repository root.
5. Pin the extension.

npm test is deterministic and local. It does not close the browser smoke checklist or the live-chain probes.

After it is installed

• Reload the extension, not only the popup, when the service worker may be stale. Chrome caches it. Reopening the popup can run new UI against old background code.
• Select dist/ again after every npm run build.
• Do not import a phrase you also use anywhere with real value.
• Custom networks cannot be activated. If a legacy row appears, Remove is the only action.

Listing versus source

If those two disagree, the source tree wins for source claims — including over docs/STATUS_AND_ROADMAP.md, which still describes contract v12. The listing wins for what Chrome will actually install today.