Sunday/Work/№ 01 · MIMBOKU

MIMBOKU.

First native liquidity aggregator and top NFT community on Story — swap tokens or earn ecosystem rewards from staking, LPs, and IP creation.

ORG
Tentou Labs
Year
2025
Role
Frontend developer
Timeline
8 weeks → mainnet
Mimboku banner
01

The brief

Context · what existed before

Story shipped a chain for IP, but the on-chain economy didn’t have a front door — no native aggregator, fragmented liquidity, and no community ritual to bring users back.

Story Protocol launched as the chain for programmable IP — a fresh EVM L1 with a thin DeFi layer and a small but loud community. Liquidity sat in a handful of pools that didn’t talk to each other, and NFT distribution was tied to one-off mint pages with no shared identity.

Tentou Labs wanted to ship the first native aggregator on Story and anchor it with an NFT community that doubled as a loyalty layer — one product surface where swap, stake, mint and rewards lived together instead of scattered across five tabs.

The job: design and ship the frontend for the aggregator, the staking flow, the NFT mint, and the connective tissue (perks, missions, leaderboard) — fast enough to land in the first wave of Story’s mainnet rollout.

02

What changed

Outcome · since mainnet launch
$2M
Total swap volume
first native aggregator on Story
2,792
NFTs minted
Mimboku · Great Mimgration
1,800+
Unique owners
≈ 64% mint-to-hold ratio
4
Products under one roof
swap · stake · mint · world
03

How it got built

Process · five moves
  1. 01

    Read the chain before drawing a screen.

    Spent the first week inside Story’s docs and Wagmi internals — mapped the IP module, the royalty primitives, and what was actually exposed via RPC. The aggregator’s UX hinged on which calls we could batch; the design followed the contract surface, not the other way around.

  2. 02

    Built the swap flow as a single state machine.

    Quote → approve → sign → confirm → settle. Modeled the whole route as an explicit state machine in useReducer, so every error path (rejected sig, insufficient gas, slippage exceeded, RPC dropout) had a named state instead of a dangling toast.

  3. 03

    Designed the NFT mint to feel like a moment, not a form.

    The Great Mimgration mint had to land like an event — countdown, queue, allowlist tiers, post-mint celebration. Built the mint flow with optimistic UI (claim renders before tx confirmation), reconciling against the contract on settle. 2,792 mints, no stuck states.

  4. 04

    Wired the loyalty layer across products.

    Perks, missions, and the leaderboard share one points ledger — earn from swap volume, NFT holds, or staking. Built a thin client SDK so each product surface (ag, app, world) reads/writes through the same hook, and a holder’s identity carries between them.

  5. 05

    Shipped to mainnet, then stayed for the next four releases.

    Mainnet went live in week 8. Then: a staking dashboard with validator picker, perk redemption, mission streaks, and a Story-native session-key flow that cuts wallet pop-ups by ~60% on repeat actions. Each release scoped to ride a specific community moment.

04

What it’s built on

Stack · web3 · no exotic picks
Frontend
Next.js· App RouterTypeScript· strictTailwindFramer Motion· transitions
Web3
Story Protocol· EVM L1Wagmi· v2ViemRainbowKit· wallet UX
Data & infra
VercelThe Graph· subgraphsRedis· session keysCloudflare· edge
Observability
SentryPlausibleTenderly· tx debugging

$2M in volume, 2,792 mints, 1,800+ holders — and zero swap-flow regressions since mainnet.

— Mimboku · Story Protocol mainnet, 2025
Shipping in web3?sunday19x3@gmail.com
Next case study →Punkga.me