Skip to content

Releases

v4.9.7

Choose a tag to compare

@ORDNET ORDNET released this 02 Sep 11:48
4611dac

Same wallet as 4.9.6 plus repository housekeeping. GitHub's web upload adds
and overwrites but never deletes, so the 4.9.6 upload left three files from
older versions in the tree - two of which the release suite rightly rejects.

Removed (see the separate deletion commits):

  • src/wallet.js (pre-split 4.7.2 monolith; engine lives in src/wallet/ since 4.9.3)
  • src/brc100-content.js (one injector, src/content.js, since 4.9.3)
  • RELEASE-4.9.5.md (4.9.5 was an internal iteration, never published)

Restored/added:

  • .github/workflows/test.yml (unit suites on every push)
  • .github/workflows/e2e.yml (loaded-extension suite, manual trigger only)

No wallet code changed between 4.9.6 and 4.9.7 apart from the version number.
Tests: 251 across 11 bare-Node suites, 0 failed.

v4.9.6

Choose a tag to compare

@ORDNET ORDNET released this 02 Sep 06:47
1e659c5

Cosmetic release on top of 4.9.3, designed mockup-first and reviewed on screenshots.

  • Home shows your balance, address and Send / Receive first, then your SNS domains, OpNS domains, BSVmaps and For sale — each with its count, each opening its own list.
  • Tap a name for its detail screen: list for sale, remove listing, send, manage target and routes, open in ORDnet search or on bsvmap.io.
  • All tools stay one tap away: the five header actions and the five bottom tabs are unchanged.
  • No colours, fonts, engines, signing paths or storage keys changed — a test enforces that the new CSS uses only design-token variables.

4.9.4 and 4.9.5 were internal iterations and were not published.

Full detail: CHANGELOG.md · RELEASE-4.9.6.md

Store package: ordplug-store-4.9.6.zip, sha256 61785a620f6f15f16d6660bb19e798bc304289d4e2fcdc649050fcac4fb25a40

v4.9.5

Choose a tag to compare

@ORDNET ORDNET released this 02 Sep 06:45
3d1135f

Second iteration of the home simplification: the five header actions and the original five bottom tabs are back, and the category rows use the same dark tile icons as the list rows.

One tile was still wrong in this iteration (OpNS showed the @ tile instead of the ORDnet mark) — fixed in 4.9.6, which is the published version. This version was not submitted to the Chrome Web Store.

Full detail: CHANGELOG.md · RELEASE-4.9.5.md

Store package (not submitted): ordplug-store-4.9.5.zip, sha256 4bab82ada22d6e0db9d55c8f99f5901de5838b8ab116802778c143e760f91918

v4.9.4

Choose a tag to compare

@ORDNET ORDNET released this 02 Sep 06:42
6239c5d

Cosmetic release, designed mockup-first. No colours, fonts, tokens, engines,
signing paths or storage keys changed; every button keeps its id and handler.

  • Home: balance large and centred (sats + dollar under it), address pill,
    Send/Receive, then four category rows — Your SNS domains, Your OpNS domains,
    Your BSVmaps, For sale — each with its count, opening one list at a time.
  • Header reduced to two actions: Accounts and a "..." menu holding UTXO tools,
    Transaction history, Settings, Open in a full tab and Lock wallet
    (same ids, same handlers).
  • Category screen (view-holdings): title + count, search, pager, bulk mode —
    the existing holdings engine rendering into the same element ids; the tab
    strip is kept hidden for it.
  • Name detail (view-namedetail): facts plus all actions under each other
    (list/delist, send, target & routes, open in ORDnet search / bsvmap.io);
    actions reuse the same data-* attributes, handlers untouched.
  • Bottom nav: "Domains" labelled "Names"; fifth tab is "More" (ORD/ner,
    UTXO tools, For sale, Transaction history, Settings).
  • After a listing/delist the wallet returns to the category screen.

Not in this release (by decision): "Change price" on a listing and greying-out
of already-listed names in bulk mode (logic, not cosmetics); watch-only.

Tests: 243 -> 250 (V49.4 layout block). Includes everything from 4.9.3.

First iteration of the home simplification, designed mockup-first: balance-first home, category rows with counts, a category screen per list, and a name-detail screen with all actions. This iteration folded the five header icons into a "..." menu and replaced the fifth tab with "More".

After screenshot review the menu/More approach was reverted (a web3 wallet shows its tools directly) — see 4.9.5 and 4.9.6. This version was not submitted to the Chrome Web Store.

Full detail: CHANGELOG.md · RELEASE-4.9.4.md

Store package (not submitted): ordplug-store-4.9.4.zip, sha256 870e1c5bf2804729476c7ac478c0fcb9b1362c735bc568d78e2dbc6a2ff66033

v4.9.3

Choose a tag to compare

@ORDNET ORDNET released this 02 Sep 06:37
409111f

4.9.3 — Security & recovery round (fee/plan integrity, BRC-100 gate, full wipe, BIP39 checksum). Store version # changed to github version # flow

This release works the fourth external review round (Grok + ChatGPT audits of 4.9.2) point by point.

