In the old internet (Web2), audience was king. The bigger your reach, the louder your microphone, the better your “influence.” But Web3 flips the script. Here, reach isn’t enough. In fact, it’s often a liability if you don’t have the trust, loyalty, and shared purpose that only a real community can provide.

If you’re trying to build something in crypto—whether it’s a protocol, an NFT project, or a DePIN-powered fitness app—you better understand the difference between an audience that listens and a community that participates.

So, What’s the Difference?

Here’s the simplest way to put it:

• An audience is a group of people who watch.

• A community is a group of people who act.

An audience consumes. They’re eyeballs. Clicks. Views. They’re the people you broadcast to.

A community, on the other hand, contributes. They co-create with you. They share memes, build bots, fork your repo, jump on governance calls, show up to your X Spaces, and help squash bugs on a Sunday night—not because they have to, but because they want to.

And in Web3, wanting to is everything.

From Fans to Fanatics (The Web2 Trap)

Let’s take an example: in the Web2 world, let’s say you’re a YouTuber with 2 million subscribers. You make good content, they smash the like button, you get ad revenue, sponsorships, and maybe even launch some merch. That’s a great gig.

But it’s one-way traffic.

Your audience can’t fork your content. They can’t stake on your next idea. They don’t have governance over what you produce next. At best, they comment. Maybe they buy something. But they’re not in the room with you when you build.

That’s not how Web3 works.

In Web3, your token holders aren’t just consumers. They’re stakeholders. And your top contributors? They’re your cofounders in disguise.

This isn’t just semantics—it’s infrastructure. Let’s break that down.

Web3 Community Has Infrastructure

Here’s where it gets technical. Community in Web3 is often tied to onchain and offchain primitives that reinforce behavior, participation, and governance.

Onchain primitives:

• Tokens: Reward engagement, voting, coordination, and status.

• DAOs: Provide structure for decentralized contribution and decision-making.

• Staking mechanisms: Align incentives across builders, users, and speculators.

• NFTs: Serve as identity, access passes, reputation layers.

Offchain infrastructure:

• Discord, Telegram, Farcaster, Lens: Spaces where the culture lives and grows.

• Snapshot, Discourse, Coordinape: Places for governance, coordination, and contribution tracking.

• Bounties, Guilds, Working Groups: The new-age departments of decentralized orgs.

Communities don’t just follow you—they show up with their own tools, their own rituals, and their own momentum.

An audience can go viral overnight. But a community? That takes time. And more importantly, it can outlast market cycles.

Why It Matters in Crypto

Let me bring this closer to home.

The reason community matters so much in Web3 is because value creation is permissionless—but so is value exit.

In other words, if you don’t give people a reason to stay, they’ll leave. They’ll dump the token. Sell the JPEG. Leave your Discord dusty.

You can’t keep people around with hype forever. Attention fades. But involvement sticks.

Take Ethereum. It’s not just a chain; it’s a culture. ETH holders don’t just believe in number-go-up. They believe in decentralization, credible neutrality, and global coordination games. Same with communities like NounsDAO, Farcaster, or even Base. They have identities. In-jokes. Shared mental models.

You’re not just holding a token—you’re joining a movement.

That’s community.

Traits of an Audience vs. Traits of a Community

Here’s a quick breakdown to crystallize this:

The Builders’ Cheat Code

If you’re building in Web3, start asking this question daily: Am I growing an audience, or cultivating a community?

Because they require different tools, different languages, and different KPIs.

Audience is about metrics. Community is about momentum.

Audience is about reach. Community is about resonance.

If you’re launching a new DeFi protocol, the goal isn’t just to get 10K users to ape into your LP. It’s to get 50 of them to actually care enough to stick around, propose changes, or spin up a subDAO to improve the docs.

If you’re building a zk-rollup, it’s not about X threads and influencer shoutouts. It’s about attracting contributors who will audit your smart contracts, host sequencer nodes, or translate your whitepaper into Mandarin.

That’s the difference.

Final Whistle: The Power of Shared Ownership

At the end of the day, the most powerful force in Web3 is shared ownership. Not just financially, but culturally and emotionally.

When people feel like they own a piece of something—when they’ve contributed to it, suffered for it, laughed through it—they defend it. They build with you. They evangelize. And when things get tough (as they always do in crypto), they stick around.

That’s not an audience. That’s a community.

And in this space, that’s how you win.

As always, my DMs are wide open—whether you want to ask questions, talk shop, or collaborate on building something amazing. Let’s connect, learn, and create together. sam orth X: @theesamkos

Let’s get it!

Instead, I found myself buried under a pile of digital calendars, endless to-do lists, and missed notifications. I was constantly context-switching: one minute deep in research about the next writing topic or projects, the next prepping for a podcast episode, then jumping into a call. It felt like I was always playing catch-up, never quite in control of my own schedule. The discipline I’d honed on the ice was being tested in ways I hadn’t anticipated.

That’s when I discovered Motion—an AI-powered scheduling app that promised not just to organize my calendar, but to fundamentally change my relationship with time.

The First Shift: Letting Go of Manual Control

At first, I was skeptical. As a coach, I was used to being the architect of my days, meticulously planning every drill and every minute. The idea of handing over that control to an algorithm felt risky. But the onboarding experience with Motion was surprisingly smooth. The app’s user interface is clean and modern, with just enough guidance to make setup feel effortless. Within minutes, I’d synced my Google and Outlook calendars, imported my backlog of tasks, and set my working hours.

Then, I watched as Motion’s AI engine got to work. My scattered to-dos were slotted into my calendar, meetings were rearranged to protect blocks of focus time, and personal commitments—like family dinners or workouts—were treated with the same respect as business calls. It was as if I’d hired a world-class assistant, one who never got tired, never forgot a detail, and always had my best interests in mind.

The Second Shift: Experiencing True Productivity

The real magic of Motion isn’t just in its automation, but in how it adapts. On a typical day, I might start with a plan to write a blog post in the morning, record a podcast in the afternoon, and fit in some research between calls. But as any coach—or founder—knows, plans rarely survive first contact with reality. Meetings get rescheduled, urgent requests pop up, and sometimes you just need to take a walk to clear your head.

With Motion, these disruptions no longer derail my entire day. If a meeting runs late or a new priority emerges, Motion instantly recalibrates my schedule, finding the next best slot for each task without me having to drag and drop anything. The AI even learns over time which types of work I prefer at different times of day, subtly optimizing my calendar to match my natural rhythms. I found myself getting more done, with less stress, and—most importantly—more time for the things that matter outside of work.

The Third Shift: From Coach to Player—Trusting the System

One of the hardest lessons for any coach is learning to trust your players—to give them autonomy and let them make decisions on the ice. Using Motion felt similar. At first, I double-checked every AI suggestion, worried I’d miss something important. But as the weeks went by, I started to trust the system. I realized that Motion wasn’t just saving me time; it was freeing up mental energy that I could invest elsewhere—whether in creative brainstorming, deep technical work, or just being present with my family.

The app’s UX deserves special mention here. It’s not just functional, but genuinely enjoyable to use. Color-coded tasks, clear priority indicators, and a drag-and-drop interface make it easy to see what’s coming up and adjust on the fly if needed. The analytics dashboard gives me insights into how I’m spending my time, how many hours of work I am getting done, and helping me identify patterns and make smarter decisions about my work habits.

The Fourth Shift: The Bigger Picture—AI as a Team Player

What excites me most about Motion isn’t just how it helps me as an individual, but how it can transform teams. In the world of Web3 and remote work, coordinating across time zones and projects is a constant challenge. Motion’s collaborative features—like smart meeting scheduling and shared availability—make it easy to align with teammates without endless back-and-forth. It’s like having a playbook that updates itself in real time, ensuring everyone is on the same page, no matter where they are in the world.

As someone who’s always looking for the next edge—whether on the ice or in the blockchain space, I see Motion as a glimpse into the future of work. It’s not just about squeezing more tasks into the day, but about working smarter, protecting your time, and creating space for what really matters.

The Fifth Shift: Taking Notes and Capturing Ideas Seamlessly

One feature that truly surprised me, and quickly became indispensable—is Motion’s built-in note-taking ability. In the fast-moving world of Web3 and AI, ideas strike at any moment. Whether I’m in a meeting, brainstorming podcast topics, or reflecting on a new blockchain protocol, I need a place to capture thoughts instantly without breaking flow.

Motion integrates note-taking directly into your schedule and tasks, so you’re not juggling multiple apps or losing context. Each task or calendar event can have its own dedicated notes section, allowing me to jot down action items, meeting highlights, or even links and resources relevant to that block of time. This contextual note-taking means my thoughts stay organized and connected to what I’m actually working on.

What’s more, these notes sync across devices and are searchable, so I can quickly retrieve ideas from weeks ago without digging through endless files or apps. The ability to attach notes directly to tasks or meetings helps me keep track of progress and follow-ups, reducing the mental clutter that usually comes with managing multiple projects.

From a technical standpoint, Motion uses lightweight markdown formatting in notes, making it easy to add bullet points, checklists, and even simple code snippets—a handy feature for anyone in tech or creative fields. Plus, the notes support rich text and links, so you can embed references or jump straight to resources.

This integration of note-taking into the scheduling workflow is a game-changer for productivity. It’s like having a digital coach not only organizing your time but also helping you capture and act on your best ideas as they happen.

How Motion’s AI Works Behind the Scenes

Now, let’s get into the nuts and bolts. Because as much as I love the end result—I’m a mechanical guy. I want to know what’s under the hood.

1. Intelligent Task Prioritization and Scheduling Algorithms
Motion uses a combination of machine learning models and advanced heuristics to analyze your task list, calendar events, and work preferences. It doesn’t just look at due dates—it factors in task complexity, estimated duration, dependencies, and even your historical work patterns. The AI dynamically stacks and reorders your day, aiming to maximize productivity while minimizing context switching.

2. Real-Time Calendar Sync and Conflict Resolution
Motion’s backend is built for seamless integration with major calendar APIs (Google, Outlook, Office 365). Any change, whether it’s a new meeting invite or a last-minute cancellation—triggers the AI to instantly recalculate your schedule. It uses constraint satisfaction algorithms to avoid double-booking and to protect your focus blocks, even as your day shifts.

3. Adaptive Learning Engine
The more you use Motion, the smarter it gets. It tracks when you actually complete tasks, how long you spend in meetings, and your preferred work windows. Using reinforcement learning, the app gradually adapts to your unique rhythms—maybe you’re sharper in the mornings for deep work, or you hit your stride after lunch. Motion’s AI will start to schedule your most demanding tasks when you’re at your peak.

