Skip to content
A native home for your wallet

The same identity. A native boundary.

The Sigil desktop wallet wraps the shared web interface in Tauri and adds a native vault backend for macOS, Windows, and Linux.

Desktop WalletIllustrated study
A COMPOSITION, NOT A BLACK BOX.
A composition, not a black box.

Compose the primitives. Keep their boundaries explicit.

Desktop Wallet / An illustrated overview
01 / Built for a purpose

Familiar interface, platform-specific custody.

The desktop architecture reuses the wallet frontend and routes native operations through Rust commands. Its vault backend uses operating-system credential storage rather than treating browser storage as the desktop security boundary.

01

OS credential storage

The native vault targets macOS Keychain, Windows Credential Manager, and Linux Secret Service. Password-based protection and keychain access are separate parts of the implementation.

02

Native application links

The shell registers the sigil:// scheme so an external request can open the application. The wallet must still validate and present the request before approval.

03

Shared wallet behavior

Identity selection, network configuration, and transaction views come from the common frontend. Native adapters handle operations that belong to the host platform.

04

A versioned release boundary

Installers and updater signatures belong to a specific release. Choose a published artifact with a known version and platform instead of an inferred download path.

The details matter

Good questions.
Clear answers.

Does the desktop app automatically import my browser vault?

The implementations have different storage backends. Export/import compatibility is a versioned contract, not an assumption; follow the supported process for the release you use.

Keep exploring

One capability.
A connected platform.

01Wallet interfaces02Operator documentation03Recovery ceremonies