Alchemy API integration for dApps: speed and reliability

When you launch a dApp on Ethereum mainnet, the first issue you face is unstable RPC: requests drop, nodes skip blocks, and syncing a new node takes days. Running your own infrastructure requires significant investment and DevOps monitoring. We solved this problem for 30+ projects by integrating Alchemy API. This is more than just an RPC provider: Enhanced APIs save development hours — alchemy_getAssetTransfers replaces manual parsing of Transfer events. Integration cuts dApp time-to-market by 60% (from 6 months to 2.4 months) and reduces infrastructure costs by 70% (from $15,000 to $4,500 monthly). Contact us for an audit of your current infrastructure.

How Alchemy speeds up dApp development?

Running your own node requires servers, syncing from genesis, uptime monitoring, and DDoS protection. Alchemy handles this: 99.9% uptime SLA and automatic failover. We compared: deployment time drops from 1–3 days to 1 hour, and monthly infrastructure costs fall several times. Our blockchain development services have integrated Alchemy for 30+ DeFi and NFT projects, reducing operational overhead by 80%.

Which Enhanced APIs are actually needed?

Alchemy provides three key Enhanced APIs that replace indexing and event parsing. Let's break down each with code examples.

NFT API

Without Alchemy, getting all NFTs for an address means parsing Transfer events or depending on marketplace APIs. With Alchemy:

// All NFTs for wallet
const nfts = await alchemy.nft.getNftsForOwner("0xAddress", {
  contractAddresses: ["0xOptionalFilter"],
  omitMetadata: false
})

// Owner of a specific token
const owners = await alchemy.nft.getOwnersForNft(contractAddress, tokenId)

// All tokens in a collection with metadata
const collection = await alchemy.nft.getNftsForContract(contractAddress, {
  pageSize: 100
})

Token API and transaction history

// All ERC-20 balances for address
const balances = await alchemy.core.getTokenBalances("0xAddress")

// Token metadata
const metadata = await alchemy.core.getTokenMetadata("0xTokenAddress")
// { name, symbol, decimals, logo }

// Full transaction history for address
const history = await alchemy.core.getAssetTransfers({
  fromAddress: "0xAddress",
  category: ["external", "erc20", "erc721", "erc1155"],
  withMetadata: true,
  maxCount: 100
})

The result includes decoded transfers with amounts, token symbols, and addresses — ready for UI. Enhanced APIs cut indexing time by 10x compared to custom event parsing.

Enhanced API comparison

Setting up Webhooks for on-chain monitoring

Polling is a bad approach. Alchemy Notify sends a POST to your endpoint on events. We implement creation and verification:

1. Create a webhook via SDK or Alchemy Dashboard.
2. Implement an endpoint that accepts POST requests.
3. Verify the signature using isValidWebhookSignature.
4. Process the event and return 200 OK.

import { isValidWebhookSignature } from "alchemy-sdk"

// Create webhook
const webhook = await alchemy.notify.createWebhook(
  "https://your-api.com/webhooks/alchemy",
  WebhookType.ADDRESS_ACTIVITY,
  { addresses: ["0xWatchedAddress"], network: Network.ETH_MAINNET }
)

// Verify signature (Express.js)
app.post("/webhooks/alchemy", express.raw({type:"application/json"}), (req, res) => {
  const isValid = isValidWebhookSignature({
    body: req.body.toString(),
    signature: req.headers["x-alchemy-signature"] as string,
    signingKey: process.env.ALCHEMY_WEBHOOK_SIGNING_KEY!
  })
  if (!isValid) return res.status(401).send("Unauthorized")
  const event = JSON.parse(req.body.toString())
  handleAlchemyEvent(event)
  res.sendStatus(200)
})

Alchemy Notify Documentation

Why WebSocket is better than polling for real-time data?

In addition to webhooks, Alchemy provides WebSocket subscriptions: alchemy_subscribe, newHead, newPendingTransactions. We set up subscriptions for mempool monitoring or new blocks. This is critical for MEV strategies and high-frequency trading. Example subscription:

const ws = new WebSocket("wss://eth-mainnet.g.alchemy.com/v2/API_KEY")
ws.on("open", () => {
  ws.send(JSON.stringify({ jsonrpc: "2.0", id: 1, method: "eth_subscribe", params: ["newHeads"] }))
})
ws.on("message", (data) => {
  console.log(JSON.parse(data.toString()))
})

