THE L8 WALLET a browser extension · EIP-6963 + EIP-1193

THE L8 WALLET

A browser extension. One 12-word seed makes a hot and a cold address on every EVM chain, the safety checks run before anything signs, and the keys never leave your machine.

ON THIS BROWSER CHECKING…

Asking this page which wallets are here.

This only sees wallets that answer the page. An extension you have switched off for this site stays invisible here, and so does one that needs a reload after installing.

▸ WHAT IT IS

A Manifest V3 extension for Chrome, Edge and Brave. The toolbar popup is the wallet: it holds the seed, shows the addresses, and is where every request from a website waits for you.

Websites find it the modern way, over EIP-6963 (rdns: studios.7slf.l8), and it also answers older pages as window.ethereum through EIP-1193. No code is fetched at runtime — MV3 forbids remote code, so every library it uses is bundled into the build you load.

HOT + COLD

One seed, two accounts, split by the BIP-44 account number: HOT is m/44'/60'/0'/0/0 for pocket money, COLD is m/44'/60'/1'/0/0 for the stack. The command-line tool derives them identically and reads the same encrypted vault, so a seed made in one opens in the other.

CHECKS THAT RUN THEMSELVES

Before a transaction reaches you, its calldata is decoded and scanned — unlimited approvals, burn addresses, value against stated intent, contract bytecode, phishing origin — and the popup shows the verdict as PASS, WARN or FAIL. You still press the button. That press is the only thing standing between a random site and your funds.

Two of those checks reach the network while they run: the chain's RPC endpoint is asked for the destination's bytecode, and api.gopluslabs.io is asked about the token. Both learn the address you are about to deal with. Nothing about your seed or your own addresses goes with it.

WHERE THE KEYS LIVE

Encrypted with AES-GCM-256 behind a PBKDF2 password, inside the extension's own storage on this machine. No account, no telemetry, and no server of ours anywhere in the path — the safety checks are the one place the wallet talks outward. A site is only ever handed an address you gave it. Your 12 words are shown once, when you create the wallet — write them down offline, because there is no reset.

WHAT IT SIGNS ON

The eleven EVM networks in the registry: Ethereum, BNB Smart Chain, Polygon, Arbitrum, Optimism, Base, Avalanche, Fantom, Sepolia, BSC Testnet, and Liqua testnet — see below for what Liqua can and cannot do. Eight further chains derive receive addresses in the CLI only; Cardano and Monero are refused outright rather than shown as a wrong address.

▸ LIQUA CHAIN BALANCES

NOT AVAILABLE YET NO RPC

The wallet lists Liqua (testnet), chain id 73377, and derives your address on it. It cannot show you a LIQUA balance, because there is no Liqua RPC to ask. The v3 chain RPC does not exist yet.

There is no public node and no public explorer, and no contract is deployed on 73377 — not a token, not a staking pool, nothing. The one endpoint answering that chain id today is the v2 mind bridge (node chain/diva-bridge.mjs), which binds to 127.0.0.1 on the author's own machine, reports growth-ledger numbers rather than chain state, and returns empty code for every address you ask about.

So this page shows you nothing for LIQUA rather than a number it cannot stand behind. When the v3 RPC is serving, the wallet gets pointed at it and this card changes. The deployment register ›

▸ HAVEN'T GOT IT?

There is no store listing, so installing means building it from this repository and loading it unpacked. It takes about five minutes and needs Node 18 or newer.

Testnet · unaudited · experimental. This is software custody: anyone holding your password and this device holds the keys. Keep anything that matters on hardware.

INSTALL IT build · load unpacked · pin

INSTALL THE L8 WALLET

Chrome, Edge or Brave, and Node 18 or newer. Five minutes, all of it on your own machine.

▸ 1 · BUILD IT

get this repository onto your machine — the folder that holds liqua/
open a terminal in liqua/wallet
npm install — ethers, @noble, @scure and esbuild, and nothing at runtime
npm run build:ext → writes dist/extension/
npm run test:ext → must print ✓ ALL PASS 22 passed · 0 failed

If that suite does not pass, do not load the build. It walks the whole dapp lifecycle — create, unlock, derive, connect, approve, reject, sign, re-lock — and a failure there is a failure in the part that holds your keys.

▸ 2 · LOAD IT

open chrome://extensions · Edge: edge://extensions · Brave: brave://extensions
turn Developer mode on, top right
Load unpacked → choose liqua/wallet/dist/extension
pin the L8 icon to the toolbar, then open it and create a vault
write the 12 words down offline. They are shown once and there is no second chance

Come back to this page afterwards and reload it: the badge on the first screen turns green once the extension answers.

NO STORE LISTING BY HAND

The extension is not in the Chrome Web Store, so there is no one-click install and no auto-update. You update it by pulling the repository and running the build again.

L8-LEDGER-extension.zip in the repository root is an older build. Rebuild instead of loading it.

FIREFOX AND SAFARI NOT YET

Both use a different extension API from Chrome's Manifest V3 service worker, so the build here will not load in either. Saying no is more useful than half-loading a wallet.

▸ THIS PAGE, PINNED

INSTALL AS AN APP (PWA) LOOKING…

Served over http, this page installs like an app, with its own icon and window, and stays readable offline. It pins the reference — the wallet itself is the extension, and lives in the toolbar.

▸ SERVING THIS PAGE YOURSELF

Only needed if you want this page on your phone, or in its own window. The wallet does not depend on it.

Windows — run install\START-WINDOWS.bat → opens on http://localhost:8088/
Linux — sh install/start-linux.sh; for a menu entry, copy install/L8-LEDGER.desktop to ~/.local/share/applications
macOS — install/START-MAC.command (first run: right-click → Open)
Phone — start it on your computer, read the http://192.168.x.x:8088 address the console prints, open that on the same wi-fi, then Chrome ⋮ → Install app or Safari Share → Add to Home Screen
Native window — cd desktop → npm install → npm start wraps this same page in an Electron window

No signed .exe, .dmg or .apk: those need platform signing keys and store accounts that do not exist yet. Everything above runs from your own files, with no sign-up and no tracking. Testnet · unaudited · experimental.