Install

Get Loroco in your browser

There are three ways to install Loroco: the Chrome Web Store (one click, auto-updates), a release ZIP loaded manually (no store account needed, works on any Chromium browser), or a build from source (full control, always the latest code).

Option 1 · Recommended

Chrome Web Store

The easiest path. One click, and Chrome keeps the extension updated automatically.

Add to Chrome →

Works on Chrome, Brave, Edge, Opera, Vivaldi and any other Chromium-based browser that supports Web Store installs.

Latest version not on the store yet
The newest release, v0.0.14, is not yet available on the Chrome Web Store — the store still serves an older build while the update is in review. To use v0.0.14 today, install it from the release ZIP (Option 2) or build from source (Option 3). Store installs will pick it up automatically once it's approved.
Option 2 · No store needed

Install from a release ZIP

Every release ships a ZIP of the built extension. You can load it manually in any Chromium browser without touching the Web Store — useful if the store is unavailable in your region, you want a specific version, or you simply prefer not to use it.

  1. Download ozoneextension-<version>-chrome.zip from the GitHub Releases page.
  2. Unzip it into a folder you'll keep permanently — e.g. ~/Apps/loroco/. Chrome loads the extension from this folder; if you delete or move it later, the extension breaks.
  3. Open chrome://extensions/ (Brave: brave://extensions/, Edge: edge://extensions/).
  4. Enable Developer mode — the toggle in the top-right corner.
  5. Click Load unpacked and select the unzipped folder — the one that contains manifest.json.
  6. Loroco appears in the list. Pin it via the puzzle-piece icon next to the address bar, then click it to create or import a wallet.
ZIPs can't be loaded directly
Chrome has no "install from ZIP" button — Load unpacked only accepts an extracted folder. If the file picker won't let you select anything, you're probably pointing it at the .zip itself or at a parent folder; pick the folder that directly contains manifest.json.

Updating a manual install

Manually-loaded extensions do not auto-update. To update:

  1. Download the new release ZIP.
  2. Extract it into the same folder, replacing the old files.
  3. On chrome://extensions/, hit the reload icon (↻) on the Loroco card.
Keep the same folder — your wallet data depends on it
For unpacked extensions, Chrome derives the extension ID from the folder's path. Load a new version from a different folder and Chrome treats it as a different extension — fresh ID, fresh storage, and your wallet looks empty. Nothing is lost on-chain (your keys come from your mnemonic), but you'd have to re-import the wallet from the recovery phrase. Replacing files in place and reloading keeps the ID, the connections and the synced state intact.
"Developer mode" banner
Chrome shows a "Disable developer mode extensions" warning on startup for any manually-loaded extension. That's expected for every unpacked install — dismiss it. It does not mean the extension is unsafe; it means it didn't come through the store's signing pipeline.
Option 3 · From source

Build it yourself

If you have the toolchain (Node 22+, pnpm, Rust + wasm-pack — see the developer guide for first-time setup), the build is two commands:

git clone --recurse-submodules https://github.com/MarvinQuevedo/loroco.git
cd loroco
pnpm install
pnpm build          # full build: WASM engine + extension (~1 min)

Then load it exactly like the ZIP install above — chrome://extensions/ → Developer mode → Load unpacked → select:

packages/extension/.output/chrome-mv3/

Or produce your own distributable ZIP with pnpm zip (written to packages/extension/.output/).

Experimental

Firefox

A Firefox MV3 build exists but is experimental. Permanent installs require the add-on to be signed by Mozilla; until Loroco ships on AMO, you can load it as a temporary add-on:

  1. Build it: pnpm build:firefox (or pnpm zip:firefox for a ZIP).
  2. Open about:debugging#/runtime/this-firefox.
  3. Click Load Temporary Add-on… and select packages/extension/.output/firefox-mv3/manifest.json.
Temporary means temporary
Firefox removes temporary add-ons when the browser restarts — you'll need to load it again (your wallet can be re-imported from the mnemonic). Treat the Firefox build as a developer preview, not a daily driver.
Stay safe

Before you trust any wallet download