Skip to content

Install

Add the extension.

The Chrome Web Store listing is the public install path. The repository is the audit path. They are not guaranteed to be the same build.

Listing 1.4.1 · 2026-10-04 · id ocahgpmgfeapjnceaknkikanjikhjgok

Recommended · Chrome Web Store

Thru Wallet

High-performance self-custody wallet and key manager for Thru.

Version
1.4.1
Updated
2026-10-04
Size
272 KiB
Permissions
5

Verify the listing

  • Extension id matches ocahgpmgfeapjnceaknkikanjikhjgok.
  • The developer website resolves to thruwallet.vercel.app.
  • Privacy policy points at the extension repository, not a random host.
  • The page says it is not affiliated with Unto Labs.
https://chromewebstore.google.com/detail/thru-wallet/ocahgpmgfeapjnceaknkikanjikhjgok

What the store build is, as of 2026-10-04

Package 1.4.1 is the betanet build — contract v15, @thru 0.4.1, and https://rpc.betanet.thru.org as the only allowed connect-src. It is the same code as source release v1.4.1, merged as cee006e a day earlier, so building from main and installing from the store now get you the same wallet. Until 04 Oct 2026 the store served 1.2.0, an alphanet package pointing at a chain that was reset on 2026-09-26.

What that does not mean: verified. Shipping is not verifying. The betanet build went from merge to store in a day on the strength of 20 automated suites, and no manual run through a real Chrome profile is recorded in the repository. The rows most worth a human are the ones newest to the package: duplicate detection while a transfer is still pending, desktop notification delivery, side-panel and popup mutual exclusion, and the dark-mode action grid, drawer ledger, and connection footer.

Developers · load unpacked

Build dist/, then point Chrome at it.

  1. Clone the extension repository and install dependencies.
  2. Run the test suite. It is local. It does not certify Chrome or the chain.
  3. Build, then load the dist/ folder as an unpacked extension.
  4. After a code change, reload the extension so the service worker updates too.

Source: https://github.com/buildbyravi/thru-wallet-ext

thru-wallet-ext
git clone https://github.com/buildbyravi/thru-wallet-ext.git
cd thru-wallet-ext
npm install
npm test
npm run build
npm audit --omit=dev
Chrome Web StoreLoad unpacked
WhoAnyone trying the walletSomeone auditing, patching, or needing betanet now
ArtifactListing 1.4.1, 2026-10-04The commit you just built
ContractWhatever that package containsStatus baseline v15 on the audited tree
UpdatesChrome updates the listingYou rebuild dist/ and reload the extension

If it misbehaves

  • You selected the repository root instead of dist/.
  • Developer mode is off, so Load unpacked is hidden.
  • The popup was reopened but the service worker was not reloaded.
  • A serialization error names a method and field path. If Chrome’s bare message appears, the failure is on the request.

Installation doc · Open checks