← Primitive Archive

A-02 / token product surfaces / 2022–2026

Mint Club

Token-backed asset and bonding-curve product work: launch flows, child-token discovery, staking/reward surfaces, cross-chain swap UX, Base/mfer views, SDK demos, and Farcaster-native product surfaces.

Mint ClubBasebonding curvesSDKtoken UXFarcaster
Mint Club proof
SDK / swap / staking / mfer-backed token / Base era
roleproduct + front-end / SDK + ecosystem UX
objecttoken product surfaces
receiptSDK / swap / staking / mfer-backed token / Base era
externalopen proof ↗

Ownership

What I owned, and where the line was.

My roleProduct + front-end / SDK + ecosystem UX
Team context

Small startup team; I led most front-end and app-layer surfaces. Deeper infra/contract work was shared with the core team.

What I directly owned
  • Most Mint Club front-end surfaces (if you use mint.club, most of the front-end is mine)
  • Swap, staking, lockup, and airdrop tools
  • Smart-contract ↔ front-end integration
  • Backend data persistence and user dashboards
  • mfer-backed token product — strongly led, including community activation and viral traction
What I influenced
  • Bonding-curve and token-backing product direction
  • Base-era featuring and child-token discovery
  • SDK examples and workshop apps
Proof

mint.club live surfaces, public Mint Club posts, and the GitHub commit trail

01

Primitive

Mint Club’s hard problem was making token-backed markets and bonding curves feel like usable product surfaces instead of raw crypto mechanics. My work sat where primitives became interfaces: launch, swap, discover, stake, reward, and teach.

02

Artifact

Product/front-end surfaces and demos across Mint Club: token-backed asset pages, child/sibling token discovery, mfer/Base views, cross-chain swap UX, staking/reward pools, Mint Club SDK examples, Mintdrop, Brainlets, and Base/Farcaster surfaces including far.cards.

Proof / Traction

Receipts before adjectives.

01BASE ERA in Mint Club — Base token featuring and child tokens backed by favorite Base tokens ↗
02Mint Club product update: mfer vision, event filtering, token detail sibling/child lookup ↗
03Mint Club child-token / mfer ecosystem update ↗
04Mintdrop metrics: $8K worth of child coins, 3,000 unique users, nearly 80,000 Base microtransactions ↗
05Brainlets — hand-drawn $BRAINLET site on Degen L3, built on Mint Club assets, still live ↗
06mint.club-v2-sdk commits by tonymfer ↗
07hunt-mint-swap commits by tonymfer ↗

Proof, up close

What the screenshots actually prove.

What this proves: bonding-curve / token-backing mechanics rendered as an operable product page — cbBTC token-backed surface I built the front-end for.
What this proves: bonding-curve / token-backing mechanics rendered as an operable product page — cbBTC token-backed surface I built the front-end for.
What this proves: Mintdrop drove $8K in child coins, 3,000 users, and ~80K Base microtransactions — a growth loop, front-end fully mine.
What this proves: Mintdrop drove $8K in child coins, 3,000 users, and ~80K Base microtransactions — a growth loop, front-end fully mine.

Surfaces in this orbit

Related product surfaces I built.

far.cards preview

far.cards ↗

Physical-social Farcaster cards — NFC identity objects you can hand someone at an event. A Farcaster-native IRL surface built in the Mint Club / onchain-social orbit.

FarcasterNFCsocial object
Mintdrop preview

Mintdrop ↗

Growth product built for Mint Club: a launcher for child coins on Base. Front-end fully mine; the project has since shut down, but the receipts stand: $8K child coins, 3,000 users, ~80K microtransactions.

Basegrowth loopchild tokens
Brainlets preview

Brainlets ↗

Hand-drawn meme token site for $BRAINLET on Degen L3, built on Mint Club assets during the Degen Chain wave — an interactive 'cut to start' brainlet world where the website itself carries the token narrative. Still live.

Degen L3token narrativeinteractive site

Field notes

What was hard, what changed, and what I learned.

My lane

Product and front-end/app-layer work: surfaces, flows, demos, SDK examples, and the public language around making token mechanics usable.

Repeated problem

Every feature had the same job: make an abstract onchain mechanic legible enough for projects, holders, and builders to use without needing protocol context first.

Proof shape

The strongest evidence is not one metric. It is the combination of GitHub commits, product screenshots, Mint Club posts, Base-era updates, and workshop demos across multiple years.

Receipt timeline

Company years, visible in public receipts.

2024-08
Cross-chain swap UX on Mint Club

Base/mainnet/BNB/Arbitrum/Optimism/Degen/Blast/Zora bridge/swap/buy support

What went right

  • The same product muscle repeated for years: turn bonding curves, token backing, swaps, staking, and reward mechanics into screens people could actually operate.
  • Mint Club forced product clarity because the primitive is abstract; the interface had to show action, value, risk, and proof without protocol lectures.
  • The Base/Farcaster push created a bridge from token infrastructure into social distribution and miniapp education.

What went wrong

  • A lot of the work is distributed across many surfaces and commits, so it needs an evidence trail rather than one clean launch page.
  • Token dashboards can look like DeFi noise if the portfolio does not explain the user action and product intent.
  • Some public posts prove launches and features, but exact ownership boundaries still need careful wording.

Next bet

Turn Mint Club into a real case study with three artifact strips: product surface, SDK/workshop app, and growth metrics. The page should show years of accumulated product work, not one screenshot.