4. Collaborative Scheduling and Shared Availability
For teams, Motion leverages group availability data and priority scoring to suggest optimal meeting times. It can analyze overlapping calendars, time zones, and even individual workload forecasts to minimize disruption and maximize collective productivity.

5. Focus Time Protection and Distraction Management
Motion’s AI actively defends your focus time. If someone tries to book over your deep work block, the app can automatically suggest alternative slots or flag the conflict. It’s like having a digital bodyguard for your most valuable hours.

6. Security and Privacy
All data is encrypted both in transit and at rest. Motion’s architecture is built with privacy in mind—your information isn’t sold or shared, and you have granular controls over what’s synced and how your data is used. For those of us in Web3 and crypto, that’s non-negotiable.

Motion: Features, Technicalities, and Standout Details

• AI-Powered Scheduling: Automatically organizes, prioritizes, and reschedules tasks and meetings based on your real-time availability and shifting priorities.

• Task Management Integration: Syncs with Google, Outlook, and other major calendar platforms; allows direct task input, categorization, and deadline management.

• Focus Time Protection: Blocks out and defends distraction-free periods for deep work, ensuring your most important tasks get done.

• Dynamic Rescheduling: Instantly adapts your schedule when meetings change, tasks run over, or new priorities emerge—no manual adjustment needed.

• Collaborative Scheduling: Suggests optimal meeting times based on team availability and priority, reducing endless email threads

• Intuitive UX: Clean, visually appealing interface with drag-and-drop functionality, color-coded priorities, and clear visual cues.

• Productivity Analytics: Provides detailed insights into your work patterns, focus time, and productivity trends, helping you optimize your habits.

• Mobile and Desktop Apps: Seamless experience across devices, so your schedule is always up to date wherever you are.

• Privacy and Security: Enterprise-grade encryption and privacy controls, ensuring your data is safe and confidential.

• Learning and Adaptation: The AI learns your preferences over time, optimizing schedules to fit your unique work style and energy peaks.

Final Whistle

Motion isn’t just another productivity tool—it’s a true AI teammate. For anyone navigating the unpredictable, high-stakes world of tech, entrepreneurship, or creative work, it’s the closest thing I’ve found to having a personal assistant who never misses a beat. If you’re ready to take your schedule, and your peace of mind to the next level—give Motion a try. You might just find, as I did, that the right technology can make all the difference.

As always, my DMs are wide open—whether you want to ask questions, talk shop, or collaborate on building something amazing. Let’s connect, learn, and create together. Let’s get it together!

Now that I’ve swapped the ice for smart contracts and Discords, I’ve been exploring what coordination looks like when you don’t have a coach, a locker room, or even fixed roles. In this piece, I want to break down how to run a sprint that actually works in decentralized ecosystems. Think of it like a game plan for async, pseudonymous teams trying to move fast without breaking trust.

What is a Scrum

Growing up, a “Scrum” was something that you would get a black eye during… maybe more. In Web3 it’s more than just a buzzword tossed around in stand-ups and sprint planning meetings. It’s a framework designed to help teams move fast, stay focused, and build real value. Ultimately, Scrum is built around the idea of breaking big. Complex work into smaller, more manageable chunks. You’re not trying to plan everything upfront and hope it goes well. Instead, you're adapting as you go. Think of it like a hockey season. You have a clear goal. Make the playoffs. But each game, each practice, each shift is a chance to adjust, regroup, and improve. Scrum gives teams that structure: short iterations (called sprints), daily check-ins, and regular moments to pause and reflect. It’s not about micromanaging or doing more work faster, it’s about doing the right work, together, with clarity and purpose. The roles are clear. The Product Owner defines the vision, the Scrum Master clears the path, and the Development Team gets the job done. The magic of Scrum isn't in some fancy tool, it’s in the rhythm it creates. A good Scrum team hums like a well-coached line on the ice: always communicating, always adjusting, always focused on the next best play.

What is Kanban?

The word Kanban comes from Japanese, and it literally means “signboard” or “visual signal.” It has roots in the lean manufacturing movement, most famously at Toyota in the 1940s. Back then, Toyota engineers were looking for a way to improve factory efficiency without the waste that came from overproduction or under-utilized resources. They took inspiration from supermarkets, where shelves are only restocked when products are running low, pulling inventory only when it’s needed. That concept became the foundation of Kanban. A pull-based system where work moves forward only when there’s capacity to handle it. In the factory, that might have looked like physical cards signaling when to refill a part bin. In today’s digital work, it looks like tasks on a board, moving from “To Do” to “Done.”

Kanban was later brought into knowledge work and software development by David J. Anderson in the early 2000s. He took those lean principles from Toyota and adapted them for modern teams who weren’t building cars, but were still trying to manage complex workflows. The core idea remains the same: visualize the work, limit how much is in progress, and manage flow. Unlike Scrum, which gives you a structured playbook of roles, sprints, and ceremonies, Kanban is more fluid. It doesn’t ask you to change your team structure, it works with what you’ve got. You just start with where you are, make your work visible, and begin to evolve your process based on real data and real bottlenecks.

Kanban is quiet but powerful. It doesn’t yell for your attention like some frameworks do. It just reveals what’s actually happening inside your team. Where are things getting stuck? Who’s overloaded? What’s the real pace at which your team delivers? Once you see the work, you can start to improve it. And you do that gradually, not through massive overhauls. It’s like a hockey player who studies film between games. Not to redesign the whole strategy, but to tweak angles, timing, and communication. That’s Kanban. Continuous improvement, one visual signal at a time.

Scrum vs Kanban

Scrum and Kanban both aim to help teams deliver better work, but they take different roads to get there. Scrum is more structured. It works in fixed-length sprints, usually two weeks, with clearly defined roles like the Product Owner and Scrum Master. There are regular ceremonies: sprint planning, daily stand-ups, sprint reviews, and retrospectives. It’s a full-on rhythm, almost like a team following a strict game schedule with pre-game meetings, line changes, and post-game analysis. Kanban, on the other hand, is more fluid and continuous. There are no set timeframes, no mandatory roles, and no required ceremonies. Work just flows. Tasks are pulled when there’s capacity, and progress is tracked visually through columns. Scrum is great when you need predictability and team discipline to push toward specific goals. Kanban thrives in environments with lots of incoming change or where priorities shift quickly. The best part? You don’t have to choose just one. Some teams even blend both, using Scrum for structure and Kanban to monitor flow and spot bottlenecks. It’s not about picking a side, it’s about understanding your team’s needs and finding the system that helps you deliver with clarity, speed, and purpose.

Team Size: Can You Sprint Too Big?

While the Scrum Guide recommends 5–11 people, in the real world, teams have pushed both ends of that spectrum. On the low end, some teams have run sprints with just 2 or 3 members. On the high end, organizations have stretched Scrum to teams of 15 or even 20 people, usually as part of a larger scaled setup.

Let’s start with tiny Scrum teams, just two or three people grinding through a sprint. The pros? Communication is instant. No meetings drag. Everyone wears multiple hats, and you get raw ownership from start to finish. It’s the kind of setup that works well in very early-stage startups or skunkworks projects where agility and speed matter more than process. But the cons hit hard. There’s often a lack of skill diversity, burnout risk is high, and if one person gets sick or pulled away, the whole sprint might crumble.

On the flip side, large Scrum teams. 15 or more people in one sprint can pull in a wide range of skills, experience, and ideas. You get specialists, deeper QA, and often higher throughput. But it’s also a coordination nightmare. Standups become status meetings. People talk over each other. Work overlaps or falls through the cracks. It’s hard to stay focused, and accountability gets diluted.

In most cases, if your team grows beyond 10 or 11, the better move is to split into multiple Scrum teams and align them using frameworks like Nexus or SAFe. That way, you preserve the benefits of small-team speed while scaling across a larger organization.

How Long Should a Sprint Be?

Most of the time, one or two weeks is the sweet spot. A one-week sprint is ideal for quick shipping cycles. Prototypes, content campaigns, or hackathon prep. Two weeks works better for deeper builds. Like smart contract deployments, rebrands, or multi-stakeholder initiatives.

You’ll want to avoid sprints if your goals are vague, your contributors are overextended, or your task is research-heavy with no clear outputs. A sprint should feel like a race, not a retreat.

Laying the Ice: Notion as Your Command Center

Before anyone can sprint, you need a clear runway. And Notion is where that starts. Treat it like a command center, the single source of truth for what’s happening, who’s involved, and why it matters. A well-organized Notion page replaces status meetings, Slack scrolls, and “Who’s doing what again?” messages.

Each sprint starts with a mission statement. This should be short, focused, and outcome-oriented, “Improve contributor onboarding.” You’ll also want a clear timeline. With start and end dates, mid-sprint check-ins, and demo or review deadlines. Use a simple kanban-style board for tracking tasks from backlog to done, along with a contributor table that lists everyone’s role, time commitment, and time zone. This matters in Web3, where your front-end dev might be in Canada and your designer’s in Singapore.

To go deeper, often embed docs, Figma links, GitHub repos, and past research directly into the page. Notion’s new button feature also helps, you can build contributor-specific onboarding flows that auto-populate based on their role or skillset. It’s not just clean. It’s fast, scalable coordination.

https://www.youtube.com/watch?v=cYbcgtK0v_Q

Building Momentum: Discord as the Locker Room

Notion is where plans live. But Discord is where the energy happens. It’s your digital locker room. Messy, loud, and full of real-time momentum. That chaos can be a superpower if you give it just enough structure.

Usually a dedicated sprint channel is created where everything related to the sprint gets dropped— Key links, updates, memes, questions. Daily check-ins happen in a pinned thread, with a simple format: yesterday / today / blockers. For voice-heavy teams, a 15-minute optional standup call can do wonders for chemistry and momentum. But async standups work just fine if you’re global or time-crunched.

Tagging contributors with roles makes it easier to coordinate across skill sets. Always make space for a meta-channel. A place where we reflect in real time on how the sprint is going. What’s working, what’s confusing, what needs more context.

Many Web3 sprints die not from lack of talent, but from silence. Discord keeps the blood pumping.

https://x.com/discord

Drivng Alignment: Using Snapshot for Community Buy-In

Once the sprint team ships something tangible: whether it’s a new feature, a governance dashboard, or a content drop. Bring that work to the broader community using Snapshot. It’s fast, free (gasless), and community-friendly.

Build a clear proposal with visual context, a concise explanation of the goal, and two or three options for voting. Also, prime the community ahead of time in Discord, using emoji polls or soft-signal threads. That way, Snapshot isn’t a surprise. It’s the final nod.

You don’t need to vote on everything. Save it for the big moments. New budgets, protocol upgrades, user-facing changes. But done right, Snapshot lets you move fast and earn legitimacy.