Headline fix: a malicious page could request an inscription with a huge miner fee while the approval screen showed the normal estimate — the difference burned to the miner. Approval screens are now rendered from the exact unsigned transaction that will be signed, the same object is signed after consent, and its fingerprint is re-checked ("Safety stop" otherwise). Page fees are clamped to at most 2x the wallet's own estimate.

Also in this release

  • BRC-100 requests share the one-at-a-time request gate; one wallet window; closing it unanswered rejects the request explicitly.
  • isAuthenticated / waitForAuthentication now reflect the real unlock state.
  • "Remove wallet" wipes every storage key, the session and the content cache (test-enforced).
  • Full BIP39 checksum validation, a recovery challenge for new wallets, and a live address preview on import.
  • Certificates and x402 reachable for dApps via a single method registry.
  • wallet.js split into 25 ordered modules; 243 tests across 11 suites plus a Playwright loaded-extension suite.

Full detail: SECURITY-FIXES-4.9.3.md · CHANGELOG.md · RELEASE-4.9.3.md

Store package: ordplug-store-4.9.3.zip, sha256 546b974afed1e678df7f18a22821a4960c98a1948f87f91f6918c4a5431c1238

v3.6.0 — Security release

Choose a tag to compare

@ORDNET ORDNET released this 13 Aug 11:45
db9c746

Four builds of security work, folded into one store release. Anyone running an
earlier build should update.

H4 — the page chose its own origin. msg.originator comes from the page, so a
site could pass originator:"https://trusted.dapp" and get three things at once:
the approval screen showed that name while the real site was asking; grants
keyed on ${_address}|${origin}|… were inherited wholesale; and
brc100-budget.decide() is keyed on origin too and auto-approves inside an
existing budget — payments up to the daily ceiling with no confirmation. The
origin now comes from sender.origin, which page script cannot set.

H7 — the BRC-100 read surface was ungated. listActions, listOutputs and
relinquishOutput had no permission check at all: any site could read the full
transaction history and every UTXO, and could loop relinquishOutput. Reads now
require per-origin consent; relinquishOutput confirms on every call and stores
no grant.

listCertificates passed its arguments in the wrong order — ('listCertificates',
args, origin) against a signature of (origin, method, args) — so the grant key
was identical for every website. Approve it on one dApp and every other dApp
inherited it.

relinquishCertificate was completely ungated: any site could permanently delete
any certificate, in a loop. relinquishOutput was gated first and the branch
beside it was missed. Both now run through one brc100RequireDestructive(),
driven by a table that a test iterates — adding something destructive without a
gate now breaks the suite.

Earlier in this series: the approval screen now shows the change address and
the miner fee (K5), on-chain content can no longer run in the extension origin
(K6), page-requested message signing refuses reserved namespaces (K7), padded
ordinals are no longer spendable as funding, and satoshi amounts are no longer
32-bit truncated.

Tests: 123 -> 192, across ten suites.

Full detail in SECURITY-FIXES-4.8.1.md, SECURITY-FIXES-4.9.0.md and
SECURITY-FIXES-4.9.2.md.

v3.5.0 — Security release (manifest 4.8.1)

Choose a tag to compare

@ORDNET ORDNET released this 11 Aug 18:31
cba65b9
  • A listing now pays the seller shown on the approval screen. The check used
    to compare two values that both came from the calling page.
  • 4.8.1 supersedes 4.8.0 the same day: review of that build found the listing
    check still comparing params against params. Do not ship 4.8.0.

Fixes three critical issues from an external review, plus two patterns that
recurred across the codebase.

K5 — the approval screen rendered outputs[] and the service fee, and nothing
else. Not the change address, not the fee. A site could name a changeAddress
of its own and the entire remainder of the selected UTXOs would leave the
wallet behind a screen reading "1.000 sats". Both are now always shown; a
foreign change address is flagged in red with an explanation. Script outputs
disclose their destination, inscription outputs their receiving address.

K6 — the viewer iframe carried allow-scripts together with allow-same-origin,
which cancels the sandbox: a srcdoc document inherits the extension origin.
Since viewer.html is web-accessible from every site, any page could open it
against an inscription of the attacker's choosing and read the session key.
allow-same-origin is removed. The service worker now sends nosniff and
replaces content types outside a render allowlist.

K7 — signMessage was exposed unfiltered to every page while the same primitive
builds registry authentication, so a site could have a domain transfer signed
under a screen that read "No coins move." Page-originated signing now refuses
messages in reserved namespaces; internal signAction is unchanged and the
registry keeps working. The approval screen states what a signature can do and
shows the message in full instead of silently cutting it at 200 characters.

Pattern: ordinal protection was value > 1 only, so any ordinal with padding
was spendable as funding — while the wallet already held the inscription
outpoints in its loaded holdings. Those are now used.

Pattern: four call sites used (fee|0), a 32-bit cast, three lines below the
file's own warning against it. feeNum() replaces all of them.

Tests: 123 -> 167 across ten suites. Full detail in SECURITY-FIXES-4.8.0.md.