Integrate wallets into your application
Users sign up with email or social login and approve wallet actions with a passkey. The passkey’s private key stays with the user’s authenticator, so Rhinestone can’t sign for the user or move their funds. See Self-custody for what the user controls and Security and self-custody for the full control path, including recovery. Each wallet has the same address across supported EVM chains. Your application can offer multichain interactions without asking users to create a separate wallet for each network.Configure how the wallet works
The smart account separates assets from the credentials used to control them. You can shape its behavior around your application:- Validation: authorize actions with passkeys and enforce the account’s approval rules onchain.
- Session keys: authorize repeated interactions and background automation without asking users to approve every action.
- Recovery: configure a way to restore account access when a passkey is lost.
Connect wallets to transactions
Wallets determine how users authorize actions. Rhinestone’s transaction infrastructure handles how those actions reach the chain. Combine them to let users transact with assets held across chains, swap tokens, and interact with protocols. Sponsor fees so users do not need to acquire gas tokens before using your application.Get started
- Embedded wallets: explore the wallet experience and capabilities.
- Session keys: enable repeated actions and automation.
- Transactions: explore relaying, multichain execution, and sponsorship.