Monolythium/Build/Downloads

Downloads.

Canonical project and store links in one place. A link is not a release attestation: verify publisher, version, permissions, checksums, signatures, and supported network before installing. No mainnet is running.

· Apps

Pick your platform.

Monolythium Wallet — Browser

verify listing

Browser-extension wallet. Standard BIP-39 recovery derives ML-DSA-65 keys; the Argon2id/XChaCha20-Poly1305 vault is extension-local and PQM-1 is removed. Verify publisher, version, and permissions at the store.

Verify browser listing →

Monolythium Wallet — Mobile

verify listing

Separate mobile-wallet product. This page does not promise platform availability, secure hardware, biometric behavior, or cross-client recovery; verify the linked publisher and release notes.

Verify mobile listing →

Monolythium Wallet — Desktop

development

Separate desktop-wallet product for macOS, Windows, and Linux. Stele embedding is being retired; an older or unreconciled build may still show a disabled legacy surface until removal ships. Treat the release page as the authority for features, artifacts, and signatures.

Inspect release page →

Monarch Desktop

development

Operator-console project. No signed-build or supported-action claim is made here; verify artifacts, checksums, signatures, and compatibility on the release page.

Inspect release page →

Looking for node software? Public operator onboarding is unavailable while development network 69420 is stale. See Run a node for the release gate.

· Packaging targets

Where products may ship.

This matrix is not evidence that an installer exists or is signed. The release page or store listing is authoritative.

PlatformArchitecturesSigning
macOSApple silicon · Intel targetVerify release artifact
Windowsx86_64 targetVerify release artifact
LinuxPackaging target variesVerify release artifact
iOSFuture targetNo release claimed
AndroidExternal listing linked aboveVerify publisher and version
BrowserChromium listing linked aboveVerify publisher, version, and permissions
· Verify

Trust, but verify.

01
Source

Start from a canonical link.

Avoid mirrors and unsolicited download links. Confirm that the final destination and publisher match the project source or official store listing.

02
Signatures

Demand release-specific evidence.

If a release claims checksums, signatures, provenance, or an SBOM, verify each artifact against the exact tag. This page does not assert that every linked build has them.

03
Reproducibility

Treat reproducibility as a gate.

A reproducible-build claim needs public source, toolchain pins, build instructions, and an independently matching hash. Do not infer it from a download button.

Need release status? Verify at the source.

Use the linked store or repository release page for current availability. Never enter a mnemonic into a website, Stele, an MCP server, or a support conversation.