Wallets and web3

A profile is a browser of its own: cookies, storage, user data folder and the proxy it leaves through belong to it alone.

Put one wallet in one profile and another in the next, and the sessions never meet. A site opened in one has nothing of the other to read.

An extension unpacked as a plain folder gets an id derived from that folder's path. The key from the store archive is written into the manifest instead, so it comes up under the id the store gave it.

A site or a wallet dialog looking the extension up by its known id finds nothing when the id is somebody else's.

• The signature is checked first

  The id is recomputed from the key inside the archive and must equal the one you asked for.

• The author key wins over the store key

  A store archive carries two signatures; the author's gives the real id.

• An extension with its own key keeps it

  Rewriting it would change the id of something already working.

• Manifest V3 or nothing

  An older manifest is refused at install and again at launch.

Two engines sit under the app: ARMANOS Browser, our own Chromium build, and a built-in engine that takes over when the build is missing or will not start.

On the built-in engine a store extension loads and then almost nothing happens. The app names the engine that will really start, so a green switch never stands for a working wallet.

Which extensions are on belongs to the profile and travels with your account. The files do not: each computer downloads its own copy from the store.

So on the other machine the wallet installs again and you unlock it yourself. Its password is the extension's own business and never passes through us.

• The on and off choice travels

  Switched on at work, on at home, in the same profile.

• A send that failed is shown

  If the choice did not reach your account you see the failure, not a green result.

• One version for every profile

  Files sit in one folder, so profiles differ only in what is on.

A profile can hold the two-factor key of the account it signs into and turn it into the current code in the same window. It is computed on your machine and no request goes out for it.

The file holding it can be read only by your account on this computer. The key itself is not encrypted, and that belongs here rather than in a surprise later.

An exchange that checks who you are asks for one account per person, and that rule belongs to the exchange. We sell no way around it and no page here offers one.

Making accounts in bulk to collect a distribution is a different thing again, and platforms treat it as an offence of its own. What is left is the honest half: one account, one profile, nothing shared.