Embed the wallet. Leave custody outside your stack.
Monstera keeps wallet key state in Sapphire while your application integrates a portable signing surface. These guides separate wallet authorization from optional infrastructure such as gas sponsors and transaction relayers.
Embed your first wallet
Install the SDK, connect a gas-paying submitter, and create a username-addressable wallet without building a custody service.
Start the quickstartGet authentication right
Understand KeyVault-targeted action hashes before you build proof generation.
Learn AuthContextUnderstand the stack
See where orchestration, authentication, storage, and cryptography begin and end.
Explore architectureAll guides
Getting started
Install the SDK, connect a transaction submitter, and embed a wallet without building a key-custody backend.
Clients and networks
Choose connected or read-only clients and configure Sapphire testnet or mainnet deliberately.
Create a wallet
Create anonymous or username-addressable wallets with an allowlisted authenticator.
Action-bound authentication
Understand AuthContext, parameter hashing, and why a login proof is not a universal wallet permission.
Ethereum signing
Derive public accounts and sign hashes, personal messages, and EIP-155 transactions.
Imported keys
Import, inspect, deactivate, reactivate, and sign with externally generated keys.
Solana signing
Configure Ed25519 HD material, derive public keys, and sign Solana message bytes.
Authenticator catalog
Select an access model based on proof semantics, operational risk, and recovery requirements.
Monstera Connect
Add a compact wallet button, approve messages and verify website login with your own server.
Embed Monstera
Embed the working public wallet explorer, then plan an authenticated integration deliberately.
Architecture
Explore the factory, beacon, per-wallet vaults, key storage, authenticators and signing engine in an interactive contract atlas.
Networks and deployments
Canonical Sapphire network configuration and the deployment addresses documented by the current blueprint.
Security checklist
Operational controls required around confidential key storage and programmable authentication.
API boundaries
Know when to use WalletLogic, KeyVaultV3, the factory, or authenticator contracts directly.
Troubleshooting
Diagnose authentication failures, configuration errors, and network mismatches at the correct layer.