Closing the Loop: Post-Sprint Retrospectives

After the sprint ends, Always run a retro. This is sacred space, it’s where process gets sharper and culture gets stronger. Start with a Tally form or Notion survey. Asking contributors, what worked? What didn’t? What was confusing? Who crushed it? What should we change next time?

Then we hop into Discord for an optional voice call. People drop feedback, call out wins, vent a little. It’s casual, but powerful. Retros are how we evolve. In a world without managers, feedback is leadership.

Final Whistle

Web3 isn’t just changing how we build, it’s changing who builds, where, and why. But all that openness brings new coordination challenges. Sprints give us a way to inject urgency, create shared purpose, and actually ship.

I’m not romantic about any one tool or framework. What matters is the rhythm: set the stage, align the team, move fast, reflect, and improve. Rinse and repeat.

Sprinting in Web3 isn’t just about shipping faster. It’s about building trust at speed, culture through action, and momentum through shared wins. If you’re experimenting with these models, I’d love to hear how you’re running your sprints. And what you’re learning along the way.

As always my Dm’s on X sam orth are open for more on this topic, other questions, or talk shop.

Lets get it together

Whether you’re wrangling engineers, talking tokenomics, or keeping Discord mods sane, being a Project Manager in Web3 means staying organized across decentralized chaos. And the right tools? They’re your playbook.

Here are some of the best apps I’ve used (or seen others swear by) for getting sh*t done in Web3.

Planning & Task Management

• Notion
  Still one of the most flexible tools in Web3. Great for sprint boards, contributor guides, process docs, and public roadmaps. I’ve seen DAOs spin up entire governance proposals and org handbooks using linked databases and synced blocks in Notion. Bonus: it plays nicely with token-gated embeds via tools like MintGate or third-party widgets if you want to blend onchain identity into your docs.

• Linear
  Ideal for protocol teams and Web3 orgs that treat product like software. Linear’s tight integration with GitHub and clean API makes it easy to build automation around PR tracking, bug triage, or roadmap tagging. Some teams use bots to link Linear issues with onchain governance proposals or Discord threads to keep feedback flowing back to the right people.

• Trello + Custom Automation
  Trello by itself isn’t “Web3-native,” but with automation (Butler, Zapier, or scripts via webhooks), it can power bounty flows, social content pipelines, or even validator onboarding. Think of it like your analog whiteboard. Customizable, but needs some setup to be useful.

Onchain Project Coordination

• CharmVerse
  This is like Notion built for DAOs, with wallet login, token-based access control, and onchain governance support. Teams like Gitcoin and Bankless use it to blend documentation with action. Where a proposal isn’t just text, it’s linked to contributors, budgets, and even attestations. You can create project dashboards that track contributions by wallet, then link them to reputation systems or bounties.

• Dework
  A legit favorite for bounty-driven orgs. Dework lets you assign tasks to wallet-connected users, attach USDC or token rewards, and track contributor history publicly. It integrates with Discord so you can push new tasks to a channel or let people claim bounties in real-time. Great for permissionless contributor flows.

• Wonderverse
  Sits in the same category but shines when you need contributor profiles, working group visibility, and lightweight reporting. You can use it to map your DAO’s pods, track contributor seasons, or segment internal teams for easier async communication.

Comms & Community Ops

• Discord
  It’s the Web3 HQ whether you like it or not. But smart teams use Forum Channels, custom bots, and thread workflows to tame the chaos. I’ve seen project managers use tools like Sesh for scheduling, Guild.xyz for access control, and Waku for bridging chat to decentralized messaging layers.

• Telegram
  Still unbeatable for fast-paced updates, regional contributors, or founder-style fire drills. Just don’t try managing ops here long-term. I’s fast, not structured. That said, tools like WalletConnect and Push Protocol are starting to let teams build more persistent conversations around wallet identities, which could open the door to Telegram-native workstreams in the future.

• Slack (For Hybrid Teams)
  Some teams (especially those with investors or external partners) run Slack + Discord in parallel. Slack’s app integrations (like Linear or Notion bots) still win for internal ops and async standups. Just be careful, splitting platforms adds overhead unless roles are clearly divided.

  Storage, Data & Version Control

• Arweave (via Bundlr, ArDrive, or Irys)
  If you’re serious about data permanence and provenance, Arweave is your go-to. Think of it like Git for data. p\Permanently storing files, documents, or snapshots in a way that’s tamper-proof and censorship-resistant. Store your org’s roadmap, token design memos, or governance snapshots here to ensure they’re accessible for years, not months. Tools like Irys make this easy with fast uploads and flexible APIs.

• IPFS + Pinning Services (Pinata, Filebase)
  While not truly permanent, IPFS is still the backbone for a lot of NFT metadata and DAO files. Combine it with pinning services or IPFS gateways to ensure file availability. Some PMs even use IPFS hashes inside governance proposals to point to offchain data in a trust-minimized way.

• GitHub (or Radicle)
  GitHub isn’t just for devs. You can track technical specs, publish open RFCs, or manage public workflows here. Especially if your org has open-source contributions. For the privacy-maxi crowd, Radicle is a peer-to-peer alternative that works without centralized platforms and is slowly gaining traction in zero-knowledge circles.

PowerPlay: Intelligence + Transparency Layers

• Dune Analytics
  Project Managers who can read smart contract data have superpowers. Dune lets you build dashboards around protocol health, DAO voter behavior, or contributor activity. It’s especially useful when tying OKRs or KPIs to onchain data. No guesswork, just queries.

• Snapshot
  Even if you’re not in charge of governance, understanding how decisions move through Snapshot proposals is crucial. You can use offchain signaling to coordinate roadmap priorities, funding requests, or community decisions without deploying contracts.

• Tally / Agora
  For teams with full onchain governance, these tools help track proposals, delegate votes, and manage multisig decisions. As a PM, they let you stay synced with governance flow and help contributors understand how their work ties into the big picture.

Real Talk

Most teams don’t need a massive tool stack. What matters most is:

• Is it open to contributors?

• Does it integrate with how your team already communicates?

• Can it grow with the project, from 5 contributors to 500?

Start simple. Build repeatable workflows. Then layer in tools that make sense for your ecosystem, not just what’s trending on Crypto Twitter.

Final Whistle

Being a Project Manager in Web3 isn’t about controlling chaos, it’s about creating clarity through it. The best tools help you organize the noise, surface priorities, and make the work feel doable.

The difference between a stalled DAO and a shipping one? Often just a well-set-up Dework board, a clean Notion workspace, and a few clear roles.

Next up in this series: I’ll be diving into how I would run a Web 3 Sprint using Notion, Discord, and Snapshot. If you want to check out the live stream with myself & Patrick Skinner talking about Breaking through into the Web3 and Crypto world: https://x.com/i/broadcasts/1ZkJzYEgOvDGv

Let’s build systems that work as well as the code we ship.

As always, I love talking and answering any questions about Web 3 or just…in general. Dm’s are open at sam orth

After spending most of my life around locker rooms, ice rinks, and chalkboards, I’ve come to believe in systems where people show up, put in the work, and win together. That same team-first mindset is what drew me to open-source software. Not just as a development approach, but as a new kind of business model that’s reshaping how value is created and shared in the digital world.

Now that I’m diving deep into Ethereum, Web3, and the future of decentralized tech, I’m convinced,
Open-source is more than code. It’s the business infrastructure of the next internet.

Let’s break that down.

What Is an Open-Source Business Model?

Open-source software is exactly what it sounds like, source code that’s made publicly available for anyone to inspect, use, modify, and contribute to. But open-source business models are something more nuanced. They answer the question:
How do you build a sustainable company when your product is free for anyone to use?

It sounds like a paradox. But here’s the reality, open-source companies are some of the most influential and enduring tech businesses of our time.

• Red Hat was acquired by IBM for $34 billion.

• MongoDB, GitLab, and Elastic went public with strong market caps.

• Ethereum itself, arguably the most composable and valuable open-source protocol. Secures hundreds of billions in assets.

So how do they do it?

Popular Open-Source Business Models

Here are some of the most common open-source monetization strategies, broken down with real-world relevance:

1. Open Core

Offer a functional, free version of your software with premium features behind a paywall.

• Example: GitLab offers a free community edition but charges enterprises for advanced CI/CD, compliance, and security features.

• Why its successful: You attract a huge user base through free tools, then monetize serious teams and organizations with specialized needs.

2. SaaS on Open-Source

Provide the same open-source product as a hosted, managed service.

• Why its successful: Most companies would rather pay for uptime, scalability, and support than run infrastructure themselves.

3. Dual Licensing

The software is free for personal or non-commercial use, but companies must pay to use it commercially.

• Why its successful: It preserves freedom while protecting commercial value.

4. Token Incentivized Protocols (Web3-native)

Instead of charging users, open-source protocols issue tokens to fund development and align incentives between contributors, builders, and users.

• Why its successful: Tokens turn users into stakeholders, letting communities grow and steer the project.

5. Grants & Sponsorships

Some projects are so essential that they’re funded like public infrastructure, through grants from the Ethereum Foundation, DAOs, or philanthropic orgs.

• Example: Prysm, Geth, Lighthouse, Ethereum client teams.

• Why it works: Decentralized infrastructure needs decentralized funding. This keeps the incentives clean and the network resilient.

Why I Believe in Open-Source Models

I’m drawn to open-source because it reflects the same values that make great teams succeed: transparency, alignment, shared accountability. Here’s why it matters more than ever, especially in a post-Web2 world.

Transparency Builds Trust

In Web2, you trust a platform because you have no choice. It’s a black box. In Web3, code is law. And that law is public. If it’s open-source, you can verify what’s happening under the hood. You can fork it. You can build on it.

In a digital world full of shadowy algorithms and exploitative business models, transparency is a moat.

Community Is Not Just a Marketing Tool

Open-source flips the script. Your users aren’t just users. They’re contributors, evangelists, and co-builders. That’s incredibly powerful.

In coaching, your bench players are often your heartbeat. The ones who push practice tempo, lift others up, and keep morale high. In open-source, it’s the same. Your contributors shape the product culture and expand what’s possible.

Composability Is a Superpower

Because the code is public, other projects can plug into yours like Lego bricks. That’s why Ethereum works, everything from Lens to Farcaster to Arweave is designed to interoperate.

This isn’t just good tech. It’s a strategic advantage. When others build on your shoulders, your reach grows exponentially.

The Future of Open-Source is Onchain

With the rise of Ethereum and decentralized protocols, open-source is entering a new era. onchain public goods.

Take Arweave for example. A permanent, censorship-resistant storage layer built with open-source ideals. Or Farcaster, which uses open-source smart contracts to build an ecosystem of social apps that don’t rely on one central feed.

