(02)
IQ.Wiki
The world's largest blockchain encyclopedia — anchored on-chain.
- Year
- 2024 — Now
- Role
- Frontend Engineer
- Stack
- Next.js 15 · GraphQL · next-intl · wagmi
- Live
- iq.wiki
(01) Overview
IQ.wiki is the world's largest blockchain encyclopedia — thousands of articles in three languages, read across the crypto world and anchored on-chain. I'm a core frontend engineer on the 72,000-line Next.js application that serves it.
Every wiki lives as JSON on IPFS with its hash committed to Polygon. The site renders that catalog with webhook-driven caching, streams AI search summaries token by token, and doubles as a market reference with live-ranked token tables.
(02) The Challenge
Serve an encyclopedia-sized catalog with encyclopedia-grade SEO: per-request rendering that must feel static, three locales that can never fork, wallet-based publishing that ordinary people can use — and search that answers before you finish typing.
(03) Architecture — and why
Tag-based caching over pre-building
Wiki pages render on demand and cache behind content tags. When the indexer publishes a change, a webhook revalidates exactly that wiki, its sub-pages and the homepage — across all three locales. ISR driven by events, not timers.
Parallelize, then degrade gracefully
A wiki page fans out to token stats, NFT metadata, ratings and related wikis in parallel, each behind its own Suspense boundary — a slow subsystem costs its own skeleton, never the page.
Typed GraphQL, end to end
Queries compile against the generated schema at build time, and every request carries an abort timeout documented against Vercel's function ceiling — hardening you can trace back to real incidents.
One auth hook, two worlds
RainbowKit for crypto natives, Web3Auth social login for everyone else — unified behind a single useAuth() so Web2 and Web3 users edit the same encyclopedia.
A catch-all route instead of a redirect table
Unknown slugs resolve at request time — wiki title, wallet address, or 404 — replacing a hand-maintained redirect map that had become unmaintainable.
(04) Engineering Highlights
Search that answers first
Ghost-text autocomplete completes the query with a cached LLM call while a Sophia panel streams a live markdown summary of results over SSE — with generation fencing so a stale stream never clobbers a newer one.
Gasless on-chain publishing
Publishing is a five-step state machine: pin to IPFS, sign EIP-712 with your wallet, relay to Polygon, await the receipt, poll ingestion. The contributor's signature anchors provenance — without them ever holding gas.
An agent takes the suggestions
Wiki suggestions go through a multi-step tool-calling agent that checks the live catalog for duplicates, collects contact info and scores crypto-relevance — every conversation traced in Langfuse.
SEO as a system
Typed JSON-LD graphs, per-locale canonicals, production-gated indexing and a proxied backend sitemap — encyclopedia SEO handled structurally, not page by page.
A locale renamed without losing a link
Korean moved from /ko to /kr through prefix mapping plus permanent redirects — a URL rebrand that kept every backlink and every ranking.
Market data where readers expect it
Rank tables for cryptocurrencies, stablecoins, AI tokens and memecoins, fed by live market stats and sparklines — the encyclopedia doubles as a reference terminal.
(05) The Flow
- 01
A reader lands from search — JSON-LD and canonicals did their job
- 02
The wiki renders from tagged cache; widgets stream in under Suspense
- 03
Search autocompletes ahead of the cursor while Sophia summarizes live
- 04
Contributors edit and sign — IPFS, Polygon and the indexer do the rest
(06) Impact
3
languages served from one routing layer
72k
lines of TypeScript
Top 3
contributor on a 5,000-commit codebase