Skip to content
GitHub

Wallet status

Testnet

Monolythium wallet surfaces are released independently. A store listing, repository, or preview build proves only that exact artifact exists; it does not establish feature parity across desktop, browser, and mobile.

Surface Current public status Important boundary
Desktop Early preview/scaffold; no certified signed production release Stele is retired from the intended product, but an older or current unreconciled build may retain a gated legacy surface; inspect the installed artifact
Browser Chromium testnet release is listed in the Chrome Web Store The listed version predates wallet-auth v1; the method is in the v0.4.5 GitHub prerelease and remains store-release pending
Mobile Android testnet release is listed in Google Play; iOS remains planned No scan-to-pay, name-resolution, private-denomination, or Stele handoff is certified by this page

Mainnet is not running. Treat every currently distributed wallet as testnet software and verify its publisher, package identifier, installed version, network, and full genesis identity before use.

These docs do not publish a supported value-transfer procedure. Name registration and resolution, private-denomination transfers, delegated agent wallets, automatic spending policy, and generic payment handoffs remain unavailable or separately release-gated.

Wallet-auth v1 is an authentication design, not transaction authority. The source implementation creates a domain-bound application proof and a separately revocable connected-site permission. Ordinary store users must wait for a compatible browser-wallet release and applications must feature-detect the method.

Stele has a public-web preview at stele.monolythium.com. The intended wallet products do not host Stele: it is retired from the intended desktop product and is not intended as a browser- or mobile-wallet screen.

That intended boundary does not prove Stele is absent from every desktop artifact. Older or current unreconciled preview builds may retain a gated legacy surface. The installed version, its release notes, and direct inspection of that build are authoritative. A compatible browser wallet may authenticate a user to the standalone web application, but that proof is not a booking, payment, or spending approval.