These aren’t just tools, they’re experiments in digital sovereignty.

You don’t need permission from a VC boardroom to participate. You just need to show up, contribute, and build something useful.

Web3’s best open-source projects aren’t fighting for market share, they’re expanding the whole pie.

Final Whistle

We’re in a pivotal moment. As AI gets more centralized and surveillance capitalism doubles down, the best defense is radical openness.

Open-source business models give us a way forward that’s honest, resilient, and regenerative. They align incentives between creators and communities. They respect the people who do the work. And they build technology that serves the public. Not platforms.

I’m not saying every project should be open-source. But I am saying this:

If we want to build a digital world where we own our data, trust our tools, and reward real contributions. Open-source has to be part of the game plan.

And that’s a team I’ll always bet on.

Let’s Keep the Conversation Going

If you’re curious about open-source, Web3, or how all this ties into the future of work. I’d love to hear from you. One of my favorite parts about this space is breaking down complex ideas in a way that actually makes sense. No jargon. No gatekeeping. Just real conversations that help more people get involved.

You can always reach out to me on X sam orth my DMs are open. Whether you're a builder, a creator, or just exploring how all this fits together, I’m here for it.

Let’s learn, share, and grow this thing together.

Coming off the heels of a deep dive into DePIN and Arweave, one thing keeps resonating. Permanence is power. Whether we’re talking about decentralized storage or community-powered networks, or the tools we’re building now aren’t just protocols. They’re foundations. And for creators, few platforms embody this shift better than Mirror.xyz.

If DePIN is rebuilding the physical world with decentralized intent, then Mirror is doing the same for digital expression. It’s not just an Ethereum-powered blogging tool. It’s a publishing frontier where creators own their work, fund their visions, and build cultural artifacts without gatekeepers.

From DePIN to Digital Legacy

In the last article, we talked about physical infrastructure: wireless networks, energy grids, and permanent storage on Arweave. But creation doesn't stop with code or hardware. It includes the stories we tell, the ideas we spread, the movements we seed.

Mirror builds on that ethos. It leverages Arweave for permanent publishing, allowing every post to live forever. The same way DePIN decentralizes access to physical tools, Mirror decentralizes the mechanics of expression, funding, and community engagement. For creators like us writers, coaches, builders. It’s more than novel. It’s necessary.

Mirror Is Not Just a Tool, It’s a Creative Protocol

At first glance, Mirror looks like a minimalist blogging platform. But beneath the surface, it's an Ethereum-based protocol that rewires what publishing can mean:

• Your work is permanently stored on Arweave. No platform risk, no takedowns, no expiration dates.

• Crowdfunds and splits are built-in, letting your ideas be community-funded and transparently shared.

• NFTs for writing let your audience own a piece of your narrative, not just scroll past it.

• Composability with other Web3 tools makes Mirror more than a platform, it's a launchpad.

In Web2, the platform is the gate. In Web3, the protocol is the invitation.

Creative Capital: From Audience to Ownership

One of Mirror’s most powerful features is its ability to turn early support into lasting involvement. You can write a post, launch a crowdfund, and reward backers not with “likes” or “follows,” but with stake. The readers who believe in your idea early don’t just cheer from the sidelines, they ride with you.

If that sounds familiar, it should. It’s the same principle that drives DePIN. Contribute early, earn real upside, and share in the value you help create.

In the old model, content was a one-way street. In this new model, creation becomes coordination. A two-way, on-chain dialogue between the writer and their readers.

Writing as Cultural Infrastructure

I used to be skeptical about “writing NFTs.” But now I see them differently, not as collectibles for the sake of novelty, but as time-stamped proof of early belief. Like a signed puck from a championship season, or a locker room photo before the breakout year.

When someone collects your writing, they’re saying: “I was here before it mattered to anyone else” And that’s a powerful layer of creative infrastructure, one we never had before in Web2.

This mirrors the deeper cultural current in Web3. We don’t just consume stories, we build them. Together.

It’s Personal for me

In many ways, Mirror is a natural continuation of what we explored in the DePIN article. It’s about independence, yes. But also about permanence, incentives, and coordination. We are witnessing the rise of platforms that not only host creativity, but incentivize and preserve it. That’s a profound shift.

Web3 isn't just about new tech stacks. It’s about reimagining the relationship between tools and the people who use them.

• In DePIN, you own the infrastructure.

• On Mirror, you own the narrative.

Both are critical. Both require trustless systems, aligned incentives.. A belief that our efforts, whether physical or creative, deserve to last.

What do we do?

I’ll be experimenting with Mirror to publish more of these reflections, and to test new models of crowdfunded writing and audience participation. If you joined us during the livestream or read my last blog on Arweave and DePIN, this is the next layer of the story. From hardware to headspace, from infrastructure to identity.

The future of the internet isn’t just decentralized. It’s earned, owned, and remembered.

Let’s keep building.

If you’ve ever coached a team, built something with your hands, or rallied people around a shared mission, you’ll feel something familiar in this movement.

Wait, What is DePIN?

DePIN stands for Decentralized Physical Infrastructure Networks. It’s a mouthful, but the idea is simple:

Instead of massive corporations owning and operating the hardware that powers our digital lives, communities and individuals contribute to and earn from physical infrastructure, whether it’s wireless nodes, sensors, GPU farms, solar panels, or permanent data storage.

You’re seeing it already:

• Helium: community-powered wireless networks.

• Render: decentralized GPU compute power.

• Arweave: permanent, decentralized data storage.

It’s the same shift we saw when open-source software outpaced closed platforms. Only this time, it’s happening in the physical world.

From Web2 Hosting to Web3 Infrastructure

In Web2, big companies like AWS, Google Cloud, or Dropbox owned the servers and made the rules. Sure, it was convenient. But it wasn’t built for permanence, fairness, or freedom.

Arweave flips that model on its head. Instead of renting server space month to month, you pay once to store something forever. That’s not a marketing slogan it’s, actually how it works. Thanks to its unique economic model, Arweave incentivizes nodes to keep your data available indefinitely.

That’s huge. Especially for creators, developers, and communities who want to own their history. Not just rent it.

It’s Crucial for Builders

DePIN gives power back to builders and contributors in three ways:

1. Ownership
   You’re not just a customer of infrastructure. You’re a stakeholder. When you run a node, store data, or provide resources, you get rewarded. Often in real-time, with on-chain transparency.

2. Resilience
   Decentralized networks don’t go down when one server crashes or a company decides to shut it down. The network is as strong as its community, like any good team.

3. Incentives That Actually Work
   Traditional infrastructure is slow to scale and hard to fund. DePIN flips that by letting anyone earn by helping grow the network. It’s like staking your time, hardware, or energy. Then being rewarded when the network thrives.

Arweave as a DePIN Trailblazer

Arweave is a perfect DePIN case study. It turns data storage into a community-run, permanent layer of the internet.

Here’s what makes it special:

• Pay once, store forever: Instead of monthly bills, you pay an upfront fee that covers permanent replication of your data.

• Miners and storage nodes: People all over the world earn AR tokens by hosting data and contributing to network reliability.

• Used by real apps: From Mirror.xyz (yep, this blog is probably stored there) to NFT metadata and academic archives, Arweave is already deeply integrated with the onchain world.

It’s not just theory. It’s live, and people are building on it every day.

So What’s the Play Here?

If you’re a builder, a writer, a founder, DePIN is a serious unlock. You can contribute to physical networks without needing to raise millions in hardware or capital. You can earn by supporting networks that matter to you, not just using them.

And if you’re a believer in Ethereum and Web3’s values. Open access, community ownership, aligned incentives, DePIN is where those values hit the ground. Literally.

Closing Thought

I grew up in a world where value came from what you could see and feel. A perfectly sharpened skate blade, a hard-earned win on the ice, or a full day’s work building something that lasted.

DePIN brings that same feeling to Web3. It reminds us that behind every line of code, there’s hardware, energy, and human effort. And now, that effort is finally being recognized, and rewarded. In a way that scales with the internet.

Let’s build the next layer together

Even more Curios?

Alot more was unpacked about DePIN, Arweave, and how this all connects to real-world use cases during a recent livestream with Myself sam orth hosted by Patrick Skinner. We talked shop, from decentralized mapping to the permanence of digital legacy. All with a dose of old-school grit and future-facing optimism. If this topic fires you up like it does me, I’d love for you to check it out, drop a comment, and join the conversation:

https://x.com/i/broadcasts/1YpKkBABrgPxj

Coming from a background in coaching, I’ve always seen the world through systems and people. how roles fit together, how trust is built (or lost), and how momentum can make or break a season. That same lens applies surprisingly well to the Web3 world. Coaching hockey and building on Ethereum aren’t that different. Both are team sports, both are about finding the right incentives, and both reward consistency and culture over hype.

After reading Read, Write, Own, it clicked. The reason onchain business models work is because they’re fundamentally aligned. Aligned with people, with communities, with builders, and with value itself.

Here’s why that matters, and why it’s worth betting your future on.

1. The Ownership Layer Is the Missing Link

Web2 gave us participation. Web3 gives us ownership. That’s the big unlock.

In the old internet, you could build a following, you could go viral, you could even monetize a little. But the house always won. You didn’t own the algorithm, the infrastructure, or the upside. In Web3, protocols like Ethereum let us flip that script. Now, the platforms are open. The code is forkable. The value you create is actually traceable. If you do it right, you and your community can own the rewards.

This isn’t theory. It’s already playing out. Think of something like Farcaster, where early contributors can build apps, attract users, and be rewarded onchain for their impact. It’s the difference between being a player who just shows up to practice and being a player/owner who helps set the team direction.

And if you’ve coached before, you know which one leads to a better locker room.

2. Token Incentives = Culture at Scale

One thing I loved about Read, Write, Own was how clearly it laid out the idea that tokens aren’t just money, they’re culture infrastructure.

Most people outside of Web3 think tokens are a speculative mess. But when done right, they’re actually tools for shaping behavior. Want users to contribute instead of just consume? Reward them. Want your early supporters to stick around long enough to see version 2.0? Let them own a piece of it. Want to experiment fast without losing trust? Put everything onchain and let people verify for themselves.

A token is like a captain’s letter on a jersey. It signals trust, commitment, and contribution. The difference is that onchain systems make that signal legible, and transferable.

3. Composability Is the Ultimate Assist

In coaching, you find some players make the final play. But others create the opportunity that leads to the play. In Web3, those quiet contributors are often the most powerful, because of composability.

Protocols can plug into each other like Lego. Someone builds a tool, someone else builds a layer on top of it, and a third person bundles both into a whole new product. This wouldn’t be possible in a traditional, closed business model. But when you’re building onchain, openness is part of the DNA.

