Use Monolythium

Testnet

Release boundary. Wallet surfaces ship independently. The Chromium browser wallet and Android wallet have testnet store listings; the desktop wallet remains preview-stage and iOS remains planned. Wallet-auth v1 is available in the browser wallet’s v0.4.5 GitHub prerelease but is not in the currently documented store release. Mainnet is not running.

A three-card mental model

Everything in this section fits one of three jobs:

Card	What it is	Where to start
Hold	Verify the exact wallet artifact and its custody boundary	Wallet status Testnet
Identify	Planned human-readable names; no registration or resolution path is released	Name status Planned
Transact	Review unavailable value paths and the implemented Stele preview	Send LYTH Planned

Start here

If you do nothing else, read these three:

Wallet status Testnet — independently versioned desktop-preview, browser-store, and mobile-store surfaces
Browser-wallet mnemonic boundary Source-merged — exact SDK/source behavior, encrypted extension storage, and explicit cross-wallet limits
Name status Planned — unavailable name-registration placeholder

Wallets

Wallet surfaces are documented separately and may ship at different times. Do not assume feature parity or shared agent sub-accounts.

Desktop wallet status Planned — preview-stage; no production install contract
Browser wallet status Testnet — Chromium store release; wallet-auth v0.4.5 prerelease pending store publication
Mobile wallet status Testnet — Android testnet listing; iOS planned
Browser-wallet mnemonic boundary Source-merged — bounded source behavior; not a generic recovery guarantee across wallets

Names

Human-readable identity is a planned wallet surface. Verify the current registered network identity and wallet release before relying on names or transfers.

Register a name Planned — namespaces and pricing are not certified
Transfer a name Planned — ownership-transfer semantics are not released

Pay and receive

Send LYTH Planned — no certified transfer or name-resolution path
Sign in with Monolythium Preview — SDK login contract and browser-wallet v0.4.5 prerelease; compatible store release pending

Agent wallet

Agent wallets and protocol spending policies are planned and unavailable. No released wallet creates a supported delegated agent account or automatically inherits a policy.

Agent wallet setup Planned — consent registry, capability scoping
Spending policy Planned — unavailable release gate; do not protect real funds with prototypes

Stele web app

Stele web app Preview — public at stele.monolythium.com, with a Browser Wallet-authenticated private provider-listing Studio; publication and economic actions remain unavailable

Privacy

Private-denomination warning Planned — no private-value, stealth-recipient, confidential-amount, or conversion path is released

Monarch Desktop (operator companion)

Monarch Desktop is a planned operator companion, not a consumer wallet. No certified public node pairing or management procedure is available.

Monarch Desktop Unavailable — planned operator surface; no certified public pairing or management release

If you’re …

An agent developer — read /agents/ and Agent wallet setup for the explicit read-only and unavailable boundaries.

An app developer — your end user signs in with their wallet. See Sign in with Monolythium and then /build/ for the SDK side.

A node operator — your tooling lives at /operate/. Monarch Desktop is referenced here because users land here first.