Skip to content

Releases: SatoriNetwork/SatoriGO

Satori GO 1.5.1

Choose a tag to compare

@WilQSL WilQSL released this 04 Oct 09:23

A quicker way to add networks, and two fixes.

Adding a network
A wallet that uses the app password no longer asks for the password again when
you add a network while it is unlocked. The new network is protected by the
same app password, and the panel says so. Wallets that still have their own
password ask for it as before.

Fixed

  • Enabling Base or another EVM network on a wallet imported from a private key
    failed with "An EVM private key is 64 hex characters". The same key is now
    reused on the EVM network, as the screen says.
  • Locking the wallet at the exact moment a wallet was being moved to the app
    password could store it under the wrong key. The lock is now detected and
    nothing is written.

Permissions, hosts and the content security policy are unchanged since 1.5.0.

Satori GO 1.5.0

Choose a tag to compare

@WilQSL WilQSL released this 02 Oct 19:17

Five new networks, and a wallet that is quicker to find your way around.

New networks
Monero, Zcash, Bittensor, Avalanche and Robinhood Chain, each marked new in the
network list. Add them to any wallet made from a recovery phrase: the address
comes from the phrase you already have, and nothing needs to be retyped.

Monero is scanned by the wallet itself, in the open wallet window. The view key
never leaves your device, and the Monero nodes only ever see the Satori GO
gateway. The first sync shows its progress and the time left, a restore can
start from the date the phrase was first used with Monero, and the standard 25
words can be shown and imported. New payments are locked for 10 blocks by
Monero's own rule; Home says how long is left.

Zcash uses transparent t1 addresses, the same ones Zashi, YWallet, Trust Wallet
and Ledger derive. Payments to them are public, like Bitcoin; shielded and
unified addresses without a transparent part are refused.

Bittensor is the native TAO network, with the same account btcli and
polkadot.js derive as a coldkey. Activity lists the sends made from this wallet
and links to taostats.io for the full history.

Avalanche C-Chain and Robinhood Chain join the EVM networks: the same EVM
account works on them, with USDC and USDt on Avalanche and USDG on Robinhood
Chain listed by default.

Easier to use

  • Favourite networks: a star puts a network in a Favourites group at the top.
  • Search the network list by name, ticker or website.
  • Balances and prices in US dollars, euros or Polish zloty.
  • Confirm & Send always in view on the review screen.
  • Max fills in the exact amount you can send, on every network.
  • Every transaction opens in its block explorer.
  • Bitcoin BLAKE2b is now shown with its exchange ticker, XBT.

Fixed

  • Avalanche Activity now lists incoming payments.
  • The Activity badge lights for new activity on every EVM network.
  • A custom block explorer saved on an EVM network or Bitcoin BLAKE2b no longer
    replaces the one saved for Evrmore.

Funded sends were confirmed by hand on all five new networks.

Downloads below: Chrome, Edge and Firefox packages, all version 1.5.0. The
extension's permissions and hosts are unchanged since 1.4.0; the content
security policy adds 'wasm-unsafe-eval' for the Monero engine.

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

SatoriGO 1.4.2

Choose a tag to compare

@WilQSL WilQSL released this 07 Sep 13:36

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.

Satori GO 1.4.0

Choose a tag to compare

@WilQSL WilQSL released this 29 Aug 15:18

Satori GO 1.4.0

Description

One wallet across many networks, coin networks and EVM networks alike. Every
network it supports has been sent a real, funded transaction on mainnet and
confirmed by hand.

EVM networks work the way you expect: one account, the same address on all of
them, and switching network changes what you are looking at rather than who
you are. Add a token by contract address or find it by name, or import the
tokens an account already holds. The wallet will only vouch for a token that
is on the network's public list and carries a registry mark; anything else is
shown as unverified rather than dressed up as genuine.

One password for the whole wallet, if you want it. You type it once and then
choose which wallet to open. Because a password you can forget is a risk of
its own, you can make a recovery code that opens the wallet and lets you set a
new one, and save an encrypted backup file of everything on the device to
restore on another computer. Nothing about your password is stored anywhere
but your own device, so there is no reset anybody can send you.

Stake natively where the network supports it, see what you have staked and
what it has earned, and pick a validator from a sortable list.

The wallet can dock in the browser's side panel and stay open beside a site.
Notices from Satori Network can now show on the home screen, one at a time,
always labelled as coming from Satori Network and never able to hold the
screen or pass itself off as the wallet talking.