This is why onchain business models don’t need huge marketing budgets to grow. The network becomes your distribution. Your partners become your sales team. And the more you lean into that, the faster the flywheel spins.

4. Trustless Doesn’t Mean Cold, It Means Scalable Trust

The term “trustless” throws a lot of people off. It sounds robotic, impersonal. But it’s not about removing trust, it’s about removing the need to trust blindly.

When everything lives onchain, you get receipts. You get clarity. You don’t have to ask if someone followed through, you check the block explorer. That kind of environment is actually more human, not less. It allows for real accountability, real ownership, and real autonomy.

In sports, you know when a player skips a duty or does something that creates a penalty. On the blockchain, the same thing applies. Everyone’s watching the tape.

5. DAOs Are Just Locker Rooms with Governance

One of the biggest takeaways from Read, Write, Own is that DAOs. (decentralized autonomous organizations) are more than just buzzwords. When you strip away the jargon, they’re just structured groups of people aligned around a shared goal, with some rules and tools to keep them accountable.

Sound familiar? That’s a team.

Of course, not every DAO is perfect. But the ones that work well feel a lot like good teams. Roles are clear, feedback is frequent, decisions are debated (and then owned), and everyone shares in the win. That’s powerful, and it’s possible at global scale because of the blockchain.

6. We're Just Getting Started

Here’s the truth, most people still don’t get Web3. And that’s okay. They didn’t get open source at first either. They didn’t get social media, or streaming, or e-commerce. But once the incentives align and the value becomes clear, the shift happens fast.

If you’ve ever been part of a team where everyone is bought in. Where trust runs deep and everyone knows they’re building toward something real. You know how unstoppable that can be.

Web3 has that energy right now. And thanks to frameworks like the ones laid out in Read, Write, Own, we can build with intention. We can build with alignment. And we can finally build businesses that feel like teams, not extraction machines.

That’s the future I want to be part of.

Funny enough, that’s exactly what it feels like working in Web3 today.

At first glance, moving from the ice rink to blockchain networks might seem like a huge leap. But the more time I spend in this space, the more it feels like I just traded one locker room for another. One filled with builders, dreamers, and communities instead of athletes.

Here’s why Web3 feels like coaching all over again:

1. It’s Still a People-First Game

In coaching, you learn fast. You can have the best plays on the whiteboard, but if you don't earn the trust and buy-in of your players, it won't matter.

Web3 is the same way. You can launch the sickest app, the cleanest smart contract. But without trust, without a real community that believes in the mission, you’re just noise.

Web3 runs on trust.
Just like a good team does.

It’s not about perfect code. It’s about shared belief, loyalty, and real connection. Things no tech stack can fake.

2. Teaching and Learning Happen at the Same Time

As a coach, there were moments when you knew exactly what the team needed. And others where you were figuring it out right alongside them. You learned by doing. By listening. By being honest when you didn’t have all the answers.

Same in Web3.
No one has all the answers here. The technology is evolving daily. New ecosystems pop up overnight. New models for ownership, governance, and incentives are being built as we speak.

You have to be a guide and a student at the same time.
That’s what keeps it real, and keeps you sharp.

3. Empowerment > Control

The best coaches don't call every play. They train their players to read the ice and make the right call under pressure.
Because you can't control every puck bounce, every line change. What you can do is empower.

Web3 builders get this too. The winning projects aren’t just handing out orders, they’re creating frameworks where the community owns the direction. They’re saying,

"Here’s the puck, you know what to do."

It’s defiantly a shift, It’s decentralized leadership in action.

4. Rapid Adaptation Is the Norm

Some games as a coach, your whole strategy gets blown up by the end of the first period. Bad bounces, injuries, opponents switching tactics. You adapt or you get left behind.

In Web3, the pace is just as fast. Maybe faster.

• New L2s launching weekly.

• Entire funding models getting disrupted overnight.

• User bases shifting with a single airdrop.

The difference?
In Web3, nobody expects stability.
Agility isn’t just a skill, it’s survival.

Coaching taught me to read momentum shifts, to trust instincts, and to be okay making calls with incomplete information.
Web3 demands the same mindset every single day.

5. Building Something Bigger Than Yourself

One of the best feelings in coaching wasn’t winning championships (although that was awesome).
It was seeing a player you mentored take what they learned and become a version of themselves.

That's the same energy that flows through Web3.

The best projects aren't about spotlighting the founders, they’re about building systems that empower others:

• Protocols that live beyond their creators.

• Communities that run themselves.

• Tools that unlock opportunity for millions.

It’s not about your name on the jersey.
It’s about building a legacy that outlasts you.

Final Whistle

When I first started getting serious about Ethereum, DAOs, and onchain communities, I thought I was pivoting into something completely different from my past life.

But the truth is, I’m not doing anything wildly new.

I’m still:

• Reading the room

• Building trust

• Empowering people

• Adapting fast

• Betting on the long game

The surface looks different, less locker rooms, more Discord servers. Less skates, more smart contracts.
But the mission?
Still exactly the same.

Web3 isn’t about chasing the next hype cycle.
It’s about coaching a brand new generation. One that’s ready to build ownership, trust, and community from the ground up.

And I couldn’t be more excited to be back behind the bench again.

But in the world of Web3, that old model feels stale.
We’re entering a new era where loyalty is based on what you actually do, not just what account you signed up with.

And at the center of this shift are two powerful ideas: POAPs (Proof of Attendance Protocols) and onchain identity.

Here’s how they could completely change how loyalty works. For brands, communities, and everyone in between.

1. Loyalty Based on Actions, Not Just Accounts

Today’s loyalty programs barely scratch the surface. You rack up points for purchases, maybe a birthday bonus if you’re lucky. But it’s surface-level stuff.
There’s no real proof of who you are as a supporter.

With POAPs and onchain identity, loyalty becomes a living history of your actions:

• You attended that live event? Here’s your proof.

• You voted on key governance proposals? It’s recorded.

• You completed a community quest, mentored a newcomer, or beta-tested a product? It’s there, too.

Every interaction becomes a piece of your onchain "resume", building a profile that shows not just that you exist, but that you showed up, contributed, and cared.

And here’s the kicker:
Because it’s onchain, it’s verifiable and transparent.
No more faking loyalty with a few swipes of a rewards card. Your loyalty lives in the open, and it’s earned.

2. Rewards Get Way Smarter

Once loyalty is tied to real actions, rewards can get way, way smarter.

Instead of the same generic points-for-purchases model, brands and communities can recognize:

• Depth of engagement (like repeated participation)

• Breadth of contributions (supporting across different areas)

• Early adoption (being there before it was cool)

Real examples:

• Attend three events and vote on two governance proposals? You unlock exclusive merch no one else can buy.

• Show up early to a project’s first hackathon and stick around to help build? You get airdropped VIP access forever.

Rewards become personal, meaningful, and they create a deeper emotional connection.
It’s no longer just "buy and get points." It’s "participate, contribute, and build history, and get rewarded because of it."

3. Interoperable Loyalty Across the Ecosystem

Right now, loyalty programs are isolated silos.
Starbucks rewards don't help you get discounts at your favorite clothing store. Your airline miles can’t get you into a music festival.

Onchain identity blows up the silos.

Because your loyalty history is public and verifiable across the blockchain, it’s portable.

Imagine:

• A POAP from a gaming conference unlocking discounts inside a Web3 gaming marketplace.

• Your record of attending Ethereum hackathons giving you early access to dev tools anywhere.

• A history of collecting digital art across platforms getting you into a curated NFT gallery show.

Loyalty becomes a passport, not a cage.
Where you’ve been and what you’ve done opens doors all over the ecosystem.

4. Deeper, More Authentic Communities

Shared experiences are powerful. They build trust faster than anything else.

With onchain loyalty:

• Communities can form around provable shared experiences.

• Holding specific POAPs becomes a ticket to private chats, IRL meetups, governance opportunities, and collaborations.

You’re no longer just a fan. You’re a participant. A builder. A part of the story.

It’s a whole different vibe when you know the person next to you:

• Also attended the launch party

• Also voted on the early roadmap

• Also stuck around during the tough times

Communities built this way are stickier and stronger. Because they’re based on doing together, not just liking the same memes.

5. Retroactive Rewards: Rewarding the Real Ones

One of my favorite parts of this whole shift is the idea of retroactive rewards.

In Web2, it was always, "You had to be there at the exact right time, or you missed out."

In Web3, loyalty records are permanent.
A project can look back, scan your POAPs, and realize:

"You were here supporting us before anyone even cared."

And they can reward you, sometimes years later.

This flips the whole loyalty model:

• Instead of being lucky or perfectly timed, you get rewarded for genuine, lasting commitment.

• It encourages people to stick around for the long haul, not just chase short-term hype.

Imagine what that does for community health, for project growth, for trust.

Simple Hockey Analogy

Right now, loyalty is like wearing a jersey.
Anyone can buy a jersey and claim they're a diehard fan.

With POAPs and onchain identity, loyalty becomes your career stat sheet.

It shows:

• How many games you went to

• What teams you played for

• What milestones you hit along the way

You don’t have to tell people you’re loyal. You can prove it.

And in a world flooded with noise, proof is powerful.

Final Thought: Loyalty Is About to Get Real

POAPs and onchain identity aren’t just gimmicks. They’re building blocks for a more honest, rewarding future.

A future where loyalty isn’t bought.
It’s earned.
It’s lived.
And it matters in ways that ripple across communities, brands, and individual lives.

I can’t wait to see (and help build) where this goes next.

Why I’m Drawn to It:
Lens Protocol isn’t just another social app, it’s reimagining what social platforms can look like when creators actually own their identities, audiences, and data. That’s a game-changer. As someone who values human connection and believes that storytelling will be one of the most powerful use cases of Web3, I see Lens as laying the groundwork for a more transparent, creator-aligned internet.

How I’d Contribute:
I’d help onboard creators from traditional platforms, demystify the tech through accessible educational content, and support ecosystem partners in building tools that enhance user experience. I can translate the vision into real-world use cases that resonate beyond the Web3 bubble.

2. Gitcoin – Funding What Matters Most

Why I’m Drawn to It:
Gitcoin is the heart of Ethereum’s public goods mission, it’s where coordination meets impact. As a former coach, I’ve spent years building team-first cultures where everyone plays for something bigger. Gitcoin’s model of community-led funding feels like a natural extension of that ethos, especially with Quadratic Funding and builder grants driving real outcomes.

How I’d Contribute:
I’d be excited to help manage grant programs, design contributor journeys, or build relationships with teams solving real problems. Whether it's operational execution or narrative design, I’d bring clarity, consistency, and commitment to helping builders grow with long-term support.

