Etherspot in 2026: Modular Smart Accounts, Bundlers, Paymasters and No Confirmed Airdrop

Etherspot is not a consumer wallet, a yield protocol or a token campaign. It is developer infrastructure for building smart-account experiences on EVM networks. Its stack combines software development kits, ERC-4337 transaction infrastructure and a React integration layer so an application can hide some of the mechanics that make onchain products difficult to use.

The practical pitch is straightforward: let an application batch actions, sponsor fees, accept supported ERC-20 tokens for gas, add programmable account permissions and submit account-abstraction operations across many chains. That can make a dapp feel more familiar, but it does not remove blockchain fees, contract risk or infrastructure dependencies. It changes where those concerns sit and who manages them.

What Etherspot currently offers

The Etherspot platform is a collection of related products rather than one wallet. The Modular SDK is a TypeScript library for ERC-7579 smart-account modules. Prime SDK is the older general-purpose ERC-4337 toolkit. TransactionKit packages account-abstraction actions into React components and hooks. Skandha is the bundler, while Arka is the paymaster service. A RemoteSigner SDK supports UserOperation signatures with remotely stored session keys.

Etherspot also advertises EIP-7702 infrastructure. EIP-7702 lets an externally owned account use smart-account behavior without forcing its owner to migrate to a separate account address. Etherspot describes gasless actions, spending caps and session keys as intended uses, and says its EIP-7702 offering connects to the ERC-4337 Shared Mempool. This matters to wallet developers more than to a user looking for a new app to deposit into.

The boundaries are important. Etherspot’s site still labels broader chain abstraction as “coming soon,” even though TransactionKit already supports multi-chain application experiences. Those are not identical claims. Supporting the same application workflow on numerous networks is different from making balances and execution universally chain-agnostic.

How the ERC-4337 architecture moves a transaction

In a conventional Ethereum transaction, an externally owned account signs and broadcasts a transaction while paying gas in the chain’s native asset. Under ERC-4337, an app constructs a UserOperation: a transaction-like object containing the smart-account sender, nonce, initialization data when needed, call data, gas limits, fee parameters, optional paymaster data and a signature.

A bundler validates UserOperations, selects operations from a mempool and submits a bundle to an EntryPoint contract. The EntryPoint performs verification and execution, calling the user’s contract account and, when present, a paymaster. Etherspot’s ERC-4337 documentation identifies UserOperations, bundlers, the EntryPoint and contract accounts as the core pieces, with paymasters and signature aggregators as optional additions.

This architecture avoids a consensus-layer change, but it introduces an offchain transaction-supply chain. The application depends on correct UserOperation construction, the bundler’s simulation and inclusion policy, an RPC provider, deployed account code and the EntryPoint. “Gasless” does not mean computation becomes free; it means a paymaster or another asset can cover the native gas bill.

Etherspot documents EntryPoint v0.6 and v0.7 addresses, while its current Skandha product page also claims support for v0.8 and EIP-7702. Developers should match the SDK, account factory, EntryPoint, bundler endpoint and paymaster version deliberately. A version mismatch is an integration failure, not a cosmetic difference.

Modular smart accounts and ERC-7579

The Modular SDK targets Etherspot’s ERC-7579 account and supports installing, querying and uninstalling modules. Etherspot’s module documentation lists validators, executors, fallbacks and hooks. Validators can define how authority is proven; executors can initiate constrained actions; fallbacks extend account behavior; hooks can run logic around execution. Etherspot notes that only one hook may be installed on its wallet implementation.

That modularity is useful because account features no longer have to be permanently baked into one monolithic wallet. A developer can add session-key permissions for a game, automate recurring actions through an executor or introduce a recovery method through a validator. The official product page also highlights social recovery, while the published session-key tooling supports enabling, disabling and rotating an ERC-20 session-key validator.

Modularity also increases the security surface. A malicious or flawed validator can weaken authorization. An executor can receive powerful capabilities. A hook can affect every execution path. Applications should identify exact module addresses, pin reviewed versions, limit session-key scope and expiry, and test removal and recovery before production use. “ERC-7579 compliant” describes an interface standard; it is not a security certificate for every compatible module.

