Appearance
Safe Smart Account
A Safe wallet is a smart contract account on EVM chains. IBEx deploys and drives Safe-compatible accounts so users can sign with passkeys instead of seed phrases for the primary signer.
What is a Safe wallet?
The Safe is a multi-signature and module-capable smart-account standard (see Safe documentation). The contract holds assets and encodes authorization rules; “owners” are addresses or abstract signers that must approve operations according to the configured threshold.
Passkey signing
IBEx uses FIDO2 / WebAuthn passkeys in the browser (or platform authenticators). For supported flows:
- The authenticator performs the WebAuthn ceremony (user presence, sometimes verification).
- Cryptographic material is derived in a deterministic way from the WebAuthn assertion and your integration parameters, consistent with passkey-based smart-wallet patterns (no raw private key export to the server).
- The resulting signature is presented to the Safe contract so it can validate the user operation (e.g. deployment, transaction batch).
This preserves a self-custody model: the service does not hold a classic EVM private key for the user’s passkey path; authorization is bound to the authenticator and your app’s challenge/registration flow.
Supported signer types
| Signer | Role on IBEx |
|---|---|
| PASSKEY | Primary supported signer for Safe operations. |
| EOA | Traditional externally owned signer — work in progress as a companion or fallback, depending on product rollout. |
Features
Typical Safe capabilities relevant to IBEx integrations:
- Recovery — social or module-based recovery patterns where the Safe design allows (configured per deployment and product).
- Multi-sig — threshold signatures across multiple owners when enabled.
- Programmable transactions — batched calls, guards, and modules as supported by the deployed Safe version and chain.
Exact module sets and policies depend on IBEx’s deployed configuration and your API contract.
API usage
- Target the correct chain with
X-Blockchain-Id(see Supported blockchains). - Follow the API guides for sign-up, sign-in, and operations that create challenges, deploy the Safe, and submit user operations or signatures.
See also
- EOA Wallet — comparison and limitations
- Ethereum — example L1 deployment context