I’ve been onchain since Bitcoin was a curiosity you had to explain to people twice. Twenty-plus years in digital and information security before that — OSINT, defensive work, the unglamorous discipline of assuming everything can be broken and acting accordingly. I started building onchain in 2019 and never stopped. So when I say what I’m about to say, understand it comes from someone who has watched this space through more than one full cycle, from the inside, with skin in it the entire time.
I don’t speculate onchain. I build on it.
That sentence sits on my about page, and people read it as a slogan. It isn’t. It’s a description of how I spend my days, where my attention goes, and what I consider a life’s work worth having. It’s also, more quietly, a judgment — not of the people who speculate, but of what speculation actually produces when you stack up ten years of it and look at what’s left standing. This piece is me developing that one line into the full argument behind it.
The culture that runs the room
Walk into any onchain conversation and the gravity is unmistakable. The dominant culture — the loud one, the one that sets the tone in most rooms — is speculation. Not building. Speculation. Buying a thing because a chart suggests it might be worth more later. Flipping it before the momentum reverses. Reading the cycle, riding the cycle, front-running the cycle. Everything is framed as a position: what are you holding, what’s your entry, when do you exit.
I want to be precise here, because it’s easy to sound like a scold and I’m not one. There’s genuine skill in some of this. Reading liquidity, understanding market structure, managing risk under real uncertainty — those are not nothing. People who do it well are doing something hard. But here is the thing that the culture never quite says out loud: speculation has a ceiling, and the ceiling is structural, not a matter of getting better at it.
The ceiling is this. When your entire relationship to the technology is ownership of things that might appreciate, you are fundamentally a passenger. You do not build the road. You do not maintain the road. You ride whatever road other people built, and you get off before the potholes. The value you extract is real, but it is extracted from motion that already exists — motion created by builders, by narratives, by liquidity someone else brought. Take away the builders and the narratives and the whole thing is a room full of people trying to sell each other the same tokens at slightly different prices. There’s a name for a market with no underlying production. It’s not a flattering one.
And the cycles make this worse, not better, because they train a specific reflex. Up-only, then capitulation, then quiet, then the next narrative, then up-only again. Live through a few of these and you internalize a lesson: nothing you touch is meant to last. You’re not supposed to hold through the trough. You’re not supposed to still be here doing the same thing in three years. The whole rhythm rewards moving on. Which is fine for a trade. It’s corrosive for anything you’d want to call work.
Owning versus building
Here is the distinction the whole argument turns on, and I want to lay it out cleanly because most people blur it on purpose.
When you own something that might appreciate, the asset does not need you. That’s the entire appeal, actually — it’s passive. You buy it, you sit, the market does whatever the market does. The token doesn’t know you exist. It doesn’t page you at 3am. It has no users who suffer when you’re asleep. It has no failure mode that becomes your failure. Your relationship to it is one-directional: you watch it, it ignores you. If it goes up, you were right. If it goes down, you were early or you were wrong, and either way the asset is indifferent. Ownership is a bet placed and then observed.
When you build something people depend on, every one of those properties inverts. The thing needs you. It needs uptime — which means it needs you to have thought about what happens when a dependency fails, when traffic spikes, when a request comes in malformed and hostile. It has users, real ones, who are relying on it to behave exactly as promised, and who are hurt in concrete ways when it doesn’t. It has failure modes, and every single one of them is yours. Not the market’s. Not the counterparty’s. Yours. You own the bug the same way you own the feature. That’s the deal you sign when you ship something into production and ask people to trust it.
This is not a difference of degree. It’s a difference of kind. The speculator and the builder are doing categorically different things even when they’re standing on the same chain. One is placing bets on motion. The other is manufacturing the thing that has to still work whether or not anyone’s watching the chart.
And I’ll be honest about the tradeoff, because pretending it away is dishonest. Building is harder and it is slower and the feedback loop is brutal. A speculator can be right in an afternoon. A builder can be right in a way that only becomes visible after two years of the thing quietly not falling over. You don’t get a green candle for uptime. You get the absence of a disaster, which nobody celebrates. That’s the deal. I took it anyway, and I’d take it again, because at the end of a cycle the speculator has a P&L and the builder has a thing that exists in the world and keeps running. I know which one I’d rather have my name on.
Why I chose the harder, slower path
I didn’t arrive at this by temperament alone. Twenty years in security does something to how you see systems. When your job for two decades is to assume the attacker is smarter than you and the failure is already in the codebase, you stop being impressed by things that merely look like they work. You want to see them survive contact. You want to see them run in production, under load, against people actively trying to break them, and still be standing.
That instinct doesn’t translate well to speculation. Speculation asks you to believe a story about the future price of a thing. Security asks you to distrust every story and verify the mechanism. Those are opposite postures. So when I moved onchain in earnest, the question I kept asking wasn’t “what’s going to pump” — it was “what’s actually broken here that I could fix, and would the fix still be running in five years.”
That’s the whole reason I build in production instead of pitching decks. A deck is a story. A running system is a claim you’ve committed to defending. I’d rather defend a claim than tell a story. And the three things I build all share that shape: they are running, they are load-bearing, and if they fail it is unambiguously my problem to fix. Let me describe them concretely, because “I build infrastructure” is exactly the kind of vague phrase I just spent five paragraphs criticizing.
What “building on it” actually means
I build three things, and they sit on one trajectory: secure → build → anchor. Secure other people’s onchain code. Build onchain infrastructure of my own. Anchor a namespace permanently for a place I intend to make home. Each one is a different answer to the same question — what does it look like to build on the chain instead of bet on it — and none of them is a thing you buy from me as an investment.
Darkwave — securing others’ onchain code
Darkwave is an independent smart contract audit practice. The work is exactly what it sounds like: senior manual review of onchain code, backed by the real tooling — static analysis with Slither, property and fuzz testing with Echidna and Foundry — and delivered as a fixed-scope engagement with a formal report and a signed attestation at the end.
Notice what this is. It’s the security discipline pointed at the one place onchain where failure is truly irreversible. A traditional bug you patch and ship again. A smart contract bug ships value out the door and there is no ship-again. That asymmetry is the whole reason contract review has to be done by someone who actually reads the code line by line and reasons about what an adversary does with it — not someone who runs a scanner and pastes the output. The tools find the shape of a problem. A human who has spent decades assuming hostility finds the problem the tools weren’t built to imagine.
This is building in the truest sense even though it produces a document. What I’m building is confidence that someone else’s system won’t betray its users. When I put my name and a signature on an attestation, I am staking my credibility on that code. That’s not a passive position. That’s the opposite of passive. It’s the most accountable thing I do.
Shaka — onchain payment routing
Shaka is a B2B payment router on Ethereum. The mechanics are the point, so here they are without slogans. A deal has multiple parties who are each owed a share of a transaction. In the ordinary world that means a chain of transfers, reconciliation, delay, and a dozen places where money can sit, go missing, or get clawed back. Shaka collapses that into a single onchain event: the buyer pays the total once, and the contract splits that total to every party in the same transaction — instant, and irrevocable, because it settled onchain in one atomic move.
There’s a rule at the center of Shaka that I hold to absolutely: the contract calculates, the app obeys. Every amount that matters is computed and enforced by the contract. The application layer does not get to recompute a number and hope it matches. It reads what the contract says and it obeys. This is a security decision dressed up as an architecture decision. The moment you let the interface do the math and trust it, you’ve created a gap between what the user was shown and what the contract will actually do — and gaps like that are where the money leaves. So there is no gap. The contract is the source of truth, and everything above it is downstream of that truth.
That discipline is why Shaka is infrastructure and not a demo. It runs. It handles real routing. Its failure modes are mine, and I’ve architected specifically so that the failure modes that would cost users money are structurally closed off rather than politely discouraged. That’s the difference between something you’d trust with a payment and something you’d trust with a screenshot.
Queensland — sovereign naming, handed to the State
Queensland is the one people find hardest to categorize, because it doesn’t fit the shape the culture expects. It is sovereign onchain naming infrastructure. The core Queensland namespaces are already minted onchain — permanent, resolving, existing. Not a roadmap, not a promise, not a mint scheduled for later. Minted. On the chain. Resolving now.
And here is the part that matters most: it is built to be handed to the State. There is no registrar in the middle extracting rent. There is no retail funnel. It is not a business I run and it is not a market I’m addressing. It is a piece of permanent public naming infrastructure for a place — anchored onchain so that it cannot be quietly repossessed, revoked, or rug-pulled by whoever happens to control a company later — and the entire point of anchoring it that way is that it can be given to the sovereign it belongs to and still be exactly what it was. Permanence is the feature. Non-ownership, at the end, is the feature.
I anchor it because I intend Queensland to be home, and the most builder thing I can imagine doing for a place you’re moving toward is to leave behind a piece of durable public infrastructure that outlasts your involvement in it. That’s the “anchor” in secure → build → anchor. It’s the furthest possible thing from a speculation. You cannot speculate on something you’re building specifically in order to give away.
Work as the credential
Here’s why the stance isn’t just a personal preference — why I think it actually matters for how you should read anyone in this space.
In a culture organized around speculation, the credential is your call. You said the thing would go up, it went up, you’re credible until the next call. It’s a track record made entirely of predictions, and predictions are cheap to make and easy to launder — nobody counts the ones you got wrong. The whole game rewards being loud and lucky and then narrating the luck as skill.
In a culture organized around building, the credential is the running system. It’s not a prediction. It’s a claim that’s currently being tested, continuously, by reality. Darkwave’s attestations are signed — my name is on the line for code I reviewed. Shaka is routing real payments under an architecture I can explain mechanism by mechanism. Queensland is resolving onchain right now; you can check. None of that is a story about the future. It’s a set of things that either work or don’t, and if they don’t, that’s visible and it’s on me.
That’s what I mean when I say the work is the credential. I don’t want to be trusted because I called a top. I want to be trusted because the things I put into the world are still standing when you go look at them. That’s a harder credential to earn and a much harder one to fake, which is exactly why it’s the one worth having. You can’t screenshot your way to it. You have to keep something alive.
Speculation isn’t evil. It’s just not building.
I want to be fair, because the manifesto version of this argument usually isn’t, and the unfair version is weaker.
Speculation is not evil. It’s not a moral failing. Markets need liquidity, and liquidity comes from people willing to take positions, and a lot of genuinely useful onchain machinery got funded and bootstrapped by exactly the speculative energy I’ve been describing. I’m not going to stand here and pretend the whole thing would be better if nobody ever bought a token they intended to sell. That’s naive and it’s false.
My claim is narrower and, I think, harder to argue with: speculation is not building. It produces a P&L, not a system. It leaves you, at the end of a cycle, holding an outcome rather than an artifact. And a life spent entirely on the speculative side of the line is a life spent riding roads other people built and never building one yourself. That might be the right life for some people. It genuinely might. It just isn’t a builder’s life, and it shouldn’t get to borrow a builder’s credibility. The two are different things, and pretending they’re the same — treating a good trade and a shipped system as the same kind of achievement — is the specific confusion I’m trying to clear up. Trade if you want to. Just don’t mistake it for having built.
The quiet satisfaction of it
There’s a feeling on the builder’s path that the speculative one can’t give you, and it’s worth naming because it’s the actual reward, more than any number.
It’s quiet. That’s the thing about it. There’s no green candle for a system that just kept running. There’s no crowd for the bug you closed before anyone hit it, no announcement for the payment that routed correctly for the ten-thousandth time exactly as designed, no applause for a namespace that resolves today the same way it resolved last month and will resolve next year. The satisfaction of building is almost entirely private, and it’s made of absences — the disaster that didn’t happen, the money that didn’t go missing, the thing that didn’t fall over while you slept.
I’ve come to prefer that. After twenty years of assuming everything breaks, there is a deep and specific calm in making something that doesn’t. It’s the calm of having your name on a signed attestation and meaning it. It’s the calm of an architecture where the dangerous failure mode is structurally impossible rather than merely unlikely. It’s the calm of anchoring something permanent for a place and knowing it’ll still be there after you’ve handed it off and moved on.
I surf, and the metaphor is too easy, but I’ll use the honest part of it. You do not own a wave. Nobody owns a wave. You can’t buy it, hold it, and sell it later at a markup — the whole idea is absurd. You can only read the ocean well enough to be in the right place when it arrives, and then do the work of actually riding it. Speculation is trying to own the wave. Building is learning the water. One of those is a fantasy about extraction. The other is a practice you get better at for the rest of your life.
I don’t speculate onchain. I build on it. Secure, build, anchor. Three things, running in production, each one a claim I’m defending rather than a story I’m telling. That’s the whole argument, and it’s also just what I do on a Tuesday. The difference between owning and building isn’t a philosophy for me. It’s the shape of the work — and after all these years, the work is the only credential I’ve ever cared to earn.