Web3Industry: Blockchain 2022 - 2023

Cross-Chain NFT Marketplace & Asset Indexing Engine

Q: How does the custom block indexer handle blockchain reorgs?

The indexer maintains a 20-block rolling history buffer and automatically rolls back and re-indexes database state if a block reorganization is detected on-chain.

Q: How are IPFS metadata files cached for fast loading?

Original IPFS asset metadata and media are ingested, compressed, and served through a global CDN edge caching layer.

Multi-chain marketplace featuring non-custodial wallet authentication, gas-optimized smart contract interaction, and high-speed asset indexing.

A striking abstract composition with neon light on a dark backdrop, perfect for modern design. — Photo: Steve A Johnson / Pexels

<500ms

Indexing Speed

Real-time block indexing for new mints and token transfers

Ethereum & Polygon

Chains Supported

Cross-chain asset browsing and checkout integration

99.95%

Platform Uptime

Continuous marketplace availability during high-demand mints

01 · Challenge

The problem on the ground

Read the full brief

Public blockchain indexing APIs suffered from rate limits and high latency, causing stale marketplace listings and failed transaction confirmations during peak minting events.

02 · Solution

How we engineered it

Read the approach

Built a custom Node.js and MongoDB block indexing engine that listens to EVM WebSocket events, paired with a lightweight React frontend.

03 · Architecture

What's running under the hood

See the execution breakdown

Custom EVM Indexer: Node.js worker threads consuming EVM logs to maintain low-latency asset state.

MongoDB Metadata Store: High-throughput document store caching NFT attributes, ownership, and sales history.

Web3 Wallet Integration: Support for MetaMask, WalletConnect, and Coinbase Wallet.

Gas Optimization: Optimized smart contract interaction logic to minimize gas overhead for buyers.

Dynamic abstract blue wave design creating a modern and futuristic aesthetic. — Photo: Pușcaș Adryan / Pexels

04 · Results

What changed for the client

See the outcomes

Delivered sub-500ms metadata updates upon block confirmation.

Handled over 100,000 active user listings with zero indexer lag.

Reduced buyer gas fee overhead by 22% through batch contract calls.

Maintained 99.95% platform availability during major collection launches.

Technical Q&A

How does the custom block indexer handle blockchain reorgs?

The indexer maintains a 20-block rolling history buffer and automatically rolls back and re-indexes database state if a block reorganization is detected on-chain.

How are IPFS metadata files cached for fast loading?

Original IPFS asset metadata and media are ingested, compressed, and served through a global CDN edge caching layer.

Planning a similar web3 project?

Consult directly with our platform engineers to assess your workload and get a zero-downtime architecture plan.

Consult Engineers