SatoriGO 1.4.2

A new network, and connecting to websites the way it should have worked.

Bitcoin BLAKE2b
A ninth coin network: Bitcoin BLAKE2b, the Bitcoin Knots proof-of-work fork
that split from Bitcoin at the end of August 2026. It is marked new in the
network list. It is Bitcoin's history under a different proof of work, so your
Bitcoin addresses are also your addresses there, and a coin you held before the
fork sits at the same address on both chains.

Sends on it are signed with the fork's own signature format (SIGHASH_UNIFIED),
which Bitcoin does not accept, so nothing you send there can be replayed onto
Bitcoin. The other direction is not in the wallet's hands: spending a pre-fork
coin on Bitcoin moves its BLAKE2b twin too, unless you have first sent the
BLAKE2b coins to yourself once. The send review says so.

The network is young, with little mining power, reaches the wallet through one
server behind the Satori GO gateway, and is priced from the NonKYC BTCB2/USDT
market. A funded send has not yet been confirmed by hand on it; every other
network's has.

Connecting to a website
A site that talks to the wallet is now always offered an Evrmore wallet. Before,
the wallet handed the site whichever network happened to be open, so with
Bitcoin open the site received a Bitcoin address, could not use it, and reported
that it could not reach the wallet.

The connection request lists your Evrmore wallets in a dropdown and you pick the
one to connect. The site stays connected to that wallet, whatever you switch to
in the wallet meanwhile, until you disconnect it in Settings > Connected sites.
Pressing a site's connect button again lets you switch to another wallet.

With the wallet in side panel mode (the default on Chrome and Edge), pressing a
site's connect or sign button slides the wallet out in the side panel and shows
the request there. If the wallet is already open, the request appears in that
window. The popup is used in popup mode, and when a site asks without you
clicking anything; it now opens in the same place every time, the top right
corner of the browser window that asked, and fits without scrolling.

Unlock once. When the wallet is locked, a site's request waits behind the lock
screen with a note saying which site is waiting, instead of a second password
box over it. Once you unlock, the request appears and a signature needs no
password again. A send still follows the wallet's own send rule.

Closing the wallet while a request is waiting counts as declining it. The site
is told, and its next request opens a fresh approval instead of being refused.

Downloads below: Chrome, Edge and Firefox packages, all version 1.4.2.
Permissions are unchanged since 1.4.0.

KNOWN_LIMITATIONS.md is kept deliberately honest and is worth a minute of your
time before you move real funds.