Safety & Security

sm1 agents are purpose-built for secure, autonomous on-chain execution. Every layer—from the protocol to the wallet—is designed to define strict boundaries around what an agent can do, when it can act, and how its behavior is monitored and enforced.

Framework-Level (sm1 Runtime) The sm1 agent framework enforces security at the execution and reasoning layer—where decisions are made and actions are generated. Agents are designed with minimal default privileges and operate within clearly defined behavioral boundaries.

• Tool-based Permissioning Only explicitly enabled tools (e.g. swap, lend, stake) are available to each agent. Others remain completely inaccessible.

• Tool-specific Constraints Enforce slippage limits, token pair allowlists, liquidity minimums, or protocol-specific ceilings.

• Natural Language Guardrails (Tripwire) Users can define high-level behavioral rules in plain language (e.g. “Never spend more than 20% of the portfolio on a single asset”, or “Avoid NFTs or meme coins”). A secondary AI model monitors the agent’s reasoning and intervenes if these constraints are violated.

• Pre-Execution Simulation Before a transaction is signed, the agent simulates the action to preview on-chain effects and confirm it aligns with its task scope and risk parameters.

Protocol-Level At the network layer, the Secret3 protocol enforces decentralized runtime policies using smart contracts and validator nodes. This layer governs how agents interact across the ecosystem—particularly for agent-to-agent and oracle-to-agent communication.

• Security Layer & Policeman Nodes All messages—whether between agents or from oracles—are intercepted and validated by a decentralized set of Policeman Nodes. These nodes enforce each agent’s declared policies before allowing execution.

• Identity & Policy Enforcement Each agent publishes its operational boundaries (e.g. who it can talk to, what types of data it can consume), which are enforced trustlessly at runtime.