> For the complete documentation index, see [llms.txt](https://0xshiven.gitbook.io/guardian-smart-wallet-contracts/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://0xshiven.gitbook.io/guardian-smart-wallet-contracts/welcome.md).

# Welcome

Build a secure and invisible wallet experience for your users!

{% hint style="success" %}
Welcome to the official documentation for Guardian Smart Wallet contracts, a smart contract to provide a secure and invisible wallet experience to your dApp users⚡️.
{% endhint %}

## Overview

> **Guardian Smart Wallet SDK** empowers you with:
>
> * **Unparalleled Security:** Say goodbye to vulnerable private keys. Guardian Smart Wallet leverages account abstraction to protect your assets and provides a very user friendly guardian-based recovery, ensuring your peace of mind.
> * **Uncompromising Control:** Take back control of your digital identity. Guardian Smart Wallet empowers you with features like secure account locking, providing you with the tools to manage your assets with confidence.<br>

> **Explore this documentation to discover:**
>
> * **Our Features:** Guardian Smart Wallet offers features that elevate the wallet experience and security for your users through [smart accounts](/guardian-smart-wallet-contracts/overview/our-features/smart-wallets.md), [asset locking](/guardian-smart-wallet-contracts/overview/our-features/social-account-locking.md) and [social account recovery.](/guardian-smart-wallet-contracts/overview/our-features/social-account-recovery.md)
>
> * **Understand how it all works:** We understand that as a DApp dev, you're concerned about how things work and should be we informed about the [Guardian Smart Wallet architecture ](/guardian-smart-wallet-contracts/overview/architecture.md)and the [role of each contract ](/guardian-smart-wallet-contracts/overview/architecture.md#contracts)deployed to bring these features to life.
>
> * **Guides:** Dive deeper into each contract and it's functions through our extensive contract [guides.](/guardian-smart-wallet-contracts/guides/smart-account-account-factory.md)
>
> * **Troubleshooting and FAQs:** Find answers to your questions and resolve any technical issues you may encounter.
>
> #### **Ready to unlock the potential of** Guardian Smart Wallet Contract&#x73;**? Let's go 🚀!**

## Quick links

{% content-ref url="/pages/Zuv8ON8itF82bKCLx4Dh" %}
[Our Features](/guardian-smart-wallet-contracts/overview/our-features.md)
{% endcontent-ref %}

{% content-ref url="/pages/QbDUhA96jBNXzo9rMxoS" %}
[Architecture](/guardian-smart-wallet-contracts/overview/architecture.md)
{% endcontent-ref %}

{% content-ref url="/pages/DbJcZUYRgTYNWGBCvk4J" %}
[Guides](/guardian-smart-wallet-contracts/guides/smart-account-account-factory.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://0xshiven.gitbook.io/guardian-smart-wallet-contracts/welcome.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