Skandha bundlers and the Shared Mempool

Skandha is Etherspot’s open-source, TypeScript ERC-4337 bundler implementation. Its job is to simulate UserOperations, maintain or connect to a mempool, choose operations and pay to submit a bundle onchain. The documentation exposes standard methods for estimating gas, sending a UserOperation and retrieving its status or receipt.

Bundling can amortize parts of transaction submission and improve throughput, but “bundled” should not be read as “always cheaper.” Smart-account validation, deployment and paymaster checks consume gas. Savings depend on the chain, calldata, bundle composition, account state and fee market. Users still need an estimate for the complete operation rather than comparing only the underlying contract call.

Skandha can be operated in public or private mode and can be self-hosted. Etherspot documents peer-to-peer canonical mempool settings and promotes Shared Mempool support, which can reduce dependence on a single private relay. For self-hosted Ethereum submission, its MEV-protection guide integrates the Flashbots Auction API. That can provide private routing and frontrunning protection, but it substitutes another transport and relay dependency; it cannot promise that every operation will be included or that every form of MEV disappears.

Arka paymasters and gas abstraction

Arka is Etherspot’s open-source paymaster service. Its documented modes include sponsored transactions, payment with a specified ERC-20 token and a multi-token mode. In sponsorship mode, an application-funded paymaster pays the chain’s native gas. In token mode, the user pays through a supported token while the paymaster handles the native-asset requirement.

Sponsorship is a business expense, not a protocol subsidy. A project must fund the paymaster, define which accounts or actions qualify and protect the service against automated draining. Arka exposes address whitelists and sponsorship policies, and Etherspot’s deposit flow has the developer obtain an API key, fund a supplied address, call the deposit API and whitelist senders.

ERC-20 gas payment has its own friction. The token must be supported, a quote is required and the user may need to approve the MultiTokenPaymaster. Etherspot’s guide shows the approval and intended action being placed in one batch. Developers should display the quoted token amount, allowance target, expiry and failure behavior. A stablecoin-denominated fee can be easier to understand, but it is still a fee and may include token price, liquidity or quote risk.

Supported workflows and network coverage

The official examples cover native-asset, ERC-20 and NFT transfers; balance and asset queries; transaction batching; sponsored operations; swaps; bridge quotes; social-login integrations; fiat onramps; guardians; and concurrent UserOperations. TransactionKit exposes similar capabilities through React components, including batches, contract calls, approvals and token transfers. RemoteSigner adds backend-authorized session-key signing through a cloud key-management service.

The Modular SDK network list includes Ethereum, Polygon, Optimism, Arbitrum, Fuse, Mantle, Gnosis, Base, Avalanche, BNB Chain, Linea, Flare, Scroll, Rootstock, Ancient8, XDC and Celo mainnets, plus a range of active testnets. Coverage can differ by product and version, so the correct check is not merely whether a chain name appears on the website. Developers must confirm account contracts, EntryPoint version, bundler endpoint, paymaster mode and desired module deployment on that chain.

For users, the result can be fewer signatures and no need to acquire a small native-token balance before a first action. For developers, the complexity moves behind the interface: simulation errors, sponsorship limits, account deployment, nonce handling and bridge or swap failures still need clear status messages and recovery paths.

What Etherspot actually costs

Etherspot’s published pricing separates API usage from network gas. Testnet access is free with 1,000,000 credits per month and a five-requests-per-second limit. Mainnet pay-as-you-go costs $1 per 250,000 prepaid credits, supports 40 requests per second and requires a $10 initial top-up. Etherspot says prepaid credits do not expire and network gas is charged separately at network cost with no markup. Enterprise terms are custom.

