Featured Start here

Hello and welcome to my blog. Don't mind the mess here while the webpage is still in development.

There’s a very specific feeling you get when you stumble into something early.

It’s quiet, focused energy. People asking better questions. People building because they want to see what happens and following personal interests.

That’s more or less how I’ve been feeling lately spending time around an exciting new leadership initiative emerging in the Monad ecosystem.

Early days (the good kind)​

I’ve been lucky in my career to work across a few different ecosystems, but every once in a while you run into a group of people that just stand out.

All stars eager to both learn and share their skills. People who you feel energized by and want to keep hanging around.

That matters a lot more than people think.

Because infrastructure, at the end of the day, is not just code. It’s coordination. It’s trust. It’s a shared understanding that you’re building something that should actually last.

Lately, I’ve been spending a lot of time thinking about what that looks like in practice.

Not just running a validator. Not just deploying infra. But building something that scales with people, not just hardware.

A different way to think about validators​

Most validator conversations start and end with:

• hardware specs
• uptime
• commission

Which is fine. Those things matter.

But they’re not the full picture.

What’s been more interesting to me is thinking about:

• how stake gets distributed
• how new operators come online
• how you can grow a coordinated movement globally without fragmenting too early

There’s a version of this where everyone just spins up a node as fast as possible.

And there’s another version where you’re a bit more deliberate. Where you create a system that lets people earn their way in, without introducing unnecessary risk upfront.

That idea has been taking up a lot of my time recently.

Building with people, not just around them​

One of the things I’ve appreciated most lately is being around people who actually want to see you grow.

Not in a performative way. Not in a “we’ll help as long as it benefits us” way.

Just genuinely. They want to make you into a better version of yourself.

You get motivated to take bigger swings.
You are eager to share ideas earlier.
You’re less worried about being “right” and more focused on being useful.

And when you’re thinking about something as coordination-heavy as a validator network, that kind of environment compounds fast.

Because the hardest problems aren’t technical.

They’re:

• aligning incentives
• building trust across regions
• figuring out how to scale without breaking what made things work in the first place

What’s been on my mind​

I’ve been spending a lot of time thinking about:

• how to bootstrap stake in a way that’s sustainable
• how to involve different regions without forcing premature infrastructure decisions
• how to balance performance with decentralization over time

There’s a version of this that is very simple.

And there’s a version of this that turns into an over-engineered mess.

Trying to stay firmly in the first category.

Subtle signals​

There are a few things I’ve been working on that I’m excited about.

Nothing I want to fully spell out yet, but if you read between the lines:

• thinking a lot about how stake is organized
• how participation is tracked before infrastructure is required
• how incentives flow before ownership is fully handed off

The interesting part isn’t any one piece.

It’s how they fit together.

Why this feels different​

Every ecosystem says they care about decentralization.

Fewer actually think through what that means operationally.

What I’ve seen so far is people who are willing to sit in that complexity a bit longer.

To ask:

• what happens at 1 node
• what happens at 10
• what happens at 100

And to design for that path, not just the end state.

Closing thoughts​

Still early. Still a lot to figure out.

But it’s been refreshing to be around a group of people who are:

• curious
• collaborative
• and not immediately trying to optimize everything for short-term gain

That combination is rare.

And it usually leads to interesting things.

More soon.

I’m calling this year the year of optimizations.

Not in the productivity-hustle sense, and not as a rigid self-improvement overhaul. More like a series of small, deliberate experiments, one per month, aimed at improving different areas of my life and health.

The rules for the year of optimizations are simple:

• Try one focused change for a month
• Measure how well it actually goes
• If it works, it stays and if it doesn't, it goes