Prices now come from the project's own gateway instead of two exchanges
directly. Your coins' server connections now prefer that same gateway too,
with each network's usual public servers kept behind it as a fallback, except
for a network or two with no safe public fallback, which go through the
gateway alone. The wallet asks for no permission to reach an exchange any
more.

Fixed

  • Two windows open on different wallets no longer act on each other. A second
    receive address, a password change, a rename or a removal now always lands
    on the window's own wallet, not whichever window happened to act first.
  • A write that lost a race with another window now says plainly that nothing
    changed, instead of reporting the wrong password, "store-conflict", or a
    false success.
  • The transaction id shown after a send is now verified against the one the
    wallet actually built, instead of trusting whatever the server names.
  • A balance with many decimal places no longer pushes its fiat value off the
    row.
  • Tokens no longer disappear from the list when a read fails or the network is
    busy; they stay until a read that actually answers says the balance is gone.
  • Activity, and a token's own history, now page further back instead of
    stopping at the first page your network's history service returns.
  • A token can no longer dress itself up as verified with an emoji, a tick mark
    or a hidden character in its name; the wallet's own "unlisted" warning is
    now a filled pill instead of a small triangle.

Downloads below: Chrome, Edge and Firefox packages, all version 1.4.0.
Permissions changed since 1.3.0: sidePanel was added, api.coinex.com and
safe.trade were dropped, and network.satorigo.app was added. None of the EVM
support in this release adds a host of its own; it reads through the same
gateway that already had to be permitted for prices.

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

Satori GO 1.3.0

Choose a tag to compare

@WilQSL WilQSL released this 16 Aug 14:21

Seven networks in one wallet: Bitcoin, Litecoin, Dogecoin, Evrmore, Ravencoin,
BitcoinGold and WojakCoin. Each has been sent a real, funded transaction on
mainnet and confirmed by hand.

Switch networks from the header. Each one derives its own address from the
wallet you already have, with its own servers, block explorer, fee policy and
address validation, and the recipient pickers and the send path always follow
the network you are on. Networks are described by their parameters rather than
by name, so adding the next one is a data entry, not a rebuild.

Choose which networks you want to see. Expert Settings can hide any of them from
the switcher and from wallet creation. Hiding deletes nothing and is reversible.

See the fee before you send. Fast, normal and slow appear only where the network
genuinely offers a choice, with the real price of each; where it does not, you
get one honest figure instead of three invented ones. You can set your own rate,
checked against that network's actual floor and ceiling.

Settings now has a basic and an expert mode. Expert adds servers, addresses,
connected sites, export, network visibility and a diagnostics page showing
storage use and connection details.

The wallet tells you when a network is the problem. If a chain stops producing
blocks, the header says so with the age of the last block instead of showing a
confident "synced" while a payment waits on a chain that has stalled.

Fixed

  • Sending on native segwit networks. Input verification compared the wrong form
    of a transaction, which stopped every send on those networks.
  • The amount shown for a transaction on a wallet with more than one address. It
    reported one address's movement as the whole wallet's, so a small payment out
    of a large coin could appear enormous. Balances were never affected.
  • A transaction reported as failed after it had actually been sent, which
    invited paying twice.
  • The maximum sendable amount on segwit networks, which reserved more fee than
    the transaction needed.
  • Recovery phrases of 15, 18 and 21 words now import; they are valid and were
    being refused.
  • A recovery phrase protected by a BIP39 passphrase now restores the wallet it
    belongs to, instead of quietly restoring a different, empty one.
  • A just-sent transaction appears immediately instead of waiting for a long
    history sync, and the unread badge stops reappearing on busy wallets.

Downloads below: Chrome, Edge and Firefox packages, all version 1.3.0 with
unchanged permissions.

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

Satori GO 1.2.0

Choose a tag to compare

@WilQSL WilQSL released this 24 Jul 13:55

Adds Ravencoin (RVN) support alongside Evrmore: create or import a wallet on either chain, send and receive the native coin and assets, with per-chain server pools, prices and explorer.

Highlights

  • Multi-chain: chain picker at create/import; recipient pickers and the native-vs-asset send path are scoped to the active chain.
  • Broadcast verifies its outcome on a server error, so a transaction that actually landed is reported as sent (not a false failure).
  • Receive shows the network, QR and address (one address per chain).
  • UI polish: readable funded balances, spacing fixes, my-wallet quick-pick highlight, long asset-name handling.

