Table of Contents
Researcher
This week, my timeline has been flooded with posts like "How to start vibe coding" and "Things I built with claude code."
Somewhat questioning for me was the absence of discussion on the changes that vibe coding might bring to CT / ecosystem. Here, I've organized a few thoughts that came to mind.
1. Yapping → Vibe Coding
Recently, community contributions have largely taken the form of yapping. Opinions vary on whether yapping holds meaningful value, but it's clear that promoting projects through written content is currently recognized as a form of contribution worthy of financial rewards.
I predict that the spread of vibe coding will significantly diminish the value of these existing contribution methods.
This is because the barrier to implementing ideas as functional PoCs will drop dramatically. This approach can introduce projects to the public in a more intuitive and engaging way, while also enabling community members to make genuinely meaningful contributions to projects. Put simply, we might see UX improvement proposals or new dApp ideas being posted on social media. As substantive contributions increase, traditional yapping will find it much harder to be recognized as valuable.
2. Vibe Coding-Friendly Projects Capturing Mindshare
If this is the case, projects where vibe coding is relatively easy will likely capture more mindshare going forward. Which projects stand to gain a comparative advantage in the vibe coding trend? In my view, the conditions are as follows:
Intuitive Fun: Areas where outcomes can be immediately experienced, such as AI agents or games, are natural applications for vibe coding.
Highly Scalable Infrastructure: The community must be able to actually deploy experimental projects created through vibe coding and drive interaction. Infrastructure offering high scalability, good UX, and low gas fees will likely gain an edge in the vibe coding ecosystem.
Developer-Friendliness: Projects that are developer-friendly (or LLM-friendly) in multiple senses will have an advantage. This includes having documentation structured in an LLM-friendly way, allowing development in general-purpose languages, or providing infrastructure that facilitates interaction with Web2.
3. Projects Worth Watching
3.1 Gaming Platforms
Verse8: This project has been appearing frequently in Korean Web3 gaming communities lately. It's a platform that allows users to create and deploy simple games directly through vibe coding. While it doesn't permit high complexity, it's gaining attention for its solid development experience. It seems to show particular strength in indie games where ideas matter most.
Abstract: As it currently hosts the largest Web3 gamer community, it provides an environment where vibe coding games can relatively easily gain attention. Since it's infrastructure built with a focus on Web2 accessibility from the start, it can also pursue broader expansion.
MegaETH: With very high scalability and low interaction costs, it offers a favorable environment for developing and deploying games through vibe coding. Through its combination with the cult platform Kumbaya, it appears positioned to expand the cult community into a gaming ecosystem.
3.2 Agent Projects
Virtuals Protocol: I believe no other project in the AI agent ecosystem can currently match it. Recently, they divided their agent launch mechanism into three tiers, enabling freer and more transparent participation. Notably, the lowest tier, Pegasus, has completely eliminated initial team allocations. This token launch model allows value to be determined by ideas and word-of-mouth, which is why I expect retail communities might actually produce vibe coding-based bangers.
3.3 Memes/IP
I believe the types of ideas any individual can generate are limited, and what can expand them is IP serving as packaging. I look forward to communities with distinctive IP and memes, such as Milady or Pudgy Penguins, producing fresh content through vibe coding.
3.4 Developer-Friendly Infrastructure
Rialo: Rialo is still in private testnet phase, so publicly available information is somewhat limited. However, it's known that interaction with Web2 environments is natively integrated. If they can elegantly support on-chain development environments, retail participants should be able to propose relatively unique products compared to other chains.
Additionally, it will be worth watching whether non-EVM chains, which have struggled with developer onboarding due to language barriers and inconvenient development environments, can benefit from vibe coding. If retail participants reach a point where they can develop and deploy through vibe coding, continued underperformance can no longer be attributed to development environment inconveniences.
4. Surviving in the Vibe Coding Era
The spread of vibe coding could serve as an opportunity to realize, on a technical level, the permissionless participation that crypto originally promised. Retail participants who had no choice but to remain consumers or promoters beyond buying and selling tokens can now build things themselves and contribute to the ecosystem, as long as they have ideas.
Conversely, content fatigue could rise sharply. Vibe coding has only made implementation easier; it hasn't made ideas more original. Channels that have consistently broadcast their own unique philosophy will become far more valuable.
In an era where anyone can build, those who will survive are the ones who have spent more time contemplating what to build.
