← Primitive Archive

A-03 / builder community OS / 2022–2026

Hunt Town

Builder-community work around Hunt Town: ideathons, Discord showcases, fireside chats, Huntzy community ops, early project support, rewards setup, Base/Farcaster education, and Korea/global Web3 activation loops.

Hunt Townbuilder educationKoreaBaseFarcastercommunity
Hunt Town proof
ideathons / fireside chats / Huntzy ops / project support
rolecommunity product + launch loops
objectbuilder community OS
receiptideathons / fireside chats / Huntzy ops / project support
externalopen proof ↗

Ownership

What I owned, and where the line was.

My roleCommunity product + launch loops
Team context

Small startup; I ran community-product operations end to end.

What I directly owned
  • Events and ideathons
  • Discord operations
  • Early-project support and reward setup
  • Workshops and builder education
  • Content and fireside-chat hosting on YouTube
  • Huntzy community operation
What I influenced
  • Base / Farcaster ecosystem direction
  • Builder adoption loops and product feedback
Proof

Public event posts, workshop receipts, and fireside-chat videos

01

Primitive

Hunt Town was the community/product layer around shipping: helping builders understand the primitives, launch small projects, get feedback, and move from Discord/Farcaster attention into actual product usage.

02

Artifact

A long-running set of builder activations: Hunt Town ideathons, fireside chats, Huntzy community operations, Warpcast Tools showcases, early project support, Mint Club rewards setup, Base/MiniKit workshops, university sessions, and community launch loops.

Proof / Traction

Receipts before adjectives.

01Hunt Town Ideathon builder/community event ↗
02Hunt Town pushing Base + Farcaster ↗
03Mint Club staking pools / backing 10 early projects with rewards + setup support ↗
04Dreamplus Gangnam / EwhaChain session building Zora-style social dApps with Mint Club SDK ↗
05Blockchain at Yonsei / Base MiniKit + Mint Club SDK workshop ↗
06

Fireside chats hosted on YouTubesource pending

07

Huntzy community operationsource pending

Field notes

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

My lane

Community product, builder education, launch support, and product translation: helping projects and builders understand what to build with Mint Club/Hunt Town primitives — plus hosting fireside chats and running the Huntzy community.

What changed

I learned that product adoption often happens outside the product UI: workshops, demos, Discord help, fireside chats, and launch narratives can decide whether a primitive becomes used or ignored.

Proof shape

The evidence is a timeline: ideathons, fireside chats, Warpcast/Farcaster showcases, early project support, Base/MiniKit workshops, and public posts around pushing Hunt Town into new ecosystems.

Receipt timeline

Company years, visible in public receipts.

2024-09
Warpcast Tools showcase in Hunt Town Discord

community demo / Farcaster utility loop

2026-01
Hunt Town live event promoted through Beeper

Beeper sent event to 768 users who set Signal Token to $HUNT

What went right

  • The work connected product to people: workshops, showcases, launch help, rewards, and feedback loops made abstract Web3 primitives usable for builders.
  • Hunt Town is strong career evidence because it shows repeated community-product execution, not just isolated coding tasks.
  • Korea builder activations made the product language sharper: if people could not build with it live, the interface or docs were not clear enough.

What went wrong

  • Community/product work is easy to undersell because the artifact is distributed across posts, sessions, Discord, demos, and support work.
  • A university/workshop photo proves activity, but the page needs more screenshots/receipts to show product depth.
  • Fireside-chat videos and Huntzy proof still need to be collected and linked.

Next bet

Build Hunt Town as the community-product case: ideathon → project setup → reward mechanics → fireside chat → workshop → Base/Farcaster distribution. It should prove that I ran adoption loops, not just frontend screens.