EIP-7702

EIP-7702 delegates an EOA to smart account code while preserving its address and history. Configure it when your signer supports EIP-7702 authorizations and you need modules, session keys, or sponsored execution without moving assets to a new address. See EIP-7702 account setup for the protocol model and tradeoffs.

Configure the account

Pass the same viem account as the ECDSA owner and as eoa. The account must implement signAuthorization in addition to the normal message and typed-data signing methods.

import { RhinestoneSDK } from '@rhinestone/sdk'
import { privateKeyToAccount } from 'viem/accounts'
import type { Hex } from 'viem'

const eoa = privateKeyToAccount(process.env.PRIVATE_KEY as Hex)

const rhinestone = new RhinestoneSDK({
  auth: {
    mode: 'apiKey',
    apiKey: process.env.RHINESTONE_API_KEY!,
  },
})

const account = await rhinestone.createAccount({
  evm: {
    owners: {
      type: 'ecdsa',
      accounts: [eoa],
    },
    eoa,
  },
})

This example runs server-side. For an embedded signer in a browser, configure short-lived JWTs as described in security. The eoa account object passed to createAccount must itself implement signAuthorization; access to an authorization method elsewhere on the provider is not enough.

walletClientToAccount does not copy signAuthorization in SDK 3.0.0. Do not use that adapter for EIP-7702. Use a provider-supplied viem account that implements authorization signing, or build a custom viem account adapter that delegates signAuthorization to the provider’s supported method.

Sign the required data

Sign initialization data before preparing the intent. Normal signTransaction then collects the required EIP-7702 delegation proofs alongside the intent proofs:

Sign the account initialization

const eip7702InitSignature = await account.signEip7702InitData()

The signature is valid across supported EVM chains. Cache it for this account configuration and include it whenever you prepare a transaction, because the account may not yet be initialized on every chain.

Prepare and sign the intent

const prepared = await account.prepareTransaction({
  ...transaction,
  eip7702InitSignature,
})
const signed = await account.signTransaction(prepared)

Here, transaction uses the v3 destination and singular source input described in Send a transaction. Delivery requires a source; user-paid execution needs a selected fee token. Only sufficiently sponsored no-delivery execution can omit the source.

Submit the signed transaction

const result = await account.submitTransaction(signed)
await account.waitForExecution(result)

Submission does not collect signatures. Do not pass a separate authorizations option. For independent owner approval, collect indexed delegation contributions with signAuthorizations(prepared) and pass them to assembleTransaction as shown in Custom signing.

Limitations

The EOA remains a root authority. Compromise or loss of its key cannot be repaired by rotating only a module owner.
Do not treat a module threshold as removing the EOA’s authority.
Wallet support varies. Use EIP-7702 only when the signer exposes authorization signing and allows the intended delegation.

For fee sponsorship configuration, follow sponsorship setup rather than embedding sponsorship credentials in the client.

Account setup

Recovery

Signing

Configuration

Integration

SDK reference

Configure the account

Sign the required data

Limitations

​Configure the account

​Sign the required data

​Limitations

Configure the account

Sign the required data

Limitations