At some point in my life, for a couple of years, I dealt with a recurring medical condition that had me visiting different clinics and medical labs. Each time I walked into a new facility, I had to repeat the same story: my symptoms, my history, my previous treatments and possibly my health progress. None of the clinics had access to my past medical records, and worse still, I didn’t either.

That’s when it hit me: why should only one institution hold my health data? Why can’t I decide who can see and use my medical history? It was a painful loophole in the healthcare system and I knew it needed to be fixed, even though I had no idea how at the time.

Discovering Web3: The Missing Piece

Fast forward to my exposure to the Web3 ecosystem, something clicked. The concept of user-owned data and permissioned access felt like the perfect fit for the problem I had experienced. So when I got into the Stacks Ascent program, it was a no-brainer to pursue that idea.

I began building Mediverse, a decentralized health platform where users could control who accessed their medical records. I learned a lot, stumbled a bit, and gradually grew my skills with Clarity smart contracts. It was one of the most fulfilling early projects I’d ever worked on.

The Power of Feedback

During one of the Ascent coffee chats, I got inspired to ask for feedback on how to scale Mediverse. That decision changed everything.

The response I got was simple but insightful and powerful: “This kind of system would require government involvement for regulation and adoption. It’s not something a solo builder can fully enforce or control.”

They were right. And it taught me two things:

A problem may be valid and worth solving
You may not yet have the power to implement the solution at scale

That feedback didn’t discourage me; it clarified my perspective. I realized how important it is to speak up early, ask questions, and seek feedback from those with more experience. Inasmuch as I acquired a good amount of knowledge during the building process. It was nice that I hadn’t gone way deeper before I received the insight that I did.

Pivoting with Purpose: EventChain

Rather than stop building, I pivoted to another idea I’ve been equally passionate about: event ticketing.

As someone who attends Web3 events and conferences, I’ve always seen the need for a transparent, decentralized ticketing platform. That’s how EventChain was born.

With EventChain:

Organizers can create events on-chain
Users can buy verifiable, tamper-proof tickets
Tickets can be transferred or refunded
And soon, attendees can receive POAPs (Proof of Attendance Protocols)

Imagine collecting POAPs for every Stacks event you attend across the globe, like digital souvenirs or even airdrop eligibility. That’s where we’re headed.

What I've Built So Far

I’ve deployed the first smart contract for EventChain on Stacks testnet. Features include:

On-chain event creation
Verified ticket ownership
Secure transfers & refunds
Ownership tracking

I’ve also written a suite of simnet tests that cover key logic and edge cases, ensuring the system is robust.

Right now, I’m building out the frontend to connect users directly to the dApp. Once it’s ready, I’ll be inviting the community to try it out and offer feedback.

The roadmap ahead includes:

POAP integration
Analytics for organizers
Feature requests from user feedback

Final Thoughts: Build Loud, Build Early

This entire experience has been eye-opening. It’s shown me the value of building in public, asking for feedback (even when it feels uncomfortable), and embracing pivots when they make sense.

The best ideas aren’t always the first ones, but every idea teaches you something that carries forward.

Thanks to the Stacks community and the Ascent team for the support and space to grow. I hope you take something valuable from my story, and if you’re building too, don’t be afraid to ask questions and pivot with purpose.

Stay tuned. EventChain is just getting started!!!!!

From Health Data to Ticketing: My Journey Building on Stacks

Table of contents