Identity in the interaction
Choose the identity that is making a connection or signing a request. Keep that choice visible rather than reducing every action to an opaque address.
Your identity. Your approval.
A clearer way to sign.
Explore Sigil’s web, extension, desktop, and mobile wallet interfaces. Understand the identity, network, and key storage behind each action.
Sigil WalletIllustrated study
Signer → signature → record
Identity establishes attribution. Trust needs context.
01 / Built for a purpose
The important details, before you approve.
A wallet connects a person to an identity and a signing key. It should make the requesting application, selected network, recipient, amount, and permission legible. Sigil’s wallet family shares protocol conventions while using platform-specific storage and integration.
A network with a name
Mainnet uses MINT, Evolve canary uses BITS, and testnet uses test SIG. The selected network changes the RPC destination and the meaning of the asset.
Custody suited to the platform
Web storage, extension storage, desktop keychains, and mobile signing environments differ. Each platform page explains its boundary without promising invisible key synchronization.
Recovery with a plan
A backed-up wallet and an on-chain guardian ceremony solve different problems. Understand the supported recovery path before depending on it.
Keep exploringOne capability.