NFT Minting Web Interface: Smart Contracts, Merkle Tree

NFT Minting Web Interface: From Contract to Transaction

Note: when a user clicks the Mint button, the frontend connects with the contract via a wallet. Errors like InsufficientFunds or InvalidMerkleProof scare users, and gas wars at peak demand require fast feedback. Without proper handling, a transaction can fail, costing the user $0.5 in wasted gas. We build interfaces that are predictable: wallet connection, condition checks (whitelist, limits, sale status), transaction submission with error decoding, and a final screen with the token. Clients often face incorrect whitelist status checks or wrong gas pricing. Our solution automatically selects optimal gas price via viem and verifies all conditions before submission. Our team has multi-year experience in blockchain development — we have implemented dozens of NFT projects with smart contract integration on Ethereum and EVM-compatible chains. We deliver clean TypeScript code using the latest wagmi and viem libraries.

Smart Contract Preparation

The first step is to study the ABI. A typical contract uses the ERC-721A standard for efficient batch minting. Essential functions: mint, whitelistMint, totalSupply, maxSupply, mintPrice, maxPerWallet, saleState, and numberMinted. Example ABI with viem — read contract state via multicall to fetch all data simultaneously:

// Typical mint contract functions
function mint(uint256 quantity) external payable;
function whitelistMint(uint256 quantity, bytes32[] calldata proof) external payable;
function totalSupply() external view returns (uint256);
function maxSupply() external view returns (uint256);
function mintPrice() external view returns (uint256);
function maxPerWallet() external view returns (uint256);
function saleState() external view returns (uint8); // 0=paused, 1=whitelist, 2=public
function numberMinted(address owner) external view returns (uint256);

For reading state, we use multicall — it fetches totalSupply, maxSupply, mintPrice, maxPerWallet, saleState, and numberMinted for the wallet in a single RPC request. This reduces provider load and speeds up the UI.

Why Merkle Tree Is the Standard for Whitelist?

Storing all whitelist addresses in the contract costs gas at deployment. Merkle tree solves this: only the root is stored in the contract, and the proof is generated on the frontend from the user's address. It is 10x cheaper in gas. Implementation in TypeScript with the merkletreejs library:

// lib/merkle.ts
import { MerkleTree } from 'merkletreejs';
import { keccak256, encodePacked } from 'viem';

// allowlist.json — array of addresses from CMS or API
import allowlist from '@/data/allowlist.json';

function hashLeaf(address: string): `0x${string}` {
  return keccak256(encodePacked(['address'], [address as `0x${string}`]));
}

const leaves = allowlist.map(hashLeaf);
const tree = new MerkleTree(leaves, keccak256, { sortPairs: true });

export function getMerkleProof(address: string): `0x${string}`[] {
  const leaf = hashLeaf(address);
  return tree.getHexProof(leaf) as `0x${string}`[];
}

export function isWhitelisted(address: string): boolean {
  const leaf = hashLeaf(address);
  return tree.verify(tree.getHexProof(leaf), leaf, tree.getRoot());
}

Deployment savings amount to 0.09 ETH — a strong argument for Merkle Tree. At an average gas of 20 Gwei, that's about $500 saved per deployment. Additionally, each whitelist check becomes cheaper, which is especially noticeable with many users.

What Are the Steps for Interface Integration?

1. Analyze the contract ABI: extract all functions and events needed for minting.
2. Design the React component structure: MintWidget, StatusBar, ErrorDisplay, TransactionProgress.
3. Implement hooks for reading state using useReadContract and useReadContracts from wagmi.
4. Add transaction submission logic via useWriteContract and track status with useWaitForTransactionReceipt.
5. Integrate Merkle Tree: generate the proof on the frontend and pass it to the contract.
6. Test on testnet, simulate all errors, deploy to production.

These steps cover the full development cycle. At each stage, we conduct code reviews and verify compliance with best practices.

How to Handle Minting Errors?

Minting fails for many reasons: insufficient ETH, wallet limit exceeded, sale not active, invalid proof. Errors from viem contain the ABI-decoded contract message:

import { ContractFunctionRevertedError, UserRejectedRequestError } from 'viem';

