Alchemy Account Kit Integration: Smart Accounts in 2 Weeks

The Problem: Users Pay Gas from Their Wallet—a Barrier to Mass Adoption

Every time a new user wants to mint an NFT or swap a token in your dApp, they must have ETH in their wallet for gas. This cuts off up to 80% of the audience who doesn't want to bother buying a native token. Alchemy Account Kit solves this through Account Abstraction (ERC-4337): the user can pay gas in tokens, or you sponsor gas via Paymaster.

We have integrated Account Kit for several DeFi protocols and games. On one DeFi project, we reduced the onboarding flow from 5 clicks to 1, increasing registration conversion by 38%. Below, we break down how we do this—with code, comparisons, and typical pitfalls.

Components of Alchemy Account Kit

Light Account — a minimal ERC-4337 implementation. Cheaper to deploy and use than Safe. Supports: single owner, session keys, EIP-1271.

Modular Account — an extensible account based on ERC-6900 (Modular Smart Account). Allows adding plugins: multisig, spending limits, social recovery.

Gas Manager (Paymaster) — gas sponsorship with policies: by amount, by number of operations, by whitelist of contract addresses.

Alchemy Bundler — built-in bundler with 99.9% SLA and support for all major EVM chains.

Light Account vs. Modular Account: Which to Choose?

Why Use the Built-in Alchemy Bundler?

The bundler is the most critical component: it aggregates user operations, signs them, and submits to the network. Alchemy runs its own bundler with 99.9% SLA and support for all major L2s (Polygon, Arbitrum, Optimism, Base). After setup, synchronization with the network takes minutes, not days. For production, we recommend it—you get uptime guarantees and priority support.

How to Configure the Gas Manager (Paymaster)?

The Gas Manager sponsors gas via policies. In the Alchemy Dashboard, you create a policy, set limits, and receive a policyId. Example configuration:

import { createModularAccountAlchemyClient } from "@alchemy/aa-alchemy";
import { LocalAccountSigner, sepolia } from "@alchemy/aa-core";
import { http } from "viem";

const client = await createModularAccountAlchemyClient({
  apiKey: "YOUR_ALCHEMY_API_KEY",
  chain: sepolia,
  signer: LocalAccountSigner.privateKeyToAccountSigner(privateKey),
  gasManagerConfig: {
    policyId: "YOUR_GAS_POLICY_ID",
  },
});

// Отправка user operation без ETH на кошельке
const { hash } = await client.sendUserOperation({
  uo: {
    target: contractAddress,
    data: encodeFunctionData({ abi, functionName: "mint", args: [] }),
    value: 0n,
  },
});

await client.waitForUserOperationTransaction({ hash });

After integration, the user doesn't notice that the transaction is paid—everything is covered by the dApp. Our clients save up to 40% on gas thanks to optimal policies.

React Hooks

Account Kit provides @alchemy/aa-alchemy/react with ready-to-use hooks:

import {
  AlchemyAccountProvider,
  useSmartAccountClient,
  useSendUserOperation,
} from "@alchemy/aa-alchemy/react";

function MintButton() {
  const { client } = useSmartAccountClient({ type: "ModularAccount" });
  const { sendUserOperation, isSendingUserOperation } = useSendUserOperation({
    client,
    waitForTxn: true,
  });

  return (
    <button
      onClick={() =>
        sendUserOperation({
          uo: { target: NFT_ADDRESS, data: mintCalldata, value: 0n },
        })
      }
      disabled={isSendingUserOperation}
    >
      {isSendingUserOperation ? "Minting..." : "Mint NFT"}
    </button>
  );
}

Session Keys

Account Kit supports session keys—temporary keys with limited permissions. The user approves the session key once, then the app can execute transactions without requesting a signature each time:

const sessionKey = await client.createSessionKey({
  expirationTime: Math.floor(Date.now() / 1000) + 3600, // 1 hour
  permissions: [
    {
      type: "contract",
      address: GAME_CONTRACT,
      functionSelectors: [MOVE_SELECTOR, ATTACK_SELECTOR], // only specific functions
    },
  ],
  spendingLimit: parseEther("0.01"), // max 0.01 ETH per session
});