3. Farcaster – A Protocol-First Approach to Social Media

Why I’m Drawn to It:
Farcaster stands out by focusing on building resilient infrastructure for communication, not just another app. The commitment to permissionless innovation, client diversity, and user-owned identity shows a long-term vision for decentralized interaction that’s bigger than any single platform.

How I’d Contribute:
I’d build bridges between users and devs. turning feedback into actionable insights, creating content that helps users understand how Farcaster differs from Web2 social, and amplifying ecosystem builders experimenting on the protocol. I’m all about helping new users feel like they belong from day one.

4. Zora – Empowering Creators Through NFTs

Why I’m Drawn to It:
Zora is shaping culture, not just tech. It’s not about hype drops, it’s about sustainable creator ownership, open protocols, and building new ways for artists to earn without middlemen. That’s deeply compelling to someone who’s grown up around both the arts and team sports. Spaces where community and recognition matter deeply.

How I’d Contribute:
I’d help artists and communities understand the mechanics of minting and sharing onchain. I could lead onboarding workshops, write how-to guides that blend culture and utility, and help launch campaigns that connect creators with meaningful moments, not just markets.

5. LayerZero – The Backbone of Cross-Chain Web3

Why I’m Drawn to It:
LayerZero is building the connective tissue of Web3. The thing that lets apps and assets move seamlessly across chains. That modular, “interop by design” approach reminds me of coaching systems that enable players to adapt and collaborate across any situation. It’s where infrastructure meets opportunity.

How I’d Contribute:
I’d work on content strategy that explains complex concepts like OFTs and DVNs in a way that even newcomers can grasp. Whether it’s working with partner teams, running cross-chain campaigns, or translating product updates into clear language, I’d be all in on helping people understand why LayerZero unlocks the next chapter of Web3.

6. Base by Coinbase – Scaling Ethereum to the Masses

Why I’m Drawn to It:
Base is where accessibility meets legitimacy. As an Ethereum L2 with a mission to onboard the next billion users, it feels like a place where I could blend my coaching background with my growing knowledge of Ethereum. It’s focused, clean, and actively helping people ship real apps. not just ideas.

How I’d Contribute:
Running workshops for new developers, supporting hackathons, writing explainers that simplify Layer 2 concepts, or contributing to community growth strategies. I want to make Web3 feel less intimidating and more empowering. Just like I did for new players learning to skate or compete..

Final Word: Why These Projects Matter

Each of these protocols plays a different role in the Web3 ecosystem. But they share a common thread: community-first, open-source values and a belief in the power of ownership. Whether it’s social identity, public goods, or creative expression, these projects are creating new growth loops rooted in trust, composability, and transparency.

And that’s exactly the kind of team I want to be on.

Here’s what I’m seeing as the core differences between Web2 and Web3 growth strategies, especially in the EVM space. If you’re transitioning into this world, these are the new fundamentals.

1. Web2 Is About Acquisition. Web3 Is About Activation.

In Web2, growth means: get users. Run paid ads, optimize your funnel, convert traffic.

In Web3, growth starts after the user shows up. The goal isn’t just usage, it’s participation. Communities grow because users become owners, contributors, and evangelists.

Think of an airdrop. You’re not just rewarding people, you’re inviting them into the team huddle.

2. Web2 Products Are Closed. Web3 Protocols Are Composable.

Web2 growth is built in silos. Companies protect their code, data, and APIs. The moat is ownership.

Web3 flips that. Growth comes from being open. If someone builds on top of your smart contracts, it’s a win. Every new integration extends your reach without marketing spend.

It’s the difference between building a wall and opening the barn doors.

3. Web2 Buys Growth. Web3 Incentivizes It.

Web2 startups raise VC money, then spend it to acquire users, ads, partnerships, influencer campaigns.

Web3 protocols bootstrap growth with tokens. Whether it’s liquidity mining, contributor grants, or staking rewards, you’re aligning incentives from day one.

But that’s a double-edged sword. Done right, it creates loyalty. Done wrong, you just attract mercenaries looking for a quick score.

4. Web2 Teams Drive Growth. Web3 Communities Do.

Web2 growth is about the people you hire, market3. Web2 Buys Growth.

Web3 Incentivizes It. developers, designers, ops.

Web3 growth comes from the people you empower. Translators, meme-makers, indie devs, DAO contributors. The crowd becomes your bench.

You don’t need a massive team if your protocol is designed to let others run the plays.

5. Web2 Optimizes for DAUs. Web3 Optimizes for Participation.

In Web2, metrics are all about the funnel. Daily active users, LTV, conversion rates.

Web3 is about how deep the user engages. How much is staked, how many proposals they’ve voted on, how much ETH flows through your contracts.

It’s less about how many people show up. It’s about who’s willing to lace 'em up and skate.

6. Web2 Rolls Out City by City. Web3 Goes Global Day One.

In Web2, you might start local. Launch a product in one city, then scale up.

Web3? You drop a smart contract, and anyone in the world can use it. Most growth happens in Discord, Telegram, and Twitter. Localization is done by the community.

It’s like launching a team and instantly having fans in 30 countries.

7. Web2 Grows Through Data. Web3 Grows Through Trust.

Web2 is about collecting user data and optimizing the experience behind closed doors.

Web3 is open by default. Source code is public. Wallets are secure. Growth comes from transparency, not clever targeting.

If you break trust in Web3, the community notices. Fast.

Wrapping It Up (With a Hockey Metaphor, Of Course)

Web2 plays like a structured powerplay: top-down, choreographed, focused on precision.

Web3 plays like pond hockey. Open ice, everyone improvising, and magic happens when the team vibes together. There's no coach yelling plays from the bench. Just players reading the ice, trusting each other, and moving fast.

In both worlds, the goal is the same: get the puck in the net. But in Web3, the crowd gets to skate too.

Let’s break down the major Web3 growth loops I’m seeing play out across the Ethereum Virtual Machine (EVM) ecosystem, and why they matter as we build toward a more decentralized future.

1. Incentives → Onchain Activity → Revenue → More Incentives

It starts with protocols offering incentives, airdrops, points, yield, you name it. This attracts users who bring liquidity, generate volume, and create transaction fees. That activity translates to protocol revenue, which then fuels more incentives.

Example protocols:

• Friend.tech- turned social activity into trading volume

• Blast - incentives tied to onchain TVL and usage

• LayerZero - multi-chain points system rewarding real usage

Why it works: Early user behavior is gamified, but the underlying activity helps bootstrap liquidity and adoption.

The challenge: If incentives dry up and the product doesn’t provide real value, the loop breaks. We're seeing smarter protocols tie rewards to useful actions like contract deployments, long-term staking, and meaningful governance participation.

2. Developer Growth → App Deployment → User Demand → Tooling Upgrades

This loop is all about infrastructure investing in builders. L2s like Base, Arbitrum, and Optimism are pouring resources into grant programs, and simplified onboarding for devs. More devs means more apps, which drives user demand, leading to more feedback and better dev tools.

It’s a loop:

• Better tooling → More devs

• More devs → More dApps

• More dApps → More users

• More users → More demand for tooling

Why it works: Ethereum’s modularity makes it easy for developers to innovate, and each new app brings its own gravity.

3. Community Ownership → Governance → Product Improvements → Retention

This loop leans into the ethos of Web3: users as owners.

When users have tokens and a voice in governance, they’re more likely to stay, contribute, and improve the product. As the product gets better, more users stick around, strengthening the community and the value of governance tokens.

Examples:

• Uniswap – protocol changes led by community proposals

• ENS – DAO steers the direction of a critical naming layer

• Gitcoin – public goods funding refined through governance

Why it works: It turns passive users into active participants, giving people a reason to care beyond speculation.

4. Composability & Interop → More Use Cases → More Adoption → More Composability

Ethereum’s modular stack is starting to look like a real interoperable engine. L2s are connecting to restaking protocols (EigenLayer), modular DA layers (Celestia), and cross-chain bridges (LayerZero). This creates a “plug and play” world where apps can mix and match tools to serve users.

The loop:

• More modular tools → More powerful apps

• More apps → More users

• More users → More incentive to innovate at the infra layer

Why it works: Builders don’t have to reinvent the wheel. They can build faster, safer, and more flexibly.

5. Identity → Activity → Reputation → Opportunity

We’re entering a new loop around onchain identity and reputation. As users create, transact, and interact, they leave behind a trail of proof, mints, social posts, governance votes, and more. This data builds reputation, which in turn unlocks more opportunities. Access to jobs, drops, collabs, and higher trust.

Protocols leaning into this:

• Farcaster – social graph onchain

• Lens Protocol – portable social identity

• Zora – creators earn reputation through minting and curation

Why it works: In a decentralized world, your wallet is your resume. The more you do onchain, the more you earn trust and access.

Final Thought: Sustainable Loops > Flashy Campaigns

What excites me most is watching the shift from hype-based growth to loop-based ecosystems. These loops, when done right, aren’t about short-term traction, They're about building systems that feed back into themselves and compound over time.

Ethereum’s EVM ecosystem is turning into a living organism, with incentives, builders, and users all playing interconnected roles.

And if you’re building in this space, or learning, these are the loops worth watching.

If you would like a even simpler version of this, DM me on X sam orth - I enjoy using real life analogies making Web3 more approachable.

This post is a breakdown of exactly what happens when you send a transaction on Ethereum. From your wallet, all the way to the blockchain. Whether you're new to the space or just want to understand it more clearly, here's how I see it.

Step 1: You Create and Sign the Transaction

Everything starts locally, right in your wallet. MetaMask, Coinbase Wallet, or something built into a dApp. You're basically saying:

• “I want to send X ETH (or tokens)”

• “To this wallet or contract”

• “And I’ll pay this much gas to get it processed”

Behind the scenes, your wallet fills in a few more details:

• To address (recipient or smart contract)

• Value (how much ETH you’re sending)

• Data (for contract interactions like swaps or mints)

• Gas limit + priority fees

• Nonce (your wallet’s unique transaction count)

Then you sign it with your private key. That signature says, “I’m the one sending this, and I’ve got the authority.”

Step 2: The Transaction Gets Broadcast

Once it’s signed, the transaction gets fired off to the Ethereum network. This is a peer-to-peer network, so it spreads out to thousands of nodes.

Each node has something called a mempool (short for Memory Pool), which is like a public waiting room for pending transactions. Your transaction hangs out there until a validator (formerly known as a miner) picks it up.

Step 3: It Spreads Across the Network (Propagation)

At this point, your transaction is basically getting passed around the network. Other nodes see it, verify it’s valid (you signed it, you have the funds, etc.), and add it to their own mempool lists.

