Safe smart accounts and identity
Every Sumvin user has a Safe smart account — a multisig contract deployed on their primary chain. The Safe is the user’s on-chain identity anchor. It is the address that appears in their user , the address that signs their PINTs (via the Safe’s signer set), and the counterparty for any on-chain action the user authorises.Why Safe rather than an EOA
An externally owned account (EOA) is a single keypair — lose the key, lose the identity. A Safe is a contract with a configurable signer set, which gives three properties that matter for identity:- Programmable ownership. Agent signers (and, later, passkeys and recovery keys) can be added and removed without changing the address.
- Contract-based signature verification. Safes implement EIP-1271, so any party can verify a signature against the Safe without knowing which signer produced it.
- Multi-device resilience. A user can authorise multiple devices and agents against the same identity without spraying addresses across surfaces.
How a Safe binds to an SRI
The Safe’s address is the identifier in the user’s SRI and in any PINT they sign:verifyingContract in the EIP-712 domain separator on every PINT the user signs, and as the wallet claim on the exchanged JWT.
Chain considerations
A Safe is deployed on a specific chain. The user’s primary EOA determines their primary chain, and the Safe is deployed on that chain asynchronously after user creation. The Platform API returns202 Accepted during that window and exposes a poll link — see the wallets guide for the full flow.
Cross-chain operations require deploying Safes on additional chains; the deterministic deployment means the same address is reachable on each.
See also
- Wallets guide — Safe creation, chain selection, ownership verification
- EIP-712 & Purchase Intents — the Safe address as
verifyingContract - Sumvin Identity overview — Safe as the identity anchor