Maren's social workspace supports discussion and payment requests. Reading a trader's activity or following an account gives no permission to spend your funds.
Social discussion and payments#
Use social posts as external information, not as transaction instructions. For a payment, name the recipient, token, amount and network in chat. Verify the resolved address and the complete card before signing. A missing or ambiguous recipient must be resolved before preparation.
Create a copy mandate#
Illustrative prompt: “Copy this Solana leader with 1 USDC per entry, 5 USDC total, for 1 day,” with the exact leader address included. Maren drafts signed entry and exit rules, limits and an end date. Review them in the mandate center; a subscription or chat message alone authorizes nothing.
Use a separate copy wallet#
The copy flow creates a separate passkey Solana smart account, distinct from your primary wallet. Its delegated role can spend any token in that copy wallet but cannot manage wallet authorities. Jupiter restrictions and dollar budgets are enforced by Maren's server, not by the broad onchain role. Read this disclosure before installing the delegate.
Fund only the amount you intend to expose. Funding through Maren accepts native Solana USDC and counts against the signed lifetime allowance. Cancellation, withdrawal and an unknown send do not replenish that allowance. Deposits made outside Maren cannot be capped by its server.
Qualify and execute copied trades#
Only qualified leader receipts can trigger an entry or exit. Receipt identity, freshness, leader, token, direction and risk checks must match the signed rules. Entries use the signed USDC size; exits use verified holdings and a fresh price. Both consume trading budget. A missing or stale read stops execution.
A receipt is claimed before execution and is not automatically replayed after an unknown send. A skipped or refused trade is not a filled trade. Aggregate smart-money summaries cannot stand in for a qualified leader receipt.
Pause, revoke and withdraw#
Pause or revoke in the mandate center to stop future submissions. A transaction already submitted may still settle. Revoke removes the server delegate key; removing its onchain role is a separate passkey operation. Owner withdrawals remain available for an existing copy wallet after its mandate is revoked. Review the withdrawal and the onchain role revocation separately.
See Mandates for limits and the event ledger.