This whole process takes seconds—but it’s one of the reasons Ethereum is so resilient. There’s no single server in charge; it’s just code running on thousands of independent nodes.

Step 4: A Validator Adds It to a Block

Now the magic happens.

Ethereum runs on Proof of Stake. A validator is selected to create the next block. They scan the mempool and usually grab the transactions with the highest fees first (because that’s how they get paid).

If your gas fee is reasonable and the block isn’t too full, your transaction gets included. It’s now officially part of a new block on Ethereum.

Step 5: The EVM Executes the Transaction

Once your transaction is inside a block, the Ethereum Virtual Machine (EVM) takes over.

The EVM is like Ethereum’s brain—it runs the logic and checks the math on every transaction:

• Deducts gas up front (Gas price depends how much the transaction is worth, and/or fee’s differ on how much traffic is going through the network is at that moment)

• Runs any smart contract code

• Moves ETH or tokens

• Updates balances, contract storage, etc.

If everything checks out, the transaction goes through. If it runs out of gas or hits an error (like trying to swap a token that doesn’t exist), it fails. But you still pay the gas.

Step 6: Ethereum’s State Updates

Assuming the transaction succeeds:

• ETH or tokens move

• Smart contracts update storage (maybe your NFT gets minted)

• Events are logged (this is how explorers like Etherscan show what happened)

• Gas is split between the validator and burned

This is when it becomes “real.” You can check your wallet and see the updated balance or NFT. It’s now part of Ethereum’s global state.

Step 7: Finality (It’s Locked In)

Even after it hits a block, Ethereum waits a few more blocks to consider the transaction finalized. Meaning it’s basically irreversible.

On Ethereum mainnet, that usually means:

• 1 confirmation: it’s confirmed

• 12+ confirmations: it’s final

Finality gives everyone (users, apps, bridges, etc.) confidence that your transaction won’t get rolled back due to a reorg.

Why It Matters,

Understanding this flow helped me move from just using Ethereum to thinking like a builder. Every transaction is more than a button click. It’s a handshake with the network, powered by cryptography, math, and thousands of independent nodes working together.

And in a world moving toward modular chains, rollups, and new Layer 2s, this flow stays foundational. The difference? Sometimes parts of it get outsourced or compressed (like calldata off-chain or finality via proofs), but the core logic stays the same. Let me know if you want me to break down how this changes on a rollup or Layer 2 next. The way they compress and batch these steps is super interesting. And totally reshaping Ethereum’s future.

In this article, I’m breaking down three Ethereum tools that save serious time, both for end users and builders. Whether you’re exploring your first smart contract or managing a treasury, these tools are the hidden MVPs that keep things moving.

1. Etherscan- The Public Ledger That Works Like Google

What it is-
Etherscan is a block explorer. It reads Ethereum’s public blockchain data and presents it in a user-friendly, searchable format. It doesn’t write to the chain, it just indexes it.

How it works-

• Every time a transaction is broadcast to Ethereum, it's mined and recorded in a block. Etherscan runs a full Ethereum node to capture that data in real-time.

• Then, it decodes that transaction- value sent, contract interactions, event logs, gas used, success/failure status.

• It maps smart contract bytecode to verified source code (if provided via Etherscan’s verification tool).

• It categorizes token transfers using standards, making token balances and histories viewable.

Why it saves time-

• You don’t need to run a full node or parse logs yourself.

• You get immediate insight into why a transaction failed (bad nonce, out of gas, revert reason).

• You can view contract interactions in real-time, down to the method and parameters called.

Lets say, You're minting an NFT and it fails. Etherscan shows the exact revert message from the contract. No guessing.

Saves time by removing doubt, digging, and guesswork.

Saves brainpower by making data accessible without needing dev tools.

2. WalletConnect- One Sign-In to Rule Them All

What it is-
WalletConnect is an open protocol that lets wallets and dApps communicate securely using end-to-end encrypted messaging.

How it works-

• WalletConnect doesn’t transmit your private keys or sign transactions itself. It establishes a session between your wallet and the dApp using a bridge server.

• When a dApp wants to connect, it generates a unique URI (usually displayed as a QR code).

• Your wallet scans this code and establishes a WebSocket-based session.

• Any transaction requests are sent to your wallet for signing, and you approve or reject them directly on-device.

Why it saves time-

• No Chrome extensions or plugin installs required. Just scan, and go.

• Works across devices- Scan a QR from desktop, approve from your phone.

• Replaces the need for username/password login flows. Your wallet is your identity.

Saves time by skipping account creation and onboarding friction.

Saves your data by replacing emails and passwords with cryptography.

3. Gnosis Safe: Team Wallets Done Right

What it is-
Gnosis Safe is a smart contract-based wallet that allows multi-signature governance over Ethereum assets. It’s used by DAOs, teams, and treasuries to prevent single points of failure.

How it works-

• A Safe is deployed as a smart contract wallet on Ethereum.

• You configure signers and a threshold (2 of 3 required to execute).

• When someone proposes a transaction, it gets queued until enough signers approve.

• Once the threshold is met, the transaction is executed on-chain.

Why it saves time and risk-

• No more chasing down approvals manually, it’s all baked into the contract logic.

• Every action (proposal, approval, execution) is logged and verifiable.

• Role-based permissions and modules let you automate recurring actions, manage access, and integrate with other apps.

Here’s an example,
Your community wants to issue a grant. One member proposes a transaction, two others sign off, and it's transparently executed with zero backroom risk.

Saves time by removing bottlenecks and errors.

Saves your project from single points of failure.

“Tools are just decoration, if you don’t use them”

I was once told by an old journeyman buliding houses, “All these tools are just expensive decorations if we don’t use em. Work smarter son, not harder.”

The same applies on-chain.

I’ve spent my career building team culture. First on the ice, now on-chain. And what I’ve learned is this. The tools you use shape the way you work.

These tools aren’t just conveniences.. they’re infrastructure. They represent the kind of UX that Web3 needs more of, powerful backend complexity hidden behind clean frontends that just work.

• Etherscan eliminates the need to trust. You verify.

• WalletConnect turns your wallet into a passport.

• Gnosis Safe enforces shared control without centralizing power.

If you're building in Ethereum. Whether you're running a DAO, managing capital, or just learning how blockchains tick. Learn these tools inside and out. They’re not just saving you time, but protecting your reputation, your resources, and your roadmap.

Final Thoughts

The Ethereum space can feel like a maze at first. Full of jargon, wallets, bridges, and unfamiliar buttons. But tools like Etherscan, WalletConnect, and Gnosis Safe act like your compass, map, and GPS all rolled into one. They're not just for developers or crypto veterans. They’re for anyone who wants to operate smarter, faster, and more confidently in Web3.

If you're just getting started, don't wait until you feel “ready.” Explore these tools today, click around, and learn as you go. The people building the future of the internet aren't sitting on the sidelines. They're experimenting, asking questions, and using the tools that make it all work.

Trust me, its worth it.

If I can make the transition, you can too.

As someone transitioning from coaching to Ethereum biz dev, I’ve been thinking a lot about user adoption, and how Layer 2s can cross the canyon from niche power-users to everyday folks.

So let’s break it down.

Challenges

1. Abstracting Complexity

Most users don’t know, or care what a rollup is. They just want fast, cheap transactions that work. But onboarding to a Layer 2 today can feel like a maze.

Download a wallet - Buy ETH on mainnet - Bridge to L2 - Wait - Cross your fingers.

That’s a lot to ask from someone just trying to send money or mint an NFT.

It’s like asking a hockey player to lace their skates, sharpen their blades, and flood the ice, and then be ready on time We need to simplify the process so the tech fades into the background—and users can just play the game.

2. Wallet confusion

Do I need MetaMask? Argent? A special L2-native wallet? Can I just use Coinbase?

Most wallets weren’t built with L2 UX in mind, which creates confusion and trust issues. Imagine if every time you entered a new rink, you had to re-learn the rules of the game.

3. Bridging Trust Gaps

Bridges are still the Wild West. Users hear “you’re moving assets across chains” and think, “I’m going to get rugged.” Until bridges feel as safe as walking through airport security with your carry-on, onboarding will stay stuck.

4. Lack of Clear Benefits

Web3 loves to preach about scaling, gas fees, and TPS. But most people just want to mint an NFT or send money. If they can do that on mainnet or another chain, why should they bother with an L2?

Ideas and Plays to run

1. Native On-Ramps to L2

Imagine buying ETH directly onto an L2 from your bank or card. No bridge, no mainnet. Just like Venmo, but decentralized. Teams like Connext and Socketare working on this. Biz dev roles here matter. Who you integrate with, what fiat partners you bring in, etc.

2. UX-Led Wallet Design

This is where design meets product meets strategy. A wallet that defaults to L2 but still lets users go cross-chain when needed. Think- one tap to go from scroll to Base. Business teams can drive partnerships to unify this across ecosystems.

3. Education-as-Onboarding

People don’t want a stagnant YouTube video you find yourself reading something else while watching. They want tooltips, walkthroughs, and real-time support. My dear friend Patrick Skinner is one of the BEST at making these. https://www.youtube.com/@PSkinnerTech https://blog.patrickskinner.tech/ https://www.youtube.com/@ar_io_network

The opportunity? Collaborate with creators, DAOs, or platforms that already have attention.

4. Social and Cultural Momentum

When L2s become the cool place to hang out, users will follow. Memes, brand identity, and community vibes play a role. Strategic BD can help seed these ecosystems with builders, creators, and collabs.

Why this is Important

Ethereum won’t scale through theory. It’ll scale through people using it. And right now, we’re still in the early innings when it comes to mainstream onboarding. If you’re like me, someone who’s lived and breathed team strategy and now sees the next era of the internet forming. This is a chance to contribute.

The ice is set. The lights are on. Now let’s help people find the door and get them into the game

And that’s where business development steps in.

What is Business Development in a Web3 Protocol?

In Web2, business development might mean partnerships, customer acquisition, or enterprise sales. In Web3, it’s all of that, but layered with the unique dynamics of decentralized ecosystems. Here’s what it actually looks like:

• Partnership Strategy- Identifying and onboarding integrations that expand protocol usage—wallets, Layer 2s, dApps, bridges, or tooling platforms.

• Community & Ecosystem Growth- Coordinating developer relations, DAO involvement, or ambassador programs to ensure organic adoption.

• Market Research & Positioning- Understanding where your protocol fits in the broader ecosystem, and how to differentiate it amid fierce competition.

• Token Incentives & Governance- Working with core contributors or DAOs to shape incentive programs, bootstrap liquidity, or align incentives between builders and users.

