Eight months at a chain

Before Katana I worked on protocols — most recently Opyn, building options and perpetuals. Then I spent eight months at Katana, a chain. The two jobs share an industry and almost nothing else.

The cleanest way I can put it: a protocol asks for depth on one thing. A chain asks for depth on several at once, with a long tail you only skim.

At Opyn we were just taking care of our own thing

The scope of my job at Opyn was bounded. One product family — derivatives. One codebase. One audit cycle. One set of users. When a counterparty came up — a wallet, an aggregator, a frontend — they wanted Opyn to support them, not the other way around. We owned the depth of one thing.

At a chain, that flips. The chain exists to host other people's protocols. By the end of my time at Katana I had context on Yearn, Morpho, Spectra, Sushi, Kensei, LayerZero, Merkl — some of it deep, most of it working. Each was a counterparty whose product needed to run on the chain, and the things I owned existed to make those products run.

What Katana is built for

Katana's economic model is something the team called productive liquidity. When you bridge to Katana, your funds don't actually move. VaultBridge takes your USDC on Ethereum, deposits it into Morpho on the mainnet side, and mints vbUSDC on Katana. The mainnet position keeps earning while you transact on the L2.

That yield doesn't go to whoever holds vbUSDC. It goes to users who redeploy vbUSDC into protocols on Katana — Yearn, Morpho on Katana, Spectra. Idle liquidity in a wallet adds nothing. Productive liquidity sits inside lending markets or AMMs, and that's what the chain rewards.

This is the chain's whole thesis. Capital is in service of every protocol on Katana — not the chain's own product, because the chain doesn't really have one without them. Every reward calculation, every integration, every product page has to know about every protocol on the chain. The economic model is defined in terms of other people's products. At Opyn we never had to think that way. At Katana every weekly conversation eventually touched it.

The super app

The product expression of productive liquidity was something we were building called the super app. One interface where users could see their positions across the protocols Katana supported, deposit into Morpho vaults, Morpho markets, and Yearn vaults from the same place, and move between them when rates shifted. If one Morpho market started paying meaningfully more APY than another, we wanted a single button that moved you there in one transaction.

Building that meant reasoning about the supported protocols simultaneously — not as separate integrations, but as one product. You can't ship a "best yield right now" button if you only superficially understand any of the underlying markets.

The first month was meetings

Engineering was five people when I started, six or seven by the end. So a lot of work was outsourced — the questing module, the original v0 of the website, parts of the staking integration — and that meant my calendar was mostly counterparty calls. Pre-TGE, every protocol launching with the chain wants something specific: parameter changes, custom configurations, joint campaigns, integration help. Multiply that by every protocol on day one and the weeks fill up fast.

Building a chain is mostly running a coordination layer. There is so much work to put one forward and keep it functioning, and almost none of it is what I was used to at Opyn — head-down in one repo, debugging one product.

Depth, but on more than one

At Opyn the depth lived in one place: options and perps. Clone the repo, follow the math, understand the invariants, ship. At Katana the depth didn't disappear — it spread. We went deep on the core set: Yearn, Morpho, Spectra. Those were the protocols the super app was built on, the protocols the rewards engine had to track at the position level, the protocols that defined productive liquidity. We knew their internals.

What changed was the periphery. The other protocols on the chain — Sushi, Kensei, parts of the LayerZero stack, Merkl, the long tail of integrations — got working understanding plus sharp questions, not deep reads. AI was a real help there: a usable mental model of ve(3,3) gauges or a Morpho market's liquidation flow in an hour instead of a day, when I needed it.

The skill the chain forced me to build wasn't surface understanding. It was depth on more than one thing at the same time.

What the chain forced me to build

Multitasking, in a real way. Not the productivity-blog version. The version where four protocol teams are negotiating campaign mechanics with you in parallel, you are the only person accountable for a TGE checklist that runs across CoinGecko price feeds, the portfolio service, staking and quests, the centralized exchange listings, and verifying that every protocol on the chain reads the right token price once it stops being hardcoded, an OFT integration needs to be live for Binance and OKX on day one, and you're running all of it with AI tools open in three windows. That's a different rhythm than protocol work.

The other thing: a sense of how systems of systems fit together. At Opyn I understood derivatives. At Katana I started to understand how lending, AMMs, yield tokenization, gauges, and bridging compose into something a user actually uses. ve(3,3) was a piece of that. Bridge economics was another. Standing inside a chain teaches you the seams between protocols in a way no single-protocol job will.

Would I do it again

Yes. Crypto already runs on accelerated learning curves. A chain compresses the curve further — there is so much happening at once that you cover ground in months that would take a year somewhere else. The trade is real. I won't know any single protocol on Katana the way I know Opyn's options codebase. But I came out understanding the shape of the space better than I went in.

A protocol asks for depth on one thing. A chain asks for depth on several at once, with a long tail you only skim. I'm glad I did both.