Maren uses account abstraction: Kernel smart accounts on supported EVM networks and Swig smart accounts on Solana. Review the account and authority used by each action before signing.
Passkeys and approvals#
Passkeys use your browser and authenticator for registration and approval. Your device may ask for a fingerprint, face, PIN or security key. Storage and synchronization depend on your authenticator; a passkey is not necessarily confined to one physical device.
A passkey approval is bound to the operation being reviewed. A chat message or saved memory cannot substitute for a required signature.
Delegated permissions#
A session permission can restrict programs, tokens, recipients, spending and expiry, according to the account and operation. A mandate adds signed standing rules and server checks; it does not grant unrestricted access to your main account.
Automated Solana execution uses a server-held delegate when the required permission is installed. Pausing or revoking a mandate stops future mandate submissions subject to an already-submitted transaction. Removing an onchain role is a separate operation.
Separate wallets#
Terminal Speed Wallets hold trading funds and sign in the browser. Mint jobs have their own funded wallet flow. Do not assume every product signs from your primary smart account or uses the same custody and recovery path.
Limits and uncertainty#
Saved limits are checked by the server. Quotes and simulation cannot guarantee inclusion, price or recovery. Gas sponsorship applies only when explicitly offered. Review transaction safety before moving funds.