Load unpacked from the matching folder, or use the attached zip for your browser: Chrome, Edge or Firefox.

Satori GO 1.1.1

Choose a tag to compare

@WilQSL WilQSL released this 15 Jul 11:44

Patch release for the Firefox add-on store (AMO) submission.

Changed

  • The Firefox manifest now declares data_collection_permissions: { required: ["none"] } — AMO submission validation requires every add-on to state what data it collects, and Satori GO collects none (see PRIVACY.md). Firefox versions older than 140 ignore the key.
  • No code changes. Chrome and Edge builds are functionally identical to 1.1.0 and rebuilt only for the version bump.

Install

Same as v1.1.0: load unpacked from the unzipped folder (chrome://extensions / edge://extensions), or in Firefox via about:debugging#/runtime/this-firefox → Load Temporary Add-on until the AMO listing is live.

Verify your download (SHA-256)

79807531201E5EBC3EBB9ADEE81E5EF9B028961915960F2A67732B8CE341FE1D  satori-go-chrome.zip
54363CB1A170D5B20D6013817A4D4C83180B83C811E77172FBF43DF31EBEC18D  satori-go-edge.zip
7213B430C5B2AC986AE06243B1E9BB40D0649008CA146688D2B6F98B901A3E3D  satori-go-firefox.zip

This wallet moves real funds on Evrmore mainnet and is unaudited beta software. Install only from this repository or the official store listing, use amounts you can afford to lose, and always do a small test send first.

Satori GO 1.1.0: Chrome, Edge and Firefox

Choose a tag to compare

@WilQSL WilQSL released this 15 Jul 10:38

The multi-browser release: Satori GO now builds for Chrome, Edge and Firefox from one shared codebase.

What's new

  • Firefox support. A genuine Gecko MV3 build (satori-go-firefox.zip): event-page background (Firefox has no MV3 service worker), add-on id satori-go@satorinet.io, minimum Firefox 128. Verified by a full manual run-through on real Firefox: wallet lifecycle, live balances, a real mainnet send, dApp connect and message signing, SATORIEVR staking read, deposit notifications.
  • Edge package. Same Chromium MV3 build as Chrome, shipped as its own zip (satori-go-edge.zip).
  • Per-browser build system. platforms/<target>/manifest.json + npm run build:chrome|edge|firefox (or npm run build for all three).
  • Fix: the popup now sizes correctly on Firefox (it previously collapsed to a thin sliver).

Install

  • Chrome / Chromium: unzip satori-go-chrome.zip, then chrome://extensions → Developer mode → Load unpacked.
  • Edge: unzip satori-go-edge.zip, then edge://extensions → Developer mode → Load unpacked.
  • Firefox: unzip satori-go-firefox.zip, then about:debugging#/runtime/this-firefox → Load Temporary Add-on → pick manifest.json. Until the add-on is signed on addons.mozilla.org, Firefox only allows it as a temporary add-on (it unloads on browser restart; your wallet data persists).

Verify your download (SHA-256)

1BC75035EE069FC2A0929C7D50C3F3E4F316AD1A655B6AAE6B42F1BA21CEB6F0  satori-go-chrome.zip
73DFE98841C85A4ED4394DDECB36067B759CB7229BBA361CBD0CDFEDDBA58A91  satori-go-edge.zip
0C3C140478B71F4409CC4772F1E8238CD76D90FE7CCEB4A558D8F2CB40B114E0  satori-go-firefox.zip

This wallet moves real funds on Evrmore mainnet and is unaudited beta software. Install only from this repository or the official store listing, use amounts you can afford to lose, and always do a small test send first. See the README's security section and KNOWN_LIMITATIONS.md.

Satori GO v1.0.0

Choose a tag to compare

@WilQSL WilQSL released this 14 Jul 10:31

First public release of Satori GO: a non-custodial EVRmore (EVR) + assets wallet for the Satori Network, shipped as a Chrome MV3 extension.

Highlights:

  • Hold, receive and send EVR and any EVRmore asset, including SATORIEVR
  • SATORIEVR pool staking (off-chain delegation, no funds move)
  • Multiple wallets, dApp connect via the window.evrmore provider
  • Keys stored only as AES-256-GCM ciphertext (scrypt-derived key); trustless input verification on every send
  • Satori Network stats tab, activity feed, address book, EN/PL

Install: download satori-go-chrome.zip, unzip, and load the folder via chrome://extensions -> "Load unpacked" (Developer mode on). Chrome Web Store listing is in review.