Account Type

In addition to the wallet type (infrastructure model), the account type you choose also determines the capabilities supported in the wallets you create. Circle offer two account types:

• Externally Owned Accounts (EOA)
• Smart Contract Accounts (SCA)

The following table shows the account types supported by product:

Blockchain support

The following table shows which blockchains support EOAs or SCAs:

Externally Owned Accounts

EOA are the most commonly used account type in Ethereum and only supported account type in Solana. They consists of a private and public key, with the public key representing the account address. EOAs require secure management of the private key and always require gas tokens for initiating transactions. While EOAs offer the flexibility to initiate any transaction, they have certain limitations, such as the need for a private key and the inability to control them programmatically.

Benefits:

• Zero Cost Creation: Creating an Externally Owned Account (EOA) does not incur any fees, making it an accessible option for users. This is especially important for Networks like Ethereum Mainnet, where gas costs are higher.
• Versatile Transaction Initiation: EOAs can initiate any transaction on the Ethereum network, allowing users to interact with various decentralized applications and perform a wide range of operations.

Limitations:

• Private Key Dependency: EOAs require the secure management of a private key. Users must protect their private key to ensure the security and control of their EOA, as it grants access to account functions and funds.
• Native Token Dependency for Gas: To perform transactions or execute operations on the Ethereum network, EOAs must hold native tokens such as Ether (ETH) to cover gas fees. These tokens must pay for the computational resources utilized during transaction validation and execution. Solana natively supports gas subsidy with feePayer, which means developers can sponsor gas fees on behalf of users.

Smart Contract Accounts (SCA)

SCA is another type of Ethereum account that replaces an EOA with a smart contract. SCAs do not have private keys but are often controlled by an EOA that interacts with the deployed smart contract. SCAs allow developers to write customized logic within the smart contract, enabling advanced functionalities. SCA can have different version types and by default modular smart contract accounts are created for all developers (one can view the exact version type in the succesful repsonse of creating a wallet).

SCAs have been in the Ethereum ecosystem for many years but recently gained popularity thanks to a new standard called ERC-4337 (account abstraction). ERC 4337 went live on Mainnet in March 2023, enabling a trustless standard the community could build SCA around. ERC-4337 also introduced the concept of paymaster - which enables simplified gas abstraction, enabling anyone to sponsor gas fees for the end user or letting the end user pay for gas in any ERC-20 token.

When considering wallet infrastructure models, choosing the most suitable combination of infrastructure model (user-controlled or developer-controlled) and account type (EOA or SCA) empowers developers to create powerful and user-friendly applications tailored to their needs.

Benefits:

• Custom Logic and Functionality: Smart Contract Accounts (SCAs) allow developers to build custom logic and functionality directly into the account. By deploying smart contracts to control SCAs, developers can create innovative and customized features, enabling advanced capabilities and automated operations within the wallet.
• Gas Abstraction and Fee Sponsorship: SCAs offer gas abstraction, simplifying gas fee management for end-users. Developers can implement mechanisms, such as the paymaster pattern, to sponsor gas fees on behalf of users. This reduces the burden on users to hold and manage native tokens for gas and enhances the overall user experience by providing a seamless gas fee payment process.

Limitations:

• Gas Tokens Required for Creation: Gas tokens are required when creating SCA wallets. However, emerging solutions like the one implemented in Programmable Wallets address this limitation by introducing a lazy deployment mechanism. This process postpones the gas fee payment until the first outbound transaction, easing the initial cost burden of SCA wallet creation.

Specify an EOA or SCA

📘

Solana only supports EOAs.

To choose between an EOA or SCA, set the accountType to SCA or EOA when creating a wallet.

Applicable APIs:

• Create a challenge for user initialization and create wallet(s): POST /user/initialize.
• Create a user-controlled wallet(s): POST /user/wallets.
• Create a developer-controlled wallet(s) POST /developer/wallets.

// EXAMPLE REQUEST BODY IN JSON
// For deveveloper-controlled wallets 
// entityentitySecretCiphertext and walletSetId are also required in the request.

// SCA
{
  "idempotencyKey": "a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11",
  "accountType": "SCA", // HERE
  "blockchains": [
    "MATIC-AMOY"
  ]
}

// EOA
{
  "idempotencyKey": "a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11",
  "accountType": "EOA", // HERE
  "blockchains": [
    "MATIC-AMOY"
  ]
}

Selection guidance

Based on our experience, SCAs generally provide a more straightforward user experience for most use cases. They allow developers to focus on creating innovative functionalities within the smart contract. However, the specific needs of each project should be carefully considered when choosing between EOA and SCA account types.

🚧

We recommend using EOAs if you are building on Ethereum: creating an SCA wallet might become expensive. We strongly recommend using SCAs if you are using any Polygon or any L2s.

Key Considerations