function parseMintError(error: Error): string {
  if (error instanceof UserRejectedRequestError) {
    return 'Transaction rejected in wallet';
  }
  if (error instanceof ContractFunctionRevertedError) {
    const reason = error.data?.errorName ?? error.message;
    const messages: Record<string, string> = {
      'ExceedsMaxPerWallet': 'Token limit per wallet exceeded',
      'SaleNotActive': 'Sale has not started yet',
      'InvalidMerkleProof': 'Your address is not whitelisted',
      'InsufficientFunds': 'Insufficient ETH',
      'MaxSupplyReached': 'All tokens have been minted',
    };
    return messages[reason] ?? `Contract error: ${reason}`;
  }
  return 'Unknown error';
}

Testing and Security

Before launch, we simulate all contract states using Hardhat fork. We test edge cases: when maxSupply is reached, when the wallet has no ETH, when the proof is invalid. We follow checks-effects-interactions principles to prevent reentrancy attacks. Additionally, we set up monitoring via Etherscan API to track successful and failed transactions. This ensures users never see an incomprehensible error, and gas is not wasted.

Work Process and What's Included

The deliverables include full TypeScript code, integration documentation, deployment instructions, and a one-month code warranty. We also provide team training on the code and support for one week after launch.

Timeline: basic version with public mint and progress bar — 2-3 days. Full implementation with whitelist, Merkle Tree, and deployment — 4-6 days.

Order minting interface development — contact us for a project assessment. Get a free consultation and an accurate cost estimate.

Frontend Development with React: From Audit to Production

Bundle grew to 3.1 MB gzip — that's a real figure from a project that came to us for an audit. The cause: moment.js (72 KB) pulled locales for all 160 languages, lodash was imported in full instead of tree-shaken, and three component libraries were connected simultaneously. TTFB was excellent, but TTI on mobile was 14 seconds. Users left, conversion dropped by 40%. We rewrote the frontend: removed duplicate libraries, implemented dynamic imports, and SSR. Result: bundle reduced to 850 KB gzip, TTI to 2.1 seconds, LCP to 1.8 s.

Frontend is not about "drawing prettily". It's about performance, typing, rendering strategy, bundle management, and maintainability for years.

Why is Next.js the Standard Choice for SEO?

React is our primary UI framework for complex interfaces. Next.js is the standard choice for projects with SEO requirements or SSR. App Router brought React Server Components, streaming, and fetch with built-in caching. Real benefits: a catalog page with thousands of products renders on the server without sending filtering logic to the client, JS bundle is 30% smaller.

But App Router is a different way of thinking. "use client" must be placed consciously. A real mistake: a developer marks the entire layout as "use client" because of a single navigation state — and loses all RSC advantages. Rule: keep Server Components as high as possible in the tree, "use client" only for interactive leaf components. ISR for a catalog with 50,000 pages using ISR and CDN delivers TTFB < 50 ms for any page.

How Does TypeScript Prevent Bugs in Production?

TypeScript is mandatory on any project planned to be maintained longer than 3 months or with more than one developer. The argument "we write fast without types" works only for the first 2 weeks. After that, bugs related to undefined values appear every week.

Specific benefit: refactoring an API response — change a type in one place, TypeScript shows all places needing adaptation. Without types, a production bug appears in a week. strict: true in tsconfig.json is mandatory. noImplicitAny, strictNullChecks, strictFunctionTypes. The pain of Type 'undefined' is not assignable in development is less than Cannot read properties of undefined in production. tRPC provides end-to-end typing from backend to frontend without separate schema — changing a procedure type immediately shows places on the frontend that need fixing.

Vue 3 + Nuxt 3 — An Alternative SSR Stack

Vue 3 with Composition API offers a different development style, closer to React Hooks. <script setup> and composables make code more reusable. Nuxt 3 is a framework for Vue with SSR/SSG, similar to Next.js. useAsyncData and useFetch are built-in composables with request deduplication and hydration. Auto-imports are convenient but can confuse during debugging. Nuxt Content is a module for Markdown/MDX files, ideal for documentation.

