Maren reads information with tools and prepares supported actions for your review. A request, a prepared card, a signature and a confirmed transaction are separate stages.
Describe the request#
Name the asset, network, amount and recipient when relevant. For example: “What is the price of SOL?” is a read. A request to move money needs the details for that specific action. Missing or ambiguous details can lead to a question.
Read and check#
Tools read balances, prices, quotes and supported routes. Quotes are estimates, go stale quickly and reserve nothing. The server checks supported actions, ownership, required evidence and applicable limits before allowing preparation.
Checks and simulation depend on the execution path. A quote is not a simulation or a guarantee of the final output. Maren does not promise that every transaction has been tested on a fork of the blockchain.
Review and sign#
Review the action card's asset, amount, network, recipient, fees and any minimum output or slippage condition. A prepared card is unsigned. Follow its signing or arming flow only when the details match your request.
Smart accounts use account abstraction. Terminal and mint workflows can use separate funded wallets with their own approval flows. A signed mandate can authorize bounded later actions; see Mandates.
Follow settlement#
Submission does not prove settlement. Follow the returned transaction reference and status. For plans, a later funding step uses what the earlier receipt says arrived, rather than the earlier quote.
If an outcome is unknown, wait for its status to resolve before trying again. Cross-chain source confirmation alone does not prove destination delivery.