Alchemy API integration deliverables

We provide a full integration cycle with clear deliverables at each stage:

• Audit of current infrastructure and selection of the optimal Alchemy plan.
• SDK setup for mainnet and testnet with multi-chain support.
• Integration of NFT API, Token API, Asset Transfers with ready code examples.
• Webhook notification creation with signature verification and event handling.
• WebSocket subscription setup for real-time data.
• Rate limit optimization and request batching.
• Integration documentation and client team training.
• Post-launch stability and performance monitoring.

Thanks to this, your dApp gets reliable access to blockchain data without the need to run your own infrastructure. The total integration cost starts at $5,000, with typical savings of $10,000+ monthly on infrastructure. Order the integration — we will conduct an audit and propose the optimal configuration for your project.

Typical integration mistakes

• Incorrect signing key for webhooks — leads to 401 errors. Verify the signing key matches the Alchemy Dashboard.
• Rate limit exceeded without batching — increases latency. Use alchemy.core.sendBatch() to batch requests.
• Wrong Network parameter for L2 — basis for reorgs. Ensure correct Network.ARB_MAINNET for Arbitrum.
• Ignoring a fallback provider — in rare cases Alchemy may be unavailable, so a backup RPC like Infura is needed.
• Missing error handling for 429 Too Many Requests — implement retry logic with exponential backoff.

Get a consultation from an engineer who has already delivered 30+ solutions for DeFi and NFT. We guarantee stability and performance at any scale.

Introduction

User clicks 'Connect Wallet' — MetaMask opens, confirms — and nothing happens. Or worse: the transaction is sent, but the UI hangs on 'pending' forever because the event listener dropped during network switch. Typical situation: contract deployed on Arbitrum, but wallet connected to Ethereum Mainnet — the interface silently shows zero balances even though the RPC responds. Web3 frontend is not React + API calls. It's working with wallets, nodes, blockchain reorganizations, and a state that doesn't belong to your server.

What is Included in Full-Spectrum Web3 Frontend Development

We design and implement dApp interfaces at all stages: from wallet connection to complex transaction logic with multichain routing. The work includes:

• UI architecture considering EIP-1193 (ethereum provider) and EIP-6963 (multi‑injected wallet)
• Integration of RainbowKit/ConnectKit for WalletConnect v2
• Data reading via Multicall3 with cache configuration (React Query)
• Transaction handling with full state chain, errors, and reverts
• Authentication via SIWE (EIP-4361) and EIP-712 signatures
• Deployment on Vercel/Netlify with dynamic imports of wallet parts for SSR
• Documentation for support (state schema, contract list, RPC fallback description)
• 30 days of free support after delivery

Source: internal regulations based on wagmi and viem best practices

Modern Stack: wagmi v2 + viem

Wagmi v2 — React hooks for interacting with EVM chains. viem — a low-level TypeScript client that replaced ethers.js in most new projects. The wagmi + viem combination provides typed access to contracts, wallets, and transactions.

import { useReadContract, useWriteContract, useWaitForTransactionReceipt } from 'wagmi'

const { data: balance } = useReadContract({
  address: contractAddress,
  abi: erc20Abi,
  functionName: 'balanceOf',
  args: [userAddress],
})

const { writeContract, data: txHash } = useWriteContract()
const { isLoading: isConfirming } = useWaitForTransactionReceipt({ hash: txHash })

Typing through viem — ABI is passed as const assertion, and TypeScript knows argument and return types at compile time. Contract errors are caught before runtime.

Why is viem faster than ethers.js?

viem processes contract calls 3 times faster and uses 60% less memory. This is achieved through native support of ethers.js ABI encoding/decoding in Wasm and the absence of a BigNumber layer. The result is loading a page with 20 tokens in 600 ms instead of 2 seconds. The libraries are developed by the wagmi-dev team and support all recent EIPs. More about viem can be found in the documentation.

Wallet Connection and Multichain Routing

RainbowKit — a UI library built on wagmi for the wallet modal. Supports MetaMask, WalletConnect v2, Coinbase Wallet, Phantom, Safe, and dozens of others out of the box. ConnectKit is an alternative with a different design. Both solutions properly handle wallet detection, deep links for mobile, and EIP‑6963 (multi‑injected wallet discovery).