Hydration mismatch is a specific pain of SSR in Vue and React. Solution: <ClientOnly> component for browser-only content, suppressHydrationWarning for dynamic timestamps.

Performance: Metrics and Tools

Bundle analysis is the starting point. @next/bundle-analyzer or rollup-plugin-visualizer — run before every major deployment. Goal: no page should require > 200 KB JS gzip for first paint.

Dynamic imports for heavy components:

const RichEditor = dynamic(() => import('@/components/RichEditor'), {
  ssr: false,
  loading: () => <EditorSkeleton />,
});

Editor (Tiptap, Quill, CodeMirror) are typical candidates for dynamic import. Without this, they end up in the main bundle. React DevTools Profiler for finding unnecessary re-renders. React.memo, useMemo, useCallback are targeted tools. Premature memoization of everything adds overhead without benefit. Profile first, optimize later.

Virtualization of long lists: @tanstack/virtual or react-window render only visible items. Table with 50,000 rows: with virtualization — 60fps, without — browser freezes on scroll.

State Management: Without Overengineering

For most applications, it's enough to have:

• React Query / TanStack Query — for server state (API data, caching, invalidation)
• Zustand — for global client state (lightweight, no Redux boilerplate)
• React Hook Form — for forms

Redux Toolkit is justified for very complex global state with many interactions. For most tasks, it's overkill. Recoil, Jotai — atomic approaches for independent pieces of state.

How to Choose the Right CSS and Design System?

Tailwind CSS latest version is our standard choice for new projects. Utility-first, excellent integration with component libraries (Radix UI, Headless UI), PostCSS pipeline. CSS Modules are an alternative when more explicit style isolation is needed. Radix UI + Tailwind (Shadcn/ui pattern) offers headless components with full control over styles. No dependency lock-in: components are copied into the project and fully customizable. Storybook is used for documenting the component library.

React DevTools Profiler — the official tool from the React team.

Testing

E2E tests via Playwright — for checkout, authentication, critical forms. Not for everything: maintaining a large e2e suite is expensive, so we select 3-5 key scenarios.

What's Included in the Scope (Deliverables)

Every frontend project we deliver includes:

• Source code in Git with full commit history and branching strategy
• Architecture document — component tree, data flow, routing decisions
• Component documentation – Storybook with stories for all reusable components
• CI/CD pipeline – automated builds, linting, tests, deployment config (Vercel / Netlify / custom)
• Access to staging environment during development and after launch
• Team training – 2‑3 live walkthrough sessions with your developers
• 3‑month warranty on any bugs found in production
• Performance report – LCP, TTI, TTFB, bundle size before/after

We also provide a pre‑deployment checklist covering browser testing, security headers, cookie compliance, and accessibility audit.

Estimates and Scope

Cost is calculated after decomposition into components, screens, and API integration. We use N+1 estimation: add 20% for risks.

What Does a Typical Performance Audit Reveal?

A recent e‑commerce project had LCP of 4.2 seconds and a monthly cloud bill of $3,000. After moving to edge‑caching (ISR + CDN) and eliminating render‑blocking scripts, LCP dropped to 1.1 seconds, and the bill fell to $1,800. The client recovered an estimated $12,000 per year in lost revenue from improved conversion. That's the kind of before‑after we regularly deliver.

Comparing tools: Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. A well‑structured bundle with code‑splitting cuts first‑paint JS by more than half.

We have 5 years of frontend development experience, over 50 completed projects, a team of 10 engineers proficient in React, Vue, Angular. We work with technologies described in React documentation and TypeScript. Additional information can be found in Wikipedia: React and Wikipedia: TypeScript.

What Stack to Choose for Frontend Development with React?

We compare tools by real metrics. Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. Savings on maintaining such a project can be significant due to reduced debugging time. If you need a lightweight SPA with minimal cost, React + Vite is enough. For a content site with SEO, Next.js with ISR gives TTFB below 50 ms even with 50,000 pages.

Get a consultation for your project: we'll evaluate your current code and propose an optimization plan. Order an audit — we'll find bottlenecks and show how to reduce budget without losing quality. Contact us to start the discussion.