Endpoint weights make the headline price meaningful. The credit table assigns 300 credits to eth_estimateUserOperationGas, 600 to eth_sendUserOperation, 700 to pm_sponsorUserOperation and 200 to an ERC-20 paymaster quote. At the published rate, estimate plus send consumes 900 credits, or $0.0036 in Etherspot API charges. Adding the 700-credit sponsorship call makes those three calls 1,600 credits, or $0.0064. Retries, reads, logs and quote calls add more.

Those fractions of a dollar are not the total transaction cost. Native network gas remains variable and can dominate on Ethereum. Initial smart-account deployment, module installation, token approval, bridge fees and failed or retried flows can add cost. If a dapp sponsors gas, the cost moves from the user to the dapp’s paymaster budget; it does not vanish.

Infrastructure and security risks to price in

A production integration has several failure domains: Etherspot’s hosted RPC, bundler and paymaster APIs; the underlying chain RPC; the EntryPoint; account and module contracts; price-quote services; and the application’s signer. Rate limits, depleted paymaster deposits, inaccurate simulation, bundler censorship, nonce contention or chain congestion can leave an operation pending or rejected. Teams that need stronger availability can self-host open-source components, but then they inherit relayer keys, monitoring, upgrades, staking, RPC quality and incident response.

Etherspot says its Prime contracts received one specialist review and a second audit from Nethermind, with reports linked through its audit page. Audits reduce uncertainty; they do not cover every future module, frontend, integration setting or operational failure. The RemoteSigner design also places session keys in a cloud KMS behind API authorization, making backend access control and key scope critical.

Paid plans offer API-key restrictions by IP address, CORS origin and smart-account sender. Sender restrictions apply to sensitive methods including UserOperation submission and estimation and paymaster requests. Teams should use those controls, keep unrestricted keys out of browser bundles, set sponsorship policies and monitor credit and paymaster balances. Users should still verify transaction intent and token allowances rather than treating a smoother interface as proof of safety.

No confirmed Etherspot token or airdrop

Etherspot’s current official website, pricing pages and developer documentation describe paid API credits, smart-account infrastructure and open-source software. They do not announce an Etherspot token, token-generation event, points conversion or user airdrop. Therefore, there is no confirmed Etherspot token or airdrop to claim. Using a testnet, creating a smart account or calling a bundler should not be presented as a reward-earning activity.

This distinction is especially important because “credits” are prepaid API usage units, not crypto tokens or points. A site or social post that turns Etherspot credits, Skandha usage or Arka sponsorship into an “allocation” is making a claim that the official product materials do not support.

Likely Etherspot-specific scams include counterfeit token contracts using the Etherspot, Skandha or Arka names; fake eligibility checkers that request wallet signatures; cloned developer portals offering “airdrop API keys”; and impostors in Discord asking users to fund a paymaster address or reveal a seed phrase. Developers also face malicious npm packages with names resembling @etherspot/modular-sdk and fake support agents requesting unrestricted API keys.

Only follow links from etherspot.io, its linked documentation and the official GitHub organization. A legitimate support process never needs a seed phrase or private key. Funding instructions deserve independent verification through the authenticated developer portal and an established official support channel, particularly because real Arka workflows do involve deposits and API keys that scammers can imitate.

Frequently asked questions

Is Etherspot a wallet?

No. Etherspot is primarily infrastructure and developer tooling for wallets and dapps. Its SDKs help applications create and control smart accounts, while Skandha and Arka handle bundling and paymaster functions.

Does “gasless” mean a transaction has no cost?

No. The chain still charges gas. A sponsored flow makes the application or paymaster pay it; an ERC-20 flow lets the user settle through a supported token. API credits are an additional infrastructure cost paid to Etherspot.

Can Skandha be self-hosted?

Yes. Etherspot publishes Skandha as open-source software and documents source, Docker and configuration-based operation. Self-hosting can reduce dependence on Etherspot’s hosted endpoint, but it creates operational and key-management responsibilities.

Has Etherspot confirmed an airdrop?

No. The official materials reviewed for this article contain no confirmed Etherspot token or airdrop. Any claim page, token address or reward schedule should be treated as unverified unless Etherspot publishes it through its official website and linked channels.