> For the complete documentation index, see [llms.txt](https://docs.gravity.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gravity.xyz/ecosystem-infrastructures/safe.md).

# Smart Contract Wallets

## Overview

Smart contract wallets are blockchain-based applications that manage digital assets through programmable smart contracts. Unlike traditional wallets, they offer enhanced functionalities like multi-signature approvals, customizable access controls, and automated transaction processes. These features provide users with increased security, flexibility, and control over their assets.

## Smart Contract Wallets

### Safe

Safe Wallet is a leading smart contract wallet offering advanced security features such as multi-signature authorization, transaction simulation, and account recovery. It provides users with secure and customizable asset management solutions.

[Get Started with Safe on Gravity](https://safe.gravity.xyz/welcome?chain=gravity) — hosted UI for Gravity Alpha L2 (`?chain=gravity`) and Gravity Mainnet L1 (`?chain=grav`).

Canonical Safe v1.4.1 contracts are deployed on:

* [Gravity Mainnet (L1)](/developer-resources/deployed-contracts.md#safe-wallet-smart-account-suite-v1-4-1)
* [Longevity Testnet (L1)](/developer-resources/deployed-contracts-testnet.md#safe-wallet-smart-account-suite-v1-4-1) — contracts live; create/execute via SDK or Foundry (testnet is not yet in the hosted UI)

When creating a Safe on Gravity, use the **SafeL2** singleton (`0x29fcB43b46531BcA003ddC8FCB67FFE91900C762`).


---

# 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://docs.gravity.xyz/ecosystem-infrastructures/safe.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.