Top ERC-4337 account abstraction SDKs in 2026, compared

Covalent TeamUpdated 12 min read

Which ERC-4337 account abstraction SDKs are current: permissionless.js, ZeroDev, Alchemy, Biconomy, Safe and Etherspot, and what a gasless dApp needs.

An account abstraction SDK builds and sends ERC-4337 UserOperations from a smart account, so your app can batch calls, sponsor gas or let users sign in without a seed phrase. The list of SDKs has changed a lot since ERC-4337 reached mainnet: some of the best-known packages are no longer maintained or have been replaced by their own vendors. This guide compares the ones that are current, says which old packages to move off, lists what a gasless dApp needs, and shows how to read the UserOperations your app sends with GoldRush.

Checked on 21 November 2026 against the npm registry, each package's published code and each vendor's documentation. This is not a ranking.

What an account abstraction SDK does

ERC-4337 adds smart contract accounts to Ethereum and other EVM chains without a protocol change. Instead of a transaction, the account's owner signs a UserOperation. A bundler collects UserOperations and submits them in one transaction to the EntryPoint, a singleton contract that validates each one against its smart account and executes it. A paymaster can pay the gas for it, or take it in an ERC-20 token.

An SDK wraps that flow: it computes the smart account's address, builds and signs the UserOperation, estimates gas, asks a paymaster for sponsorship and sends it to a bundler. Two things decide which SDK can work with which account and infrastructure:

  • The EntryPoint version. Each version is a different contract at a different address, and a smart account is built for one of them. These are the addresses in viem's constants:
EntryPoint Address
v0.6 0x5FF137D4b0FDCD49DcA30c7CF57E578a026d2789
v0.7 0x0000000071727De22E5E9d8BAf0edAc6f37da032
v0.8 0x4337084D9E255Ff0702461CF8895CE9E3b5Ff108
  • EIP-7702. It lets an existing EOA delegate to smart contract code, so a user keeps their address and gains smart account features such as batching and sponsored gas. Several SDKs now support it alongside ERC-4337.

The SDKs at a glance

Each row is the package the vendor's documentation points new projects to. "EntryPoint" lists the EntryPoint addresses the package's published code ships with; "EIP-7702" is yes where the vendor documents it.

SDK npm package Latest (published) EntryPoint EIP-7702
permissionless.js permissionless 0.5.2 (2026-10-23) v0.6, v0.7, v0.8 Yes
ZeroDev @zerodev/sdk 5.5.12 (2026-11-06) v0.6, v0.7 Yes
Alchemy Wallet APIs @alchemy/wallet-apis, @alchemy/smart-accounts 5.3.0 (2026-10-05) v0.6, v0.7, v0.8 Yes
Biconomy AbstractJS @biconomy/abstractjs 2.0.3 (2026-11-17) v0.7 Yes
Safe Relay Kit @safe-global/relay-kit 6.1.5 (2026-10-28) v0.6, v0.7 Not in its docs
Etherspot Modular SDK @etherspot/modular-sdk 6.1.2 (2026-06-25) v0.7 Not in its docs
viem viem (viem/account-abstraction) 2.58.4 (2026-11-21) v0.6, v0.7, v0.8 Yes

All seven are MIT licensed TypeScript packages. Every one except Etherspot's depends on viem.

permissionless.js (Pimlico)

permissionless.js is Pimlico's TypeScript library for ERC-4337, built on viem. It isn't tied to one account: its account support table lists Safe, SimpleAccount, Kernel, Biconomy, LightAccount, Trust Wallet and Thirdweb accounts, each with the EntryPoint versions it works on. SimpleAccount is the one listed for EntryPoint v0.8. It works with any ERC-4337 bundler and paymaster, and Pimlico runs its own, which its docs list for EntryPoint v0.6, v0.7 and v0.8 and EIP-7702. Its EIP-7702 guides turn an EOA into a smart account and send a sponsored UserOperation from it.

Pick it when you want to choose the smart account separately from the infrastructure, or support several account types in one app.

ZeroDev

The ZeroDev SDK is built on Kernel, ZeroDev's modular smart account, and on viem. Kernel is extended with plugins: validators such as passkeys, permissions (session keys) for keys with limited rights, and recovery. The SDK's constants cover EntryPoint v0.6 and v0.7, and its quickstart uses EntryPoint v0.7 with Kernel v3.1. ZeroDev has a separate EIP-7702 quickstart.