This is especially valuable for games and applications with frequent small transactions.

How We Integrate Account Kit: Step-by-Step Process

The entire cycle takes 1–2 weeks. We include documentation with code examples and team training.

What's Included in the Service

• Selection and customization of smart account (Light or Modular) — turnkey
• Gas Manager setup with sponsorship policies
• Integration with existing auth (email, social, Web3)
• Adaptation of React UI to Account Kit hooks
• Testing on testnet and mainnet
• Documentation and storybook of components

We have done dozens of integrations for DeFi protocols and NFT marketplaces. Alchemy Account Kit is a mature tool but requires deep understanding of ERC-4337. Get a free assessment of your project—contact us.

Typical Integration Mistakes

When integrating, it's important to avoid: using LocalAccountSigner in production (not safe—replace with Web3Auth or WalletConnect); neglecting nonce management (different from EOA); failing to test Gas Manager policies to prevent budget overruns. We account for these points in every project.

Order your integration today to boost your dApp's conversion. Contact us to discuss details.

We develop crypto wallets turnkey — from custodial solutions for fintech to smart contract accounts on EIP-4337. 5+ years in blockchain development, 40+ projects implemented. Let's examine which architecture to choose for your task and why MPC or Account Abstraction solve the private key problem that MetaMask and classic HD wallets could not close.

Why are classic wallets dangerous for business?

A seed phrase in a browser extension is the only way to restore access. For retail users, this is a barrier to entry (lost phrase = lost money). For corporate treasuries, it is incompatible with compliance (KYC/AML, role model, multisignature). Any single key leak compromises all funds. These risks are built into the architecture, not poor UX.

We eliminate them at the protocol level: MPC wallets (key never fully assembled), smart contract wallets (authorization logic in code), hardware HSM for institutional storage. Details below.

What is the real difference between custodial and non-custodial?

Custodial — the provider stores the private key. User authenticates via email/password/OAuth. Recovery is trivial, KYC/AML built-in. For centralized financial applications, often the only regulatory acceptable option. Risk: single point of failure (e.g., Bitfinex hack — $72M, FTX — $600M+ client funds).

Non-custodial — keys are with the user. Provider has no access to funds. Storage responsibility falls on the user. For 99% of people, this model is unworkable without additional protection — hence MPC.

MPC wallets: the key that doesn't exist

Multi-Party Computation (MPC) is a cryptographic protocol that allows multiple parties to jointly sign a transaction without revealing their partial secrets. The private key never exists in its assembled form.

Standard scheme: 2-of-3 MPC between user (share on device), provider server, and backup cloud storage. Transaction is signed by any two of three parties. Lost phone — recovery via server + cloud. Server compromised — attacker holds only one share, signing impossible.

TSS (Threshold Signature Scheme) is a concrete implementation of MPC for ECDSA/EdDSA. Algorithms: GG18, GG20, CGGMP21 (the latter is faster and has better security proofs). Libraries: tss-lib (Go, from Binance), multi-party-sig (Go, from Coinbase), ZenGo-X/multi-party-ecdsa (Rust).

MPC requires no on-chain changes — to the blockchain, the signature looks like a normal single-key signature. This saves gas and keeps the key management scheme confidential (not published in chain) — unlike multisig.

Account Abstraction (EIP-4337): smart contract as wallet

EIP-4337 completely changes the model: instead of EOA (Externally Owned Account), a smart contract Account is used. Authorization logic is in contract code, not in protocol cryptography. This opens up arbitrary signing logic, social recovery, session keys, sponsored transactions, and batch operations.

How the EIP-4337 stack works:

User → UserOperation → Bundler → EntryPoint contract → Account contract
                                          ↑
                                    Paymaster (optional, pays gas)

UserOperation — a new type of object (not an L1 transaction). Bundler collects UserOps from an alternative mempool, packs them into one transaction, and sends to EntryPoint. EntryPoint calls validateUserOp on the Account contract — Account decides if the signature is valid.

Practical capabilities:

