# Safe

> Smart account infrastructure for multisigs, treasury operations, and programmable account controls.

- Readiness score: **80/100** (score.v2)
- Integration difficulty: low
- Chains: arbitrum-one, bsc
- Categories: accounts, multisig, smart-accounts
- Last verified: 2026-05-29 by composewith.eth seed research (confidence: medium)

## Resources

- docs: https://docs.safe.global/
- sdk: https://github.com/safe-global/safe-core-sdk
- template: https://docs.safe.global/sdk/overview
- support: https://help.safe.global/
- grant: https://safe.global/ecosystem

## Good for

- team treasuries
- protocol operations
- account modules
- transaction policies

## Avoid for

- consumer onboarding without extra wallet UX work

## Capabilities

### Smart account treasury (production-ready)
Best for: multisig governance, admin controls, treasury security
- Module and transaction service support varies by chain and feature.

## Composes with

- **biconomy** (transactions_and_paymasters; supports) — Biconomy can add paymasters, relaying, and session-key-style UX around smart account flows.
- **gelato** (automation; supports) — Gelato can automate approved operational transactions and recurring protocol tasks.
- **x402** (payments_and_commerce; supports) — Safe can hold treasury and operational controls for x402-enabled marketplaces or paid APIs.

## Per-chain support

### bsc (production-ready)
- Docs: https://docs.safe.global/advanced/smart-account-supported-networks
- BNB Smart Chain (chain id 56) is in Safe's supported networks; point the Safe SDK and transaction service at the BSC deployment.
- Limitations: Module and transaction-service feature support can differ by chain; confirm the specific Safe features you need are available on BSC.
- Verified 2026-06-10 (source: https://docs.safe.global/advanced/smart-account-supported-networks)

## Advisories

- **Reported Safe singleton address change on Arbitrum** (new_known_issue, recommended) — A community report claims the Safe singleton factory address changed on Arbitrum One. This advisory has no protocol-owner signature and no onchain verification handle, so it must not be treated as an actionable address swap. The gate downgrades it to a verify-with-the-team known issue.

---
Canonical: https://composewith.eth/protocols/safe · JSON: https://composewith.eth/protocols/safe.json