• Metrics That Matter- Tracking TVL, active wallets, protocol usage, and ecosystem engagement to inform strategic decisions.

Business development is part growth strategist, part ecosystem architect, and a bridge between the protocol’s tech stack and its real-world value.

Why This Role Aligns with My Journey

I've spent my entire career focused on high-performance systems and communication. As a hockey coach, my job was to analyze the game, translate strategy, and get every moving piece to function together. That’s exactly what business development in Web3 demands.

Here’s what I bring-

Systems Thinking- Whether designing plays or coordinating Layer 2 partnerships, it’s about reading the full ice, seeing the gaps and aligning each move with the bigger goal.

Strategic Communication- My background in leadership and writing helps me translate complex concepts to different audiences. Whether it’s developers, DAOs, or partner teams.

Growth Mindset- I’m leveling up fast. Studying the EVM, understanding rollups, writing deep-dive articles, and using every learning as momentum toward real-world contribution.

Execution Under Pressure- In both sports and tech, the clock is always ticking. I know how to operate in fast-paced environments where trust, clarity, and timely execution make the difference.

Where I Want to Go From Here

I’m not just trying to break into Web3. I’m aiming to be part of the infrastructure that makes the next generation of the internet possible. I want to be part of a protocol team that’s solving real problems- scalability, UX, privacy, and financial inclusion.

Business development lets me connect the dots between technical teams, users, and long-term impact. It’s the role where my skills, mindset, and ambition all intersect.

Final Thoughts

Just like in hockey, the game isn't always won with flashy plays. It’s won with coordination, trust, and systems that work under pressure. That’s the kind of team I want to build in Web3. And that’s why business development is where I may be skating next.

Let’s break this down simply. No jargon, just vibes.

Why We Even Need Layer 2s

Ethereum is like the main NHL arena-

• It’s where the official games happen.

• It’s secure, decentralized, and the gold standard.

But there’s only so much ice time. Every transaction clogs the rink. Gas fees spike. Everything slows down.

Layer 2s like Optimism and Arbitrum are elite practice facilities that handle the games faster, cheaper, and then submit the final footage back to the league (Ethereum) for validation. You get speed and savings without compromising security.

What They Have in Common

Both Optimism and Arbitrum are what’s called Optimistic Rollups. Translation?

They assume transactions are good unless someone challenges them. Like a coach’s challenge in hockey or football. Instead of reviewing every play in slow motion, they keep things moving and only stop if something looks off.

• the reduce gas fees

• they increase speed

• they settle back in Ethereum for security

• they’re built to scale Web3

Optimism: The Team Player

This is the system player that builds trust through consistency.

• Simple and developer-friendly- Easy to build on because it sticks closely to Ethereum’s base rules.

• Governed by the Optimism Collective- A structure that rewards public goods. Think of it like a league that funds the development of better rinks and training gear for everyone.

• Base by Coinbase- Built on Optimism’s OP Stack, which is onboarding millions of new users.

Optimism feels like- That disciplined, structured team that makes everyone around them better.

Arbitrum: The Flashy Speedster

This is the skater who’s always inventing new plays on the fly.

• Tech-Forward- Offers more advanced features like Arbitrum Stylus (lets devs code in more languages).

• High Adoption- It leads in Total Value Locked (TVL) aka the most players on the ice.

• Always Evolving- Rapid innovation with upgrades and feature rollouts.

Arbitrum feels like- Fast, innovative, and always testing the limits.

So Who Wins?

That’s like asking if you’d rather have a star scorer or a reliable team player. They’re both essential to winning.

So honestly.. they both do.

Optimism and Arbitrum aren’t enemies. They’re TEAMMATES in scaling Ethereum. It’s not about which is better overall, it’s about which one fits your play style. And how they compliment each other.

Final Whistle

The best teams weren’t made of just superstars or just grinders. You needed both.

• Ethereum Layer 1 = The League Office

• Optimism = The Structured Team-first player

• Arbitrum = The Creative Speedster

Together, they’re making Ethereum scalable, affordable, and ready for mass adoption.

If you’re a builder or just learning the game, this is the layer where things get exciting. It’s time to lace up. The puck’s already dropped.

Not the Ethereum bench. My old coaching bench. We’d just finished a brutal first period, and my team was frustrated. Sloppy passes, missed chances, and one too many penalties. The guys were fired up, but the problem wasn’t effort. It was structure. We were trying to win the game with only speed and flash. Trying to do everything through the top line. Ignoring the grinding, foundational play that happens behind the scenes.

That lesson has come back to me this week as I’ve continued diving deeper into Ethereum.

Because the same thing is happening here.

Everyone’s talking about NFTs, DAOs, and the next big crypto app. But the real game is being won by the infrastructure no one sees at first glance. The gritty, often invisible, Layer 2 networks that are doing the heavy lifting.

And without them? The Ethereum ecosystem would buckle under its own success.

Whats the problem with Ethereum today?

Ethereum’s base layer (Layer 1) is secure, decentralized, and programmable. It’s the foundation of Web3. But it’s also congested and expensive. With every transaction recorded on-chain, gas fees spike during peak demand, and throughput is limited to about 15 transactions per second.

It’s like having ONE NHL-caliber rink and trying to host the entire season. Every game, every practice, every event for EVERY TEAM. On just 1 playing surface. Its just not built to scale.

Enter Layer 2- The scaling system

Layer 2 solutions solve this by offloading transactions from the main chain, bundling them together, and posting a single proof back to Ethereum.

They don’t replace Layer 1, they build on it.

There are two dominant types of Layer 2s:

• Optimistic Rollups- Assume transactions are valid unless someone challenges them during a dispute window.

• zk-Rollups- Use zero-knowledge proofs to cryptographically prove that a batch of transactions is valid. Without revealing personal information

Both achieve the same goal- more productive, lower gas fees, and faster UX. Without compromising Ethereum’s security or decentralization.

Why It’s the Backbone (Not Just a Feature)

Without Layer 2, Ethereum can’t support global-scale apps.

Think about identity, gaming, DeFi (Decentralized Finance), and social platforms. These don’t need one-off transactions. They need millions. Reliably and cheaply. A single NFT mint or swap on Layer 1 might cost $20+ in gas. On Layer 2? It’s often pennies.

The backbone of Ethereum isn’t the flashy stuff. It’s the architecture that makes mass adoption viable. It’s the system play that lets the stars do their job.

Security and Trust

Here’s the important part. Layer 2s inherit Ethereum’s security. They don’t compromise decentralization. Every transaction on a Layer 2 settles back to Ethereum eventually. Like submitting the official game tape to the league office.

You get speed and trust. It's not a tradeoff anymore

What This Means for Builders (and people Like Me)

If you’re developing in Web3, or just starting to explore. It’s time to think beyond Layer 1.

• Learn to deploy on a Layer 2.

• Understand how rollups handle data availability and fraud proofs.

• Pay attention to modular scaling- How Layer 2s fit into a broader vision of execution, storage, and consensus layers.

Skate to Where the Puck Is Going

I tell my players, don’t just follow the puck. Read the ice. See space with your eyes, TAKE it with your legs.

Same here. Ethereum Layer 1 isn’t going away. It’s the foundation. But Layer 2 is where the game is evolving. It’s where the speed, the flexibility, the mass adaptation happens.

If you want to build in Web3, Layer 2 is no longer optional.
It’s the system you need to trust.
It’s the infrastructure that lets your plays work.

It’s time to skate with the structure.
It’s time to build where the game’s headed.

Seven days ago, I was sitting in my home office, a coffee going cold on the desk, and a blinking cursor daring me to explain “zk-Rollups” in a way that made sense to anyone outside the dev trenches. I’d just stepped away from coaching, a world where I knew the rules, the plays, the locker room energy. Now I was trading whiteboards and whistles for smart contracts and scalability debates.

I didn’t have it all figured out. But I had a feeling. A sense that something big was happening in Web3, and I wanted to not just watch from the sidelines, but step into the playing field.

Here’s what I’ve learned from seven straight days of writing, reading, and wrestling with Ethereum. And what it taught me not just about the tech, but about trust, voice, and showing up in this new digital era.

Analogies Are Bridges, Not Crutches

When I started this blog, I leaned into what I knew, hockey. I used blue lines and strategy notebooks to explain cryptographic proofs. I made jokes about goalies and data breaches. And you know what? It worked. for me… and some people.

But by Day 3, I realized something. Analogies are helpful only when they serve the reader. They’re a bridge, not the destination.

Story moment-
One reader messaged me saying, “I dont care for the sport of hockey, but the way you explained zk-Rollups using a team’s playbook was super easy to understand and relate to” That was the moment I knew I wasn’t just writing about Ethereum. I was translating it.

Lesson:
The challenge isn’t explaining Ethereum. It’s making people feel it. If a metaphor helps someone cross the bridge into this new world, then I’m building more than a blog. I’m building access.

Ethereum Is Rebuilding Trust (One Block at a Time)

The more I learned about Ethereum, the more I saw it wasn’t just about gas fees and cryptographic innovation. It was about trust. Not the kind you hand over to a company and hope they don’t mess it up. But trust built on math, code, and public accountability.

Writing about zk-Rollups opened my eyes to something powerful. Your private information doesnt have to live within the app. With zero-knowledge cryptography, your identity can be proven without being exposed. Even if an app is hacked, your data isn’t sitting there waiting to be stolen.

That’s a game-change. Not just for developers, but for everyday users.

Ethereum isn’t just software. It’s a shift in how we treat people’s rights. Privacy isn’t a “feature” anymore. It’s becoming a default.

Consistency > Expertise

I’ll be honest. I didn’t feel qualified to write about this space. I’m not a developer. I’m not a VC. I’m a blue collar boy and coach who got curious about Ethereum.

But I wrote anyway. And after seven days, I’ve learned more than I expected. Not just about rollups and EVMs. But about myself.

Every blog post took me deeper. Into zk-proofs, sequencers, the future of DAOs. But it wasn’t the research that made the biggest impact. It was showing up. Writing through the confusion. Sharing ideas before they felt perfect.

And surprisingly, people responded to that more than if I had tried to be an expert from day one.

In Web3, curiosity compounds. You don’t need to be first or best. You just need to be here.

This Is Just the First Period

This week reminded me why I’m here. Not just to chase the next trend, but to help others see that this space is for them, too. For the 9-5’er. The dad. The person who grew up in the ‘90s and refuses to get with the times. Web3 doesn’t need more buzzwords. It needs people who can make it real.

Seven days in, and I know one thing- I’m not turning back.

If you’ve been following along, I appreciate that. If you are just coming across this, welcome. I’m building this blog not just as a place to explore Ethereum, but as a conversation space for people who care about trust, privacy, and ownership.