WalletConnect v2 — a protocol for communication between dApp and mobile wallets via QR code or deep link. Requires a ProjectID from cloud.walletconnect.com. Migration from v1 to v2 is mandatory.

The main UX case that breaks: user connected wallet on Ethereum Mainnet, but the contract lives on Arbitrum. You need to:

1. Detect the wrong network.
2. Offer switching via wallet_switchEthereumChain.
3. If the network is not added — wallet_addEthereumChain.
4. Wait for the switch confirmation before sending the transaction.

Wagmi handles this via useSwitchChain(), but the UX flow must be explicitly designed — automatic switching without explanation scares users.

How to handle multichain switching without losing UX?

We intercept chain.id via useAccount and update the state of all useReadContract calls on every network change. On network errors, we show a toast with a human explanation — not raw hex codes. This gives a 95% successful switch rate without support requests.

const config = createConfig({
  chains: [mainnet, arbitrum, optimism, polygon, base],
  connectors: [injected(), walletConnect({ projectId }), coinbaseWallet()],
  transports: {
    [mainnet.id]: http(alchemyUrl),
    [arbitrum.id]: http(arbitrumRpcUrl),
  },
})

Contract addresses are stored in a typed map by chainId — not hardcoded separately for each network. This reduces the time to add a new network to 20 minutes instead of 2 hours.

Transaction and Data Reading: How to Avoid Typical Errors

A transaction goes through several states: idle → pending (wallet) → submitted → confirming → confirmed. Each transition can fail with an error.

Gas estimation failures are caught before sending using estimateGas(). If the gas estimate falls with a revert reason, we show the reason to the user and prevent sending a knowingly failing transaction.

Data Reading: Multicall and Caching

One RPC request per balanceOf when loading a page with 20 tokens — 20 requests. Wagmi automatically batches useReadContract calls via the Multicall3 contract (deployed on all major networks at the same address). This reduces RPC load by 5 times and speeds up loading by 70%.

React Query under the hood of wagmi provides caching and automatic refetch. Configuring staleTime (2–5 seconds for prices, 10–30 seconds for balances) and refetchInterval is important for balancing data freshness and RPC load.

For complex queries — historical data, event aggregation — we use The Graph subgraph or Ponder. A GraphQL query to the subgraph instead of scanning thousands of blocks via RPC saves up to 90% of computing resources.

Authentication and Signatures: SIWE, ENS, and EIP‑712

EIP‑4361 (SIWE) — authentication standard via wallet signature without a transaction. The server generates a nonce → the user signs a message via personal_sign → the server verifies the signature. Replaces username/password for Web3 applications. siwe npm package on client and server.

ENS integration: normalize from viem for resolving .eth addresses and reverse lookup (address → ENS name). Show vitalik.eth instead of 0xd8dA... where possible. Avatar resolution — getEnsAvatar().

Signatures for off‑chain operations (EIP‑712 typed data) — structured data that MetaMask displays human‑readable instead of a hex blob. Used for approve, order signatures in DEX, permit (ERC‑2612).

Performance and Optimization

The bundle of wagmi + viem + RainbowKit weighs ~200–400kb gzipped. For NextJS, use dynamic imports with ssr: false for all wallet‑dependent components. SSR hydration + web3 providers — a known state mismatch problem. Pattern: render connected state only on the client.

// components/wallet-provider.tsx
'use client'
import { WagmiConfig } from 'wagmi'
import { RainbowKitProvider } from '@rainbow-me/rainbowkit'
import { config } from './config'

export default function WalletProvider({ children }) {
  return (
    <WagmiConfig config={config}>
      <RainbowKitProvider>{children}</RainbowKitProvider>
    </WagmiConfig>
  )
}

Development Timelines and Cost

Cost is calculated individually based on the volume of contracts, number of networks, and UI complexity. We offer a fixed price after code audit — no hidden extras.

Guarantees and Support

After project delivery, we provide 30 days of free support and acceptance according to a 50+ point checklist. All source code undergoes audit; we use formal contract verification (Slither + Mythril). 10+ years of experience in smart contract and Web3 interface development — from Solidity 0.4 to 0.8, from Truffle to Foundry. 50+ successful dApps in production on Ethereum, Polygon, Arbitrum, Optimism, and Base.

Contact us for a project evaluation — we will prepare a technical specification and architecture within 3 business days. Order turnkey development and get a finished product with documentation, tests, and deployment scripts.