Social recovery. The contract stores a list of guardians (other addresses or a service). Lost key — guardians vote for replacement. Argent has used this scheme since 2020.

Session keys. A temporary key with limited rights: interaction only with a specific contract, until a certain date, up to a certain amount. For GameFi and dApps — user does not sign every micro-transaction.

Paymaster. A third-party contract pays gas for the user. Onboarding pattern: user does not hold ETH, gas is sponsored by dApp or taken from ERC-20 tokens.

Implementations: Safe{Core} Protocol, Biconomy SDK (Stackup), ZeroDev (Kernel), Alchemy (Rundler bundler). EntryPoint v0.6/v0.7 is deployed and active on Ethereum mainnet, Polygon, Arbitrum, Optimism. We guarantee compatibility with the latest contract versions.

What is a Hardware Security Module for corporate wallets?

For treasuries and institutional storage: HSM (Hardware Security Module). The key is generated and never leaves the secure chip. Signing happens inside the HSM. Hardware attestation is supported. Solutions used: AWS CloudHSM, Azure Dedicated HSM, Thales Luna, YubiHSM 2 (for small volumes). Integration via PKCS#11 or cloud-specific API.

A combination of HSM + MPC is optimal for institutional use: key shares are stored in HSMs on different servers/jurisdictions, signing via TSS. This ensures compliance with regulatory requirements (e.g., for crypto custodians).

Integration with dApps: WalletConnect and standards

Any wallet must be able to interact with dApps. Standard: WalletConnect v2 (Sign API): QR code or deep link, peer-to-peer encrypted channel via relay server. For browser extensions: EIP-1193 (Ethereum Provider API).

On the frontend, we use wagmi + viem — one interface for MetaMask, WalletConnect, Coinbase Wallet, injected providers. For Account Abstraction: EIP-5792 (wallet capabilities) and EIP-7677 (paymaster service).

Development process

1. Threat model — who is the user (B2C, B2B, institutional), what operations, what is the acceptable risk model. Architecture depends on this.
2. Selection and design of key storage scheme — MPC, HSM, multisig, or a combination.
3. Development of Account contract (if EIP-4337) or integration of MPC library.
4. Backend — MPC coordination, session management, paymaster service (if needed).
5. Mobile/browser application — UI with WalletConnect integration, biometrics, QR.
6. Integration with dApps — EIP-1193, WalletConnect v2.
7. Audit of contracts and cryptographic implementations — mandatory step. MPC libraries have known vulnerabilities (GG18 susceptible to attack with malicious participant without abort protocol). We use libraries with up-to-date security reviews (CGGMP21). Experience passing audits with Certik, Hacken, Trail of Bits — we have certificates.

What is included in the work (deliverables)

• Source code of smart contracts (Solidity/Rust) with documentation
• Backend MPC coordination service (Go or Rust) with API
• Mobile application (iOS/Android) or browser extension
• Integration with WalletConnect, Ledger/Trezor (if required)
• Preparation for security audit (vulnerability report)
• Administrator and user documentation
• Access to repository, CI/CD, monitoring (Tenderly, Etherscan API)
• Training of your team (2-3 sessions)
• Post-launch support — 1 month

Timeline and cost

Cost is calculated individually for your project. We will estimate within one day — contact us by email or Telegram. We provide a guarantee on code and timeline.

Typical mistakes in crypto wallet development (and how to avoid them)

• Using outdated MPC libraries — GG18 without abort protocol. Choose CGGMP21 or tss-lib with up-to-date audit reports.
• Tight coupling to a single blockchain — not abstracting for L2/sidechains. Use viem/wagmi for cross-chain.
• Ignoring MEV attacks — when using multisig without timelocks. Add tx simulation (Tenderly) and sandwiching protection.
• Lack of fallback recovery mechanism — for Account Abstraction, not setting up social recovery. Include from the first release.

We eliminate these pitfalls at the design stage — for each project, we create a threat model and security checklist.

Need a reliable wallet with no compromises? Get a consultation from our architect — we will analyze your task and propose an architecture with a precise estimate. Leave a request — we will respond within a day.