> For the complete documentation index, see [llms.txt](https://docs.autonos.vip/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autonos.vip/4.-core-mechanisms-and-security-the-architecture-of-trust/4.1-cryptographic-guardrails-and-native-wallet-abstraction.md).

# 4.1 Cryptographic Guardrails and Native Wallet Abstraction

At the heart of the AutonOS security model is the decoupling of "Ownership" from "Execution." Traditional DeFi interactions require a user to sign every transaction with their private key, exposing the primary vault to the network for every move. AutonOS utilizes an advanced implementation of **Native Wallet Abstraction**, creating a specialized relationship between a user’s Primary Vault and an Agent’s Operational Wallet.

#### The Policy-Driven Execution Model

Instead of granting the agent full access to a wallet, the user signs a high-level "Policy Mandate." This mandate is a cryptographic proof that defines the boundaries of the agent’s authority. The agent operates within a restricted execution environment where its ability to interact with the blockchain is filtered through an **Embedded Policy Engine**.

| Security Component    | Functional Description                                                                 | Risk Mitigation                                                                              |
| --------------------- | -------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| Asset Segregation     | Assets are allocated to specific agent sub-accounts rather than a general pool.        | Limits potential loss to only the capital assigned to a specific strategy.                   |
| Contract Whitelisting | Agents can only call functions on pre-approved, audited smart contract addresses.      | Prevents "drainer" attacks or interactions with malicious, unverified protocols.             |
| Value Outflow Caps    | Hard limits on the total amount of value that can leave the system in a single period. | Prevents catastrophic loss in the event of an unforeseen logic error or oracle manipulation. |
| Slippage Enforcement  | Mandatory minimum return parameters hardcoded into the transaction payload.            | Protects against MEV (Maximal Extractable Value) attacks and sandwiching.                    |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.autonos.vip/4.-core-mechanisms-and-security-the-architecture-of-trust/4.1-cryptographic-guardrails-and-native-wallet-abstraction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.