If you're looking for a long-term hire or open-ended consulting, I'm probably not the right fit.

Selective engagements

I take on a limited number of scoped engagements per year. Below: what I do, and what I don’t—so we can figure out quickly if we’re a fit.

Most engagements start after a bounty contribution, some research collaboration, or a direct referral. That’s usually how it goes.

What I can do

I focus on protocol-level and infrastructure work. Good fits look like:

  • Protocol development: smart contracts, upgrades, integrations, cross-chain logic—the meaty stuff
  • Infrastructure and tooling: indexers, relayers, dev tooling, automation. The plumbing teams actually need
  • Research and design: architecture, security thinking, feasibility for new systems. Not deckware—actionable
  • Fixed-scope deliverables with clear milestones and handover.

What I don’t do

To keep focus and quality where I want them, I don’t take on:

  • Generic dApp frontends or marketing sites without real protocol or infra scope. Just not my lane
  • Ongoing retainer work with no defined scope or deliverables. I’ve seen how that ends
  • Pure non-technical consulting or business-only strategy. There are people who do that well—I’m not one of them
  • Projects outside protocol, infra, or security-adjacent work.

How engagements work

  1. Step 1: quick technical brief (30 minutes async or call)
  2. Step 2: scope + milestones + fixed price
  3. Step 3: delivery + handover + optional maintenance

Typical deliverables

  • repo + PRs
  • deployment notes / runbook
  • architecture notes
  • tests + basic monitoring hooks (if relevant)