Pick it when you need fine-grained permissions, such as a session key that an agent or backend can use for a limited set of calls.

Alchemy Wallet APIs

Alchemy's SDK has been replaced twice. @alchemy/aa-core (v3) was followed by Account Kit (v4, the @account-kit/* packages), and Alchemy's docs now mark Account Kit as deprecated with Wallet APIs as its successor. In the current (v5) packages:

  • @alchemy/wallet-apis is the high-level client: EIP-7702 smart wallets, signing and sending transactions, with gas sponsorship and batching. It works with Privy, Turnkey, Openfort or any viem-compatible signer.
  • @alchemy/smart-accounts replaces @account-kit/smart-contracts: viem smart account implementations of LightAccount, Modular Account v1 and Modular Account v2, the last with EIP-7702.

The smart accounts work with any ERC-4337 bundler through viem's bundler client. Alchemy's own bundler is Rundler.

Biconomy AbstractJS

Biconomy's current SDK is AbstractJS (@biconomy/abstractjs). It manages a Nexus smart account that has the same address on every chain, and runs batched and cross-chain flows through Biconomy's Modular Execution Environment (MEE), signed once by the user. For embedded wallets such as Privy, Dynamic and Turnkey it has an EIP-7702 mode that keeps the user's EOA address.

The packages the old version of this guide described, @biconomy/account, @biconomy/bundler and @biconomy/paymaster, were last published in October 2024. Biconomy's docs have a migration guide from Smart Account V2 to Nexus that keeps the account's address, balance and history.

Safe Relay Kit

Safe's smart accounts support ERC-4337 through the Safe4337Module, which must be used with Safe v1.4.1 or newer. In the Safe{Core} SDK, the Relay Kit's Safe4337Pack builds and sends UserOperations for a Safe, with EntryPoint v0.6 and v0.7 addresses in its code, and the Protocol Kit (@safe-global/protocol-kit, 8.0.11) handles the Safe itself. permissionless.js also supports Safe accounts.

Two Safe kits from the old version of this guide are deprecated on npm: @safe-global/auth-kit (use an auth provider directly) and @safe-global/onramp-kit (use an onramp directly). The Relay Kit's Gelato relaying isn't supported from 1 September 2026; Safe points to its ERC-4337 guide instead.

Pick it when the account should be a Safe, for example a multisig treasury or a team wallet.

Etherspot Modular SDK

The Etherspot Modular SDK works with Etherspot's ERC-7579 modular account: it installs, lists and removes validator, executor and hook modules, and batches transactions. Its code uses EntryPoint v0.7. Etherspot's bundler, Skandha, lists EntryPoint v0.6 and v0.7 as compatible. The older Prime SDK (@etherspot/prime-sdk), on EntryPoint v0.6, was last published in December 2024.

viem's account abstraction module

viem, the TypeScript library most of these SDKs are built on, has its own viem/account-abstraction module: a bundler client to send UserOperations to any ERC-4337 bundler, a paymaster client, and smart account implementations including Coinbase Smart Wallet, Solady's account and a Simple7702 account for EIP-7702. It is the lowest-level option: you choose the account, bundler and paymaster yourself. Its constants also include an EntryPoint v0.9 address.

Packages that are no longer current

If your code imports one of these, plan a move:

Package Last published Status on 21 November 2026
userop (StackUp) 2024-04-07 No release since 0.4.0-beta.5. Its README's docs link now returns 404, and Pimlico's docs have a migration guide for Stackup users. EntryPoint v0.6 only.
@biconomy/account, @biconomy/bundler, @biconomy/paymaster 2024-10-11 Superseded by @biconomy/abstractjs, with a migration guide to Nexus.
@alchemy/aa-core 2024-08-02 v3, followed by Account Kit (v4), now deprecated in favour of @alchemy/wallet-apis (v5).
@account-kit/* 2026-08-11 Account Kit is deprecated in Alchemy's docs; Wallet APIs is the successor.
@safe-global/auth-kit, @safe-global/onramp-kit 2024 Marked deprecated on npm.
@etherspot/prime-sdk 2024-12-23 Still in Etherspot's docs, but on EntryPoint v0.6; the Modular SDK is the maintained package.

What a gasless dApp needs

A gasless dApp lets a user sign in and act onchain without holding ETH for gas. Whichever SDK you pick, it has four parts:

  1. A signer for the owner key. The smart account is controlled by an owner key, and users shouldn't have to manage it as a seed phrase: an embedded wallet, a passkey or a social login gives them one behind a familiar sign-in. Alchemy's Wallet APIs and Biconomy's AbstractJS work with embedded wallets such as Privy and Turnkey, and ZeroDev has a passkey validator.
  2. A smart account. Created from the owner with one of the SDKs above. Its address is known before it is deployed; the first UserOperation deploys it, so the user never sends a deployment transaction.
  3. A paymaster with a sponsorship policy. The paymaster pays the gas for the UserOperations it agrees to, and the policy decides which: the contracts, users or spending limits you will pay for. Pimlico, Alchemy, Biconomy and ZeroDev each offer a paymaster service.
  4. Sending the sponsored UserOperation. The SDK asks the paymaster to sponsor each call, such as a mint or a tip, and sends the UserOperation to a bundler. Batch several calls into one UserOperation where the account supports it.

Older tutorials build this on Biconomy's BiconomySmartAccount with @biconomy/account, @biconomy/bundler and @biconomy/paymaster; that flow has moved to AbstractJS and the Nexus account, and Biconomy's migration guide from Smart Account V2 to Nexus covers existing accounts. Once the dApp is live, the GoldRush section below shows which of its UserOperations went through your paymaster.

How to choose an account abstraction SDK

  • Start from the account. If you need a Safe, a Kernel or an Alchemy Modular Account, the vendor's SDK is the direct route, and permissionless.js and viem support several of them too.
  • Check the EntryPoint version. A new project should use an account on v0.7 or later; v0.6 accounts are only worth it to stay compatible with accounts you already deployed.
  • Decide on EIP-7702. If your users already have EOAs, such as embedded wallets from Privy or Turnkey, an SDK with EIP-7702 support upgrades them in place without a new address.
  • Keep bundler and paymaster swappable. viem, permissionless.js and Alchemy's v5 smart accounts all accept any ERC-4337 bundler URL, so you aren't tied to one provider's uptime or pricing.
  • Check the release date before you install. Several well-known packages from 2023 and 2024 are no longer maintained; npm view <package> time lists the date of every release.

See your UserOperations onchain with GoldRush

Whichever SDK sends them, every UserOperation ends up as logs on the EntryPoint contract: a UserOperationEvent for each one, with the smart account (sender), the paymaster, whether it succeeded and the gas it used, and an AccountDeployed event when the first UserOperation deploys the account. The GoldRush Foundational API reads them with log events by contract address, which returns every event from a contract in a block range, decoded into named parameters.

This lists the UserOperations the EntryPoint v0.7 contract handled on Base in a range of blocks:

const API = "https://api.covalenthq.com/v1";const ENTRYPOINT_V07 = "0x0000000071727De22E5E9d8BAf0edAc6f37da032";const headers = {    Authorization: `Bearer ${process.env.GOLDRUSH_API_KEY}`,}; // The UserOperations an EntryPoint handled in a block range, one row each.async function getUserOps(chain, startBlock, endBlock) {    const url =        `${API}/${chain}/events/address/${ENTRYPOINT_V07}/` + `?starting-block=${startBlock}&ending-block=${endBlock}`;    const res = await fetch(url, { headers });    if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);    const { data } = await res.json();    return data.items        .filter((log) => log.decoded?.name === "UserOperationEvent")        .map((log) => {            const p = Object.fromEntries(log.decoded.params.map((x) => [x.name, x.value]));            return {                txHash: log.tx_hash,                block: log.block_height,                // Topic 1 is the userOpHash as hex; the decoded bytes32 value is base64.                userOpHash: log.raw_log_topics[1],                account: p.sender,                paymaster: /^0x0+$/.test(p.paymaster) ? null : p.paymaster,                success: p.success,                gasUsed: BigInt(p.actualGasUsed),                gasCostWei: BigInt(p.actualGasCost),            };        });} const ops = await getUserOps("base-mainnet", 59706003, 59706012);console.table(ops);console.log(ops.filter((op) => op.paymaster).length, "of", ops.length, "used a paymaster");

On 19 November 2026 those ten Base blocks held three UserOperations; one went through a paymaster. Here is that one's UserOperationEvent as the API returned it, abridged:

{    "block_height": 59706008,    "tx_hash": "0x81b482bac688cde56d66216aea1e8a37a9bf044b987236946e8003b8df4470dd",    "raw_log_topics": [        "0x49628fd1471006c1482da88028e9ce4dbb080b815c9b0344d39e5a8e6ec1419f",        "0xa74fd058e0926b6bcc2ab24e5dc6448fa6e852b43fadb73b66b9658f8a7fcb7a",        "0x0000000000000000000000006897a6523119f1221e70e6afb9ec5483d091852b",        "0x000000000000000000000000777777777777aec03fd955926dbf81597e66834c"    ],    "decoded": {        "name": "UserOperationEvent",        "params": [            { "name": "userOpHash", "type": "bytes32", "value": "p0/QWOCSa2vMKrJOXcZEj6boUrQ/rbc7Zrllj4p/y3o=" },            { "name": "sender", "type": "address", "value": "0x6897a6523119f1221e70e6afb9ec5483d091852b" },            { "name": "paymaster", "type": "address", "value": "0x777777777777aec03fd955926dbf81597e66834c" },            { "name": "success", "type": "bool", "value": true },            { "name": "actualGasCost", "type": "uint256", "value": "1362205202214" },            { "name": "actualGasUsed", "type": "uint256", "value": "195851" }        ]    }}
  • The EntryPoint also emits other events, such as BeforeExecution and AccountDeployed, so filter on decoded.name.
  • A paymaster of the zero address means the account paid its own gas.
  • Results come 100 to a page by default. When pagination.has_more is true, add page-number for the next page, or narrow the block range.
  • To follow one smart account rather than the whole EntryPoint, read its transactions with the wallet transaction history endpoint. How to fetch UserOps for a wallet address shows the full approach.

What it costs

Log events by contract address costs 0.01 per item in GoldRush credits, and each log event returned is one item, including the BeforeExecution and AccountDeployed events you filter out. The pricing calculator estimates a month of calls.

Frequently asked questions

What is an account abstraction SDK?

A library that builds, signs and sends ERC-4337 UserOperations from a smart account. It computes the account's address, estimates gas, asks a paymaster to sponsor the operation and submits it to a bundler, so your app doesn't implement the ERC-4337 flow itself.

Which ERC-4337 SDKs are still maintained?

As of 21 November 2026, permissionless.js, the ZeroDev SDK, Alchemy's Wallet APIs, Biconomy's AbstractJS, Safe's Relay Kit and viem had all published a release within the past two months, and Etherspot's Modular SDK in June 2026. StackUp's userop.js, Biconomy's @biconomy/account and Alchemy's @alchemy/aa-core have not been published since 2024.

Is userop.js deprecated?

It isn't flagged as deprecated on npm, but it has had no release since April 2024, the documentation link in its README returns 404, and it targets EntryPoint v0.6 only. Pimlico's docs have a migration guide for Stackup users. For a new project, use one of the maintained SDKs.

Which EntryPoint version should I use?

For a new smart account, v0.7 or later: every SDK in this guide supports v0.7, and permissionless.js, Alchemy's smart accounts and viem also ship v0.8. Stay on v0.6 only for accounts already deployed against it, since an account is built for one EntryPoint.

Do I still need ERC-4337 with EIP-7702?

Not to use EIP-7702 itself: a delegated EOA that holds ETH can batch calls on its own. To sponsor its gas or let it pay in ERC-20 tokens, someone else has to send and pay for its transactions, usually an ERC-4337 bundler and paymaster. Pimlico's docs recommend using the two together, and ZeroDev, Alchemy and Biconomy support both.

How do I build a gasless dApp with account abstraction?

Give users a signer for the owner key (an embedded wallet, passkey or social login), create a smart account for it with a current SDK, set up a paymaster with a sponsorship policy that covers your contracts, and send each action as a sponsored UserOperation through a bundler. The user signs, and the paymaster pays the gas.

How do I track UserOperations onchain?

Read the EntryPoint contract's UserOperationEvent logs. GoldRush's log events by contract address endpoint returns them decoded, with the smart account, paymaster, success flag and gas used for each UserOperation.

Next steps

Get new guides by email

New tutorials and best practices for building with blockchain data, sent as they're published.