Check every review card before signing. Server checks, route limits and simulation reduce some errors but cannot guarantee a fill or prevent every loss.
Review the card#
- Confirm the executing account, network and exact token.
- Verify the amount and recipient or destination.
- Inspect the quoted output, minimum received and slippage where applicable.
- Review Maren fees, provider costs and gas separately.
- Approve only if the complete action matches your request.
A quote moves nothing. A prepared action is unsigned. A submitted action can still be pending or fail.
Limits and permissions#
Memory settings show saved server-enforced limits. A mandate also has signed budgets, scope and an end date. Installed account permissions can be narrower still. A chat instruction cannot relax a saved limit or expand a signed mandate.
There is no universal daily, weekly and per-transaction policy editor covering every product. Review the actual limits on the account, wallet, mandate and action you use.
Simulation and settlement boundaries#
Simulation reflects the state and execution path checked at the time. It does not guarantee future inclusion or output, and Maren does not claim universal fork-based testing or private routing for every transaction.
Separate cross-chain operations do not revert as one atomic transaction. Check destination delivery and refund status. A later plan step waits for the earlier outcome and does not undo an earlier settled transaction.
Handle a failed or unknown result#
Read the existing transaction reference and status before retrying. An unreadable or unknown result is not proof that nothing moved. Check balances and the chain result, and get a fresh quote before another approval. Network costs can remain payable after failure.
Illustrative prompt: “Check this transaction,” followed by the transaction hash and network. Never share private keys, passwords or authentication tokens in chat.