Why I Decided to Lead Protocol Camp and What I Learned Running It

Protocol Camp reflections: how crypto builders find product-market fit and ship MVPs fast

💡 Before we start, if you missed our last post and want to learn more about Protocol Camp, check this out:

Protocol Camp - The Web3 Bootcamp for Everyone

---

Written by Jun Lee, Lead Mentor at Protocol Camp

Protocol Camp Cohort 8 just wrapped. I wanted to write down a few reflections while it’s still clear in my mind. ✍️

If you’re thinking about joining the next cohort, I hope this helps you understand what this is actually like.

Why I started this

I’ve been in crypto for almost 10 years. And the longer I stay, the more I’m convinced of one thing.

We need more truly great builders.

A lot of money and talent have entered this space. Still, mass adoption hasn’t shown up in a real way. The gap between blockchain’s potential and things people genuinely use is still wide.

I don’t think the bridge is another narrative. I think it’s products!

Good products are what unlock the full potential of this tech. I’m still waiting for that day to feel obvious, and I want to help pull it closer.

I also remember my own early days in crypto. Everything felt unfamiliar: the concepts, the market logic, even the language people used. I struggled more than I expected. And I kept thinking, if there were a place that helped builders understand the ecosystem, build something real, and learn from the market quickly, that would’ve saved me years.

So I asked myself: How can I contribute in a way that matters, especially to builders?

Then I found the initiative that became Protocol Camp Asia edition. And honestly, I’ve been one of the most motivated people in the room ever since, because this work feels worth doing.

What I actually did as a mentor/operator

I’m a developer, and I’ve spent a lot of time in early-stage startups. I’ve lived that messy “0 → 1” phase. You sketch the first version, ship too early, fix it, launch again, and learn from the market the hard way.

So naturally, I wanted to help teams with things like:

• shaping a product direction from a fuzzy starting point

• building fast without breaking everything

• launching early and learning fast

• handling feedback without losing the plot

But I tried not to be the person who tells teams what to do.

What I cared about more was helping teams get to their goal, under their direction, with less waste and more momentum.

We started with two weeks of education sessions. We invited experts from the blockchain industry, and I also ran sessions myself. That wasn’t for “more content.” It was to clear the ground so that once the camp really started, teams could focus on building.

During the build phase, I met each team weekly for about 30 minutes. It wasn’t a formal review. More like: Where are you stuck? What do you need this week? Who do you need to talk to?

Sometimes it was VC feedback.
Sometimes it was intros for customer interviews.
Sometimes it was an architecture problem that needed a clean way out.

My job was basically to listen carefully, help remove blockers, and keep the pace honest.

The moments I won’t forget ⚡

The best moments were watching teams notice the problem themselves and move.

In this recent cohort, almost half the teams looked at the mid-demo feedback and decided, “This doesn’t match the market.” And they pivoted.

That’s a painful call.

What impressed me wasn’t the pivot itself. It was what happened after.

With about six weeks left, teams were proposing multiple hypotheses, testing them, pulling real numbers, and then rebuilding around what they learned. Not hand-wavy “validation.” Actual experiments. Actual signals.

And by the final demo, most of them had something that felt production-level. Working. Shippable. Not perfect, but real.

Seeing teams recover under pressure, with fast decisions and fast execution, that’s one of the strongest memories I’m taking from this cohort. 🔥

The question I wrestled with the most

Here’s the hardest part of crypto building: The market doesn’t care that your tech is new.

A lot of crypto products get built. Most don’t last. Often the engineering is solid. But the product doesn’t land because it’s not solving a need people truly feel.

So I kept coming back to the same question, over and over.

What problem should we solve with this technology so real users actually show up?

That’s not a philosophical question. It’s an operating question. And it’s also the builder’s job in this industry, I think.

So with teams, the conversation often turned into something very practical. How do we test market need quickly, cheaply, and honestly, within a short timeframe?

Not “build for months and hope.” Test, learn, adjust. Repeat.

If you’re considering the next cohort 🚪

Protocol Camp isn’t a place where you build an idea and then move on.

It’s a place where you try to build something that can survive contact with the market and generate real reactions. So if what you want is not just making something, but actually solving a problem people have, this program is for you.

One more thing: the next cohort will lean much more into AI. Because of AI, the cost of building has dropped a lot, and we’re entering a world where even non-developers can build MVPs that used to require a full engineering team.

So if you can’t code yet, it’s okay.

If you have a problem you care about, we’ll show you how to use AI to build, test, and iterate inside the camp. Practically, not as a buzzword.

If that sounds like you, I’d love to see you in the next cohort. 🙌

Stay tuned for details on our upcoming application period at www.protocolcamp.com