Browser-wallet mnemonic boundary

Source-merged

This page is narrowly scoped to the reviewed Monolythium browser-wallet source implementation and @monolythium/[email protected]. It is not a promise that every desktop, mobile, hardware, store, or future wallet uses the same import UI or storage system. Verify the exact installed artifact before relying on recovery with anything of value.

Deterministic SDK behavior

The SDK accepts a standard 24-word BIP-39 mnemonic, validates its wordlist/checksum, derives the standard BIP-39 seed, then derives the ML-DSA-65 seed under the monolythium.mldsa65.v1 domain. The ML-DSA-65 public key is converted to the Monolythium account-address representation.

There is no BIP-32 or BIP-44 account path in this bounded flow. A classical wallet can use the same BIP-39 words with a different key algorithm and derive a different key; that does not make the phrase a portable account across wallet families.

The selected chain ID, genesis, and RPC endpoint are not inputs to mnemonic or account derivation. Selecting a different network does not derive a different account. Network identity still matters before reading state or preparing any transaction, but it is a connection check rather than a recovery variable.

Reviewed browser-source behavior

The reviewed source calls the SDK mnemonic derivation when creating or importing a vault. Its multi-vault container is stored under chrome.storage.local["mono.vaults.v4"]. The container uses:

Argon2id to derive a master-encryption key from the wallet password;
a wrapped per-vault encryption key; and
XChaCha20-Poly1305 envelopes for the ML-DSA-65 seed and mnemonic.

That is extension-managed encrypted local storage. These docs do not claim that the seed lives in an OS keychain, that biometric unlock is available, or that a browser storage backup is independently sufficient for recovery.

Safe verification

Use only a wallet artifact whose publisher, extension ID, and version you have verified.
Keep the original mnemonic offline and never paste it into a website, chat, support ticket, or documentation search box.
Use the artifact’s own import flow; a web page, Stele, hosted MCP server, and this documentation site must never request the phrase.
Compare the derived account identifier with the one in your own backup before treating the import as successful.
Separately verify chain ID, full genesis hash, and endpoint health before any state read or future transaction operation.

A valid phrase that derives an unexpected account usually indicates different words/order, a different mnemonic, or a different derivation algorithm. A wrong network selection is not a derivation explanation. Stop and re-check the exact artifact and backup; do not send the phrase to support.

Release boundary

The deterministic SDK behavior is exercised by local fixtures, and the encrypted-container behavior above is verified against browser-wallet source. This page does not certify that the currently installed Chrome Web Store binary contains an identical recovery implementation. The browser wallet and wallet-auth source/store boundaries are tracked separately on the install page.