> **Can't find what you're looking for?** Use `search_docs` on the docs MCP server at `https://www.openfort.io/api/mcp` to find what you need.
>
> **Have feedback?** Use `submit_feedback` on the same MCP server.

# Delegate to 7702 account

[EIP-7702](https://eips.ethereum.org/EIPS/eip-7702) lets a plain EOA **act as a smart account**, so the user keeps their familiar EOA address while gaining gasless, sponsored sends. Configure `accountType: .delegatedAccount` (with a `chainId`):

```swift
let account = try await OFSDK.shared.configure(
    params: OFEmbeddedAccountConfigureParams(
        chainId: 84532, // Base Sepolia
        recoveryParams: OFRecoveryParamsDTO(recoveryMethod: .password, password: recoveryPassword),
        accountType: .delegatedAccount
    )
)
// account.address == the user's EOA; account.implementationType == "CaliburV9"
```

A delegated account's **first** send on a chain must carry a one-time EIP-7702 authorization that delegates the EOA to the Calibur implementation. The SDK signs and attaches it for you through the embedded signer — no key export, no extra call — so you just [send](#send-a-sponsored-transaction) through the provider exactly like a smart account. Subsequent sends on the same chain skip it automatically.

:::note
Delegated accounts are chain-scoped — pass the `chainId` at configure time. The active chain a send executes on follows the provider (see [Switch chains](https://www.openfort.io/docs/products/embedded-wallet/swift/wallet/switch-chains)).
:::

## Delegate to a different implementation

On a [supported EVM chain](https://www.openfort.io/docs/configuration/chains), `accountType: .delegatedAccount` delegates to Openfort's [Calibur](https://www.openfort.io/docs/configuration/addresses) implementation, which keeps your transactions visible in the [dashboard](https://dashboard.openfort.io). Calibur is the recommended target on iOS.

To delegate to a different implementation — for example the `Simple` 7702 account or your own contract — or to delegate on a chain Openfort doesn't natively support, you sign the EIP-7702 authorization for that implementation manually and submit it through viem's bundler/paymaster clients, as shown in the [React](https://www.openfort.io/docs/products/embedded-wallet/react/wallet/actions/eip-7702-authorization#delegate-to-a-different-implementation) and [JavaScript](https://www.openfort.io/docs/products/embedded-wallet/javascript/smart-wallet/eip-7702-authorization#delegate-to-a-different-implementation) guides.

:::warning
Only [Openfort-supported implementations](https://www.openfort.io/docs/configuration/addresses) appear in the dashboard and can be tracked. Transactions from a smart account Openfort does not natively support will not show up there.
:::

## Next steps

* [Send a transaction](https://www.openfort.io/docs/products/embedded-wallet/swift/wallet/send) — the non-sponsored flow.
* [Switch chains](https://www.openfort.io/docs/products/embedded-wallet/swift/wallet/switch-chains)
* [Set up a wallet](https://www.openfort.io/docs/products/embedded-wallet/swift/wallet/recovery)